The Pharma CIO Quarterly Innovation Review Template

Why the Quarterly Innovation Review Matters in Pharma

Pharma has always run on stage-by-stage approvals. The scientific pipeline runs on structured, evidence-driven decisions at defined transition points, and every senior leader in the room understands the discipline of killing programs that no longer earn their place in the portfolio. Yet when it comes to the digital and technology innovation portfolio, the same rigor rarely applies. Pilots accumulate. Vendors stack up. Nobody wants to be the one who kills the AI project that a functional leader personally sponsors, even when the metrics do not support it.

The Quarterly Innovation Review exists to bring the same stage-by-stage approval discipline to the technology portfolio. It is not the day-to-day operating cadence of the CIO’s team. It is the quarterly moment when the executive committee, or in some organizations the board technology committee, sees the whole portfolio at once and is asked to make or ratify decisions that individual functional leaders cannot make alone.

The gap between the ambition captured in the third statistic and the failure rate captured in the first is where the QIR earns its place on the calendar. It is the mechanism that converts enthusiasm into a portfolio that can survive contact with reality. Biogen’s CIO Guy Hadari has been public about the same point in his interviews with PharmaVoice: he explicitly refuses to opt into “dozens of Blue Sky pilots” and instead ties each investment to a specific business outcome, replacing bespoke systems with integrated platforms first, then layering AI on top of a stable foundation.⁴

That posture, disciplined selection over pilot proliferation, is exactly what a well-run QIR reinforces. HFS Research has argued that the reinvented pharma CIO agenda must “create an enterprise innovation framework that identifies and addresses specific market differentiators over multiple time horizons” and must own the innovation budget with a whole-of-company view.⁵ The QIR is the artifact where that ownership becomes visible to the rest of the executive team.

The Full QIR Document Template

What follows is the QIR document as it would appear in a CIO’s binder or executive committee pre-read. It is designed to be roughly 20 to 25 pages when fully populated. The presentation deck, covered in the next section, is a compressed narrative version of the document. The document itself is the record of decisions and the artifact you re-read next quarter to see whether the commitments held.

Section 1: Portfolio Velocity Dashboard

The dashboard is a one-page numerical snapshot of movement through the portfolio, quarter over quarter. It is not a list of projects. It is a set of counts and rates that make the portfolio’s health legible at a glance.

The velocity dashboard is deliberately opinionated about kill rate. A healthy innovation portfolio has a kill rate, and tracking it over time tells you more about portfolio governance than any project success metric.⁷ A quarter with zero kills is either a sign the portfolio is unusually strong or, more commonly, a sign that the team is avoiding difficult conversations. The QIR is where the executive committee makes it psychologically safe to kill work.

Section 2: In-flight Pilots with Kill Criteria

Each active pilot gets a single page. The template forces the sponsor to state the kill criteria in advance, then updates the status against those criteria every quarter. If a pilot does not have written kill criteria, it is not a pilot; it is a project waiting to become permanent overhead.

Section 3: Graduation Candidates (Pilot to Scale)

Graduation is where the executive committee earns its money. Moving a pilot to scale means committing operating budget, headcount, change-management effort, and often validation resource. Each graduation candidate gets a two-page dossier.

• Pilot recap. Original hypothesis, kill criteria, and the evidence produced. Include the honest read on where the pilot fell short of its most optimistic claims. Executives learn to distrust CIOs whose pilots always exceed expectations.
• Scale-up business case. Investment required, expected annual benefit, payback period, and the confidence interval around each number. A range is more credible than a point estimate.
• Operating model post-graduation. Where the capability lives permanently, who owns it, and what the funding model looks like once it is out of innovation budget.
• Regulatory and quality readiness. Validation strategy, data integrity considerations, and any FDA, EMA, MHRA, or Annex 22 implications. This section is the one most often skipped in tech-company templates and the one most needed in pharma.
• Change-management and adoption plan. Explicit named champions inside the business function, training approach, and adoption metrics with baselines.
• Sunset trigger for scaled program. Even a graduated program should carry a written trigger for future reconsideration, so that scaled programs do not become immortal.

