Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

The roadmap says one thing, the data another, the user a third — now what?

You did the hard part. You learned to listen — to users, to numbers, to the plan someone above you set. Now you sit in the middle of three voices that rarely agree, and you feel the pull as if it were a malfunction. It is not. This is the job. Here is what you are actually doing when you feel torn: you are hoping one of the three will settle the matter for you, so no one can blame you for the choice. That hope is the problem. The roadmap will not decide. The data will not decide. The user will not decide. You decide, with your pod, and you own it. A team that names its tension out loud moves faster than one that hides it behind process. The pull you feel is not a flaw in your judgment. It is three legitimate claims competing for one finite hour. Your work is to rank them, together, for this decision — not forever.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The concept is simple to explain; the difficulty is entirely in the daily discipline of choosing and owning a rank under pressure, with others watching.
How the two dials adapt to you →
What’s really going on

The tension will not resolve. Stop waiting for it to. Your job is not to end the pull between roadmap, data, and user need — it is to choose, today, in this decision, which one governs, and say why out loud to your team. Undecided is also a choice, and a worse one.

🔒 What you’ll build togetherUnlock by starting
A moveBefore your next planning meeting, write down which of the three — roadmap, data, user need — will govern this specific decision, and why. Say it out loud to your pod before anyone asks.
A moveWhen the pull hits mid-project, stop and name it to your team in one sentence: 'Here is the tension I feel, and here is what I am weighting.' Do not resolve it silently and hope no one notices.
A movePick one recent decision where you let the loudest voice win by default rather than by choice. Say plainly what you would rank differently now.
A moveSet a standing five-minute check with your pod: which of the three claims won this week, and was that the right call? Keep the record short and honest.
A moveWhen data and user need conflict and the roadmap is silent, do not wait for permission. Choose, tell your pod what you chose and why, and let the record show your reasoning, not your comfort.
PractiseRank the Claim · a Pod of 4 · 30 min

What changes unlock by starting

  • You stop treating the tension as a problem to solve and start treating it as a decision to make, repeatedly
  • Your pod names competing claims out loud instead of each person silently weighting them differently
  • You can point to a clear reason for each recent tradeoff, not a vague sense that it 'felt right'
  • Decisions move faster because the team argues about the ranking, not about who is to blame afterward
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.