The Facilitator
The STAIR Master
Not the boss. Not the AI expert. The curious facilitator who creates space for honest reflection.
The STAIR Master knows the principles and their dimensions. They guide without controlling — using active listening, neutrality, comfort with silence, and follow-up questions.
Key traits: asks, doesn't tell. Stays neutral. Makes room for the quiet voices. Follows up on what's unsaid.
Step 1 of the Cycle
Prepare
Pick 2–3 principles relevant to the topic. Not all eight — just the ones that matter for this conversation.
Two modes: "General AI reflection" (scheduled, recurring — e.g. monthly) or "Specific use-case" (ad hoc, triggered by a new tool or situation).
Build on previous insights — check what was captured last time. This is where the continuous learning loop lives.
Decide format: a quick 20-minute discussion or a deeper workshop.
Step 2 of the Cycle
Facilitate
Use principles as inspiration, not a checklist. The goal is a conversation, not an interrogation.
Suggested format: 10 min context → 20 min reflection → 10 min capture.
The quiet voices matter most. The STAIR Master's job is to draw them out — not to fill silence with their own thoughts.
Listen for tensions. Follow the energy. Trust the process.
Step 3 of the Cycle
Capture
Four types of insight to capture:
- Things to circle back to later
- Feedback to IT/product owners on how the AI should adapt to you
- Discoveries where actual use differs from intended — and is better
- Tensions or open questions worth tracking
Think of it as a STAIR Board: Insights / To Revisit / Feedback / Resolved.
Step 4 of the Cycle
Act
Feed insights back into the organization. Share discoveries across teams. Give IT and product owners concrete feedback on how AI should change for you.
This isn't a project with an end date. The arrow from Act → Prepare IS the whole point.
The cycle doesn't end — it compounds. Each loop sharpens the next.
The Core Outcome
Joint Optimization
Technology and the social organization of work must be designed together. That's what the cycle produces naturally over time.
Adaptation is bidirectional. You don't just adapt to AI — you feed back so AI adapts to you. You discover that your actual use differs from what was intended, and that's a feature, not a bug.
This IS joint optimization in action: you shape AI, and AI shapes around you.
Prepare builds →
Awareness
See AI's real impact on work, roles, and relationships — not the vendor pitch, not the hype, but what's actually happening on the ground.
Each time you prepare, you become sharper at identifying what matters. The noise fades. The patterns emerge.
Facilitate builds →
Reflection
Think critically, not reactively. Structured facilitation trains your team to engage with AI deliberately rather than drifting into passive adoption.
Over time, reflection becomes second nature — not something you schedule, but something you do.
Capture builds →
Continuous Learning
Insights compound. Each cycle sharpens the next. What you captured last month becomes the foundation for this month's preparation.
This is the opposite of episodic change management — it's a living record that grows with your team.
Act builds →
Adaptation & Adoption
Shape AI around your values, and let AI shape around you. Feed back to IT and product owners how the solution should change for you.
This is bidirectional. You adapt to AI. AI adapts to you. You discover your actual use differs from what was intended — and that's valuable. This IS joint optimization in action.