Section 4: Sunset Candidates

Sunset candidates fall into two buckets: pilots that should be killed and existing scaled programs that have outlived their utility. Both belong in the QIR because both compete for the same finite talent and change-management capacity. McKinsey’s 2025 analysis of biopharma operating-model simplification identified more than seven billion dollars in cost savings sitting inside simplification and rationalization opportunities across the industry.⁸ A share of that lives in the technology portfolio.

Each sunset candidate carries a short template: what it was originally intended to do, why it is being sunset, what capability (if any) replaces it, what data or user population must migrate, and the expected timing and cost of the sunset itself. This forces the acknowledgment that killing systems is not free and creates a small stream of transition work that the CIO must plan for.

Section 5: External Environment Scan

Every quarter, the CIO briefs the executive committee on what changed in the external environment that affects the portfolio. This is a two- to three-page section, not a bibliography.

• Regulatory movements. EMA’s Annex 22 evolution, FDA AI guidance updates, MHRA GCP AI guidance, ICH consultations, any Warning Letters or 483s that reference technology systems. This is a place where regulatory intelligence and IT strategy visibly meet.
• Peer and competitor moves. Named deals and announcements from top-20 pharma peers that reset the competitive floor. Roche’s decision to scale NVIDIA-based accelerated computing to more than 3,500 GPUs, moving AI “from isolated pilots to an enterprise-wide capability,” is exactly the kind of external anchor that belongs in this section.⁹
• Vendor and platform shifts. Major roadmap or pricing changes from Veeva, Benchling, Palantir, Databricks, Snowflake, Microsoft, ServiceNow, SAP, and the AI foundation-model providers.
• Talent market signals. Notable hires and departures inside peer companies’ technology functions, compensation shifts, and location strategy changes that affect our own recruiting and retention.
• Deal environment. M&A activity that could pull work forward or introduce integration debt. McKinsey has argued that 2026 will reward “precision” in life-sciences dealmaking, with targeted bets on differentiated science and advantaged platforms.¹⁰

Section 6: Capability Gaps

The capability gap section is the CIO’s chance to be honest about what the organization cannot yet do. Less than a third of the 50 biopharma leaders McKinsey surveyed in 2025 believed their organizations had the talent and capability required to support future product portfolios, including new modalities and technologies.¹¹ Naming the gaps in the QIR is how a CIO makes it socially acceptable to ask for investment against them.

The template lists each named gap, the business impact of leaving it unaddressed, the two or three viable ways to close it (build, buy, partner, or defer), and a recommended path with a rough cost envelope. Common examples in pharma include: ML engineering talent for GxP environments, data engineering for real-world evidence, GxP-grade cloud landing zones, MLOps at scale, and change-management capacity to absorb multiple concurrent rollouts.

Section 7: Resource Asks

Resource asks are the point of the whole exercise. If a QIR ends without at least one clear ask of the executive committee, the CIO has under-used the forum. Each ask includes what is being requested, from whom, by when, and what happens if the ask is not granted (specifically which pilots slow, which graduations slip, which capability gaps persist).

Section 8: Benchmark Comparison

The benchmark section places the portfolio in industry context and forces some external pressure onto the internal narrative. Gartner has forecast that global healthcare and life-sciences enterprise IT spending will grow 7.3 percent in 2025 to reach 311 billion dollars, with life-sciences companies historically spending in the higher end of the 8 to 12 percent of revenue range typical of regulated industries.¹² The template invites comparison across four axes:

• Total IT spend as percent of revenue vs Gartner benchmarks and disclosed peer figures.
• Innovation budget as percent of total IT spend, with the aspiration usually in the 8 to 15 percent range depending on strategy.
• Portfolio horizon mix vs the classic 70 / 20 / 10 three-horizon distribution.⁶
• Pilot-to-scale conversion rate vs the 5 percent that MIT observed across enterprise AI pilots.¹ A pharma CIO should not settle for consumer-tech-industry pilot survival rates and should be able to defend a materially better number.

Section 9: Quarter-Forward Commitments

