direction — mission
Mission
A Vision describes the world the team is working toward. A Mission names who specifically they build for, which moments matter, and — most importantly — what they will not try to do.
The third part is what most Missions omit, and its absence is why scope expands indefinitely. Everything is adjacent to something. A platform for teachers is adjacent to tools for parents. A grading tool is adjacent to a parent communication system. Without an explicit boundary, the adjacency is always a reasonable next step. With one, the team can say no without a meeting.
Mission with boundary vs Mission without one
✗ "We build tools for educators to manage learning in their schools."
This describes a category. It does not select. A parent communication feature, a timetabling tool, a facilities booking system — all pass through it. The scope is the entirety of school administration.
✓ "We build for classroom teachers at schools in the Amit network — specifically the moments where their teaching work and their administrative work collide. We do not build for school administrators, parents, or ministry reporting. Those are adjacent problems we are choosing not to solve."
This rejects three categories of work before anyone has to argue about them.
The out-of-scope statement is where the meaning of the Mission lives. Without it, the Mission describes what you do. With it, it protects what you are building toward.
The Mission connects to the chain: it is the filter that determines which initiatives are worth naming a gap for. An initiative that does not serve the population in the Mission is out of scope before it is ever written. Without the Mission, every initiative requires a political decision. With it, most decisions are obvious.
How to apply this
- ✓ Write an explicit out-of-scope statement. Name the adjacent problem you are choosing not to solve. Until it is written, the boundary does not exist as a filter.
- ✓ Can this Mission be used to decline a feature request? If not, rewrite it.
- ✓ Name specific people, not categories. "Classroom teachers at Amit network schools" is more useful than "educators." The more specific, the more decisions the Mission makes automatically.
- ✗ Do not write who you want to serve. Write who you serve well today and who you are choosing not to optimise for.