proposal-storytelling-and-evaluator-journey

name	proposal-storytelling-and-evaluator-journey
description	Use when a proposal needs a stronger narrative spine, evaluator journey, case-study story, design rationale, executive argument, or presentation/sign-off flow.

Proposal Storytelling and Evaluator Journey

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, [phone].

Use When

• The proposal is technically correct but flat, fragmented, or hard to remember.
• The executive summary, understanding section, methodology, case studies, or presentation needs a clear narrative.
• The proposal must explain design, software, service, AI, or strategy decisions to different stakeholder groups.
• Evaluators need to see the journey from current state to desired state, not only a list of tasks.

Workflow

1. Define the evaluator's journey: what they believe now, what they worry about, what proof they need, and what decision they must make.
2. Build a narrative spine: current situation, complication, decisive question, proposed answer, evidence, implementation path, and measurable outcome.
3. Align each major section to the same spine so the cover letter, summary, methodology, experience, work plan, and price tell one story.
4. Turn case studies into proof stories: context, stakes, intervention, decision logic, result, and relevance to this bid.
5. Explain design decisions through audience-specific rationale: client goal, user need, evidence, trade-off, and approval point.
6. Use storyboards or journey examples where they make a method concrete and help evaluators imagine the delivered service.
7. For premium or public-facing writing, run the commercial writing gate so the story supports value, proof, risk control, and reader discoverability where relevant.

Quality Standards

• The story must be accurate and evidence-based; do not dramatise beyond the facts.
• Narrative should clarify logic, not add decorative language.
• Every story beat must support evaluator confidence in delivery, value, or risk control.
• Case studies must state role, scope, outcome, and relevance.

Outputs

• Proposal narrative spine.
• Executive summary and understanding-section improvements.
• Case-study story cards.
• Design-rationale and presentation language.

References

• ../references/proposal-narrative-patterns-and-case-story-spine.md - evaluator journey, case story structure, and design rationale patterns.
• ../references/ethical-persuasion-and-evaluator-psychology-gate.md - ethical persuasion and evaluator psychology checks.
• ../premium-commercial-writing/SKILL.md - premium commercial writing quality gate for evaluator-friendly prose, case studies, documents, and public content.
• ../05-relevant-experience/SKILL.md - relevant experience section owner.