Skip to main content

Author: Kiron Bondale

Applying Consumer Marketing to Project Prioritization

 It is hard to refute the position that an objective approach to prioritizing projects can result in better realization of business value than subjective methods.  For determining order of execution as well as for resolving resource contention during execution, objective methods can reduce the influences of politics, bias and emotions from the decision making process.

However, this is not an easy evolution for most organizations given the size and complexity of their project portfolios.  With a small portfolio size, a governance committee could use pair-wise comparisons to order the projects, but the significant effort involved in applying this methodology to fifty or a hundred projects reduces the benefits and applicability of this approach.  Scoring models are another commonly used method that can be used to prioritize portfolios – the challenge with these is that scoring of individual factors is often done subjectively, and it is difficult to guarantee a lack of bias from the analysts that are performing the scoring.

Instead of just relying on financial portfolio management theory which emphasizes the use of key performance indicators as a prioritization method, perhaps we can apply some lessons from modern consumer marketing theory?

In her book, The Art of Choosing, Dr. Sheena Iyengar explores a common consumer paradox – we like the idea of choice when selecting products, but we overestimate our capacity to effectively manage those choices.  Faced with too many product choices, the actual task of choosing causes us stress or pain instead of the pleasure that one would expect.  Given this, four approaches are suggested which can be adapted to project prioritization.

  1. Cut the number of options – It will be easier to prioritize 10 critical projects than 50.  Of course, this requires more discipline in selecting which projects will be accepted now, and deferring all others.
  2. Create confidence through expert recommendations – While scoring models must not exclusively be used to prioritize project portfolios, they can “capture” expert opinions and could be a valuable input into a governance committee’s discussions.
  3. Categorize your offerings so that the consumers better understand their options – This is a basic principle of project portfolio management as this categorization or classification can facilitate multi-dimensional analysis which in turn can increase the likelihood of balanced decision making.
  4. Help consumers by gradually introducing complexity – While a governance committee might be overwhelmed if asked to prioritize 50 projects during their first review meeting, starting them off with a handful of projects and then slowly increasing the number as their confidence and capabilities improve might be a better approach.

Bringing objectivity to project prioritization can be an arduous task, but exploring and applying the lessons from other business disciplines may help to ease your governance committees through this transition.

Don’t forget to leave your comments below

Compliance Projects – “Good Enough” is Sometimes Good Enough!

Jim Collins wrote “Good is the enemy of great” as a corollary to Voltaire’s quote “Le mieux est l’ennemi du bien” (“The best is the enemy of the good”).

This phrase comes to mind when reviewing a common approach to improving organizational project management capability.  A catalyst motivates the leadership team to invest in project management improvements – perhaps it’s a string of failed projects, or reduced market share resulting from poor portfolio decisions or from increased time-to-market.  A consulting firm is brought in to implement a governance framework, processes & tools to address the issues.  The organization’s project management capabilities initially improve but then they stagnate.  Sometimes, this is a conscious decision if the perceived benefits resulting from continuous improvement are less than the change management and financial costs incurred.   Unfortunately, a many times it is simply a shift in priority – once project management maturity is no longer the “flavor of the week” or the management team is more keenly aware of the change management involved, the initiative gets shelved.

The one scenario where a commitment to greatness can hurt an organization has to do with regulatory projects.  The FUD (Fear, Uncertainty & Doubt) factor associated with Y2K, Sarbanes-Oxley & HIPAA generated obscene amounts of effort and money to be squandered on projects that at best were gold-plating and at worst created critical opportunity costs for strategic (albeit discretionary) spending.  While we hope that management teams learn from their mistakes, it won’t be long before some new regulation emerges that restarts this process.

This is an opportunity for project management to evolve beyond its traditional role of planning and executing projects to ask the important question “Are we doing the right thing?”. 

The project manager can first confirm that their organization has a defined policy for the regulations.  I’ve witnessed some compliance projects whose scope was purely defined by a third-party consultant – this is akin to the fox guarding the hen house!  If your organization has not established a documented stance for compliance with a particular regulation, the project manager should push for that. 

Once an organization policy is in place, the project manager can facilitate the discussion between the compliance champions (who might be inclined to do too much) and business stakeholders (who might be inclined to cut corners) to forge a scope for the project that everyone can live with. 

