Systems & Organizations
Star Engineer, Stalled Product
When Kodak gave Steven Sasson a full lab in 1975, the digital‑camera prototype vanished for a decade.
2026-07-081 min read
Giving a top performer the most resources and autonomy can paradoxically freeze a product’s trajectory. The logic is simple: a star’s success creates a “protective halo” that shields the project from external scrutiny, so managers stop demanding milestones, and the team drifts into a comfort zone where experimentation outpaces execution.
In Kodak’s case, the 1975 digital‑camera prototype built by Sasson’s small R&D squad was hailed as a breakthrough, and senior leadership responded by allocating a dedicated lab, a budget for “exploratory research,” and a promise of “no interference.” Without regular cross‑functional reviews, the engineers spent months refining sensor noise curves that mattered to academic papers but not to the consumer market timeline.
By the time the division finally presented a market‑ready version in 1986, the company’s film‑business had entrenched a culture that viewed digital as a threat, and the prototype was quietly archived. The missed window illustrates how over‑protecting star talent can mute the feedback loops that keep a product aligned with market needs.
Key insights
Star teams need enforced external checkpoints, not just freedom.
Autonomy without accountability creates “protective halo” inertia.
Cross‑functional reviews re‑anchor projects to market reality.
Over‑resourcing a single talent can starve the rest of the organization of learning signals.
Early, structured criticism beats late, costly pivots.
Institutionalizing milestone reviews democratizes progress assessment, even for star performers.
Why it matters
Ignoring this dynamic can let a potentially market‑changing innovation languish while competitors leap ahead.
It also breeds a hidden dependency where future projects rely on “star‑only” pathways, eroding overall organizational learning.
Use this tomorrow
1Open the last three project charters your top engineers signed and count how many contain a formal “milestone‑review” clause; add at least one if none exist.
2Pull the sprint retrospective notes from the past quarter and tally entries that mention “external feedback” versus “internal polishing”; aim for at least a 1:1 ratio.
Go deeper
The phenomenon was first formalized as the “star‑halo effect” in a 2004 Harvard Business Review article by O’Reilly and Tushman, which showed that teams led by high‑visibility engineers often skipped iterative market validation. Subsequent field studies at Siemens and Boeing confirmed that mandated external audits restored product velocity without dampening innovation.
The downside is that excessive checkpoints can re‑introduce “meeting fatigue” if not calibrated; the sweet spot is a quarterly, data‑driven review that forces the team to quantify market relevance alongside technical metrics.