Mission

Origin & evolution

The modern split between mission and vision🔭VisionStrategyA long-term aspirational statement of the future stateView reference → crystallised in James Collins and Jerry Porras's Built to Last (1994) and the companion Harvard Business Review essay Building Your Company's Vision (1996). Their framework has two halves. Core ideology is what you preserve: core values plus a core purpose, the organisation's reason for being, which they argued should hold true across decades and never be fully completed. Envisioned future is what stimulates progress: a BHAG, a big hairy audacious goal with a clear finish line ten to thirty years out, plus a vivid description of reaching it.

This maps cleanly onto the words teams already used. Mission sits close to core purpose: the enduring contribution that gives the work meaning. Vision sits close to the BHAG and its vivid description: a concrete future state you can declare won, then replace. Collins and Porras warned against the most common failure, a "mission statement" so generic it could belong to any company in the sector, which inspires no choice because it forbids none.

Practice has since drifted in both directions. Some writers reverse the labels, treating vision as the timeless ideal and mission as the present-tense action. The substance that survives the terminology is the pairing itself: a permanent purpose held alongside a finite, ambitious goal, with each protecting the other from collapse.

How it works in practice

A graph tool for product teams writes its mission as "give every product creator a single source of truth for what they are building and why." It is testable as a filter. A proposed Gantt-chart export passes, because shared truth includes timelines. A proposed in-app chat feature⭐FeatureProduct SpecificationA product capability or featureView reference → fails, because it serves coordination, not truth, and three other tools already own that job🔨JobUserJob To Be Done: what the user is trying to accomplishView reference →. The mission settles the debate in one sentence without a meeting.

Alongside it sits the vision, the finite goal: "by 2032, the product graph is a standard a hundred thousand teams build on." That has an end state and a date, so the team can mark it reached and write a new one. The mission has neither, so it persists. When a board member asks why the company turned down a lucrative services contract that would have pulled engineers off the core, the mission is the answer: the contract did not advance a single source of truth, and the goal already had a measurable target it would have starved.

Mission vs. its neighbours

• Vision names the destination; the mission names the reason for the journey. A vision can be achieved and retired ("a hundred thousand teams by 2032"); a mission is a standing commitment with no finish line. A team that conflates them either sets a purpose with an expiry date or a goal that can never be declared won.
• Value proposition✨Value PropositionBusiness ModelA unique value offered to customersView reference → is a promise to a specific customer about a specific benefit, and it changes as the market and the offering change. The mission is the company-level reason that benefit is worth delivering at all. One is read by a buyer; the other is read by the team deciding what to build.
• Strategy is the chosen path: the bets, sequencing, and trade-offs that move toward the vision under real constraints🔒ConstraintStrategyA constraint entityView reference →. The mission supplies the test those bets must pass. Strategy answers "how, given what is true this year"; the mission answers "to what end, regardless of the year."

In the graph

In the Unified Product Graph, mission🧭MissionStrategyThe purpose and reason the product exists lives in the Strategy & Outcomes🏆OutcomeStrategyA desired business or user outcomeView reference → region, where the mental model runs aspiration to direction to bet to measurable to proof. It is a container, fed from above by vision_realised_through_missionVisionrealised throughMissionhierarchy and branching downward through mission_supported_by_strategic_pillarMissionsupported byStrategic Pillarhierarchy. That placement is the structural argument: a mission with no pillars beneath it is an unexecuted slogan, and a mission with no vision above it is direction without a destination. Both gaps are queryable, so the graph can show when the reason to exist has stopped guiding anything built.