Improving agility at scale is one of the hardest things an organization can take on. Many companies set out to “become agile”, but few manage to change the very structures, governance, and financial steering models that hold them back.

Over the past decade, I’ve had the privilege of guiding several large enterprises through their transformations — across different industries, cultures, and continents. A clear pattern has emerged: if we want to accomplish real improvement of business agility, the most impactful transformation has to happen at the top. There has to be significant change in how we fund, govern and organize the portfolio.

Why Portfolio Management Matters

When I ask why a company chooses to organize initiatives into a portfolio, I’m often met with complete silence. There’s a lot of do’s and don’t, but very few Why’s.

One thing I’ve learned is that the likelihood of be successful with managing your portfolio is more related to clarity of the purpose than how you manage it. If a clear goal is missing then the best you can do is to hope for a couple of lucky breaks to come your way.

The simplest answer I can come up with on the purpose of a Portfolio is this:

To utilize common governance over everything within the portfolio, believing that doing so will create better results than not doing so.

In other words: portfolio management isn’t about control — it’s about enabling competitive advantage through combining different options within the portfolio into a coherent value proposition which outperforms your competitors’ propositions.

The Flow Fundamentals

A portfolio should really be viewed as more than a set of initiatives or projects. It’s a system — a dynamic network of people, processes, and tools working together to create value for customers.

Work flows into and out of this system, and how that flow is managed determines how quickly, sustainably, and happily we deliver outcomes than provide real value for our customers.

By viewing a portfolio as a system where work enters and leaves in a controlled way, it has the characteristics of a queuing system.

Just as gravity shapes our physical world, certain laws shape how work moves through a system — whether we recognize them or not. I call these the Flow Fundamentals:

• Little’s Law: There’s a relation between the number of ”things” in process, processing time for each ”thing”, and the lead time of it through the system.
• Kingman’s Formula: Variability kills flow. Lead time in a high variability flow will be severely worsened already at low resource utilization level.
• Theory of Constraints: Improving the overall flow through a system can only be done by improving the current bottle neck.

When we start to understand these fundamentals, we stop fighting the system and instead use them to our advantage. Other ways of controlling the flow become possible.

Systems thinking and flow fundamentals are pillars of modern portfolio management, contact us to learn how you and your organization step up your game.

Creating Clarity

An effective portfolio needs three basic things to be clear for everyone working within it; scope, direction, and metrics. These provide answers to questions such as

• What’s in the portfolio and what’s out?
• Where are we heading? How is the portfolio intended to evolve? What should it not evolve?
• How do we know we’re moving in the right direction? What key metrics can be used to gauge progress or lack thereof?

Strategic themes help align teams and leaders around shared objectives, while metrics provide feedback loops that guide adaptation. The goal isn’t to measure everything, but to measure what matters — focusing on leading indicators of progress rather than lagging lack of results.

From Projects to Flow

Traditional, project-centric governance often clashes with modern product development. Projects assume predictability, but product development thrives on learning. Projects have a fixed end date, but successful products require change and adaption during their full product life cycle.

Most organizations focus mainly on project-centric governance, where projects are vehicles for major new products, change in how products or services are provided, or retirement of them. Much senior management attention is devoted to ”getting it out the door”. There is lack of focus on continuous improvement and innovation.

Focus need to shift from managing projects to managing flow in the portfolio. In one large retail we started by visualizing all ongoing initiatives across domains, define clear prioritization principles, and introduce lean portfolio management practices.

Governance that Enables, Not Constrains

Good portfolio governance is about setting the minimum necessary constraints — guardrails that guide decision-making without limiting it. The same goes for portfolio operations: they should connect people, celebrate progress, and surface challenges early.

Establish minimum necessary portfolio governance, not maximum possible

Capacity management plays a key role here. Note, true portfolio capacity is not FTEs (Full Time Equivalents)! Product development is about collaboration and learning. Individuals are unique and have different skills. They too can learn and change. Interaction and teamwork have a great influence over both effort and result in work. These perspectives are not well represented by using the overly simplistic assumption that capacity can be represented by a number corresponding to 8-hour work units per day.

There is very little correlation between number of people working in the portfolio, and our ability to fulfill our business ambitions & customers’ needs. Furthermore, equating portfolio capacity with FTEs implies that the only way to increase capacity is to add people. This is simply not true.

