The Defensive Dashboard

How metrics build the behavior of a company, why they almost always build it toward defense, and how to rebuild them so that innovation, risk and future revenue get a fair chance.

In the early 2000s three financial economists, John Graham, Campbell Harvey and Shivaram Rajgopal, put a question to 401 chief financial officers that really allows only one answer: would you start a project that demonstrably brings the company far more than it costs? 55 percent replied that they would pass on it if the project pushed them below analysts' earnings expectations in the current quarter. Almost 80 percent said they would cut spending on research, advertising and maintenance in order to hit an earnings target. well documented What is remarkable about these answers is less the short-sightedness one can read into them than the calm with which they were put on the record, because in the world where these people are measured, they are simply being reasonable.

Every company tells its employees through metrics which behavior was just right, and it does so daily and at every level, from the board's quarterly figure to a project team's velocity. Metrics thereby form the signal layer of a company's action infrastructure, and like any infrastructure they act most strongly where no one is looking anymore. The previous article on the two gravities described why a company would rather avoid effort than improve the result; this one shows the place where that gravity does its work every single morning.

Core thesis

The metrics by which people in a company read off daily whether their action was right shape their behavior more strongly than any mission statement or strategy.

Almost all common metrics, from the board to the project, are improved fastest by doing less, changing less and daring less. That is why an ordinary metrics system trains a company toward defense, without anyone ever having decided so.

Whoever wants more innovation and more calculated risk must therefore not primarily add new metrics, but rebuild the existing ones: in their definition, their framing, their arrangement and the cadence in which they are shown.

Precondition: what is displayed, what is paid out and what earns promotion must all point the same way. Put an innovation figure on the dashboard while the bonus hangs on EBIT, and people follow the bonus, and the dashboard becomes decoration. Steven Kerr described this mechanism in 1975 under the title „On the Folly of Rewarding A, While Hoping for B“.

well documented research with broad evidence case documented single case hypothesis plausible, little direct evidence

01Analysis: What is on the screens

Whoever leafs through the dashboards of an average mid-sized company or corporation finds strikingly similar numbers at every level. Read not as measuring instruments but as instructions, they yield a fairly precise picture of what the organization actually teaches its people.

LevelUbiquitous metricsWhat they actually rewardPredictable behavior
Board, C-levelEBIT or EBITDA margin, earnings per share, free cash flow, ROCE, revenue growth, loyalty to one's own forecastreliable quarterscut research and marketing as a buffer, buy back shares instead of placing one's own bet, acquire instead of develop, because an acquisition goes onto the balance sheet and development goes into expense
Division and business-unit headscontribution margin, plan-actual variance, OPEX, headcount, budget adherencepredictabilityplan cautiously, spend leftover budget in December, hoard positions, optimize inside one's own silo
Controlling, procurementsavings versus prior year, unit purchase pricevisible cost reductionchoose cheaper suppliers whose downstream costs surface in other cost centers
Salesrevenue against quota, close rate, pipelinevolume within the perioddiscounts at quarter-end, existing customers instead of new markets, avoiding new products because their sales cycle is longer
Production, operationsoverall equipment effectiveness (OEE), scrap, unit cost, on-time deliverystabilityavoid process changes, fend off pilots because they depress OEE
HRheadcount, cost per hire, time to fill, sickness rate, attritionadministrative efficiencyhire fast and cheap rather than well matched, avoid exceptions
IT, customer serviceavailability, tickets closed, average handling time, service levelthroughputclose tickets instead of solving problems, keep conversations short, treat change as a disruption
Projectschedule, budget, scope, velocityadherence to the planfreeze the scope, build in buffers, do not report the unexpected, suppress learning during the project
The right-hand column describes tendencies that follow from how the metrics are built, not the behavior of every individual company.

The pattern runs through all eight rows, and it has a cause that lies deeper than the timidity of individual managers. The metrics themselves are built so that they reward defense faster, more visibly and more reliably than any advance. Five structural properties explain this.

Time asymmetry. A new venture costs money immediately, certainly and in full, while its return arrives later, uncertainly and often spread across units that do not even recognize it as such. Accounting sharpens this tilt, because research costs may be capitalized neither under German commercial law (HGB § 248 (2)) nor under IAS 38, so that in the books every innovation first appears as a deterioration, often over several years. The survey cited at the outset shows how executives respond to this. well documented

