Team Cloud workshop
The workshop was good. By Wednesday nobody remembers it.
Twenty-five minutes, one large sheet on the table, and everybody writes the true thing about their week at the same time. Then the studio runs a full craft session, and each person's line goes onto the thing they made. The sheet goes on the team's wall.
SGD 3k-5k workshop
25 min, then the craft
Everyone makes something
Optional second session
Session one · press the button
Everybody writes on one sheet, at the same time.
Nobody signs it and nobody reads it out. This is what a real one looks like an hour in.
Four of twelve. The rest go wherever on the sheet was nearest them.
One line each, for somebody
Everyone writes one, sealed. At the end each person is drawn one of the others — never their own, and never a straight swap.
Session two · press the buttons
The cloud grows when an ask gets used.
The working session, weeks after the first one. Mark what happened after somebody used an ask.
6
asks used
3
helped
4
this week
Participant flow
1. A person gets a private read after a workshop or reset.
2. They edit one ask and approve it for the team.
3. The requester marks what happened after someone uses it.
Team dashboard
12
participants in this team space
Open asks
5
approved by team members
Needs edit
2
rewrite before relying on them
This week
Clear & Ready
Quiet questions get missed when the team moves this fast.
Holding It Together
Blockers show up late, usually the day before they matter.
Full & Fast
People take on more than the week holds, and skip the last check.
Finding The Thread
Ownership stays vague and open loops pile up.
Request board
These are approved asks. The requester checks the result.
When the deadline moves, tell me what to stop doing first.
After the meeting, write the decision in one message.
When I go quiet, ask what part is unclear.
Before you hand this to me, name the first file to open.
When the work feels too wide, ask me for the smaller version.
Next team habit
Before Friday planning, write the top 2 priorities in the channel.
Workshop package
Before the session
A prep call with the team sponsor, and a studio booked for the craft. The check-in link is ready before anybody arrives.
First 25 minutes
Everybody sits down and checks in on their own phone. Then one large cloud sheet goes down the middle of the table and the room writes on it at the same time, and reads it without anybody being made to read aloud.
The craft session
The studio runs its own session for the rest of the afternoon. Near the end each person puts their line onto the thing they made, and it goes home with them.
Buyer handoff
The buyer gets the shape of the room and the one thing worth doing about it. Never a person, never a ranking.
What the team gets
This is why it is not a one-hour talk. A person runs the first part, the studio runs a real session after it, and everybody leaves holding something with their own sentence on it.
Sponsor prep call
Facilitator run sheet
Printed cloud sheet, sized for the room
25 facilitated minutes, then the studio's session
A private read on each person's own phone
One line each on the team's cloud
One thing each person made, with their line on it
One message drawn for each person, from everybody in the room
Aggregate buyer summary
Optional second session, and the team space after that
Why it can be a paid workshop
Facilitated first
Twenty-five minutes, seated, no rounds and nobody reading out. Then the room is loose for the rest of the day.
A studio session, at its length
Clay, type and blending each take about an hour and a half. The studio runs its own, and gets paid for it.
The sheet stays
One large cloud everybody writes on at once. It rolls up, goes on the wall, and is what a second session opens on.
A private read
Each person's own phone tells them one thing about their week. It never leaves the phone and no manager sees it.
Buyer summary
The shape of the room and one thing to do about it, at the team level and only above the size floor.
Second session
The asks and the board are session two, offered after this one has happened.
Buyer case
Accountable facilitator
A named person runs the first part and writes the buyer summary.
A real craft session
Not fifteen minutes of pottery inside a workshop. The studio runs its own session at its own length.
Something that stays
The cloud rolls up and goes on their wall, and it is still legible in March.
Nothing to action
Nobody leaves holding a task, which is why people write the true thing on the sheet.
Second session
The asks, the board and the follow-up are the next session, sold after this one has happened.
What comes after
The first session does not sell the second one.
Nothing on the day asks anybody to buy anything. The sheet on the wall is the reason a team comes back, and the asks are worth writing only once people have said the true thing out loud.
The day itself: one line each, and something made to put it on.
The weeks after: the sheet is on the wall and nobody has been given a task.
Session two: one ask each, in their words, and a board for the weeks after that.
After that: the monthly team space, if the team wants the ritual to continue.
Packages
One true thing
SGD 3,000-5,000
One team. Up to 25 in a room, more than that and it splits into rooms.
- Prep call with one team sponsor
- 25 facilitated minutes, then the craft session
- A private read on each person's own phone
- One large cloud sheet the team writes on and takes away
- Something each person made, with their own line on it
- Buyer summary at the team level
Both sessions
SGD 8,000-15,000
The craft session, then the working one a few weeks later.
- One true thing, for the whole team
- What we do about it: 75 minutes, no craft
- One ask each, in their words, shared only if they say so
- Team request board for the weeks after
- Manager handoff guide
Later: team space add-on
SGD 500-2,000 / month
For teams that want the cloud to stay current after the workshop.
- Weekly reset
- Request board
- Monthly pattern read
- Team rescue prompts
Trust boundary
Built as a team ritual, not employee monitoring.
The read on somebody's phone is theirs. The company view stays at the team level, and stays quiet when the team is small enough that a percentage would point at a person.
Personal check-ins stay private.
Managers see aggregate team patterns only.
A team ask is shared only after the person approves it.
No personal rankings, worker ratings, or hidden state reads.
Run a Team Cloud workshop this month.
Start with one team and one afternoon. The second session and the monthly team space come later, or not at all.
Send an email