The final section is a short, numbered list of the specific commitments the CIO is making for the coming quarter. Not aspirations, not “we will explore,” but commitments with named owners and dates. This is the section that gets re-read at the start of the next QIR, and it is how the executive committee holds the innovation portfolio accountable without micromanaging.

Presentation Flow: 13 Slides for the Executive Committee

The document is the record. The slide deck is the narrative. In our experience, 13 slides is the right length for a 45-minute committee slot with 15 minutes of discussion built in. Any longer and the CIO is asking the room to process too much; any shorter and important context is lost.

Some CIOs prefer a 15-slide flow that inserts a “portfolio outcomes since last QIR” slide after slide 2 and a “financial view of the innovation portfolio” slide after slide 3. Both are legitimate additions when the executive committee has specifically asked for more granularity. In most cases, 13 is the ceiling and 11 is the floor.

Kill, Graduate, Sunset: The Three Hardest Decisions

The QIR mechanically produces three categories of decisions each quarter: kill, graduate, sunset. Each has a distinct psychology and a distinct governance pattern.

The kill decision and the courage gap

Killing pilots is the single hardest thing to do inside a large pharma organization. Industry analysts have described a “courage gap” in pharma portfolio management, where ending a program carries organizational and personal consequences that often seem worse than letting it continue for another quarter without discussion.¹³ The QIR mitigates this by making non-decisions visible.

The pattern that works: pre-declared kill criteria that were approved at pilot launch, a status page that shows the pilot against those criteria, and a QIR ritual in which the executive committee explicitly acknowledges when kill criteria have been met. The committee’s role is not to invent the kill decision. It is to ratify the decision the criteria have already made.

Graduation and the operating-model trap

Graduation looks like the easy decision because it is the one everyone wants to make. The trap is that “graduate to scale” is often approved without the operating model to sustain the capability. When a pilot moves out of innovation budget and into steady state, someone must own the capability, someone must fund it, someone must manage the change, and someone must own the future sunset trigger. If any of those roles is missing, the graduation decision is theater and the capability decays within a year with no one noticing.

The sunset decision and the sunk-cost distortion

Sunset decisions on already-scaled programs are politically difficult because someone approved the original investment and someone champions it today. The QIR normalizes the sunset decision by making it routine: every scaled program carries a written sunset trigger from day one, and every QIR reviews at least one scaled program against its trigger. The committee is not asked whether a program “should still exist.” It is asked whether the pre-declared trigger has fired.

Capability Gaps and Resource Asks

The capability-gap section is where the QIR produces its most durable outcomes. A well-run gap review does three things: it names the gap in language the executive committee can act on, it presents a small number of viable paths to close it, and it makes an explicit recommendation the committee can approve, modify, or reject.

Common gap patterns we see in pharma CIOs’ portfolios in 2026 include:

• ML and MLOps engineering talent qualified for GxP environments. The gap is not “data scientists.” It is engineers who can operate models under validation, change control, and audit-trail expectations. This is a hire-and-partner gap more than a hire-alone gap.
• Data engineering for real-world evidence at scale. As RWE becomes a first-class input to regulatory submissions, the volume, complexity, and provenance requirements of the data expand rapidly. Underinvestment shows up as slow clinical and medical requests, not as a headline problem.
• Cloud landing zones and platform patterns that meet regulatory expectations. Every pilot the CIO approves creates future validation debt if the underlying platform is not treated as a first-class investment.
• Change-management capacity across the enterprise. Pharma organizations are not usually change-constrained by IT delivery. They are constrained by the business’s ability to absorb concurrent rollouts. Naming this in the QIR is how the CIO shifts the ownership of the constraint back to the executive committee.
• Vendor-management and partnership maturity. MIT’s 2025 research found that vendor-partnership implementations of AI succeed roughly twice as often as internal builds, yet many pharma organizations lack the vendor-management muscle to run partnerships well.¹

Resource asks flow naturally from named gaps. A resource ask that does not tie to a named gap or a named graduation is usually decoration. Executive committees are surprisingly willing to approve a well-framed, small-to-medium ask that maps cleanly to a specific decision the portfolio already needs to make.