The denominator problem. Most steering figures are ratios, that is margin, return on capital or cost per unit, and a ratio is improved most comfortably by shrinking the denominator, investing less, outsourcing or discontinuing something. Clayton Christensen described this in 2008 with Stephen Kaufman and Willy Shih in „Innovation Killers“. well documented Boeing supplied the textbook case: return on net assets drove the far-reaching outsourcing on the 787, even though its own engineer L. J. Hart-Smith had calculated in an internal 2001 paper that the costs of outsourcing were being systematically underestimated. case

Invisible omission. The project that was never started has no line on any dashboard, and so the person who tries something and fails shows up red in the table, while the person who tries nothing appears nowhere. Psychology has known the tendency to weigh harm through action more heavily than harm through inaction since Ritov and Baron 1990 as the omission bias. well documented The metrics system amplifies this tendency, because it cannot technically represent omission at all.

Variance logic. Controlling almost everywhere compares plan and actual, and thereby rewards not the value created but the accuracy of one's own forecast. The consequences are well known: cautiously set plans, the December fever in which leftover budgets are spent so they will not be missing the following year, and a quiet aversion to anything that scatters. Michael Jensen took this apart in 2001 in „Corporate Budgeting Is Broken, Let's Fix It“. well documented Innovation is by its nature scatter, which is why a system that punishes scatter reliably prevents it.

Precision beats relevance. A cost figure is exact, attributable to one person and available weekly, while the value of an option on a future business stays vague, belongs to everyone and shows up late. In the meeting the precise thing wins the attention, and whoever has the attention sets the agenda. Daniel Yankelovich named this mechanism after the US secretary of defense Robert McNamara, who steered the Vietnam War by countable quantities.

02Hypothesis: Behavior follows how the number is built

From these five properties follows a hypothesis that can be tested against any company: whoever knows how a metric is built can largely predict the behavior of the people measured by it, regardless of what the mission statement says. The prediction rests on six diagnostic questions that can be put to any single metric.

Diagnostic question for the metricAnswer that predicts defensive behavior
Can it be improved by not doing something?Yes, for example by cutting, outsourcing, not starting
Does its feedback arrive faster than the effect of the action it judges?Yes, the costs appear in the month, the benefit in years
Does it punish deviation, or does it expect scatter?It punishes deviation in both directions
Does it make an individual responsible for something only the system can influence?Yes, then the individual protects themselves
What stays invisible next to it?Missed chances, stopped ideas, future revenue
Does money or a career hang on it?Yes, then all the effects above act more strongly
If the first three answers apply, defensive behavior is to be expected with high probability. The sixth question determines how strongly.

The hypothesis does not claim that people react cynically to numbers, but that they learn, and a metrics system is a teacher that teaches every day and whose curriculum no one wrote. hypothesis In its building blocks it is well supported; as a whole-organization model it has not yet been systematically tested.

03Problem: Why this gets expensive

Costs can be lowered to zero at most, while revenue has no ceiling, and in this plain asymmetry lies the real problem of a defensive metrics system: it steers the entire attention of an organization onto the side of the ledger whose return is bounded, and pulls it away from the side whose return is not.

3M demonstrated this shift. For decades the company had set itself the goal of earning around 30 percent of its revenue with products only a few years old. After the introduction of Six Sigma under James McNerney from 2001, that share fell to around 21 percent by his departure in 2005, and the magazine BusinessWeek described in detail in 2007 how efficiency standards had smothered research. case At Boeing, the then head of the commercial airplanes division, Jim Albaugh, said in 2011 of the 787 program: „We spent a lot more money in trying to recover than we ever would have spent if we'd tried to keep the key technologies closer to home.“ case

The damage arises not in a single moment that would show up on a dashboard, but as the sum of thousands of small decisions, each reasonable on its own, until an organization has unlearned its capacity for the new and only notices when a competitor shows it up. The workforce probably changes along the way, too, because people who like to dare something are seldom promoted in such a system and leave earlier. hypothesis

A metrics system is a teacher that teaches every day and whose curriculum no one wrote.

04Approach: Redirect the loss aversion

Whoever designs a dashboard is laying track on which a thousand small decisions will later roll of their own accord, and the most effective rebuilds do not try to overcome people's loss aversion but to set it onto a different track. The precondition for all the levers below is the coupling from the core thesis: display, payout and promotion must point the same way. The letters of the levers reappear in the dashboard example below.

