DORA Metrics vs. a True North Dashboard: How Busy Leaders Choose the Right Metrics Without Creating Noise
If you are leading software work and your biggest pain is late delivery, long lead time, or unstable releases, a delivery-focused set of metrics (often discussed as “DORA metrics”) can help you see the flow problems you need to fix.
If you lead a broader team, a department, or several groups that must work together, you will usually get better results with a True North dashboard, a small, balanced set of measures across quality, delivery (lead time or cycle time), productivity, capacity utilization, human development, and a clear future target.
This is for leaders who want metrics to reduce stress and confusion. It is not for leaders who want a scoreboard to rank people. When metrics become a weapon, people hide problems and the system gets worse.
Start with the real job of metrics: make reality easier to see
“The primary purpose of visual performance metrics isn’t to make sure things are working well in your department. It’s to create a thinking environment which makes it easier for multiple departments, teams, groups to work together.”
That line changes the whole conversation.
Many leaders ask, “What should we track?” A better first question is, “What do we need to see that we cannot see right now?”
Because hidden problems do not get solved.
Metrics work best when they do three things:
- Make the “actual reality” visible, not the story we tell ourselves
- Help people make better decisions faster, not just report upward
- Create better teamwork across handoffs, not stronger silos
One more warning that matters: “Visual metrics provide focus. Just making them visual, doesn’t work any magic. Making decisions and taking action gives credibility to the numbers.”
When to use delivery-focused software metrics (the “DORA” path)
Use a delivery-focused dashboard when your goal is clear: improve how work moves from request to done. The material here talks about delivery in plain terms: delivery, lead time, cycle time (the bottleneck).
Choose this path when:
- Your work is mainly software development or another type of work where speed and reliability matter day to day
- People argue about delivery because the process is hard to see
- You need a shared view of “Are we getting faster and cleaner at finishing work?”
Do not choose this path when:
- Your biggest problems are not inside the delivery team, but in the handoffs between groups
The material calls this the “white space” between departments, where handoffs often cause failures. - Leaders plan to use the numbers to “catch” people
When management focuses on blame instead of the process, people game the system.
Here is the simple truth: output metrics will tell you that you are late, but they rarely tell you what to do next.
So if you track delivery, do not stop at outcomes.
When to use a True North dashboard (the balanced path)
“True North Metrics is a phrase often used by companies adopting Toyota type (or lean) improvement practices. True North metrics require a blend of perspectives.”
The categories are meant to be universal. The exact measures change by context (manufacturing, software development, hospital care), but the balance stays.
A practical set, straight from the material, includes:
- Safety (where physical work is being done)
- Quality
- Delivery, lead time, cycle time (bottleneck)
- Productivity improvement
- Capacity utilization (because capacity is often invisible in office work)
- Human development (more than hours trained)
- A future performance target (what does better look like 12 months from now?)
Choose True North when:
- Your results depend on several groups working together, not one team
- You need help making trade-offs on purpose
“Trade-offs exist.” - You want a small set of measures that stay steady enough to guide behavior, not a “laundry list” of 20+ items that fight each other
A True North dashboard is not about getting a high score. “The goal here is not to see how high you can score. The goal is to use this instrument to foster a dialog and to change your perspective on improvement opportunities.”
The mistake that breaks both approaches: measuring outputs, ignoring drivers
Most leaders measure the end of the process because it is easy to see. The material is blunt: “Most performance metrics focus on process outputs, not the actual process itself.”
If you want early action, you need process drivers.
A simple way to find them is to keep asking what drives the metric, then ask again, then ask again.
Here is the model to hold in your head:
Inputs → Process → Outputs
When you only track outputs, you often find out too late.
A story that shows why this matters (and why fear is so costly)
A patient died in a hospital after a nurse accidentally used the wrong medication vial. The write-up describes a chain of small issues: similar vial colors, small print, low light, bottles close together, and weak standards for pointing out problems.
It is painful to read, and it makes the point: smart people can still fail inside a weak system.
“It takes effort by leaders to build trust where their team members are comfortable pointing out process issues.”
If your metrics make people scared to speak, you will miss the warning signs.
A simple way to start (without making a “metrics project”)
Here’s how you do it, plain and practical.
Step 1: Pick something important that is hard to see
“Consider something important to your success but difficult to see or perhaps subject to different interpretations.”
Step 2: Write down the purpose in one sentence
Ask, “Why is this important?” and keep refining.
Step 3: Decide what the visual should cause people to do
Ask, “What decisions might your visual drive?”
Step 4: Keep it light enough to maintain
Daily updates should take less than 10 minutes.
You should be able to see the key issues in less than 10 seconds.
Step 5: Run it as an experiment, then adjust
Try it for a week, a month, or a quarter. Then evaluate what happened versus your purpose.
One more tip that keeps this human: when bad news shows up, treat it like a gift.
“Share bad news first, no problem is a problem.”
The strongest signal that your dashboard is working: people change how they act
A visual can change behavior without anyone forcing it.
In one example, a team posted an RFP board and reviewed it twice a week. Sales could suddenly see, in public, how many proposals were unlikely to win. The win rate moved from about 33% to over 60% over time, because people changed what they did upstream.
That is the point. Not the board. Not the numbers. The change.
“The most important choice you make is what you choose to make important.”
So choose one: do you need tighter visibility into delivery flow, or do you need a balanced True North view that keeps the whole system healthy?
Then build the smallest visual that helps your team tell the truth and act on it.