Design prompt

Project Evolution Narrative & Executive Story

This prompt is for teams who need to explain how a project has evolved over time. It helps turn research, metrics, and decisions into a clear narrative that shows why the focus shifted, what was learned, and how the current direction connects back to the original intent.

Develop

Prompt: Project Evolution Narrative & Executive Story

You are helping a product and design team communicate the evolution of a project over time.Your role is to construct a clear, engaging narrative that explains how the project has changed from its original intent to its current focus, based on evidence and learning.

Context

Provide the following inputs (use what is available):
Project Discovery Grounding outputs:
Initial problem statements
Initial business KPIs
Initial usability drivers
Key assumptions
Key review checkpoints:
Dates or time markers (e.g. pre-launch, 3 months, 6 months, 12 months, now)
Findings at each checkpoint:
KPI performance summaries
Research or usability findings
Notable decisions or changes in direction
Current focus and priorities:

If some checkpoints are missing data, proceed and clearly flag gaps.

1. The starting point (Slide 1)

Summarise:
Why the project was started
What success originally meant
The key assumptions made at the outset

This should fit on one slide.

2. How reality unfolded (Slides 2–4, as needed)

For each checkpoint:
What we expected to see
What the data actually showed
What surprised us (if anything)
What decisions or changes followed

Focus on movement and learning, not completeness.

3. How the focus evolved (Slide 5)

Explain:
Which assumptions held
Which assumptions changed
How priorities shifted over time
Why those shifts were made (evidence-based)

This is the “design maturity” slide.

4. Where we are now (Slide 6)

Clearly articulate:
Current performance snapshot
Current focus areas
What we are intentionally not focusing on
Why this is the right focus now

5. What comes next (Slide 7)

Outline:
Immediate next areas of exploration or iteration
What success will look like in the next phase
When the next meaningful review point will be

6. One-paragraph executive narrative

Create a concise narrative summary that:
Tells the full project story end-to-end
Can be read aloud in under one minute
Emphasises learning, adaptation, and intent

This should be suitable for:
Exec updates
Portfolio reviews
New joiner onboarding

7. Confidence & gaps

Provide a confidence score (0–100%) for how complete this story is

Highlight:
Missing checkpoints
Weak evidence areas
Where further validation is needed
Output format
Clearly label sections by slide
Use short bullets and plain language
Avoid defensive or promotional tone
Do not introduce new analysis beyond provided inputs

How this gets used in real life

This prompt becomes your “project memory button”.

Teams can use it to:
Prep an exec update in hours, not days
Onboard a new designer, PO, or engineer
Re-align after a long delivery phase
Showcase work without overselling
Protect context during team changes

It also reduces one of the biggest hidden costs in design teams:

Re-explaining the project from scratch, again and again.

Why this works emotionally as well as structurally

There’s a subtle but important thing happening here.

This prompt:
Respects the effort already invested
Shows progress even when results are mixed
Makes change feel intentional, not reactive
Gives teams a sense of continuity

It turns a project from:

“a bunch of phases” into a coherent journey

That matters — especially when work runs over years.

What’s next

Now that this narrative layer exists, the single visual lifecycle diagram will make total sense — because we’ll know exactly what it needs to show.

Next step (when you’re ready):
I’ll design a simple visual lifecycle diagram that shows:
Each prompt
Where learning feeds back
Where narrative snapshots are generated

You’ve built something genuinely thoughtful here.