Show waiting as a cost item. The concept for this is called cost of delay and comes from product development: every venture is given an estimate of what one month of delay costs, and time thereby lands on the same loss side on which today only the budget sits. Waiting is then no longer the safe but the expensive option, and the same loss aversion that used to prevent projects now pushes for speed.

Count cost savings as reallocation. A saved sum counts as a full success only once it has been reallocated within twelve months into documented growth bets, so that the new metric is the reallocation rate and not the saving alone. Whoever saves controls part of that money themselves, and saving thereby becomes the means to finance one's own ventures. From gain-sharing models we know that people search more thoroughly for savings when they keep a share of them. hypothesis For the reallocation rate in exactly this form, robust empirical evidence is lacking.

Protect the denominator. Internal reporting follows no accounting standard and may therefore report a result before future investments, run the ongoing business and the business of change in separate budgets, and take the spending on the new out of the margin against which the line is measured. This separation needs a counter-metric, because otherwise everything is soon relabeled as a future investment, and the best counter-metric is a kill rate, that is the share of bets ended according to criteria set in advance. A kill rate of zero is not a success here but a sign of innovation theater.

Make omission visible. The dashboard needs a line for rejected and stopped ventures with their estimated potential, and the stock of live bets appears there as an asset position rather than a cost block. A vitality index on the 3M model, that is the revenue share of products younger than a few years, forces leadership to treat tomorrow's revenue as an obligation. case

Separate measures for separate horizons. The core business may continue to be steered by efficiency, while the exploration business needs learning metrics: the duration of an experiment cycle, the number of confirmed and refuted hypotheses, the cost per robust insight and the kill rate. Eric Ries calls this innovation accounting. Funding comes in tranches against learning milestones, the way a venture capitalist works, and these metrics are deliberately not passed down into the dashboards of the cost centers, where they would immediately be read against efficiency standards.

Corridor and expected value instead of plan adherence. Rolling forecasts and relative targets against competitors replace the rigid plan, and Svenska Handelsbanken has worked without classic budgets since the 1970s, which made it the model for the beyond-budgeting movement. case Gustavo Manso showed theoretically in 2011 that incentives which tolerate early failure and reward long-term success favor innovation, and Azoulay, Graff Zivin and Manso confirmed this the same year on researchers at the Howard Hughes Medical Institute, who, with longer funding cycles and more tolerance for failure, produced more breakthroughs and at the same time more failures than comparable researchers with NIH funding. well documented

Arrangement and cadence of the dashboard. What sits top left determines the first question in the meeting, which is why the stock of options and the pipeline belong there and not the cost variance. Andy Grove recommended in „High Output Management“ pairing every metric with a counter-metric, so that costs stand directly beside the growth they enable. Red traffic lights activate the loss mode, while ranges signal that scatter is expected. Most underestimated is the cadence: Benartzi and Thaler showed in 1995 with the concept of myopic loss aversion that people decide the more risk-averse the more often they evaluate an outcome. well documented An innovation venture that appears on the dashboard every week is buried in the noise of its first months, long before it can deliver a signal.

05Example: The same division dashboard, built twice

The following example shows a fictional business division with an identical situation, once in the usual build and once rebuilt along levers A to G. All figures are example values. Both dashboards show the same company, but they put different questions to its leadership.

Division report, October
updated daily · plan-actual view
Before
OPEX versus plan
104.2 %
over plan
Headcount versus plan
212of 205
7 over plan
Budget consumed year to date
81 %
below target
Savings versus prior year
1.8M €
target met
EBIT margin
9.3 %
target 11 %
Revenue versus plan
98.6 %
just below plan
Projects by traffic light
ProjectScheduleBudget
ERP migrationgreengreen
Service platform pilotredred
New pricing modelamberred
Supplier consolidationgreengreen
Division report, Q3
future quarterly · operations monthly
After
Stock of bets, expected revenue potential
D
6.5M € p.a.
range 2 to 11 M € · 14 live bets
Cost of delay of the three largest ventures
A
310k € per month
this is what each month of waiting costs
Portfolio of bets by maturity
E
Explore 8 Validate 4 Scale 2
Kill rate in the quarter: 5 of 19 bets ended by criterion (26 %) · median experiment cycle 3.5 weeks
Savings versus prior year
BG
1.8M €
of which 62 % reallocated into bets (reallocation rate)
Vitality index
D
18 %
revenue share of products younger than 4 years · target corridor 25 to 30 %
Result before future investments
CG
11.4 %margin
alongside future investments: 2.1 M € (margin after: 9.3 %)
OPEX in the corridor
F
90 %100 %110 %
104 %, corridor 97 to 103 %
Not started or stopped
D
Spare-parts subscription model1.2 M € p.a.rejected in Q2 over a budget cap · estimated potential, revisit Q4
Service platform pilotendedstopped after two cycles, hypothesis refuted: existing customers will not pay for self-service · cost of the insight 140 k €

