Track 3 — R&D Capital Management

Module 3.3: Board Reporting & Executive Communication

The 4-quadrant board slide, tiered KPI dashboards, and investment proposal frameworks. Speak the language that gets engineering funded.

3 Lessons~55 minAdvanced / Executive
1

Lesson 1: The Board Deck Engineering Slide

Most CTOs present engineering to the board as a list of shipped features. Boards want to see engineering as an investment — returns, risks, and trajectory. One slide changes everything.

The 4-Quadrant Slide

Top-left: Engineering ROI (APER, revenue trend). Top-right: Delivery Performance (DORA metrics with benchmarks). Bottom-left: Risk Exposure (PDI, TID). Bottom-right: Investment Allocation (build vs maintain vs debt).

One slide. Four quadrants. Dollar amounts. Trend arrows. Benchmark comparison.
The Narrative Arc

Frame the story: "Last quarter we invested $X. It generated $Y in returns. Our risk exposure is $Z. Next quarter we propose investing $A to generate $B."

Every board presentation should follow: invested → returned → risk → proposal
Anti-Patterns

Never: list shipped features (shows effort, not value). Never: report story points (meaningless to finance). Never: show Gantt charts (shows activity, not outcomes).

Board members want: dollars in, dollars out, risk level, trajectory
📝 Exercise

Create a single board slide for your engineering org using the 4-quadrant framework. Include APER, at least 2 DORA metrics, PDI score, and investment allocation split.

2

Lesson 2: Engineering KPI Dashboards

Continuous executive visibility into engineering health prevents surprises and builds trust. The right KPI dashboard shows trends, not snapshots, with automatic alerting.

Tier 1: Executive KPIs

APER (revenue per engineer), Innovation Tax (% time on new features), and Deployment Frequency. Updated monthly. Visible to CEO and board.

3 KPIs maximum at the executive tier. More = noise.
Tier 2: VP-Level KPIs

All four DORA metrics, team-level velocity, sprint completion rates, incident counts & MTTR. Updated weekly. Visible to VP Engineering and CTO.

8-12 KPIs at VP level. Drill-down from executive tier.
Tier 3: Team-Level KPIs

Code review time, PR merge rate, test coverage, build time, individual team velocity. Updated daily. Visible to engineering managers.

Teams own their metrics. Manager aggregates for VP reporting.
📝 Exercise

Design a 3-tier KPI dashboard hierarchy for your org. For each tier: list the KPIs, update frequency, audience, and alerting thresholds.

3

Lesson 3: Investment Proposal Framework

When engineering needs budget — for debt remediation, platform investment, or new capabilities — it must speak the language of investment proposals: cost, return, timeline, risk.

The Business Case Template

Problem statement (in dollar terms) → Proposed solution → Investment required → Expected return → Timeline → Risk factors → Alternative approaches. This is how finance evaluates every investment.

Every proposal: 1 page executive summary + supporting detail
ROI Calculation

NPV (Net Present Value) of the investment. Include: freed engineering capacity × burdened rate, reduced incident costs, faster time-to-market revenue, avoided risks.

Target: 3-5x ROI for tech debt remediation. 5-10x for new capabilities.
Risk-Adjusted Returns

Not all returns are certain. A platform migration has 30% risk of 2x cost overrun. Present scenarios: best case, expected case, worst case.

Always include: probability-weighted expected value for each scenario
📝 Exercise

Write an investment proposal for a real engineering initiative using the template: problem ($), solution, investment, ROI, timeline, risks. Get feedback from your CFO.