Skip to main content
HBR IdeaCast

The Case For Becoming a Project-Based Org

30 min episode · 2 min read
·

Episode

30 min

Read time

2 min

AI-Generated Summary

Key Takeaways

  • Ruthless Prioritization: Leaders should launch new projects only after finishing or canceling two to three existing ones, as most organizations could eliminate 80 percent of current projects without impact. Use company purpose as the filter to cut half of initiatives immediately, ensuring capacity exists for strategic work rather than creating organizational overload.
  • Leadership Time Allocation: Senior executives currently spend less than half a day per week on transformation work, dedicating 80 percent of time to operational comfort zones. Leaders must shift to spending at least three days weekly on change projects, making quick decisions in uncertain environments and personally sponsoring cross-departmental initiatives.
  • Six-Month Project Cycles: All transformation projects should run maximum six months before evaluation, allowing organizations to stop, pivot, or accelerate based on results. This strategic fluidity replaces long-term rigid planning with iterative cycles that match the pace of market and technology changes, requiring trust from boards and shareholders focused on long-term capability building.
  • Internal Transformation Capability: Companies must stop outsourcing change to consultants and build transformation muscles within existing employees. Reskill operational workers whose tasks face automation into project roles rather than layoffs. Organizations like Haier tripled profits within five years by redeploying staff into self-directed teams working on innovation rather than repetitive tasks.
  • Structural Experimentation: Start organizational redesign by fully empowering one critical transformation team with 90 percent decision-making authority and priority resource access. This creates visible success that generates demand across the organization, avoiding the resistance that comes from eliminating hierarchy company-wide overnight. Let the snowball effect drive adoption rather than forcing top-down structural change.

What It Covers

Antonio Nieto Rodriguez argues organizations must transition from operations-focused to project-driven models to survive rapid technological change. This requires restructuring around temporary, cross-functional teams that prioritize transformation work over routine tasks, with leaders spending at least half their time on strategic projects rather than daily operations.

Key Questions Answered

  • Ruthless Prioritization: Leaders should launch new projects only after finishing or canceling two to three existing ones, as most organizations could eliminate 80 percent of current projects without impact. Use company purpose as the filter to cut half of initiatives immediately, ensuring capacity exists for strategic work rather than creating organizational overload.
  • Leadership Time Allocation: Senior executives currently spend less than half a day per week on transformation work, dedicating 80 percent of time to operational comfort zones. Leaders must shift to spending at least three days weekly on change projects, making quick decisions in uncertain environments and personally sponsoring cross-departmental initiatives.
  • Six-Month Project Cycles: All transformation projects should run maximum six months before evaluation, allowing organizations to stop, pivot, or accelerate based on results. This strategic fluidity replaces long-term rigid planning with iterative cycles that match the pace of market and technology changes, requiring trust from boards and shareholders focused on long-term capability building.
  • Internal Transformation Capability: Companies must stop outsourcing change to consultants and build transformation muscles within existing employees. Reskill operational workers whose tasks face automation into project roles rather than layoffs. Organizations like Haier tripled profits within five years by redeploying staff into self-directed teams working on innovation rather than repetitive tasks.
  • Structural Experimentation: Start organizational redesign by fully empowering one critical transformation team with 90 percent decision-making authority and priority resource access. This creates visible success that generates demand across the organization, avoiding the resistance that comes from eliminating hierarchy company-wide overnight. Let the snowball effect drive adoption rather than forcing top-down structural change.

Notable Moment

A risk management executive with 25 years in the same banking role faced displacement when automation replaced his department. After two months leading cross-European transformation projects, he reported never feeling more engaged, crediting diverse teams, daily variety, and meaningful challenges that utilized his expertise in ways repetitive operational work never allowed.

Know someone who'd find this useful?

You just read a 3-minute summary of a 27-minute episode.

Get HBR IdeaCast summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from HBR IdeaCast

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

This podcast is featured in Best Business Podcasts (2026) — ranked and reviewed with AI summaries.

You're clearly into HBR IdeaCast.

Every Monday, we deliver AI summaries of the latest episodes from HBR IdeaCast and 192+ other podcasts. Free for up to 3 shows.

Start My Monday Digest

No credit card · Unsubscribe anytime