R&D Spend by Strategic Theme

Goal of the analysis:

Quantify how R&D dollars and capacity are allocated across the company’s strategic themes (e.g., growth pillars, customer problems, platforms/technology domains), assess alignment with strategy, and identify over- or under-funded areas. For executives, this reveals whether investment is concentrated on the few bets that matter, whether sustaining/technical debt is crowding out growth, and how shifts in spend map to outcomes (launches, ARR growth, TAM capture). A robust view distinguishes Opex vs capitalized development, direct vs shared costs, and growth vs sustaining work within each theme, and sets the foundation for fact-based portfolio rebalancing.

Data required:

• Strategy and theme taxonomy:
  • List of strategic themes/growth pillars and definitions (e.g., AI platform, edge/5G, sustainability solutions, SMB segment, geographic expansion).
  • Theme ownership, target outcomes (revenue, margins, TAM), time horizons, and prioritization.
• Project and product portfolio mapping:
  • Project IDs, names, BU/product line, platform; stage (discover/define/develop/validate/launch) or TRL.
  • Theme tags (primary/secondary) and percentage allocations where projects span multiple themes.
  • Type: research, platform, new product/feature, sustaining/technical debt, regulatory/compliance.
• Financials and capacity:
  • GL/ERP: R&D expense by account/cost center (labor, contractors, materials, labs, software/tools), capitalized development additions, amortization, impairments.
  • FTEs and contractors by month, role, and location; time-tracking or allocation data by project/theme.
  • Grants/credits, partner reimbursements, co-development contributions.
• Outcome and pipeline context (overlays):
  • Launches by theme, pipeline milestones, bookings/ARR or revenue by theme-linked products, customer adoption metrics, business cases (NPV/IRR) where available.
• Systems and references:
  • PPM/ALM/PLM (Jira/ADO/Planview/Teamcenter), ERP/GL, FP&A, HRIS/time-tracking, MDM for product hierarchies.
  • Accounting policy for capitalization (IAS 38/ASC 350-40/730), theme tagging standards.

Detailed step-by-step instruction on how to conduct the analysis:

1. Define and lock the theme taxonomy.
   • Confirm 5–10 strategic themes with crisp inclusion criteria (customer segments, technology platforms, use cases).
   • Agree on rules for multi-theme work (e.g., primary theme plus percentage split across secondaries capped at 100%).
   • Publish a tagging guide and governance (who approves theme tags and changes).
2. Tag the portfolio.
   • Assign each project a primary theme; add secondary tags with percent allocations where justified.
   • Classify work-type within each project: Growth (new product/platform/research) vs Sustaining (maintenance/technical debt) vs Regulatory.
   • Backfill tags for legacy projects; require tags at gate approvals for new projects.
3. Assemble spend and capacity.
   • Pull GL/ERP R&D expense, capitalized additions, and amortization by month; map cost centers to projects and themes.
   • Extract FTEs/contractors and time-tracking; where timesheets are unavailable, allocate shared costs using drivers (e.g., project labor $, FTEs, hours).
   • Separate one-offs (impairments, acquisition-related IPR&D) for transparency.
4. Allocate shared and cross-cutting costs.
   • Define allocation drivers for shared services (test labs, tools, platform teams) to themes (e.g., proportional to project labor within each theme).
   • Apply split allocations for multi-theme projects per agreed percentages; prevent double-counting by enforcing 100% totals.
5. Compute core KPIs.
   • Total R&D Spend by theme (TTM and quarterly), and % of total.
   • Growth vs Sustaining vs Regulatory spend mix within each theme.
   • FTE share by theme; skill/bottleneck allocation (e.g., firmware/data science) by theme.
   • Capitalization intensity by theme = Capitalized additions ÷ (R&D expense + capitalized additions).
   • Unit intensity: R&D per $100M revenue served by the theme or per $ forecasted TAM captured (if mapped).
   • External leverage: % of theme spend from partners/grants; co-development share.
6. Trend and variance analysis.
   • Quarterly trend of spend share per theme; show 8–12 quarters (actuals) with next 4 quarters (plan).
   • Variance bridge vs prior year/plan for each theme: Volume (absolute spend), Mix (growth vs sustaining), Capitalization, FX, Grants/credits, Reclassifications, One-offs.
7. Outcome overlays (where available).
   • Launch/milestone attainment by theme; revenue/ARR contribution and pipeline coverage; cost-to-next-milestone and expected payback.
   • Theme score: composite of progress (milestones), early market traction, and risk.
8. Scenario modeling.
   • Model rebalancing (e.g., shift 10% from Sustaining in Theme A to Growth in Theme B) and show impact on H1/H2 delivery, milestones, and resource constraints.
   • Simulate ring-fencing guardrails (e.g., minimum 20% to AI platform) and trade-offs.
9. Quality checks and reconciliation.
   • Reconcile theme totals to GL/FP&A (no leakage/overlap); validate allocation drivers; sample-tag audits against project charters.
   • Confirm capitalization eligibility consistency; highlight themes where optics (capitalization) materially shift P&L appearance.
