The how it started how it’s going template helps teams capture origins and current status in a repeatable format. This structure turns scattered stories into a clear, shareable record that stakeholders can reference quickly.
Designed for projects, products, and initiatives, the template aligns people on where something began and where it stands now. Below you will find focused sections, a detailed summary table, and practical guidance to apply the template effectively.
| Phase | Origin Story | Current State | Owner |
|---|---|---|---|
| Idea | Customer pain observed in support tickets | Live service with 200k users | Product Lead |
| Launch | MVP built in 8 weeks by small internal team | Quarterly releases, 3 product lines | Engineering Manager |
| Growth | First paid customers via direct outreach | Partner channels and automated onboarding | Growth Lead |
| Scale | Manual processes, informal documentation | Standard playbooks, metrics dashboard | Operations Director |
Define the Problem Space
Before applying the how it started how it’s going template, clarify the specific problem or opportunity. A sharply defined problem space makes origin stories meaningful and current status assessments actionable.
Focus on the user impact, the constraints encountered, and the outcome that stakeholders care about. This focus prevents the template from becoming a generic history lesson and keeps it strategically valuable.
Root Cause Snapshot
Document the initial trigger, whether it is a customer complaint, market gap, or technical limitation. Pair this trigger with the intended effect, such as improved retention or reduced processing time.
Map the Origin Story
Capture how the initiative, product, or project began in a structured way. The origin story should highlight context, motivations, and the first concrete steps taken by the team.
Use concrete details instead of vague descriptions, naming tools, decisions, and constraints that shaped early work. This practice builds credibility and makes comparisons to the present more insightful.
Key Early Milestones
List pivotal events such as first user test, prototype demo, or regulatory approval. These milestones serve as reference points when discussing progress and shifts over time.
Capture the Current Status
Describe where the initiative stands today using measurable indicators and clear ownership. The current status section should reflect systems, people, and outcomes that define performance now.
Balance quantitative data, such as user counts and revenue, with qualitative context like market perception and team maturity. This balance ensures the status view is both factual and informative.
Performance Indicators
Include metrics that matter to stakeholders, for example conversion rate, uptime, or compliance score. Group indicators by area such as product, operations, and finance for quick scanning.
Strategic Evolution Insights
Use the template to reveal how decisions and external factors shaped the path from origin to current state. Highlight pivots, resource shifts, and lessons that altered direction.
Link each insight to evidence, such as meeting notes, performance trends, or customer feedback. Evidence turns observations into shared understanding and supports better decisions.
Apply the Template Consistently
- Clarify the problem space and intended outcomes before documenting
- Use specific data, dates, and names in origin and status descriptions
- Assign clear ownership for each section to ensure accountability
- Review and refresh the template at defined intervals
- Share the documented template with stakeholders to align understanding
FAQ
Reader questions
How do I decide what to include in the origin story section?
Focus on context, initial goals, key decisions, and constraints that shaped early work, using specific examples rather than general statements.
What metrics are most useful for the current status section?
Include user adoption, performance, revenue, and operational reliability metrics that reflect value delivery and health of the initiative.
Can this template be used for personal career development?
Yes, treat each role or project as an initiative, mapping how it started in terms of skills and responsibilities and how it is going in terms of impact and growth.
How often should the template be updated to keep it relevant?
Update the current status with each major milestone or on a regular cadence, such as monthly or quarterly, to maintain an accurate picture of progress.