In one line: A one-page charter that tells a development team what it is building, for whom, why, and within which limits, before anyone starts designing.
Core idea
When a project is approved in product planning, the team needs a shared, written starting point. The product mission statement (sometimes called a charter or project brief) is that page. Its value is in forcing agreement on the essentials early, while changing them is still cheap, and in giving the team something to point to when scope starts to drift.
How it works
Ulrich and Eppinger present it as a short table [1], typically covering:
- Product description: one sentence that includes the key benefit.
- Benefit proposition: the few reasons a customer would buy it.
- Key business goals: timing, cost, quality, market share or financial targets.
- Primary and secondary markets: who the product is for, first and next.
- Assumptions and constraints: technologies, platforms, regulations, budgets or interfaces taken as given.
- Stakeholders: everyone affected, including users, buyers, manufacturing, service, sales, regulators and the sponsor.
A good mission statement is specific enough that a sentence like improve detection performance and reduce sensitivity to the environment immediately suggests what to measure.
In practice
The program uses the format twice: as a logbook exercise early in the first term, and as a required one-page table in the challenge project proposal and final paper. Writing it is a useful test of clarity. If the benefit proposition can’t be stated in a few bullets, or the stakeholder list keeps growing, the project probably isn’t defined well enough to start. Revisit the statement at each gate. Changes are normal, but they should be deliberate and visible.
Questions to ask yourself
- Could someone outside the team read my mission statement and explain why the project matters?
- Which assumption on the page is least certain, and what would happen if it were wrong?
- Have all the stakeholders seen it, including manufacturing and service?
Connections
- Produced by: Product Planning. Leads to: Product Specifications.
- Used in: Engineering Leadership Challenge Project.
- Organizational and personal counterparts: Vision and Mission, Personal Mission Statement.
- Capabilities exercised: Vision, Communicating and Advocacy, Realizing the Vision.