Marcus Andrey Study
Ler em português Library

Framework · Influence & change · 3 min read

BLUF executive summary

Bottom Line Up Front: a one-page summary that opens with your recommendation, then gives why now, the plan, the impact, what you need and the risks, so a senior reader can decide fast.

1Recommendation

What you want them to approve. It goes first.

e.g. Approve two designers for a quarter
2Why now

The problem and the cost of doing nothing, in two lines.

e.g. Booking errors drive support tickets
3The plan

Three bullets of action. Detail goes in an appendix.

e.g. Test, redesign, release in phases
4Impact

A measurable outcome, not a list of outputs. Add one human story.

e.g. Error rate cut by a third
5Resources

The budget, people or decision you are asking for.

e.g. Two designers, one quarter
6Risks

Two risks, each with a mitigation.

e.g. Busy season: short remote tests

One page, one ask, answer first

A BLUF executive summary puts the recommendation first and gives a senior reader only what they need to decide.

Use it when

  • You need budget, people or a decision from senior management for a UX initiative.
  • You are asked for a status update and want it to lead to action, not just inform.
  • A long research report needs a front page that a busy director will actually read.

How to use it

  1. Write the ask first. In one sentence, say what you want them to approve or support. If you can't write it, you aren't ready to send the summary. Output: one recommendation sentence.
  2. Say why now. Give the problem and the cost of doing nothing, in two lines. Use their terms: errors, cost, risk, time. Output: two lines that create urgency.
  3. Describe what you'll do, in three bullets. Keep it to actions, not methods. Leave the detail for an appendix or a follow-up. Output: a three-bullet plan.
  4. State the impact as an outcome. Write "Reduce booking errors by X%", not "Redesign 14 screens". Add one human story, for example a short clip of a user struggling, next to the numbers. Output: one measurable outcome and one story.
  5. Name what you need and the risks. Be concrete about budget, people or the decision. Add two risks, each with a mitigation, so they see you have thought it through. Output: a clear ask and two risks with mitigations.
  6. Cut to one page. Read it as the busiest person on the list. Remove anything that doesn't help them decide. Output: a one-page summary, ready to send or pre-meet with.

Worked example

A UX lead on an internal operations platform wants two designers for a quarter to fix the shipment-booking flow.

Part What the lead wrote
Recommendation Approve two designers for next quarter to redesign shipment booking.
Why now Booking errors are the top cause of support tickets. Each wrong booking needs manual correction by the operations team.
What we'll do Run usability tests with 8 bookers. Redesign the three steps with the most errors. Release in two phases, measuring after each.
Impact Fewer booking errors and support tickets. Target: error rate cut by a third within two months of release.
What we need Two designers for one quarter; one product manager to own the release plan.
Risks & mitigations Teams are busy with year-end: test with short remote sessions. Old habits: release with in-app tips and a short demo.

The lead attached a 30-second clip of a booker re-entering the same address three times. In the meeting, the clip did more than the chart.

Watch out for

  • Building up to the answer. Background, method, findings, then the ask is the academic order. Reverse it.
  • Reporting outputs. "We ran 12 interviews and made 40 screens" is activity. Report what changed or will change for users and the business.
  • Several asks at once. Two or three asks on one page dilute each other. Pick the one that matters most now.
  • Numbers without a story, or a story without numbers. Data shows the size of the problem; a human story makes people care. Use both.

Template

Copy this, fill it in, and keep it to one page. For regular status updates, use the three-part version at the bottom.

Recommendation:   [what you want them to approve]
Why now:          [problem + cost of inaction, 2 lines]
What we'll do:    - 
                  - 
                  - 
Impact:           [measurable outcome]
What we need:     [budget / people / decision]
Risks & mitigations:
                  - 
                  - 

Status update version:
Done:
Next:
Need from you:
Source
Minto Pyramid Principle / military writing
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close