Marcus Andrey Study
Ler em português Library

Framework · Presence & career · 2 min read

Propose, don't just report

A four-part habit for raising problems: bring the evidence, why it matters, a proposed solution (even a rough one) and what you need, so you shape the decision instead of handing it to others.

  1. 1Problem

    What you found, with evidence: where, how many, how often.

    "4 filter patterns across 3 apps."
  2. 2Impact

    Why it matters, in your audience's terms: rework, errors, risk.

    "It costs developers rework."
  3. 3Proposal

    Your proposed solution, even a rough one. Say "I propose".

    "I propose we standardise on one."
  4. 4The ask

    What you need, specific enough that the other person can say yes.

    "2 hours from each designer."
Four parts that turn a reported problem into a proposal someone can approve.

Use it when

  • You notice a problem nobody is addressing, such as inconsistent patterns across products.
  • You raise a risk in a meeting and want it to lead to action, not just a nod.
  • You want to move from contributor to initiator, a key step in leading without the title.

How to use it

  1. State the problem with evidence. Be specific and concrete: what you found, where, how often. Numbers and examples beat adjectives. Output: one or two sentences of problem plus evidence.
  2. Say why it matters. Name the cost in terms your audience cares about: rework, user errors, delays, risk. Output: one sentence on impact.
  3. Give your proposed solution. Say what you would do, even if it is rough. Use ownership language: "I propose…" or "I recommend…", not "maybe we could…". Output: one clear proposal.
  4. Say what you need. Time, people, a decision or a budget. Be precise, so the other person can say yes. Output: a specific ask.
  5. Make it a weekly habit. Every Friday, spend 15 minutes asking: what did I notice that nobody is addressing, what will I propose next week, and whom do I need to talk to first? Output: one proposal planned for next week.

Worked example

A UX lead on an internal operations platform with 6 product teams notices that table filters behave differently across apps.

Line
Report only "The table components are inconsistent across products."
Problem + evidence "I found 4 different table filter patterns across 3 apps."
Why it matters "It costs developers rework and confuses users who switch between apps."
Proposal "I propose we standardise on one in the next design-system release. I can draft it with the product designers."
What I need "I'd need 2 hours from each of them."

The full version takes under a minute to say, and it ends with something the manager can approve on the spot.

Watch out for

  • Waiting for the perfect proposal. A rough proposal now is more useful than a polished one after the decision is made.
  • Hedging the proposal away. "Maybe we could possibly look at…" is a report in disguise. Say "I propose".
  • No ask. Without "what I need", nobody knows how to help, and the proposal stays an idea.
  • Evidence-free problems. "Users hate this" invites debate. "Three support tickets a week" invites action.

Template

Copy this into your notes before a meeting or a message.

Problem (with evidence):
Why it matters (cost, risk, users):
I propose:
What I need (time, people, decision):

Friday check (15 min):
- What did I notice this week that nobody is addressing?
- What one thing will I propose next week?
- Whom do I need to talk to first?
Saved only on this device.

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