Benchmarking and the External Environment Scan

The external scan is the section most often skipped and most often missed by the executive committee once it is left out. The room wants to know how the CIO’s read of the environment compares to what they are hearing from peer CEOs, board colleagues at other companies, and their own advisors. A CIO who cannot answer “what did our peers do this quarter” cedes the strategic-technology conversation to whoever else in the room happens to have read a McKinsey report on the flight in.

Benchmark comparison is where a CIO earns credibility over multiple quarters. The point is not to claim the organization is above every benchmark. It is to make honest, defensible statements about where the organization sits and why. Some benchmark axes are stable enough to review quarterly:

The external environment scan should also incorporate regulatory movements that materially reshape the technology agenda. In 2026 the CIO should expect the executive committee to ask about FDA and EMA joint AI principles, EMA Annex 22 developments, MHRA GCP AI guidance updates, and the growing body of AI-related expectations across regulatory bodies.¹⁴ A CIO who has already thought through the implications is a CIO whose credibility grows every quarter.

How to Run the Executive-Committee Meeting

The QIR is a working meeting, not a broadcast. The CIO or the CIO’s chief of staff should treat running the meeting as a design problem, not an accident of the calendar. A few patterns that work in the rooms we have sat in:

Pre-read discipline and the 48-hour rule

Send the pre-read document 48 hours in advance, no exceptions. The pre-read is the QIR document; the deck is what the room sees on the day. When the pre-read is late, discussion collapses into re-explaining rather than deciding. When the pre-read is thorough, the meeting can spend most of its time on the two or three contested decisions.

Open with the ask, not the achievements

The most common structural failure of a QIR is opening with a recap of activity. The room stops paying attention around slide four. Open with the decisions being sought today and the risks the CIO wants the committee to help absorb. Then walk the evidence back to those decisions. Every CIO who has switched from “here is what we did” to “here is what I need” has told us the room’s engagement roughly doubled.

Route disagreements into named actions

Executive committees rarely resolve disagreements in the room. What they can do is agree on the next step. When two committee members disagree on a graduation, the meeting lead’s job is to translate the disagreement into a named action with an owner and a date: “By next QIR, sponsor and CFO will present a joint recommendation on the operating-model funding split.” Progress compounds when the QIR reliably converts debate into named next steps.

Protect the airtime for kills

Kill decisions get squeezed when the room is running late. Rearrange the flow if needed so that the two or three kill decisions are not the last five minutes of the meeting. Killing pilots is the discipline the CIO most needs the committee to see happening, quarter after quarter.

Close with the read-back

The last five minutes of the QIR should be the CIO reading the quarter-forward commitments verbatim, and the committee acknowledging them explicitly. This ritual creates the accountability that makes the next quarter’s QIR meaningful. Without it, the QIR is a forum of good intentions that never quite compound.

Common Failure Modes and How to Avoid Them

The QIR fails in predictable ways. Naming the failure modes explicitly is how the CIO’s team protects the ritual across CIO transitions, executive committee changes, and shifting strategic priorities.

Conclusion

The Quarterly Innovation Review does one thing that no other forum in a pharma organization does. It gathers the executive committee around the full technology innovation portfolio, four times a year, and forces a set of explicit kill, graduate, and sunset decisions. Done well, it prevents the slow drift into a portfolio of unread pilots and unowned programs that MIT’s 2025 research documented across enterprises. Done poorly, it accelerates that drift by giving it a governance stamp.

The template in this article is not the only viable structure. It is a structure that has held up in pharma-specific settings, where regulatory scrutiny, validation cost, and scientific-committee culture all shape what “innovation governance” has to mean. Adapt the sections to your organization’s realities, but hold the discipline: kill criteria in writing, operating-model tests before graduation, sunset triggers on every scaled program, external scan every quarter, and asks that can be approved or denied in the room.

Sakara Digital works with pharma and biotech organizations building the innovation governance rituals that outlast the CIO who introduced them. If you are designing a QIR from scratch, revising one that has drifted into activity reporting, or preparing to present a first QIR to a new board technology committee, we are happy to have that conversation and share what we have seen work.