A senior executive from a technology company was frustrated. Prior to expressing his frustration he was describing the design engineers and how well they were working with the sales engineers. To win contracts in their exacting industry, the teams collaborated for 18-24 months to win design approval from a client. This approval was a signature on a document, a promise to produce the designed component for inclusion in a larger product scheduled for future production. The dollars involved were substantial and all participants were professional and passionate about their business.
The Frustration
The frustration he expressed concerned the CFO, who was asking for a way to make this lengthy, expensive, and critically important interaction accountable. Apparently unwilling to wait for up to 3 years for something to count (it took at least that amount of time for an approved design to be incorporated into the final product and for that product to begin production, start shipping and generate sales), he demanded daily and weekly numbers to ensure these teams of valuable employees were working and being effective.
The Real Frustration
The trouble was that even with sales-engineering teams working diligently and responding well to clients' design requests there was virtually nothing to record on a spreadsheet, except expenses, and those mounted quickly as projects progressed. The CFO wanted numbers to represent movement, to provide accountability to this extended design-build sequence.
To make him happy the teams created numbers. The trouble was that they had little relationship to the vitality or potential of the design projects. The teams were disappointed to realize that the CFO didn't understand their business - he only understood numbers. "He thinks we're a production floor," was the comment.
Interaction is Hard to Measure
He wanted to provide objective (from his perspective) proof to the senior management team that these projects were progressing. It didn't work. The numbers offered represented a distortion of the complex design environment. Rather than make the design area more productive, it became more resentful. Bringing ideas into reality always means those involved actively trade off competing priorities to produce an optimum solution from a number of perspectives. As a result, selecting a metric with a bearing on only one aspect of a complex, knowledge-based environment may not be realistic or helpful.
A New Tool is Needed
The CFO mentioned and those overseeing innovation efforts should understand development is comprised mostly of observable interactions between talented people and very few numerically measurable activities. We call this knowledge work, since the work appears as a stream of activity which eventually results in a benefit or outcome but doesn't produce spreadsheet-style transactions while work progresses.
We shouldn't be quick to judge the CFO - bringing accountability to a business is their responsibility. The tool was the problem. The CFO requires the ability to align and drive the knowledge work interactions between employees and groups of employees. We understand this requirement as it is our area of expertise.
In North America, we must move quickly to bring accountability to crucial innovation activities, but not with previous generation, manufacturing-style methods. Innovation is the art of describing the context required to produce outstanding outcomes and using new accountability tools to ensure this positive context continues.