Measurement That Means Something
Are we measuring performance, or just collecting numbers?
We look at how KPIs, scorecards, and reporting shape decisions, where metrics lose context, and what makes a measure useful enough to act on.
Insights
Better questions can change the way a problem looks.
Measured Resolve explores the ideas behind better measurement, stronger operations, clearer reporting, thoughtful technology decisions, and better judgment under uncertainty.
We challenge assumptions, share practical lessons, and spend time with questions that deserve more than a quick answer. Some are best explored in writing. Others are better shown through examples, walkthroughs, and longer conversations.
What we think about
Six subjects that shape a lot of our thinking.
They surface in different forms across organizations, industries, and decisions. Each gives us room to test assumptions, share lessons, and explore what better measurement, systems, technology, and judgment can look like in practice.
Root Cause & Operational Learning
Why does the same problem keep coming back?
We explore how recurring symptoms can be traced upstream, how competing explanations can be tested, and how organizations can learn from failure instead of repeatedly reacting to it.
Technology With Purpose
Does the new tool solve a meaningful problem, or just add another tool?
We examine when new software, automation, artificial intelligence, or custom tools create useful leverage and when the better answer is to improve what already exists.
Forecasting Without False Certainty
What can the evidence tell us about what comes next, and where should confidence stop?
We look at forecasts, scenarios, assumptions, and ranges as decision tools rather than promises about the future.
Reporting Systems That Survive
Would the reporting still work if the person who built it left tomorrow?
We explore what makes reporting reliable, maintainable, understandable, and transferable instead of dependent on one person remembering how everything works.
Useful Friction
What question needs to be asked before everyone agrees too quickly?
We make room for constructive disagreement, context, and intellectual humility when a better question can lead to a better decision.
Featured thinking
A few ideas we are developing now.
Here are a few questions and claims we are working through now. Some will become written pieces. Others are better suited to a video, example, or walkthrough, depending on what the idea needs.
A dashboard cannot fix a disagreement about definitions.
What looks like a reporting problem may actually be a measurement problem. Before adding another view, the definitions underneath it have to agree.
Content previewWhen automation makes the wrong process faster.
Efficiency is not automatically improvement. Before automating a workflow, it is worth asking whether the workflow itself deserves to survive.
Content previewA forecast is not a promise.
The range around an answer can matter as much as the point estimate when a decision has to hold up as conditions change.
Content previewIdeas we keep coming back to
Some principles are worth examining more than once.
More information does not necessarily create more understanding.
More fields, pages, charts, and alerts can make a reporting system busier without making a decision easier. The useful question is which information actually changes how someone understands or acts.
Automation should remove friction, not understanding.
Removing repetitive work is valuable, but not if the process becomes impossible to inspect, explain, or recover when something goes wrong. Good automation should make the work easier without hiding how it works.
Forecasting should make uncertainty more useful, not invisible.
A useful forecast should show what the evidence suggests, where the conclusion is fragile, what could change it, and which decisions still make sense across a reasonable range of outcomes.
The visible problem is not always the material problem.
The thing that gets noticed first is often only the symptom. We keep looking upstream at definitions, incentives, handoffs, process design, data, technology, behavior, and the way those pieces interact.
Where to follow
Follow the conversation where you prefer to have it.
Good ideas need the right amount of room. Some are best tested in a concise written argument. Others are easier to understand when we can show the work. These are the places where we keep the conversation going.
Written analysis & discussion
Short-form analysis, business questions, case-study lessons, practical observations, and conversations that benefit from being written and discussed in public.
Long-form video
YouTube
Longer explanations, walkthroughs, demonstrations, case-study discussions, and ideas that are easier to understand when there is room to show the work.
Selected adaptations
Other Channels
Visual excerpts, shorter ideas, announcements, and platform-specific versions will be used when the format adds something useful rather than simply repeating the same post everywhere.
Publishing standard
Shorter should not mean louder.
We do not publish simply to stay visible. We would rather share fewer ideas with something useful behind them than add more noise to an already crowded feed.
When evidence matters, we show it. When uncertainty exists, we say so. When a popular idea deserves questioning, we question it. And when something can be explained simply, we do not make it complicated just to sound more sophisticated.
Start a conversation
Some questions are better discussed than searched.
If something you are reading connects with a question inside your own organization, you do not need to wait for us to publish the exact post or video. Bring us the question and we can start there.
Start a Conversation