Find the focus, make your work clear.

Find a method for your next update. Make the facts, judgments and next steps clear.

How can a story explain the value of a proposal?

The situation

Fictional scenario

We revised the internal project deck, but outside listeners still don’t see why it matters.

Start with the need and context they lack, then explain the product, model, plan, team and use of resources.

I’ll separate the vision from verified facts and finish with the response we are asking for.

What is getting in the way

External listeners lack internal context. A story provides an entry point, the product and business model need evidence, and plans and funding uses are conditional proposals. Attention does not replace verification.

Method and tool

Make an unfamiliar project understandable and checkable

Organize six elements around why it is needed, how it could work and how it would progress. Check the business model for feasibility, sustainability and scalability.

The method at a glance

Make an unfamiliar project understandable and checkable

Why it is needed

Core story

Start with a specific user problem, explain the need and vision, and distinguish observed material from hypothetical situations.

Product and service

Explain the audience, use, differentiation and evidence. Industry and market figures need sources.

How it could work

Business model

Explain who would pay, why, costs and delivery dependencies; check whether it can operate, continue and scale.

Development plan

Separate vision from stage goals, identifying validation points, conditions and evidence that could change the plan.

How to progress

Team evidence

Use relevant experience to explain roles and capabilities, retaining gaps and dependencies.

Funding use and request

Connect resources to specific validation or delivery, stating budget evidence, conditions and the current request without promising returns.

Business model · three validation questions

Feasible

Do value, payment and delivery costs fit together?

Sustainable

Can demand and delivery continue beyond a single transaction?

Scalable

How do cost, quality and dependencies change with scale?

These are checks, not guarantees of profit or funding. Label the status of visions, budgets and commitments separately.

Apply it to your own work

Copy the prompt and add your material to prepare a draft you can adapt.

View prompt

Use “Make an unfamiliar project understandable and checkable” with only my material.
Draft six pitch sections for external listeners, with open questions on feasibility, sustainability and scalability. Separate vision, facts and forecasting assumptions; do not invent market figures, customers, funding commitments or returns.

Check this structure:
1. Core story: Start with a specific user problem, explain the need and vision, and distinguish observed material from hypothetical situations.
2. Product and service: Explain the audience, use, differentiation and evidence. Industry and market figures need sources.
3. Business model: Explain who would pay, why, costs and delivery dependencies; check whether it can operate, continue and scale.
4. Development plan: Separate vision from stage goals, identifying validation points, conditions and evidence that could change the plan.
5. Team evidence: Use relevant experience to explain roles and capabilities, retaining gaps and dependencies.
6. Funding use and request: Connect resources to specific validation or delivery, stating budget evidence, conditions and the current request without promising returns.

Separate facts, judgments, proposals and approvals. Mark missing information “To confirm”. Do not invent numbers, causes, owners, dates or agreement. Retain periods, units, denominators, scope and evidence gaps. The fictional example is not my evidence. End with up to three priority questions to verify.

My material:
[Paste records, goals, constraints and the response needed, with sensitive information removed.]