Scaling Execution in Complex Technology Organizations

Complex technology organizations rarely fail for lack of talented people. They struggle as they scale because alignment frays, priorities collide, decisions slow, dependencies multiply, visibility drops, and capacity binds. The strategy-to-execution gap is rarely a planning problem. It opens in execution.

The work is to build the operating system that closes it, turning strategy into funded priorities, priorities into commitments, and commitments into predictable outcomes.

Every complex technology organization needs these capabilities to scale. What differs is how each is delivered: some I bring directly as a leader, others must be institutionalized to hold up across the whole portfolio. The enterprise PMO is how I institutionalize the ones that need it, the mechanism, not the point.

The function that institutionalizes these capabilities exists to turn strategy into predictable execution. It owns the operating system (governance, rhythm of business, lifecycle standards, decision mechanisms), portfolio visibility and the prioritization process, decision support, and the program-management discipline.

It does not own the delivery outcomes of individual programs, the technical solution, or the funding calls themselves. Leadership decides those, and the function frames them and ensures follow-through. Not every capability requires a PMO; the function exists to institutionalize the ones that must operate continuously and at scale.

On structure and sizing: the PMO separates portfolio and investment governance (what we fund) from operations and delivery excellence (how we execute). Size it to decision load, not project count: about 4% of the product-development staff, roughly one PMO professional per 25, scaling with portfolio complexity.

Program leaders are held to a leadership standard, not an administrative one: create clarity when priorities conflict, drive decisions when the organization stalls, surface risks early, influence without authority, and own the outcome.

• Most schedule slips begin as unresolved decisions, not execution failures.
• Capacity, not ideas, is the real constraint.
• Standardization is what makes delivery efficient.
• The best systems keep running after you leave.

The model is drawn from a career delivering complex hardware and software products at scale: commercializing smartphones and owning carrier certification at Motorola (35 million units across 50-plus countries), founding the technical PMO at HP, leading a billion-dollar robotics portfolio and standardizing the phase-gate NPD lifecycle at iRobot, and establishing lifecycle governance at Sony PlayStation. It is tuned for gated, safety- and compliance-intensive domains spanning hardware, software, and connected platforms.