10. Set targets and governance cadence.
    • Agree target spend shares per theme (and growth vs sustaining mix) with a 12–24 month horizon.
    • Review monthly in operational forums and quarterly at the Portfolio Council; adjust starts/kills and hiring plans accordingly.

Format of the output of analysis:

• Executive summary: theme spend shares, growth vs sustaining mix by theme, FTE share, capitalization intensity, and variance vs plan/prior year.
• Treemap or stacked bar showing R&D spend by theme; small multiples for TTM trend.
• Heatmap by BU/product × theme with traffic-light markers vs target ranges.
• Variance bridges for top themes (prior period → current) with driver labels.
• Theme scorecards: spend, FTEs, milestones attained, next milestones/cost-to-go, revenue/ARR contribution (if applicable).
• Scenario sheet: current vs proposed rebalance with quantified capacity and milestone impact.
• Appendix: taxonomy, allocation rules, capitalization policy, reconciliation to GL, data quality notes.

How to interpret results:

• Concentration: 2–3 themes consuming the majority of growth R&D is healthy if aligned to strategy; over-fragmentation (many small themes) can dilute impact.
• Underfunded strategic themes with large TAM but low spend share suggest capacity or capability constraints; check bottleneck skills and pipeline readiness.
• High Sustaining within a theme indicates technical debt; invest in platformization/automation or revisit roadmap scope.
• Rising capitalization intensity in a theme may lower P&L optics but increases future amortization; ensure eligibility and avoid masking spend shifts.
• Spend without outcomes: persistent high spend in a theme with weak milestone/revenue progress signals a need to tighten gates or pivot scope.
• Rapid share shifts can reflect reclassifications; confirm real resource moves vs labeling changes.

Steps a company can take to improve on this measure:

• Strategy and guardrails:
  • Set target spend bands per theme (e.g., Core Platform 25–35%, AI Solutions 15–25%, Sustainability 10–15%); ring-fence minimums for priority themes.
  • Cap Sustaining/technical debt at ≤35–40% within each theme; fund platform fixes to reduce run-the-business drag.
• Portfolio governance:
  • Enforce stage-gates and kill criteria tied to defined learning milestones; rebalance quarterly based on progress and market signals.
  • Limit concurrent starts; apply WIP limits by theme to protect focus and cycle time.
• Resource and capability shifts:
  • Reallocate scarce skills to underfunded priority themes; create centralized platform teams that serve multiple themes with clear cost allocation.
  • Use partnerships or acquisitions to accelerate capability in emerging themes (e.g., AI/ML, cybersecurity).
• Operating model and tooling:
  • Standardize theme tagging in PPM; require tags for funding approval; automate GL–project–theme rollups.
  • Implement dashboards with near real-time spend/FTE by theme; alert on deviations from target bands.
• Economic discipline:
  • Tie theme funding to NPV/IRR where feasible; use option-based tranche funding for high-uncertainty themes.
  • Track cost-to-next-milestone and expected payback; pause or pivot low-yield themes.
• Scenario guidance:
  • If a priority theme is underfunded: freeze low-ROI sustaining features, shift 5–10% FTEs, and add external partners; set a 2-quarter milestone plan.
  • If spend is diffuse: consolidate adjacent themes, kill subscale efforts, and concentrate on 3–5 pillars.
  • If a theme shows high spend but slow outcomes: tighten gates, reduce scope to MVPs, and reassess product–market fit.

Benchmark comparisons:

General benchmarks:

• Theme concentration:
  • Focused portfolios typically allocate 60–80% of growth R&D to 3–5 themes; top theme often 20–35%.
• Sustaining within themes:
  • Target ≤35–40% of total R&D (declining over time with platformization and automation).
• Capitalization intensity:
  • Software-heavy themes: 10–40%; hardware-centric: lower; use internal targets to ensure policy consistency.

Segment- or industry-specific benchmarks:

• Software/SaaS: significant platform/AI themes (often 20–40% combined of growth R&D); customer segment themes (SMB/Enterprise) common; sustaining can be driven down with DevOps and automation.
• Industrial/manufacturing: platform and electrification/digital themes feature prominently; 2–3 core themes often consume ≥60% of growth spend.
• Medtech/devices: regulatory and clinical platforms (e.g., digital surgery, diagnostics) as themes; sustaining share higher during compliance waves but should normalize.
• Consumer electronics/CPG: category/experience themes tied to seasonal launches; marketing-tech alignment critical for outcomes.

External benchmarks vary due to strategy and accounting policy differences. Construct internal benchmarks by setting a 12–24 month baseline of spend/FTE mix across themes, adopting target bands for each theme based on strategy, and tracking quarterly progress with outcome overlays (milestones, revenue/ARR). Use internal top-quartile performers (by theme) as reference points and refresh targets annually or after major strategy shifts.