Pull mechanisms and Queue management enable optimal flow within given system constraints. System constraints can be changed to improve flow over time, without adding people. This is where the flow fundamentals mentioned before come into play.

Capacity allocation, i.e. deciding which portion of capacity should be utilized for what, enables separation of concern & decentralized decision-making – it’s both-and, not either-or. Decentralized decision-making enables better solutions and empowers people.

Not every decision in a portfolio should be decentralized, but most development portfolios benefit from enabling aligned and parallel decision-making. An ever changing world requires better decisions and more decisions per time unit in order for the company o continue to thrive.

Prioritization with Purpose

Prioritization doesn’t need to be complicated, but it should be clear how it’s done. Start simple, evolve over time, and don’t replace thinking with formulas. Use methods like WSJF (Weighted Shortest Job First) as a guide, not a crutch. Enable re-prioritization when necessary.

In the end, business agility isn’t about being faster — it’s about learning faster what customers want, aligning better on how to provide solutions to those needs, and creating environments where people can thrive.

At Business Caddy, I help organizations find their rhythm — balancing structure and freedom to achieve meaningful results. If you’d like to explore how lean portfolio management can help your organization, let’s talk.

You can easily get in touch by using this form – we promise a fast response!

The post What I’ve learned about Leaner and more Adaptable Portfolio Management first appeared on Business Caddy.

Agile transformations often start with big ambitions: cross-functional teams, happier employees, faster feedback loops, and more value delivered. But years later after the initial energy fades, many organizations find themselves right back where they started — slow, siloed, and stuck in legacy way of working. Major investments made in time, effort and money but with little to no visible effect on the business.

Why?

Because governance didn’t change.

The Hidden Constraint

You can coach teams, adopt frameworks like SAFe, and run Lean training for months. But if your governance model — how decisions are made, how funding flows, how progress is reviewed — still reflects a traditional, project-based mindset, your transformation will always hit a ceiling.

This is especially true if your organization is tasked with building complex products that consist of both hardware and software. You can’t unlock agility on the ground if the top is still wired for control and predictability.

Symptoms of Governance Misalignment

Here’s what it looks like when governance is out of sync with development and delivery:

• Teams are forced to commit to detailed plans years in advance
• Progress is reported in terms of milestones, not outcomes or insight from solution integration
• Funding is tied to projects, not value streams — leading to stop-start-stop work
• Decisions pile up at steering groups instead of being made closer to teams
• Risk is managed by review gates, not through fast learning and iteration

These aren’t just growing pains. They’re signs that your system is protecting itself from real change.

What Needs to Change

Transforming governance doesn’t mean removing oversight. It means rethinking how oversight works.

Transforming governance doesn’t mean removing oversight. It means rethinking how oversight works. For that to happen, mindset needs to change. It needs to shift from focusing mainly on execution of a largely outdated plan to making sure the organizational capabilities are focused on achieving desirable outcomes.

Here are three key shifts I’ve seen succeed in large, legacy-heavy organizations:

1. Fund Value Streams, Not Projects

Move from temporary project budgets to long-lived funding for persistent teams. This enables flow, long-term ownership, and better alignment with customer value.

2. Empower Decentralized Decision-Making

Push decisions down to the level of greatest insight and accountability. People organized in long-lived cross-functional Value Streams is a huge enabler for this. Governance should enable clarity, not create bottlenecks.

3. Measure Progress in Outcomes, Not Milestones

Shift focus from “Did we do what we said?” to “Are we solving the right problem?”
Use OKRs, lean metrics, or customer impact to steer.

Start With One Conversation

You don’t need to overhaul everything at once. But someone — usually at the executive leadership level — needs to name the gap between an ambition to increase organizational responsiveness and traditional governance.

Start by asking:

• What are we funding — projects, or capabilities?
• How do we make the connection between our Strategy and ongoing initiatives?
• How fast can a team respond to validated insight?
• Where are decisions getting stuck, and why?

Changing governance is hard. But without it, even the best teams will be constrained by a system that wasn’t built for agility.

Final Thought

If you want to meaningfully improve agility at scale, you have to change funding and steering — not just roles and events, but governance itself.

I help leaders and organizations make this shift in a practical, grounded way.
Want to explore how? Get in touch — or start by sharing this with someone asking why agile isn’t working.

The post Why Most Agile Transformations Fail Without Governance Reform first appeared on Business Caddy.