At the portfolio level, it can become difficult to prioritize individual non-discretionary projects against the discretionary, strategic ones.  Depending on who has more influence, either the non-discretionary projects will get higher scores, or the discretionary ones will.  A better approach is to not try to prioritize these two different sets of projects against each other individually, but rather to focus on defining what percentage of financial or resource capacity will be allocated to each in aggregate.  Once that has been defined, it can then be left to the appropriate governance committees to decide how this allotted funding will be spent for individual initiatives.

Regulatory and other compliance projects are hygiene factors –  your organization won’t succeed through over-investment in these projects as your clients and regulatory bodies expect that you will be compliant.  Project management can play a key role in helping the organization strike the “good enough” balance between catastrophic risk and gold-plating.

Don’t forget to leave your comments below


Avoiding Speed Bumps when Adopting Agile Practices

Agile methodologies have achieved mass market status for many different types of projects, demonstrating that they are applicable beyond their roots in technology.  Significant coverage at conferences, courses, and in online content have cemented their reputation as a best practice.  This does not imply that an organization hoping to transform itself from traditional to agile approaches can do so without facing some hurdles.  A lot has been written about the organization change management challenges associated with the transition, but here are some other road blocks to realizing the benefits from agile methods.

 1. Executing Iteratively, but Delivering Waterfall

 An attribute of agile methods is that project scope is delivered regularly over the project lifetime.  Some organizations might structure their projects into a set of iterations, but do not deliver customer usable products as an outcome of these iterations (documentation is usually not considered a true business value deliverable).  This limits a customer’s ability to refine or reprioritize remaining work items and can incur opportunity costs if the project team continues to enhance certain “in progress” deliverables which the customer might have considered good enough.  A variant on this issue is a project team that delivers frequently, but the customer insists on waiting till the end of the project instead of evaluating whether their business needs have been sufficiently met.

 2. Insufficient Involvement of the Customer

 Agile methods work best when the distance between the customer and the project team is reduced so that refining and prioritizing the work item backlog, decision making and deliverables review can occur in a timely fashion.  This can require a significant commitment of effort on the part of the customer but selling the necessity for this involvement is preferable to accepting the risks associated with compromises such as having a project team member act as a proxy for the real customer.

 3. Multitasking Impacts both Velocity and Team Cohesion

 Excessive multi-tasking hurts projects, regardless of their delivery approach.  However, it can be lethal for agile projects as the context switching and knowledge gaps that result will reduce productivity, introduce quality issues and make it difficult to predictably calculate or use delivery velocity.  These outcomes can cause organizations to lose faith in their agile initiatives and revert to more traditional approaches without understanding that the issue is not one of methodology

