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

How do we stay user-first when the numbers don't agree yet?

You say you build for what users need, holding ego and numbers loosely. Good. But you wrote to me as if this is still a fight — as if ego might win tomorrow if you stop watching it. That tells me the real trouble isn't the holding. It's the waiting. You are waiting for the dashboard to tell you the work mattered. No dashboard arrives in time to comfort you. The user you helped yesterday does not show up as a line that moves for weeks, if ever. You will sit with your team, looking at flat numbers, knowing you built the right thing — and doubt will whisper that right and effective are not the same thing. Here is what is in your power: whether you can state, plainly, what one real person needed and what you gave them. That sentence is yours to make today. The number is not.

◆ 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 team already knows the principle; what they need is a repeatable practice for trusting it under pressure, so guidance dominates.
How the two dials adapt to you →
What’s really going on

You are not struggling to hold ego and metrics loosely — you already do. The real test is trusting the work before the dashboard confirms it. Each week, have every person state one sentence: the specific thing a specific user needed, and what you gave them. If no one can say it plainly, you have drifted.

🔒 What you’ll build togetherUnlock by starting
A moveAt your next team meeting, go around the room. Each person says one sentence: 'This week, [specific user] needed [specific thing], and we gave them [specific thing].' No sentence about traffic, signups, or revenue. If someone can't name a person, they built for the dashboard, not the user.
A moveBefore you ship anything, ask the group out loud: what is the one task a real user is trying to finish right now? Write it on the board. Build toward that sentence, not toward tomorrow's chart.
A moveWhen the numbers disappoint, do not call a meeting about the numbers. Call one about your last five user conversations. Reread them aloud. Let the room judge whether the work served, from the words of real people — not from the line on the graph.
A moveName one teammate the ego-watcher for the month. Their job: when talk turns to 'how will this make us look,' they say so out loud. Not to shame anyone — to pull the room back to the user.
A moveSet a thirty-day rule: no verdict on a feature's worth before thirty days of real user contact. Any metric read before that is noise pretending to be judgment.
PractiseThe User Sentence · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team can state, in one sentence each, what a real user needed this week — without checking a dashboard first.
  • Slow or flat metrics stop derailing meetings; conversation returns to users instead of charts.
  • Ego-driven moves get named and interrupted before they shape the roadmap.
  • The team trusts the work itself as evidence of serving well, not only its score.
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.