From Distorted

How to Examine a Promise About the Future

The result may be years away. You can still check the starting point, the plan, and who is responsible today.

A speaker promises to cut service delays in half within five years. There is a deadline and an animation where everything runs smoothly.

There is no starting measurement or approved budget. No one explains what happens between the applause and year five.

You cannot check a result that has not happened. You can check the promise.

First, identify the statement

An aspiration is a hope: “We want everyone to receive a response sooner.” It does not say what will be delivered or when.

A commitment is something a person or group agrees to do: “We will publish response-time data every quarter.” Here, that means sharing the figures every three months. Ask who will do it and what money or power they have to carry it out.

A conditional forecast predicts a result if certain things happen: “If demand stays within this range and hiring proceeds, we expect the average wait to fall.” Those conditions are part of the claim.

Inevitability means something cannot be avoided. Question that claim when choices, money, and events could still change the result.

One speech may include all four kinds of statement. Check each one.

Put the promise on one page

Fictional example. The agency, promise, dates, figures, and plans below are invented. They show what a reader can check.

The reader asks for documents behind the presentation. They answer some questions and leave others open.

The original promise

“By December 31, 2031, we will halve the average waiting time for routine service appointments across all six branches.”

Published: December 15, 2026. Captured: December 16, 2026. Both dates are fictional.

The starting point

Reported baseline: The baseline is the starting point. The agency reports a mean wait of 30 calendar days, including weekends, for routine appointments booked from January through November 2026 at all six branches. To find the mean, add the waits and divide by the number of appointments. Each wait runs from the first request to the earliest suitable appointment offered.

Target implied by the promise: Half of 30 is 15 days. But which period must meet that target? A full year's average could differ from December's average. The promise leaves this unclear. The agency should explain now.

Evidence status: The agency reports the starting figure. No one outside it has checked the records in this example. Urgent appointments are outside the promise.

Delivery and dependencies

Dependencies are things the plan needs to work.

Responsible owner: The service director is named. Money for staff needs separate approval.

Proposed route: Hire more booking staff. Test a system at two branches. Check who gets appointments and how long they wait before deciding whether to expand.

Conditions to examine: Can the agency find staff and get the money? Will requests rise? Will the system work? Could a better number come from leaving some requests out?

Unresolved: There is no approved staffing budget. The promise gives no condition that allows the deadline to move. Do not add one for the speaker.

Now there is a plan to check, even though its success is unknown.

Follow evidence before the deadline

These are suggested check-in dates for this fictional example. The agency has not agreed to them.

Open a checkpoint to see what to examine.

  1. June 2027 · Is the route supported?

    Check whether money was approved, someone is in charge, and a clear measuring method is published. A budget shows money was approved. It does not show that waits fell.

  2. December 2028 · What did the trial show?

    Compare waits using the same rules and periods. Check appointments offered, requests left unmet, cancellations, and each branch's results. The recorded wait could fall while fewer people get appointments.

  3. December 2030 · Is the target still plausible?

    Compare results so far with the work left. Keep any changed prediction and its reasons. Did the deadline, group covered, or measure change? Keep the old and new terms together.

Set your own date to check again. This page does not send reminders.

Leave room for more than one future

What if requests rise? What if hiring succeeds but the system fails? What if one branch improves and another gets worse?

A useful prediction explains how these changes could affect the result. Keep a range of possible results when evidence supports one. Do not invent an exact chance of success when it is unknown.

Allow three answers: the promise was met, it was missed, or there is too little evidence to tell. If the final measuring period stays unclear, encouraging figures may not settle the question.

Return to what was actually promised

At the deadline, check the result against the original promise and its terms. Report meaningful changes. A new target may make sense. It should not quietly replace the old one.

A failed prediction does not prove someone lied. You need evidence about what they knew and did. A future deadline also does not excuse a false claim today about money, progress, or a finished test.

If someone predicted harm, ask what people did to prevent it. The harm may not have happened because that work helped. Its absence alone does not prove the warning was wrong. The claim that prevention worked needs evidence too.

What should we save today to judge the result fairly later?

Next: Keep a Claim Record of the promise, including its original wording and conditions.

From the book

This guide builds on Chapter 21 of Distorted, “Tomorrow, Sold Today,” particularly “The Inevitability Script” and its counter-moves. It uses the Clarity Framework: Investigate Claims, Analyze Narratives, and Live with Discernment.

Save this page

You can copy this link to your notes or bookmarks.