Searching for a Loose Fitness Function
Why putting a financial officer in command is a structural problem, not a personnel problem — and what to watch for
The Fitness Function Trap
Why putting a financial officer in command is a structural problem, not a personnel problem — and what to watch for
I want to be honest with you about something uncomfortable.
If you're reading this in the early morning and you've been tracking the mood in your building — the way certain conversations get quieter, the way the roadmap reviews have shifted from "what are we building next" to "what can we cut" — then you already know what I'm about to say. Your instincts are correct. You're not being paranoid.
What you may not have is the vocabulary to explain why it works the way it does.
I got that vocabulary from a single sentence.
A Sentence That Changes How You See It
A few weeks ago I was fortunate enough to watch to a video with Stephen Wolfram, the physicist and mathematician whose work sits at the intersection of computation and natural law. Almost in passing he made an observation that I haven't been able to stop thinking about.
He said: the reason evolution works is that it operates on an extraordinarily loose fitness function.
The rules of natural selection, stripped to their core, are this: stay alive long enough to reproduce, and repeat. That's it. There is no specification for how you accomplish that. Whether you're a patch of moss on a rock face or a basking shark working a thermal in the Atlantic, the same loose set of rules applies. And within that looseness, nature has produced millions of distinct solutions — ecological niches, body plans, survival strategies — that no central planner could have anticipated or designed.
The looseness is not a bug. The looseness is the entire point.
Now flip it. What happens when you tighten the fitness function?
What Tightening Looks Like in a Company
When a company installs a financial officer in the command position, something very specific happens to the measurement system. Every unit of expenditure gets attached — or is required to attach — to a known unit of incremental revenue. Programs that cannot demonstrate a direct line from cost to return get cut. Variance gets driven out. Predictability becomes the primary virtue.
This is not incompetence. It is a measurement system doing exactly what it was designed to do.
The problem is what it selects against.
Noting that Tim Cook is stepping down, let’s look at his efforts over his leadership term in comparison to Steve Jobs last leadership term.
Apple launched revolutionary products under Steve Jobs that created new markets, while Tim Cook's era focused on ecosystem expansion and services for sustained revenue.
Jobs Era Products (Late Launches)
Jobs oversaw category-defining hardware from 2005-2011, driven by bold innovation to redefine user experiences.
iPod nano (2005): Created portable video/music players; innovation-driven (new form factor).
iPhone (2007): Invented the modern smartphone; innovation-driven (touch interface, app ecosystem).
MacBook Air (2008): Pioneered ultrathin laptops; innovation-driven (design revolution).
iPad (2010): Launched tablet computing mainstream; innovation-driven (new computing category).
iPad 2/iPhone 4S (2011): Refined tablets/phones; innovation-driven (performance leaps).
Cook Era Products (Key Launches)
Cook's recent products since 2011 emphasize wearables, services, and integration, often business-driven for ecosystem lock-in and recurring revenue.
Apple Watch (2015): Wearable health tracker; new category but business-driven (services tie-in).
AirPods (2016): Wireless earbuds standard; business-driven (ecosystem expansion).
Apple Silicon M1 (2020): Custom chips for Macs; innovation-driven (performance shift).
AirTag (2021): Item tracker; business-driven (Find My network growth).
Vision Pro (2024): Spatial computing headset; innovation-driven (new VR/AR paradigm).
Key Differences
Jobs' launches were riskier, innovative, creating standalone categories from a technical vision. Cook's build on the iPhone ecosystem for expanding profitability.
Innovation, by definition, cannot demonstrate a direct line from cost to return before the work is done. The entire value of early-stage research is that it explores territory whose yield is unknown. You are not buying a result. You are buying the possibility of a result — and the landscape of possible results is exactly what gets eliminated when you tighten the fitness function.
With less focus on innovation, you get a company that is very, very good at producing derivative and incremental advancements.
The Accountability Gap Nobody Books
Here is the part that makes this a structural problem rather than a personnel problem.
A financial executive who cuts an innovation program can claim credit on the P&L immediately. The cost savings are legible, auditable, and attributable. The destroyed optionality — the future products that will never be developed, the capability that will atrophy, the engineers who will leave — those costs never appear in any financial statement. There is no line item for "strategic opportunity destroyed." There is no reserve requirement for innovation the way there is for legal liability.
This is an asymmetric accountability structure. You are rewarded for variance reduction and never penalized for eliminating the explore budget.
A famous era of industrial cost discipline proved this at scale. The methodology was sound in manufacturing — tolerance matters, and variation is the enemy on a shop floor. But when the same logic was applied to the innovation pipeline, it produced the same result it always produces when you tighten the fitness function on a complex adaptive system: you eliminate the territory where the next generation of products was supposed
to come from.
The engineers in those companies knew it before management did. They always do.
The Pipeline You Can't See Until It's Empty
Innovation is not a faucet. It is a pipeline. Between the decision to fund early-stage work and the product that reaches a customer, there is a lag — typically measured in years, never in quarters. Which means when you cut the front end of the pipeline, nothing changes at the product end for a long time.
The cuts happen in Q1. The P&L looks better in Q2. By Q4 leadership is taking credit for margin improvement. Three years later, the product pipeline runs dry, the competitors who kept investing are two generations ahead, and the cuts that produced the margin improvement are three organizational structures in the past.
By then, the damage is done and the person who made the decision is long gone or entrenched.
A mature company that understands this builds something equivalent to a governance and reserve function for innovation — a protected, multi-year commitment treated as an obligation, not a discretionary line item. The same way a legal reserve fund exists because nobody asks the CFO to gut it to hit this quarter's number, the innovation budget requires its own protected structure to survive the pressure.
Most companies don't build that structure. They discover they needed it when the pipeline is already empty.
What to Watch For — In Both Directions
If you're in a building where the signals are going the wrong way, here is what I would tell you directly: update your resume now. Not after the announcement. Not after the first round of cuts. Now.
When a financial executive moves into command authority, the first 90 days are almost always a cost rationalization exercise. That is what they know how to do. Being low in the organization does not protect you — it makes you a legible line item. Moving early costs you nothing. Waiting costs you leverage, time, and potentially your severance position.
But here is what you also need to know: not every company in trouble is finished. Some of them figure it out. And when they do, the signals are observable.
• Watch what gets protected when the cuts come. If R&D gets a named carve-out — even a modest one — someone at the top understands the pipeline has a lag. That is the signal.
• Watch who gets promoted. One promotion cycle tells you what the organization is optimizing for. Are the people moving up builders, or are they operators and financial controllers? The org chart is always honest.
• Watch the weird projects. Any advanced concepts group, any small team working on something that won't ship for three years — if that survives the restructuring, somebody is thinking in pipeline terms. If it gets zeroed, the pipeline is being consumed, not refilled.
• Listen to the language. "We're going to out-engineer this problem" and "we're going to optimize our way out of this" are not the same sentence. Engineers hear the difference before anyone else does.
• Look for a funded long-horizon roadmap. Not a vision statement. Not a town hall slide with aspirational language. A named, funded, multi-year technology program with actual resources attached. That is the innovation reserve obligation. That is the company saying: this is not discretionary.
The One Thing That Matters
The story everyone tells about a famous company's comeback gets told as a story about one person. That is the wrong lesson.
The right lesson is that a board made a categorical decision: we are going to put a builder back in command. The specific identity of that builder mattered, yes. But the generalizable truth is the category of the decision, not the name.
Tim Cook's successor is John Ternus, currently Apple's Senior Vice President of Hardware Engineering. He is set to become CEO on September 1, 2026, while Tim Cook transitions to Executive Chairman.
Ternus is called a "brilliant engineer," he is described by Tim Cook as having the "mind of an engineer" and the "soul of an innovator" .
Ternus represents a shift back to product and engineering DNA. His main task will be navigating Apple through the AI era and global supply chain complexities while preserving its design culture .
A company that is serious about coming back from a cost-discipline spiral makes a specific kind of move. It puts someone in command whose hands have built things. It protects the front end of the pipeline even when the pressure is highest. It treats innovation as a core competency, not a gift.
If you see those signals, you have reason to stay.
If you don't, you already have your answer.
Herbert Roberts, P.E., is a licensed Professional Engineer with 32 years in aviation R&D and 62 U.S. patents. He writes about engineering, invention, and the systems that make or break both at Inventor's Mind on Substack.