Back to playbooks

One-Ask Engine

Use when: you do not know what to do, or you want clean leverage without spiraling.
Output: one clear ask + one measurable outcome + one next step.

This is the default move: turn emotion into something useful.

The promise

You do not need to be a policy expert. You need to be:

• specific
• calm
• consistent
• measurable

The shape of a strong ask

A strong ask usually names four things:

• Rule: what should change
• Owner: who can actually do it
• Metric: how you will know it worked
• Deadline: when movement should happen

If one of those is missing, the ask may still be worth sending, but it is probably weaker than it needs to be.

Steps (10 minutes)

1. Name the problem (one sentence, plain words)
2. Pick one decider (the person/body that can actually move it)
3. Name the rule (what should change)
4. Define success (metric + timeline)
5. Make the next step easy (yes/no by date, staff contact, 15-minute call)
6. Offer one tradeoff sentence (optional, shows seriousness)
7. Log it (so you can be consistent)

A quick fill-in pattern

“Will [owner] [rule] by [deadline], and report [metric] so the public can see whether it worked?”

Common failure modes (avoid these)

• Too many asks
• Vague asks (“do better”)
• Motive-mindreading
• “Here is my whole worldview” emails
• Anger freelancing
• No clear owner
• No deadline

Quick examples

• “Will the city publish monthly permitting timelines by project type starting in April, and cut median review time by 25% within 6 months?”
• “Will the state require all-in move-in cost disclosure before any application fee is paid, and publish compliance data by quarter?”
• “Will this agency publish prior-authorization turnaround times by payer and service line by July 1, with monthly updates after that?”
• “Will the transit authority publish route reliability monthly and improve Route X by 15% within 6 months?”

Done is better than perfect

One ask sent > ten hot takes.

Back to playbooks