# Design the Container Co-Design the Change ## Summary Change should usually be designed **with** the people affected, not done **to** them. The facilitator, coach, or leader can design the container: the purpose, safety conditions, structure, questions, timeboxes, decision boundaries, and review loop. The people affected should normally help co-design the diagnosis, the friction map, the experiments, the operating agreements, and the next moves. This principle extends [[Principles]], [[Participation Design Lens]], and [[Work Visibility Makes Friction Discussable]]. ## The distinction Design the container: - why we are meeting - what is in and out of scope - what constraints are non-negotiable - how the conversation will be made safe enough - how real work will be inspected - how decisions or experiments will be captured - when the loop will be reviewed Co-design the change: - what the real problem is - what friction actually feels like in the work - which assumptions need testing - what agreement would make work easier - what small safe-to-try experiment should happen next - what signal will tell us whether it helped ## Why it matters People support what they help make sense of. When change is designed without the affected people, the intervention may be tidy but illegitimate. It may solve the leader's story rather than the team's reality. In Owlery terms, participation is not an engagement trick. It is how groups build shared reality, shared ownership, and better sensing. ## Useful prompts - Who is affected by this change? - Who needs to help shape the work? - What real work should we inspect together? - What is already decided, and what is genuinely open? - What operating agreement or rhythm should emerge? - What would make participation safe enough and meaningful enough? - What small experiment should we review later? ## Counter-indicators Do not involve everyone in the same way when: - there is a formal HR, legal, safety, or misconduct concern - involvement would expose people to retaliation or harm - confidentiality is required - the issue concerns one person and public discussion would be unfair - leadership has already made a non-negotiable decision and pretending co-design would be fake participation - the team is overloaded and a smaller sensing group is more humane - conflict is acute and a safer container is needed first Even then, do not treat affected people as objects of change. Design a careful path toward appropriate involvement where possible. ## Claim status Type: Owlery synthesis Evidence base: Practice-grounded synthesis connected to participation design, psychological safety, work visibility, legitimacy, and learning loops. Confidence: High as a design principle; medium for any specific application until the local context is understood. Use as: A default stance for training, onboarding, team formation, change, coaching, conflict, performance, behaviour, and new ways of working. Do not use as: A reason to create fake participation or to ignore safety, confidentiality, legal, or ethical constraints. ## See Also - [[Principles]] - [[Participation Design Lens]] - [[Invite Participation]] - [[Psychological Safety Map]] - [[Work Visibility Makes Friction Discussable]] - [[Decision Snapshot]] - [[After Action Review]]