How to measure progress on a vague goal.

Measuring Something Hard to Measure

I spent three hours last Tuesday watching a mid-sized logistics manager stare at a $50,000 Tableau dashboard, looking for an answer that wasn’t there. He was trying to figure out how to measure progress on a vague goal like “improving operational synergy,” as if a shiny heat map could magically define a process that didn’t even exist on paper. Most companies treat software like a magic wand; they buy expensive licenses to avoid the uncomfortable, manual work of actually mapping out their workflows. If you don’t have a written sequence of events, you aren’t measuring progress—you’re just watching numbers move and calling it data.

I’m not here to sell you on a new productivity framework or a subscription to some bloated SaaS platform. I’m going to show you how to strip the fluff away and find the actual levers of movement. We are going to stop chasing phantom metrics and start building a functional baseline by defining the work first. By the end of this, you’ll know exactly how to turn that “vague intention” into a sequence of measurable, repeatable actions that actually matter to your bottom line.

Table of Contents

The Fallacy of Measuring What You Havent Defined

The Fallacy of Measuring What You Havent Defined.

I see it every week: a manager spends three months and fifty thousand dollars on a SaaS subscription because they want to “track team engagement.” They are trying to solve a lack of clarity with a software license. This is the fundamental mistake. You cannot start quantifying qualitative goals if you haven’t even decided what “quality” looks like in a repeatable sequence of actions. If your goal is “better communication,” you don’t need a dashboard; you need a written protocol for how information moves from Point A to Point B.

When you attempt to measure a vague objective without a defined process, you aren’t tracking progress—you’re just chasing ghosts. You end up stuck in the trap of objective vs subjective progress, where your metrics are based on how people “feel” rather than what they actually did. Without a baseline process, your data is just noise. I’ve seen entire logistics departments try to optimize “efficiency” before they even mapped out their loading sequence. They didn’t need better metrics; they needed to stop guessing and start documenting. Until the workflow is on paper, any number you pull from a spreadsheet is a lie.

Quantifying Qualitative Goals Through Rigorous Process Design

Quantifying Qualitative Goals Through Rigorous Process Design

You can’t put a ruler against “improving company culture” or “enhancing customer experience” because those aren’t tasks; they’re outcomes. Most managers fail here because they try to measure the feeling instead of the friction. If you want to succeed at quantifying qualitative goals, you have to stop chasing the sentiment and start looking at the mechanics. You don’t measure “happiness”; you measure the frequency of specific, repeatable actions that lead to it.

This requires shifting your focus toward setting leading indicators that actually correlate with your target. If your vague goal is “better communication,” don’t ask people if they feel heard—that’s subjective nonsense. Instead, map the process: how many decision-making loops are closed within 24 hours? How many cross-departmental handoffs require a follow-up email? When you turn an intangible aspiration into a series of measurable checkpoints, you move from guessing to auditing. You aren’t tracking moods; you are tracking the behavioral output of a designed system. If the process is documented and the inputs are consistent, the progress becomes visible. Anything else is just expensive guesswork.

Stop Guessing and Start Mapping: 5 Ways to Turn Fog into Data

  • Identify the lead indicators, not the lag indicators. If your goal is “better customer service,” don’t wait for the end-of-year survey to see if you failed. Measure the time it takes to resolve a ticket today. The survey is a post-mortem; the resolution time is the pulse.
  • Break the “vague” goal into discrete, repeatable steps. You can’t measure “innovation,” but you can measure how many documented process improvements were submitted to the floor this month. If you can’t count the step, you can’t track the progress.
  • Define your “Definition of Done” before you start. Most teams drift because they haven’t agreed on what success actually looks like in a spreadsheet. If “increased efficiency” isn’t assigned a specific percentage or a specific time-save, it’s just a wish, not a goal.
  • Stop using vanity metrics to soothe your ego. A dashboard showing “user engagement” means nothing if your actual process is leaking money through unfulfilled orders. Measure the bottleneck, not the noise.
  • Audit the measurement tool itself. I’ve seen companies spend $50k on a SaaS subscription to track a metric that nobody actually uses to make a decision. If the data doesn’t trigger a change in the process, stop collecting it. It’s just expensive clutter.

The Bottom Line

Stop buying software to track “vague progress.” If you can’t map the steps of the task on a piece of paper, no dashboard in the world will give you a meaningful number.

Metrics are lagging indicators of a process, not a substitute for one. You don’t find clarity in a spreadsheet; you find it in the workflow you designed before you opened the spreadsheet.

If your goal is “better communication,” your metric isn’t “number of emails sent.” Your metric is the specific, repeatable process that ensures the right information reaches the right person at the right time.

Stop Chasing Ghosts

Stop Chasing Ghosts with defined processes.

We’ve spent this time dismantling the idea that a fancy dashboard can save a directionless team. You can’t track progress on a “vague goal” because vagueness isn’t a metric; it’s a lack of discipline. If you haven’t translated that nebulous ambition into a repeatable, written process, you aren’t measuring anything—you’re just watching numbers dance. Stop looking for a software solution to bridge the gap between your intention and your execution. Define the steps, map the inputs, and identify the specific outputs. Only once the process is codified can you actually quantify the qualitative and stop wasting billable hours chasing ghosts.

At the end of the day, clarity is your most valuable operational asset. Most managers spend their lives trying to automate chaos, but you can’t optimize a mess. Stop waiting for the “perfect tool” to arrive and start doing the heavy lifting of documentation. It’s tedious, it’s unglamorous, and it’s exactly what separates the professionals from the enthusiasts. Get the process on paper, measure the friction points, and then—and only then—can you actually move the needle. Now, get to work.

About Idris Haverkamp

A tool cannot fix a process you have not written down. I start with the process.

Idris Haverkamp

A tool cannot fix a process you have not written down. I start with the process.