Adapting One Story to Several Questions

Change the lens, not the facts

A rich story can answer different questions if you change the emphasis while keeping the facts identical. A delayed migration can be a story about pressure (how you renegotiated scope), about failure (the estimate you got wrong and what you changed), or about collaboration (how you aligned two teams). Start by naming what the question is really about, then choose the part of the story that best shows it and trim the rest. Do not reshape facts to fit; if a story only answers the question with stretching, pick another one or say you need a moment to think.

One story, three angles

A fictional database migration story.

Core facts: I led moving a service to a new database; the first
estimate was 4 weeks, it took 7; we avoided downtime.

"Tell me about a failure"
  Lead with: my estimate ignored data back-fill time.
  Emphasise: how I raised it early, re-planned, and now estimate
             with a spike first.

"Tell me about working under pressure"
  Lead with: a hard deadline from a vendor contract ending.
  Emphasise: scope cut (read path first), daily updates, trade-offs.

"Tell me about cross-team collaboration"
  Lead with: two consuming teams with different needs.
  Emphasise: the shared rollout plan and how I handled pushback.

One dataset, several dashboards

The underlying events are like one dataset; each question is a different dashboard over it. You choose which metrics to display, but you never change the data.

Quick check: What should change when you reuse a story for a different question?

• Your role in the story
• The facts, to fit the question better
• The emphasis and which details you highlight, not the facts
• The outcome, to sound more impressive