4. Agile does not Imply “just do it”

 Contradictory to the manager’s doctrine from this Dilbert cartoon (http://www.dilbert.com/fast/2007-11-26/), planning is not wholly replaced by execution in agile projects.  While the depth of planning is inversely related to the “nearness” of an activity or decision, a lack of pragmatic, right-sized planning will result in chaos for any project.  This is a part of the agile transition change management process – learning to strike the right balance between too much and too little planning.

Adopting agile approaches can be a positive step towards increasing business value realization and project throughput, but ignoring the potholes along the journey will give your transformation initiative a flat tire!

Don’t forget to leave your comments below


Five Lessons that Project Managers can Learn from Star Trek

Learning using analogy is a common approach used when gaining knowledge, and as most project managers will likely have seen at least a few episodes of the original Star Trek series, here are some PM lessons to be learned from the valiant crew of the Starship Enterprise (beyond knowing when not to wear a red shirt!). 

  1. Infinite Diversity in Infinite Combinations (IDIC). This tenet of Vulcan philosophy supports the rationale for cross-functional teams.  The diversity of the Enterprise’s crew contributed both varied experiences and versatility to their shared purpose and demonstrated that the whole can be more than just the sum of the parts.  Project managers sometimes complain about the challenges of building teams with resources that come from different backgrounds and departments, but it is this variety that can help overcome the toughest project issues or come up with truly innovative solutions.
  2. Leverage the Specialized Skills of Your Team Members (and don’t get in their way!)  While Captain Kirk might have had a general understanding of most disciplines, he still knew when to defer to the advanced scientific, engineering, medical, communication or navigation skills of his direct reports.  Project managers, especially those that have played an SME role in the past, have the tendency to roll their sleeves up.  This is a good thing, but they should ensure that they are not neglecting their primary commitments or stepping on the toes of the team members that are responsible for those areas.
  3. Hold Yourself and Others Accountable for Responsibilities and Commitments Although Kirk was a people person, he had no difficulty in throwing direct reports in the brig if they deserved it, removing himself if he felt he was not fit to command, or challenging authority figures if he felt that they were not “doing the right thing”.  Turning a blind eye to people issues might avoid conflict in the short term, but will undermine team morale or productivity and can eventually fester into a much bigger problem.
  4. Follow Process but Don’t be a Slave to it.  The crew of the Enterprise embraced the policies and procedures established by the Federation, but also broke these rules if the situation necessitated it, so long as their actions were in line with the overall mission or vision of the Federation.  Project management methodologies and policies are tools to be used consistently, but they need flexibility to allow project teams to make their own decisions under special circumstances.
  5. Communicate Bad News Effectively in a Timely Fashion. When the situation took a turn for the worse, Kirk would get on the PA and let the crew know what was going on.  Project leaders sometimes follow the “ignorance is bliss” approach, but a lack of consistent, open communication is a common cause of team morale issues and project failures.  It is important to present bad news in a solution-focused format – Kirk refused to believe in the “No Win” scenario, and that optimism is something else that project managers could adopt!

 Follow these lessons from Star Trek, and your PM career may “Live Long & Prosper”!

Don’t forget to leave your comments below 


An Elevator Pitch for Project Management

If you have been involved with project management for any length of time, you likely have been asked to explain or justify the value of project management.  The challenge in answering this question is that while it is fairly easy to provide a comprehensive response, you may not feel that confident if you are put on the spot to answer this question in a stereotypical “elevator pitch” of thirty words (or seconds) or less! 

A reasonable assumption is that the answer will be role-specific based on who is asking the question so let’s evaluate this from the perspective of key stakeholders.

Project sponsors provide financial and influence funding and support for projects.  In this capacity, they act in a similar fashion to investment managers in a brokerage. To be successful, they need their investments to provide guaranteed returns.  While a project manager cannot be held solely responsible for the successful realization of the benefits of a project, application of project management practices can reduce the surprises and increase the likelihood of projects being completed within established constraints.  This in turn helps to reduce uncertainty for the sponsors so that they can focus on ensuring that the benefits of the project are achieved.

For resource managers, gaining better visibility into the demands on their staff while simultaneously reducing resource contention is a key benefit.  Without knowing when resources are needed, for how long, and with what skills, as well as knowing when changes occur on projects that can affect these commitments, it is very difficult for them to do their jobs as resource providers or to motivate their staff.  Project management can extend the knowledge of planned resource allocations and can improve visibility into those factors that could affect the planned allocation.

For senior executives, projects are a means to an end. They help to deliver the strategic plan for the organization as well as supporting other objectives, including regulatory compliance and maximizing shareholder value.  In the absence of project management practices, the likelihood of success for large initiatives rests solely on the skills, motivation and dedication of staff. This is certainly a critical success factor for any project, but insufficient to assure executives that long running projects will complete on time and on budget, while providing the expected “bang for the buck”.

Finally, let’s consider project resources. They might perceive project management as an administrative burden.  However, with appropriate project management skills being applied to their projects, they should have a better understanding of their short and long term task lists as well as how the work they are doing will benefit the organization.  The issues they encounter on their projects will hopefully be escalated and resolved in a timely fashion, and the expectations for how they perform their work, as well as the performance evaluations they receive, should not be unexpected.

While each role may experience slightly different benefits from the use of project management, a commonality to all of these value propositions is improved predictability.  The advantage of using this simple statement is that the focus of the predictability is in the eye of the beholder. For a sponsor, it is about having their project completed when they expected at a price point they had justified. For a project resource, it could be knowing what they will work on this week and feeling confident that hurdles they encounter will be appropriately escalated and addressed.

So the next time someone puts you on the spot to “sell” project management, counter with “improved predictability.” Of course, when those elevator doors open, you might be invited to deliver a more comprehensive explanation!

Don’t forget to leave your comments below