When the system around the work is no longer keeping up
Growth creates complexity. Sometimes the challenge is fixing what is already breaking. Sometimes it is building the systems needed for what comes next.
That can mean more priorities. More dependencies. More teams. More customers. More decisions. More ways for important information to get lost between functions.
At some point, the informal ways of coordinating work that used to be “good enough” stop being good enough.
That is usually where I come in.
I help founders and scaling technology organizations build the operating structures, delivery systems and team capabilities needed to make execution clearer, more coordinated and more predictable.
The specific activities depend on the organization, but my work usually falls into three areas.
Build or Improve the Execution System
Sometimes the problem is not the people or even the strategy.
It is the system used to turn priorities into coordinated work.
I help organizations design or improve the operating structures that connect planning, prioritization, capacity, delivery and decision-making.
That can include:
Demand intake and prioritization
Capacity and workload planning
Portfolio visibility
Planning cadences and operating rhythms
Delivery workflows
Governance and decision-making structures
Risk and dependency visibility
Executive and team reporting
The way work moves from strategy into execution
The goal is not to add process for its own sake.
It is to create enough structure so that people can see the work clearly, understand tradeoffs earlier and make better decisions before problems become crises.
Improve Cross-
Functional Delivery
Many execution problems do not live inside a single team.
They live between teams.
Product, engineering, sales, customer success, finance and leadership may all be looking at the same work through different lenses, with different priorities, language and incentives.
I help create a more coherent operating view across functions so that everyone can better understand:
What matters most
What is actually in flight
Where capacity is constrained
What dependencies exist
What is at risk
What decisions need to be made
How teams depend on one another to move that work forward
That can mean redesigning planning conversations, improving handoffs, creating shared portfolio views or clarifying how priorities and commitments move across the organization.
The objective is not forced uniformity, but enough alignment for the organization to move together more predictably and with less friction or contention.
Build the Teams and Capabilities That
Make the System Work
A process is only useful if the people responsible for it can operate it effectively.
I help build, strengthen or reshape the teams and leadership capabilities that support execution.
That can include:
Building PMOs or delivery organizations from scratch
Maturing existing project or program management functions
Clarifying roles, responsibilities and ownership
Coaching project, delivery and operational leaders
Developing teams that identify and solve problems rather than simply report status
Helping leaders operate more effectively in ambiguous or fast-changing environments
I have repeatedly built first-of-kind project, portfolio and delivery functions across organizations including ASAPP, TuneCore and 2U.
The goal is to leave the organization with stronger people, stronger systems and teams that work together more effectively.
Common Situations I Help With
My work is often useful when:
Growth is exposing limitations in the way work is planned, coordinated or delivered.
You can see greater complexity coming and want the operating system to be ready before it becomes a problem.
Priorities, demand and capacity are becoming difficult to reconcile.
Work crosses team or functional boundaries and the existing coordination model is no longer sufficient.
Leadership needs a more reliable view of the portfolio to make tradeoffs and decisions.
A PMO, delivery function or execution capability needs to be built, matured or redesigned.
What the Work Can Look Like
The shape of the engagement depends on what the organization needs and how far the problem has already been defined.
Diagnostic and Advisory
Sometimes the first need is clarity.
I can help identify where execution is breaking down, how work is actually moving through the organization and which changes are most likely to improve the system.
That can include reviewing planning, prioritization, capacity, ownership, dependencies, decision-making and cross-functional coordination.
The objective is a clearer picture of the current system, the most important failure points and the highest-value next moves.
System Design and Implementation
When the problem is understood, I can help design and implement the operating model needed to address it.
That may include planning systems, portfolio visibility, intake and prioritization, demand and capacity alignment, delivery workflows, governance, decision structures and cross-functional coordination mechanisms.
The work is iterative: introduce useful structure, test it in the real environment and refine it with the people using it.
Fractional Operating or Delivery Leadership
Some organizations need more than advice or system design.
They need someone to take hands-on ownership while the system is being built, improved or stabilized or provide ongoing operating or execution leadership.
In those situations, I can work as a fractional execution or delivery leader, partnering directly with founders and leadership teams across planning, delivery, portfolio management, team development and cross-functional execution.
The exact role depends on the organization, but the common thread is practical ownership of the work, not just recommendations.
How the Work Typically Unfolds
1 - Discovery & System Mapping
Understand how work actually moves through the organization.
Before changing the system, I need to understand the system that already exists.
That means looking at how work enters the organization, how priorities are set, how decisions are made, where ownership is clear or unclear and where coordination begins to break down.
Depending on the situation, this may include:
Mapping intake sources
Understanding how priorities are set and communicated
Identifying breakdowns in cross-team coordination
Looking at team-level problems and friction
Assessing roles, responsibilities and decision ownership
Surfacing interruption, rework and recurring failure points
The objective is a clear, shared view of the current delivery system - including both structural gaps and the human impact of those gaps.
2 - System Design & Alignment
Define a delivery model that supports how the organization actually works.
Once the failure points are understood, I help design the structures needed to improve execution.
That may include:
Portfolio, project management or planning models
Demand intake and prioritization
Capacity alignment
Clearer roles and ownership
Planning and coordination mechanisms
Executive decision structures
Operating rhythms across teams and functions
The model has to fit the organization.
Its people, stage, complexity, constraints and work all matter.
The objective is not to import a “best practice” model from somewhere else. It is to create an operating model that reduces friction rather than adding overhead.
3 - Incremental Implementation
Introduce structure in a way that adds value without disrupting delivery.
Rather than treating implementation as a large process rollout, I introduce changes iteratively, test them in the real environment and refine them with the people using them.
It is a triaged approach: address the highest-value or most urgent problems first, then use what we learn to inform later stages of implementation.
That can include:
Team-level portfolio views
Cross-team portfolio visibility
Lightweight tooling aligned with existing systems
Planning cadences
Coordination mechanisms
New roles or ways of working
The goal is to create useful improvements quickly while allowing the organization to adapt naturally.
4 - Continuous Planning
Enablement
Move from disruptive planning cycles toward ongoing visibility and decision-making.
Planning becomes more effective when the organization does not have to periodically stop, reconstruct reality and make large decisions from incomplete information.
I help build planning systems where work is visible and continually evaluated.
That can include:
Ongoing portfolio visibility
Incremental reprioritization
Better alignment between demand and capacity
Stronger connection between delivery planning and financial planning
More reliable commitments
Less dependence on “big bang” planning events
The goal is a planning system that can adapt as conditions change without creating unnecessary organizational disruption.
5 - Stabilization & Cultural
Adoption
Make the system sustainable.
A new operating model is only successful if the organization can own it.
That means reinforcing new roles, creating feedback loops, supporting leaders in using the system and embedding the coordination mechanisms into the way the organization operates.
This can include:
Establishing clear ownership
Strengthening cross-functional coordination
Reinforcing new responsibilities
Developing continuous improvement habits
Helping leaders use the system for prioritization and decision-making
Building confidence and trust in the information the system produces
The objective is not a static end state.
It is a stable system that can continue adapting as the organization changes.
How I Work
My approach is hands-on and collaborative - I partner with leadership and teams to understand the environment, design the system and make it work in practice.
A few principles guide how I engage:
Work with the organization, not around it
The people doing the work usually understand important parts of the problem already.
They need to be part of understanding, designing and refining the solution.
Introduce change iteratively
Large process rollouts create disruption and often fail because too many assumptions are made up front.
I prefer to introduce useful structure, observe what happens and refine it.
Use the tools that make sense
The solution does not start with software.
I am tool-agnostic and generally prefer to leverage existing systems where possible rather than introducing unnecessary new technology.
Design for both structure and adoption
A technically elegant process that people do not use is not a useful system.
The operating model and the human behavior around it have to reinforce one another.
Maximize value and minimize disruption
The objective is to improve execution as quickly and broadly as possible without creating unnecessary administrative overhead, complexity or distraction.
The exact results depend on the organization and the problems being solved, but my work generally creates:
Better coordination across teams and functions
Clearer visibility into priorities, dependencies and capacity
Less conflict caused by competing priorities
Earlier visibility into delivery risk
More reliable planning and commitments
What Better Looks
Like
Better alignment between operational work and financial planning
More effective use of project and program management
Less firefighting
More intentional execution
Stronger organizational capability to adapt as conditions change
Less frustration and stronger collaboration
The Common Thread
The work may involve planning, portfolio management, delivery systems, PMO design, operating models, team development or cross-functional coordination.
But the common thread is the same:
Understand how the work actually happens. Identify what is getting in the way. Build only the structure needed to make the organization stronger.
If execution is getting harder as your organization grows, I am always happy to compare notes.