Farwell Team Member Spotlight: Tammy Adler
October 15, 2017
PLD Meetup – “Exploring Projects, Programs and Project Management in a Digital World”
January 23, 2018

Ruthless Prioritization in Project Environments

In resource-constrained project environments where everything is a priority, nothing can truly be a priority. A key responsibility of senior leadership is to provide ruthless prioritization and leave no doubt as to the organization’s top projects.

My experience and research in project environments reinforces my belief that contemporary organizations have the ability to execute their projects consistently. When addressing a troubled project environment, a significant impediment may emerge – lack of direction from senior leaders on the priorities. This holds up project planning and execution, regardless of the technology or project methodology.

In this article, I discuss some scenarios which are solved by regular and ruthless prioritization, and offer a harsh view of senior leaders not willing or able to own prioritization. I close by offering some definitions of “ruthless prioritization”.

Let’s take a look at four scenarios:

The Compromise – Think of the compromise scenario as a defensive play driven by risk aversion. Fear of slowing some projects that are perceived as important in favor of other projects that are also considered important pushes leaders to a poor compromise. No tough decisions are made, no projects are paused or deprived of resources, and all projects continue. But to enable this, resources are diluted and spread thinly across these projects, reducing progress to a crawl.

By prioritizing too many things, the organization makes minimal progress on several projects, but makes no value-creating progress on any. Failure to prioritize value-creating projects surrenders the organization’s competitive advantage.

Trying to Do It All –  The Evil Twin of the compromise approach is the variant that asks teams and resources to work 80-hour weeks to make measurable progress on multiple “priority” projects. Sometimes it is necessary – examples include the rapid growth phases of start-ups, and rare “bet the company” scenarios where this approach is warranted for a short, intense time. One example is Intel during the early 80’s and Andy Grove’s “125% solution.” In that case, Intel made an enormous bet, and the demand of employees to work a minimum of two extra hours per day on top of normal sixty hour weeks was temporary and strategic. It took a toll, but it worked.

Too often, the 80-hour week solution is a consequence of senior leaders’ failure to prioritize a vital few projects, combined with a willingness to place the burden for their failure to prioritize on their teams and resources. In the short term, this can yield some results. Over the mid-term, any realized acceleration of value delivery will be unsustainable. Long-term, this tactic burns out teams, creates toxic workplaces, and results in expensive turnover.

Analysis Paralysis – Slightly less destructive to employees is the analysis paralysis scenario. This emerges when the organization’s senior leaders feel low sense of urgency to prioritize and direct the project teams and resources accordingly. Instead, their endless deliberations and requests for “what-ifs” burn cycles from key resources (with zero value creation), create a false impression of progress and ”careful consideration” while concealing indecisiveness.

The organization afflicted with analysis paralysis can’t advance their major projects. Team morale suffers as they handle maintenance and low-value work while developing scenario after scenario to be considered by senior leaders at their next project review meeting. When any decision is finally made, too much time is lost, hours wasted, that could have been saved by decisive leadership through ruthless prioritization.

All Projects Are High Priority – This worst of all scenarios finds senior leaders telling subordinates to treat everything as top priority and “find a way.”  Leaders engaging in this behavior are, at best, ready for reassignment to less demanding duties – they’ve lost the right to lead. At worst, they’re impeding their organizations’ performance and violating their fiduciary duties.

Prioritization decisions are not easy decisions. As a senior leader, you put your reputation, credibility, and sometimes your career, on the line. That is why you are well-compensated. The expectation is that you know your business, your strategy, and your teams, therefore you can make these tough calls. That’s also why it’s so unacceptable to hold this role and then kick the can to your subordinates. It’s insulting to pass tough priority decisions and consequences to subordinates when you are literally paid to prioritize.

 

The antidote to these project prioritization scenarios is a regular and ruthless prioritization process for department, division, and strategic projects. This seems obvious – yet, some organizations lack this, or lack the ability to pull it together and execute it at critical times.

Much like security or disaster planning, ruthless and rigorous prioritization can’t be reactive or situational. It must be injected into the DNA of companies, and become as routine and natural as coming to work. Making difficult but critical project priority decisions on a regular cadence becomes easier to sustain over time.

In organizations where this becomes the norm, any pause or deviation from this cadence becomes impactful for its absence. The organization comes to rely on the process, even take it for granted. This is a good thing – it means everyone at all levels is bought in, the rhythm is there, and it’s a natural business process.

The challenge is getting this in place. Like all evolution or change, it takes realization of the problem and its importance to the organization to fix it. Once an organization follows through on the commitment to put a rigorous prioritization process in place, they must work it, stick to it – every week.

It means from the C-level down, there is an environment of accountability and rigor in assessing priorities and recognition of the critical role of constrained resources as engines of value creation: They can be driven hard, but selectively, and only when priorities support this, lest you burn them out or run out of fuel.

 

What does ruthless prioritization really mean? In my view and experience, it means having a vital few projects with senior leaders being accountable for ranking them and acting accordingly. It means senior leaders are willing to make (and have the data and process to support) decisions such as:

  • Pulling resources off an important project (and dealing with customer or sponsor fallout) in order to execute on a more important project.
  • Delaying or canceling “nice to have” projects that might please some internal or external stakeholders, but provide little or no value creation or competitive advantage.
  • Stopping all other projects to take advantage of a narrow window of opportunity, and accept that your near-complete product release might slip.
  • Holding off an angry customer for one more sprint in order to ship your near-complete product release (or the exact opposite – delay the release to fix the angry customer situation).

Finally, it means scrutinizing the project and product portfolio every 2 – 4 weeks without fail, and revisiting decisions if new or changed conditions warrant.

To learn how Farwell can help right-size project prioritization to your organization’s needs, contact us to schedule a free Discovery meeting.

 

By Shawn Belling

 

Follow Farwell on LinkedIn, Facebook or Twitter for more tips and trends on your changing industry.

Show all
Action