6.2 · Keep the work within its decision boundary
Chapter 6: Facilitation and Scope
Watch the chapter or work through its reading pages at your own pace.
Chapter video not yet released. Registered participants will be notified when it becomes available.
Development edition. Each chapter has its own follow-along PDF, which may be updated when that chapter’s video is released.
Reading pages in this chapter
Chapter 6 · Page 1 of 2
Facilitate rigorous challenge
Learning objective: Intervene in conventional thinking while keeping the team responsible for its solutions.
A facilitator should make reasoning visible without becoming the team’s substitute expert. Ask for the outcome, premise, source, inference or test that is missing. Avoid supplying a preferred solution and then questioning the team until it agrees.
Set a working agreement: challenge statements rather than status; distinguish experience from evidence; invite exceptions; record disagreement accurately; and allow people to correct their claims. Amy Edmondson’s 1999 study found an association between team psychological safety and learning behavior in 51 work teams. It does not make agreement the goal. In this course, respectful challenge and evidence standards operate together.
| Signal in the room | Useful intervention |
|---|---|
| “We have always done it this way.” | “What outcome did that arrangement protect, and what evidence says it is still necessary?” |
| “The system will not allow it.” | “Which specific capability is missing? Who can verify that limitation?” |
| “Let us just automate it.” | “Which necessary function would automation perform, and which assumption are we preserving?” |
| “That is best practice.” | “Under what conditions did it work, and do those conditions hold here?” |
| “Everyone knows customers hate this.” | “What observations distinguish a common pattern from a memorable incident?” |
| “That would never work.” | “Which premise fails, or what test would reveal the failure?” |
Use a short reset: quote the claim neutrally, ask the person to classify it, request the source or test, and return it to the correct stage. Give inquiry a time limit. If evidence is unavailable, record an owner and conditional decision rather than repeating the same argument.
Balance participation with silent writing, round-robin contributions and pairs before plenary debate. Invite control owners and frontline staff to describe what a change would break. Ask a senior sponsor to speak after others when their position could anchor the group.
When conflict becomes personal, pause. Restate the shared outcome and separate factual disagreement from different priorities or authorities. A facilitator cannot settle a genuine authority conflict by a group vote; route it to the decision owner.
Practice
Form triads: facilitator, SME and observer. The SME uses two conventional-thinking statements from the table. The facilitator has six minutes to surface the premise and agree a next step without proposing the business solution. Rotate roles. The observer records the exact intervention and its effect in W9.
Check your reasoning
How can a facilitator challenge a senior SME without dismissing their expertise?
Worked response
Acknowledge the experience, ask for the conditions and supporting example, then make the inference explicit. Invite the SME to identify a counterexample or test. The target is the claim, not the person’s competence.
BrightPath: help the team examine its claim
A facilitator's intervention sequence
Use this additional fictional workshop exchange: an adviser says, “Every client needs a meeting; that is how we build trust.” Treat the experience respectfully while separating an observation about some interactions from a claim about every client. Do not present the role-play statement as evidence that all BrightPath advisers hold that view.
| Facilitator move | Example prompt | Reasoning output |
|---|---|---|
| Clarify the claim | What happens in the meeting that supports trust in the advice? | Observable candidate properties: understandable reasoning, candid limits, reliable commitments |
| Find the basis and limits | Which examples support that? Which clients or situations were different? | Evidence with scope, plus exceptions and unknowns |
| Include missing perspectives | What do clients who cannot attend experience? What does the follow-up owner see? | Access, comprehension, recontact and unresolved needs remain visible |
| Compare mechanisms fairly | How could each option provide clarification, relevant expertise and accountable follow-up? | Function-based alternatives rather than a preferred platform |
| Close the uncertainty | Who will investigate this, by when, and which decision depends on the result? | A conditional recommendation and an owned evidence action |
Participation and authority
Use a short silent-writing round before discussion, ask the sponsor to hear others before stating a preference, and invite both advisory and follow-up perspectives. Challenge the claim without treating an individual's experience as worthless. The facilitator may contribute subject expertise, but should identify when they are switching from guiding the discussion to offering content advice.
The supplied case permits redesign of intake, channel, scheduling and clarification. Additional expertise or a new response-time guarantee requires the service owner's decision. A team vote does not create that authority. Keep applicable privacy conditions and competent ownership in the recommendation; record unresolved dependencies rather than promising them away.
W9 connection · within a five-minute explanation and role-play block
Use three roles: adviser, facilitator and observer. The adviser makes the meeting claim. The facilitator asks for its basis, includes a missing perspective and closes with an evidence action. The observer records the exact question that clarified the reasoning and any question that pushed a preferred answer. Swap one intervention for a more neutral question.
Observer debrief
Look for a claim with a status, evidence or a stated gap, an alternative explanation, a named investigation owner and a decision boundary. Agreement alone is not the output. “Wouldn't a hybrid be best?” steers toward a design; “Which functions need live interaction, and how would we test that?” leaves the mechanisms open.
References and their limits
Edmondson (1999) — Psychological Safety and Learning Behavior in Work Teams. The study of 51 work teams found an association between team psychological safety and learning behavior. It supports the relevance of a climate where people can raise questions and errors; it does not prove these particular role-play prompts work or determine BrightPath’s design.
BrightPath and its observations are original fictional Colabmo teaching material. Sources support the methods; they do not establish case facts or achieved results. References checked 18 October 2026.
Read-along slides and narration script (audio not yet available)
6.01 · Facilitation and Scope
Welcome to Colabmo.
I'm Diggy Breiling, founder of Colabmo. Welcome to First Principles Thinking for Business Process Redesign. This is chapter six, Facilitation and Scope.
In this chapter, we'll practise facilitation and make clear decisions about the scope of the work.
6.02 · The facilitator’s contribution
We begin with facilitation.
The team owns the solution. The facilitator helps the team examine its reasoning and make clear decisions about what belongs in the work.
A facilitator should make reasoning visible without becoming the team’s substitute expert. Ask for the outcome, premise, source, inference or test that is missing. Avoid supplying a preferred solution and then questioning the team until it agrees.
6.03 · A short reasoning reset
Set a working agreement: challenge statements rather than status; distinguish experience from evidence; invite exceptions; record disagreement accurately; and allow people to correct their claims. Amy Edmondson’s 1999 study found an association between team psychological safety and learning behavior in 51 work teams. It does not make agreement the goal. In this course, respectful challenge and evidence standards operate together.
Use a short reset: quote the claim neutrally, ask the person to classify it, request the source or test, and return it to the correct stage. Give inquiry a time limit. If evidence is unavailable, record an owner and conditional decision rather than repeating the same argument.
If someone says, “The system will not allow it,” ask which capability is missing and who can verify the limit. If someone says, “Let us automate it,” ask which function the automation performs and which assumption it preserves. If someone says, “That would never work,” ask which premise fails or what test would reveal the failure.
6.04 · Balanced participation
Balance participation with silent writing, round-robin contributions and pairs before plenary debate. Invite control owners and frontline staff to describe what a change would break. Ask a senior sponsor to speak after others when their position could anchor the group.
When conflict becomes personal, pause. Restate the shared outcome and separate factual disagreement from different priorities or authorities. A facilitator cannot settle a genuine authority conflict by a group vote; route it to the decision owner.
6.05 · BrightPath: help the team examine its claim
Let’s return to the BrightPath team. Imagine an adviser says, “Every client needs a meeting. That’s how we build trust.”
I’d want to understand the experience behind that statement. I might ask, “What happens in the meeting that helps the client trust the advice? Can you give us an example?”
Perhaps the answer is that the adviser explains the reasoning, admits a limit, or clears up a misunderstanding. Now we have something more specific to examine.
Then I’d ask, “Where have we seen that work? Which clients have difficulty attending? And what would help us find out whether another approach can do those things?”
Give people a moment to write before the discussion. Invite the person who handles follow-up to describe what happens after the meeting. Someone may leave satisfied and still not know what to do next.
We don’t have to settle every disagreement in the room. If the evidence is missing, record the question, who will investigate it, and which decision has to wait.
And watch the scope. The team can explore how guidance is delivered. Promising a faster response or expertise we haven’t established needs the service owner’s decision.
Use this situation for the W9 role-play. Your aim is to help the team reason clearly, not steer everyone toward your favorite channel.
6.06 · W9: facilitator role-play
Now apply the reasoning. Form triads: facilitator, SME and observer. The SME uses two conventional-thinking statements from the table. The facilitator has six minutes to surface the premise and agree a next step without proposing the business solution. Rotate roles. The observer records the exact intervention and its effect in W9.
Pause the video while you work. Before resuming, record your answer to this question: How can a facilitator challenge a senior SME without dismissing their expertise?
When you return, compare your reasoning with this explanation. Acknowledge the experience, ask for the conditions and supporting example, then make the inference explicit. Invite the SME to identify a counterexample or test. The target is the claim, not the person’s competence.
Chapter 6 · Page 2 of 2
Keep the work within its decision boundary
Learning objective: Manage new ideas and dependencies without losing the agreed outcome.
First principles inquiry can expose problems beyond the original process. That is useful information, but discovery is not automatic authorization to redesign the whole organization. Preserve a clear current decision, an explicit boundary and a small set of outputs.
When a new issue arises, classify it as necessary to this decision, a dependency requiring another owner, or a future opportunity. If it is necessary, estimate the impact of including it and ask the scope owner to decide the tradeoff. If it is a dependency, record what assumption the current work uses and what happens if it is false.
Use an evidence gate at each transition. Before reconstruction, the outcome, functions and material premises must be sufficiently clear. Before testing, authority, measures and stop conditions must be set. These are teaching checkpoints for the exercise, not new company-wide mandatory approval procedures.
A useful scope response is: “This issue may affect our result. Within today’s boundary we can test the routing mechanism, but we cannot decide the company’s delegation policy. We will document the dependency and ask its owner to resolve it.” This keeps the inquiry honest without hiding the constraint.
Close with decisions and evidence, not only a diagram. Capture which options remain, why one test is next, who owns it and when results will be reviewed. Use the organization’s existing task system for commitments. The worksheets support reasoning; they are not a parallel task-status system.
Practice
Use W10 to handle a proposal to replace the entire customer database during an intake redesign. State what is within scope, what evidence is needed, the decision owner and the consequences of accepting or deferring the change.
Check your reasoning
Should the team ignore an outside dependency to protect scope?
Worked response
No. It should expose the dependency and its effect, assign it to the appropriate owner, and keep its own recommendation conditional where necessary. Scope discipline controls decisions; it does not suppress relevant evidence.
Read-along slides and narration script (audio not yet available)
6.07 · The decision boundary
We now begin the section on Scope and the decision boundary.
First principles inquiry can expose problems beyond the original process. That is useful information, but discovery is not automatic authorization to redesign the whole organization. Preserve a clear current decision, an explicit boundary and a small set of outputs.
6.08 · Scope decisions with evidence
When a new issue arises, classify it as necessary to this decision, a dependency requiring another owner, or a future opportunity. If it is necessary, estimate the impact of including it and ask the scope owner to decide the tradeoff. If it is a dependency, record what assumption the current work uses and what happens if it is false.
Use an evidence gate at each transition. Before reconstruction, the outcome, functions and material premises must be sufficiently clear. Before testing, authority, measures and stop conditions must be set. These are teaching checkpoints for the exercise, not new company-wide mandatory approval procedures.
6.09 · An actionable close
A useful scope response is: “This issue may affect our result. Within today’s boundary we can test the routing mechanism, but we cannot decide the company’s delegation policy. We will document the dependency and ask its owner to resolve it.” This keeps the inquiry honest without hiding the constraint.
Close with decisions and evidence, not only a diagram. Capture which options remain, why one test is next, who owns it and when results will be reviewed. Use the organization’s existing task system for commitments. The worksheets support reasoning; they are not a parallel task-status system.
6.10 · W10: a proposed database replacement
Now apply the reasoning. Use W10 to handle a proposal to replace the entire customer database during an intake redesign. State what is within scope, what evidence is needed, the decision owner and the consequences of accepting or deferring the change.
Pause the video while you work. Before resuming, record your answer to this question: Should the team ignore an outside dependency to protect scope?
When you return, compare your reasoning with this explanation. No. It should expose the dependency and its effect, assign it to the appropriate owner, and keep its own recommendation conditional where necessary. Scope discipline controls decisions; it does not suppress relevant evidence.
Keep a record of the questions that helped the team reconsider its reasoning. In the next chapter, you will apply the method to two fictional business cases.
6.11 · Next: Business Process Cases
You’ve completed chapter six, Facilitation and Scope, in First Principles Thinking for Business Process Redesign.
Thank you for learning with Colabmo. Bring your expertise, keep your reasoning visible, and put what you’ve learned to work.
Scroll within the reading area. Use the page buttons above to review within this chapter. The course sidebar and Prev / Next buttons open another course page.
There are no comments for now.
to be the first to leave a comment.