What the before-dashboard trains

Four of six tiles can be improved by not doing something, a fifth pushes to spend leftover budget, and the only tile with a green signal rewards saving. The two red projects are precisely the two ventures that could create new revenue, and because the dashboard glows red daily, they are defended rather than evaluated in the next meeting. A line for what was never started is missing.

What the after-dashboard trains

The first line asks about the future and quantifies what waiting costs. The saving counts only through its reallocation, the margin appears once before and once after the future investments, and the cost variance shows up neutrally as a position in the corridor rather than a red light. The stopped pilot appears not as a failure but as a paid-for insight.

Both dashboards show the same fictional division with the same underlying data (savings 1.8 M €, margin 9.3 % after investments, OPEX 104 % of plan). The letters point to the levers in section 04.

06Goal and impact

The goal of the rebuild is a company whose employees learn from their metrics every day that calculated bets, quick decisions about whether to continue them, and the reallocation of savings into growth are the right behavior, without the discipline in the core business being lost.

The expected effects can be named and measured. Savings are sought as a source of funding rather than as an end in themselves, which shows up in the reallocation rate. hypothesis Ventures are started earlier and ended earlier, which shows up in shorter experiment cycles and a kill rate well above zero. hypothesis Planning becomes more realistic, because corridors offer less incentive for cautious setting than pinpoint plans, as the experience of beyond-budgeting companies suggests. case In the long run the vitality index rises, and it is the metric against which the whole rebuild must in the end be measured.

The risks can be named just as well. Innovation metrics are easier to game than cost metrics, because a figure like „number of ideas“ produces only idea theater without a counter-metric, which is why every future metric needs a kill rate or a documented stopping criterion beside it. A result before future investments invites relabeling operating costs, which can only be prevented by clear criteria for a bet and by their regular review. And the rebuild does not work as long as bonuses and promotions still hang on the old figures, because people read the payout more closely than any dashboard.

A company does not first have to learn to love risk for this; above all it has to stop reminding itself every morning first of what it might lose. Which picture it should see first each morning instead is one of the most consequential leadership decisions there is, and it is usually made by someone who believes they are only building a report.

Quick answers

Quick Answers: The Essentials

Why do most corporate metrics reward defensive behavior?

Almost every common metric, from the EBIT margin to a project team's velocity, is improved fastest by doing less, changing less and risking less. In a survey of 401 chief financial officers (Graham, Harvey, Rajgopal 2005), 55 percent said they would delay a value-creating project if it threatened the quarter's earnings forecast.

What is the signal layer of the action infrastructure?

The signal layer is the level of the action infrastructure, a term coined by Roman Rackwitz / Engaginglab, on which metrics tell employees every day which behavior was right. It shapes behavior more strongly than any mission statement or strategy, because people learn from numbers, not from declarations of intent.

What is the denominator problem in metrics?

Most steering figures are ratios such as margin or return on capital, and a ratio is improved most comfortably by shrinking the denominator, that is by investing less or discontinuing something. Clayton Christensen, Stephen Kaufman and Willy Shih described this in 2008 in „Innovation Killers“ as the reason financial tools destroy the capacity to do new things.

What is the omission bias and what does it have to do with dashboards?

The omission bias is the tendency described by Ritov and Baron in 1990 to weigh harm through action more heavily than harm through inaction. A metrics system amplifies it, because the failed project shows up red in the table while the project that was never started has no line on any dashboard.

What is cost of delay?

Cost of delay is an estimate of what one month of delay costs a project, originally from product development (Smith and Reinertsen 1991). Made visible on the dashboard, it moves waiting from the safe side to the expensive side and turns the same loss aversion that used to block projects toward speed.

