Skip to content

Vision & Mission ​

A vision names a person and a falsifiable claim about their life. A mission names what the organisation does to bring that vision about. Both are written down, re-read every cycle, and the only artefacts every initiative ladders up to.

Owners: Founder, CEO, Leadership Phase it lives in: Why We Build → Direction (Volume II) The corpus principle this enacts: Witnessed, not described — including at the highest level.

Where it lives in the chain ​

How to do this ​

Vision shape:

A world where [named person] can [change in their life] without [the friction the product removes].

Example: A world where a small-school teacher can grade with confidence and clarity, without the 47-minute administrative tax that turns the last hour of every Friday into rote work.

Mission shape:

We [verb] [domain] [for whom] by [mechanism].

Example: We design and build software that reshapes the operational moments small-school teachers spend on grading, by sitting next to them, modelling what we see, and shipping the smallest change that demonstrably moves the minutes.

What good practice looks like ​

The vision is falsifiable. "Make the world a better place" is not. "A world where Gal's grading session drops from 47 minutes to under 15" is — measurable, attached to a person, with a number. The mission is concrete. "Through innovative AI" is not; "by sitting next to them, modelling what we see, and shipping the smallest change" is.

The vision and mission show up in every brief. Not as a banner — as a re-read. "This initiative: does it move us closer to the named person's life-change?" If not, the initiative is either misframed or the strategy has shifted (and Why We Build needs updating).

A team without a clear vision/mission spends every quarter relitigating "what are we actually doing?" A team with one moves through cycles knowing which question the cycle is trying to answer.

200apps · How We Work · NWIRE