~ 680 words | ~ 4 minute read
In most organizations, the work arrives at the PM’s desk already shaped.
An opportunity has been identified. Someone assessed it, determined it was worth pursuing, and built the investment case. Leadership approved it. The PM is brought in with a scope, a start date, and an expectation to deliver.
That sequence is so common it rarely gets examined. It shapes how organizations structure their teams, how they write job descriptions, and how they define what project leadership looks like. Over time, it becomes the assumed model. The way things work, not a choice that was made.
There is another model. Less common, but gaining traction.
A new model
In some organizations, the PM does not wait for an approved initiative. They identify the opportunity in the first place. They assess it, analyze whether it deserves to become a project at all, and build the business case for leadership review. When the initiative is approved, they lead the delivery. One role. One person. The full cycle from opportunity to outcome.
To work well, the full-cycle model asks more of the PM. It requires analytical thinking, the ability to size an opportunity, pressure-test assumptions, and make a case that leadership can act on with confidence. It requires financial fluency and the judgment to recognize when an opportunity is not worth pursuing, and the clarity to say so. These are skills most organizations do not think to develop in their PM population, because they have never asked their PMs to need them.
It also asks more of the organization. Leadership has to extend trust into the front end of the work, not just the execution phase, and that is a meaningful shift. The instinct to keep strategy and execution in separate hands runs deep. When those two things are separated, work gets handed off. The person who led the analysis is no longer in the room when delivery begins. The person leading delivery did not participate in the decisions that shaped the work. How much that gap matters depends on the complexity of the work, the strength of the handoff, and how well context travels between the two phases.
That last cost is worth further consideration. The people with the deepest, most practical view of what execution requires are often the PMs themselves. They have led similar work before. They have seen where assumptions fall apart mid-delivery, where risks materialize late because nobody pressed hard enough early, and where the scope and cost of the work only became clear after commitments had already been made. That experience is directly relevant when assessing a new opportunity. A PM who has delivered similar work knows what a realistic timeline looks like, where the plan is likely to get stressed, and what has to be true for the business case to hold. That accumulated experience changes what the PM sees when they look at a new opportunity.
The shift
When the PM who built the case also leads the delivery, something shifts.
The business case becomes more realistic. It is built by someone who understands what the work actually requires, how long it takes, what can go wrong, and what assumptions need to hold. When the person writing the case is also the person who will execute against it, optimistic assumptions become a liability. The case gets written with more honesty, because the PM will have to answer for every number it contains.
The delivery becomes more grounded. The PM understood the reasoning behind every decision in the assessment phase. They do not need to be briefed on the why. When conditions change mid-execution, they have the context to adapt without escalating every judgment call upstream.
Assumptions surface earlier, because the person who made them is also the person executing against them. Risk identified early leaves room to respond. Risk identified late tends to arrive after the options for responding have already narrowed.
This model is not the right fit for every organization or every initiative. It works best where the work is complex, the stakes are high, and the PM has the experience to credibly own both phases.
In your organization, does one person own the full cycle, or does the work change hands between analysis and delivery?
Want more like this?
If you’re responsible for guiding complex work, setting direction, and being accountable for outcomes, you can subscribe to receive occasional insights on project leadership and delivery.
Thoughtful notes. Practical ideas. Unsubscribe anytime.
Interested in taking this further?
If you’re responsible for the success of critical initiatives — or you’re developing the project leadership skills to support them — I’d be glad to connect.