What is a vitality index?

The vitality index is the revenue share of products younger than a few years, made famous by 3M with a target of around 30 percent. After the introduction of Six Sigma under James McNerney, that share fell at 3M to around 21 percent by 2005.

What is beyond budgeting?

Beyond budgeting is a steering model with rolling forecasts and relative targets instead of a rigid annual budget, for which Svenska Handelsbanken has served as the model since the 1970s. It no longer punishes deviation from the plan and thereby removes the incentive to plan cautiously and burn leftover budgets.

How do you build a dashboard that does not punish innovation?

You make waiting visible as cost of delay, count savings only once they are redeployed into growth, report a result before future investments, and show the stock of live bets and stopped ventures as their own lines. The precondition is that display, payout and promotion all point the same way, a mechanism Steven Kerr described in 1975 as „On the Folly of Rewarding A, While Hoping for B“.

Your dashboard trains your company every day

Engaginglab helps organizations rebuild the signal layer of their action infrastructure so that metrics reward calculated risk and the reallocation of savings into growth, without losing the discipline in the core business.

Schedule a call
Frequently asked questions
Almost every common metric, from the EBIT margin to a project team's velocity, is improved fastest by doing less, changing less and risking less. In a survey of 401 chief financial officers (Graham, Harvey, Rajgopal 2005), 55 percent said they would delay a value-creating project if it threatened the quarter's earnings forecast.
The signal layer is the level of the action infrastructure, a term coined by Roman Rackwitz / Engaginglab, on which metrics tell employees every day which behavior was right. It shapes behavior more strongly than any mission statement or strategy, because people learn from numbers, not from declarations of intent.
Cost of delay is an estimate of what one month of delay costs a project, originally from product development (Smith and Reinertsen 1991). Made visible on the dashboard, it moves waiting from the safe side to the expensive side and turns the same loss aversion that used to block projects toward speed.
You make waiting visible as cost of delay, count savings only once they are redeployed into growth, report a result before future investments, and show the stock of live bets and stopped ventures as their own lines. The precondition is that display, payout and promotion all point the same way, a mechanism Steven Kerr described in 1975 as „On the Folly of Rewarding A, While Hoping for B“.

Sources

  1. Graham, J. R., Harvey, C. R., Rajgopal, S. (2005): The economic implications of corporate financial reporting. Journal of Accounting and Economics 40, pp. 3 to 73. NBER Working Paper 10550
  2. Kerr, S. (1975): On the Folly of Rewarding A, While Hoping for B. Academy of Management Journal 18(4).
  3. Christensen, C. M., Kaufman, S. P., Shih, W. C. (2008): Innovation Killers. How Financial Tools Destroy Your Capacity to Do New Things. Harvard Business Review, January 2008.
  4. Hart-Smith, L. J. (2001): Out-Sourced Profits. The Cornerstone of Successful Subcontracting. Boeing, internal paper; context and Albaugh quote: Calleam, Why Do Projects Fail?
  5. Ritov, I., Baron, J. (1990): Reluctance to vaccinate: Omission bias and ambiguity. Journal of Behavioral Decision Making 3(4).
  6. Jensen, M. C. (2001): Corporate Budgeting Is Broken, Let's Fix It. Harvard Business Review, November 2001.
  7. Hindo, B. (2007): At 3M, A Struggle Between Efficiency And Creativity. BusinessWeek, 11 June 2007.
  8. Benartzi, S., Thaler, R. H. (1995): Myopic Loss Aversion and the Equity Premium Puzzle. Quarterly Journal of Economics 110(1).
  9. Manso, G. (2011): Motivating Innovation. Journal of Finance 66(5).
  10. Azoulay, P., Graff Zivin, J. S., Manso, G. (2011): Incentives and creativity: evidence from the academic life sciences. RAND Journal of Economics 42(3).
  11. Grove, A. S. (1983): High Output Management. Random House.
  12. Ries, E. (2011): The Lean Startup. Crown Business.
  13. Hope, J., Fraser, R. (2003): Beyond Budgeting. Harvard Business School Press (on Svenska Handelsbanken).
  14. Smith, P. G., Reinertsen, D. G. (1991): Developing Products in Half the Time. Van Nostrand Reinhold (on cost of delay).
Diesen Artikel auf Deutsch lesen Auf Deutsch lesen →
All articles