Connect financial, operational, customer and people measures to specific strategic goals, with clear baselines and responsibility for review.
Many organisations report a great deal and learn surprisingly little from it. Dashboards grow over time, each new initiative adds its own indicators, and monthly reviews become an exercise in explaining variances rather than making decisions. The problem is rarely a lack of data. It is that the measures were never clearly connected to what the strategy is trying to change. This article sets out a practical way to choose and use measures so that they inform decisions rather than simply describe activity.
Start with the intended outcome
A measure is useful when it helps answer a decision. Define what the strategy aims to change, the starting point and the review period before choosing a dashboard of indicators.
A simple discipline is to write each strategic goal as a change in a specific condition. “Grow the business” is too broad to measure meaningfully. “Increase repeat orders from existing accounts in the Irish market over the next eighteen months” points directly to the data required, the population concerned and the timeframe for judging progress. Once the goal is written this way, leaders can ask which decision the measure will support. If the figure moved up or down, what would the organisation do differently? If nobody can answer that question, the measure is probably informational rather than decision-relevant, and it may belong in a background report rather than the leadership review.
Business results are influenced by many factors. An improvement after a new initiative is evidence to examine, not automatic proof that the initiative caused it.
Consider a sales team that introduces a new account planning process and sees revenue rise in the following quarter. The process may have contributed, but so might a competitor’s supply problem, a price change or seasonal demand. Treating the result with appropriate caution, and looking for supporting evidence such as changes in the behaviours the process was meant to encourage, leads to better decisions than declaring success on the headline figure alone.
Financial and operational measures
Revenue, margin and cost can show different aspects of business performance. Choose the measures that fit the objective and consider external factors such as demand, pricing or a change in product mix.
Financial measures are usually lagging indicators: they confirm what has already happened. They remain essential, but they rarely tell a leadership team early enough that something needs attention. Pairing each financial outcome with one or two operational measures that are expected to influence it gives earlier warning and a clearer sense of where to intervene.
Operational measures might include cycle time, rework, completion rates or cost per transaction. Define each measure consistently and check the quality of the underlying data.
Definition matters more than it first appears. Cycle time can start when a request is submitted, when it is accepted or when all information has been received, and each choice produces a different number. If two teams calculate the same measure in different ways, comparisons between them are misleading. Writing a short definition for each measure, including its source system and any exclusions, prevents a surprising amount of debate later. Where data is held in spreadsheets or entered manually, it is also worth testing a sample against the underlying records before relying on it. In our process improvement and digital strategy work, clarifying these definitions is often one of the most valuable early steps.
Customer and people measures
Customer satisfaction, retention, support requests and research can help explain the experience behind financial results. A recommendation score measures stated willingness to recommend; it does not establish future behaviour by itself.
Quantitative customer measures work best alongside qualitative insight. A fall in satisfaction scores tells you something has changed; conversations with customers, a review of complaint themes or observation of how people use a service tell you why. Leaders should be wary of setting targets for survey scores in isolation, because targets can encourage teams to manage the score rather than the experience behind it.
Employee feedback, workload and retention can also reveal whether a change is workable. Interpret survey findings with context and avoid treating a single result as a complete assessment of a team.
People measures are particularly important during periods of change. A new system may meet every operational target while placing an unsustainable load on a small group of experienced staff who handle the exceptions. Looking at workload distribution, overtime patterns and turnover in key roles can reveal this before it becomes a retention problem.
Use a balanced view
A balanced scorecard can bring financial, customer, process and learning measures together. It is one approach, rather than a requirement for every organisation.
Whatever framework is used, the principle is the same: no single dimension should be allowed to dominate in a way that hides costs elsewhere. Reducing processing time is welcome, but not if error rates rise or customer queries increase as a result. Presenting related measures together makes these trade-offs visible.
Agree an owner, definition, data source and review frequency for each measure. Keep the set small enough to support decisions and revisit it when priorities change.
A practical way to build the set is to work through a short sequence:
- List the strategic goals and write each as a specific intended change.
- For each goal, choose one outcome measure and no more than two leading measures.
- Record the definition, source, baseline, owner and review frequency for each.
- Test whether the data can actually be produced reliably at that frequency.
- Remove anything that does not support a decision.
Where data is scattered across systems, a modest investment in collecting it consistently can transform the review. A workflow application that replaces spreadsheet tracking, for example, can make status, cycle time and volume measurable as a by-product of everyday work rather than a separate reporting task.
Turn reporting into action
Discuss what the results mean, what remains uncertain and what should change next. Record decisions so that the next review can assess whether the response helped.
The quality of a review meeting depends less on the dashboard and more on the questions asked. Useful prompts include: which results are outside the range we expected, what do we believe is causing them, what evidence would confirm or challenge that view, and what are we going to do before the next review? Keeping a simple decision log turns each meeting into part of a learning cycle, so that the organisation can see over time which interventions worked and which did not.
Where to start
If the current reporting feels heavy but unhelpful, begin with a single strategic goal. Rewrite it as a specific intended change, select a small number of measures with clear definitions and owners, and run two or three review cycles before extending the approach. Glyz can support strategy, process review and reporting requirements, connecting the measures to the work and systems involved.
