Inclusive design processes
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
run a design process where every affected team shapes the decision.
Planned topics
- Identify affected teams from the dependency map, not from who is easiest to invite.
- Share a short problem statement and options before the meeting, so the meeting is for deciding, not presenting.
- Give each team a defined role: proposer, reviewer, or informed; record decisions and open questions in one place.
- Set a decision date; silence after the date counts as agreement and is recorded as such.
- Avoid "designing alone and presenting": by then, objections feel like delay.
Draft outline details
Demonstration
A design-session agenda: 5 min problem, 15 min options with trade-offs, 20 min per-team constraints, 10 min decision and owners, with a pre-read link.
Check your understanding
Why circulate a pre-read?
Show answer
So the session spends time on decisions and constraints instead of explanations.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.