Managing a portfolio of projects may sound straightforward: allocate people, track progress, and deliver results. But the reality is far more complex. Four major challenges—ranging from resource allocation to organizational misalignment—can quietly sabotage even the most ambitious strategies if left unchecked.
Studies show that multitasking between projects can reduce productivity by over 30%—not because of laziness, but due to the mental effort required to switch gears. Stable teams are not just happier; they’re more profitable.
Four key challenges, when they’re not handled effectively, prevent good portfolio management:
- People allocation and prioritization
- Dependencies and fragmentation
- Disconnect between products and business objectives
- Displaced accountability
People allocation and prioritization
Above all else, not having enough time, money, or people is the biggest constraint on portfolio management. Lack of resources forces leaders to prioritize effectively, reduce organizational drag (such as thrashing) on talent, or push the burden down to a level that doesn’t have the clout to fight back. Unfortunately, many leaders choose the latter. Corporate strategy, not whims or the loudest voice, should drive prioritization.
Effective prioritizing means choosing only the highest-value and highest-risk product development efforts and feeding them to stable teams one at a time. If you have only one scrum team, feed it one development effort at a time. If you have five teams, feed each team only one development effort at a time. If one product is too big for one team, have as many teams as needed swarm around the highest-priority development effort until it’s done; then, feed the next product to the teams.
Racing in reverse is a concept we teach regarding spending too much time on the wrong things. If you’re not effective, you’re racing in reverse. If you’re pushing people to work more, put in overtime, and pump out beyond their means, you increase the number of defects, which increases future work and cost. You can see Mark’s webinar on this topic at https://platinumedge.com/blog/video-mark-laytons-racing-reverse-presentation.
Think about a recent project in your organization. Was talent allocated based on priority—or on availability? How did this impact the outcome?
The prioritization conundrum can be addressed by asking one question: If this product isn’t high-priority enough to have dedicated talent, is it necessary right now? If the answer is no, the best thing to do is finish the highest priority product development effort first and then ask this question again.
Thrashing is the productivity loss caused by teams or individuals constantly switching between tasks or projects, resulting in wasted time and cognitive energy.
Want to go deeper? The science of cognitive switching costs
Cognitive psychology reveals that every time a person switches tasks, their brain must “remobilize”—reloading context, priorities, and goals. Even short interruptions can erode focus and efficiency, leading to significant productivity loss across a team. This is why Scrum’s practice of stable teams with singular focus is so effective at reducing drag.
Reflect on your current work environment: At what level of thrashing does your team typically operate? What might change if your team’s stability increased?
Dependencies and fragmentation
With product development efforts running simultaneously, bottlenecks from dependency issues arise, as do delays because of integration difficulties. In traditional project management, people, money, and equipment are shared. It’s not uncommon for managers to allocate each person across multiple projects (50 percent here, 40 percent there, and the last 10 percent for some other project) just to feel as though they’re using every ounce of power available and making the organization as efficient as possible.
People lose a minimum of 30 percent of time in the cognitive mobilization–demobilization associated with task switching. Having employees divide their time among multiple product development efforts is detrimental to their productivity.
Historically, project managers end up trying to do everything at the same time because they’re under pressure from business owners to deliver across several areas. They end up racing after different goals without separating and prioritizing what needs to be done first. Dependency issues tie the projects in knots because the core dependent project wasn’t executed first.
In a global tech company, developers split across three projects frequently missed deadlines and delivered lower quality work. When management shifted to dedicated teams per project, overall productivity and morale improved—and so did customer satisfaction.
Dependencies are relationships between projects or tasks where one cannot proceed until another is completed, often causing bottlenecks if not managed properly.
Disconnect between projects and business objectives
Most projects begin in line with business objectives, but as time passes, managers continue to brainstorm product ideas and hypothesize all the directions the product could take. Unfortunately, the scope creeps in many directions without consistent feedback loops with customers and stakeholders or daily coordination with the developers. The more time that has passed since the initial planning, the more the common understanding of the objectives breaks down until the original objectives become unknown.
This scope creep reflects the lack-of-prioritization issue at the core of the problem. With scrum, prioritization and reprioritization happen continuously throughout product development at the roadmap, release, sprint, and daily-scrum levels. The product backlog always has the next-highest-priority items ready to go, and products are released in order of priority.
It’s more efficient to keep teams working on multiple projects to maximize utilization.
Splitting attention across multiple projects creates fragmentation, leading to lost productivity and reduced quality. Stable, focused teams actually deliver more value over time.
People allocation and prioritization
Tap to revealThe process of assigning the right resources to the most critical and valuable projects, in alignment with business strategy.
Dependencies and fragmentation
Tap to revealProblems that arise when projects or teams rely on each other, causing bottlenecks, delays, and lost productivity due to divided focus.
Scope creep
Tap to revealThe uncontrolled expansion of project goals or features, often leading to misalignment with original business objectives.
The more stable your team, the higher your profitability.
Visualize how your team spends its time and identify thrashing points.
- List all projects your team is involved in this week.
- Estimate how much time is spent on each, including time lost to context switching.
- Identify one way to reduce fragmentation or increase team stability for next week.
- Understood how resource allocation and prioritization shape portfolio outcomes
- Recognized the impact of dependencies and fragmentation on productivity
Why might continuous feedback loops help prevent the disconnect between product development and business objectives?
Think of a time when a project you worked on lost alignment with its original business objectives. What warning signs were there, and what could have been done differently?
What is the most effective way to reduce thrashing and maximize team profitability, according to Scrum principles?
Stability and focus in team allocation drive the highest productivity and quality in portfolio management.
Splitting teams across multiple projects and neglecting business objectives leads to fragmentation, bottlenecks, and misalignment.
The Shift
- Effective portfolio management depends on prioritizing efforts and stabilizing teams to minimize thrashing.
- Dependencies and fragmented focus erode productivity—dedicated, focused teams deliver better results.
- Continuous feedback and alignment with business objectives prevent scope creep and maximize organizational value.