- May 20
Two questions every R&D leader should be able to answer
- Niklas Sundgren
- Field Notes
I have run this exercise with senior R&D leaders many times. Two questions, simple to state, hard to answer.
What capabilities will we need in three years.
What capabilities do we have now.
Most leaders cannot answer either at a granularity that supports decisions. The forward question is hard because the technology roadmap is unclear, ambiguous, or unintegrated with capability planning. The backward question is hard because the HR system cannot describe what the organization actually has, only what was written into job descriptions and broad skill categories that do not map to R&D-specific work.
Both inputs to a capability gap analysis are absent. Decisions get made anyway. Hiring decisions, development investments, project staffing, partnership choices, build-versus-buy calls. They get made on guesses written up as plans, and the cost compounds quietly across cycles.
Bain's 2023 research on engineering and R&D talent gaps documents the structural picture: capability planning is among the lowest-maturity practices in technical functions across industry. Most organizations operate with static capability assumptions while their strategy moves around them.
The deeper issue is structural. R&D capability is not job descriptions. It is not generic competency frameworks from HR. It is the combination of technical depth in specific domains, integration knowledge across domains, judgment built from years of project experience, and tacit knowledge that does not appear in any system. Most organizations track none of this in a way that supports forward planning.
What this looks like in practice:
The strategic plan calls for entering an adjacent market. Nobody can say with confidence whether the engineering function has the capability to deliver, or what it would take to acquire what is missing.
A senior engineer leaves. The function discovers six months later that they were the only person who could integrate two specific subsystems, and that integration is on the critical path for next year's flagship program.
A development program slips. The retrospective concludes that the team was missing a specific technical capability nobody flagged at staffing time.
These are not bad luck. They are the visible symptoms of operating without a capability picture.
The fix is not a heavier HR system. It is an R&D-specific capability map at useful granularity, integrated with the technology roadmap, integrated with project staffing decisions, and refreshed with light governance. Phaal and Farrukh's technology roadmapping research at Cambridge has been documenting this integration for two decades. Most organizations skip it.
What changes when you build the picture:
Strategic conversations get specific. "Can we do this" stops being a feeling and becomes a defensible claim or named gap.
Hiring decisions get prioritized by what the roadmap actually needs, not by what worked last year.
Project staffing surprises drop because the capability inventory is visible at commit time, not at delivery time.
Investment in development gets directed at the capabilities the next three years require, not the ones that felt important when budgets were set.
If your function cannot answer the two questions at a granularity you trust, your medium-term capability is being shaped by attrition, hiring market conditions, and stakeholder pressure rather than by your strategy. That is not a leadership choice you have made. It is a leadership choice you have been allowing to happen by default.
If this is the gap you have been carrying alone, let's talk.