Your Pharma Portfolio Is 83% Green. Should the CEO Be Happy?

by Phanindra Venkata Gottipati CEO, VirtuNx

Imagine walking into a pharmaceutical portfolio review. The executive dashboard looks reassuring.

• 83% of projects are Green.

• 12% are Amber.

• Only 5% are Red.

At first glance, the portfolio appears healthy. But I would ask a different question:

Are the green projects still the right projects to invest in?

That question gets to something I have increasingly noticed in conversations around pharmaceutical portfolio and project management.

Organizations can become very good at measuring whether projects are progressing according to plan without continuously asking whether those projects still represent the best business decisions.

In generics and API development, that distinction matters. A project can be operationally green and strategically wrong. And a strategically critical project can appear healthy to leadership while execution risks underneath it are quietly increasing.

Green Doesn't Mean Valuable

Consider Project A.

• Development is progressing well.

• Milestones are on schedule.

• Risks are manageable.

• The project is Green.

But since the original investment decision, three additional competitors have emerged, expected pricing has weakened and the commercial opportunity has narrowed.

Should leadership celebrate because the project remains on schedule?

Now consider Project B.

• It is Amber.

• A technical dependency has delayed a development milestone.

But the molecule remains commercially attractive, fits the company's manufacturing capability and has a strategically important market window.

Should Amber automatically make Project B less attractive than Project A? Probably not. This is where traditional project status begins to lose meaning at portfolio level.

Project health and investment attractiveness are related, but they are not the same thing.

A Delay Is Not Just a Schedule Variance

Consider another example.

• A critical milestone moves by three months.

• At project level, the response might be:

Original date. Revised date. Variance. Root cause. Mitigation. All necessary.

But leadership needs another layer of information.

1. Does the delay affect the critical path?

2. Does it move the expected ANDA or DMF filing?

3. Could it affect the market-entry window?

4. What commercial opportunity might be exposed?

5. Could additional resources recover the schedule?

6. What other priority project would lose those resources?

Suddenly a project-management issue has become a portfolio allocation decision. This is why I believe portfolio intelligence must connect:

What happened → Why it happened → What it affects → What decision is needed.

The CEO and Project Manager See Different Portfolios

This isn't because either side lacks information. They have different responsibilities. The CEO or business leader asks:

1. Are we investing in the right opportunities?

2. What is our portfolio exposure?

3. Where should we put incremental capital?

4. Which projects deserve acceleration?

5. What should we stop?

The portfolio leader asks:

1. Are our strategic priorities translating into execution?

2. Where are our biggest cross-program risks?

3. Where are resources constrained?

The project manager asks:

1. What is preventing the next milestone?

2. Which dependency needs resolution?

3. Who needs to act?

4. What decision is blocking progress?

All three perspectives are legitimate.

The problem occurs when they exist in separate systems, spreadsheets, presentations and meetings. Then leadership has one version of the portfolio. The PMO has another. Functions have several more.

This Is What Customer Conversations Have Changed for Us

This challenge has strongly influenced how we think about PortiVix at VirtuNx.

It would be easy to define PortiVix simply as pharmaceutical portfolio and project management software.

Projects | Milestones | Tasks | Dependencies | Risks | Reports | Dashboards.

Those capabilities matter. But they are not the reason the problem is interesting. The harder question is:

How do we connect strategic intent at the top with execution reality underneath?

A portfolio leader shouldn't have to wait for the next governance meeting to discover that three important programs depend on the same constrained resource.

Leadership shouldn't see only a red milestone without understanding the business outcome it threatens.

And project teams shouldn't execute against priorities without visibility into whether the strategic assumptions behind those priorities have changed.

That requires something more than project reporting.

AI Can Help Find the Story Behind the Status

This is an area where AI can create meaningful value.

Imagine the underlying system observes:

• A critical milestone is trending six weeks late.

• Two upstream dependencies remain unresolved.

• A specialist resource is shared across three priority projects.

• The expected filing date may move.

• The molecule's commercial opportunity is particularly time-sensitive.

• A traditional dashboard may display five separate signals.

AI can potentially connect them into a story:

This program has an increasing probability of missing its planned filing window. The primary drivers are unresolved dependencies and resource contention. Leadership intervention may be required.

That is far more useful than simply changing a project from Green to Amber. But the system still shouldn't make the final portfolio decision. Leadership understands trade-offs the algorithm may not.

AI surfaces the situation. People decide what to do about it.

Portfolio Management Is About Choices

One of my biggest learnings from working around this problem is that the term "portfolio management" can sometimes be misleading.

It sounds like managing many projects together. But a portfolio is really a collection of investment choices.

• What will we fund?

• What will we prioritize?

• Where will we accept risk?

• What will we accelerate?

And perhaps the hardest question:

What will we stop?

Project management helps organizations execute projects right. Portfolio management must continuously ask whether the organization is executing the right projects.

Both questions matter. Neither can operate independently.

From Systems of Record to Systems of Decision

Enterprise technology has spent decades building systems of record.

Then we built dashboards and systems of engagement on top of them.

I believe the next opportunity, particularly in complex industries like pharma, is to create better systems of decision.

Systems that don't merely tell the CEO:

83% of projects are Green.

But help leadership understand:

• Are those still the right projects?

• Which assumptions have changed?

• Where is value at risk?

• Where does intervention matter?

And which decision cannot wait until the next portfolio review?

Because the most dangerous portfolio isn't necessarily one with too many red projects.

It may be the portfolio where everything looks green while the business context has already changed.

If 83% of your portfolio is Green, how confident are you that they are still the right projects to invest in? Share your views in the comments.