Prioritizing: Nice to Have Vs. Mission Critical

Prioritizing: Nice to Have Vs. Mission Critical

We have some projects that we need to get through, and not enough hours in the day to do it. Can you help me figure out what’s the best way to tackle this problem.

Pull together and prioritize a resource-demand list. Decide if projects are mission critical or nice to have.  Figure out which projects will need skills in-house in the future, and which are one-off, or highly specialized beyond the level of skill your firm is likely to need for the foreseeable future. Decide if you need to hire teachers or doers. Set a budget, and a process to fund projects, and stick to it.

Ask everyone in the company to submit suggestions for projects that need to be completed. Have people indicate:

  • why they put the project on the list
  • whether they have internal resources necessary to implement the project
  • what kind of outside resources may be needed, at what cost
  • how the outcome of the project will benefit the company

Once you have a complete list of potential projects, it’s time to start prioritizing.

Categorize the projects as “need to have” and “nice to have”. The difference between mission critical and nice to have is often a fine line, and opinion may differ based on who’s making the judgment call. Any projects that are listed as “need to have”, ask the department making the recommendation to justify their position. If there are differences of opinion, ask people to meet to discuss the projects in question and make a group decision about “need to have” versus “nice to have”.

Focus on the “need to have” list. Indicate the likely timing of each project as “now”, “short term” = within a year, mid term = within 2 years, long term = over 2 years away. Estimate whether the project can be completed with resources available inside the company, or if additional outside expertise or assistance is needed.

Develop a list of additional resources and skills needed to complete the “need to have” list of projects. Make a list of skills that keep coming up. Separate those from skills that are more “one time” in nature, specific to one project. Repeat need for skills may indicate that it’s time to promote or hire someone.

Think through skills the company will have to have on board, once the projects are completed. For example, if you’re considering programming software, you may not need a programmer in the future. You will, however, probably need someone on board who is skilled enough to operate the software program day to day.

Make a list of future skills needed within the company. Look around the firm to see if there is a ready learner who could step into the role. If not, that set of skills will also need to be filled from the outside, and added to payroll. Factor that into the cost of managing the project in the future.

Now it’s time to decide whether to hire teachers or doers to get the key projects implemented. Some people will come on board and “do for” you. They’ll put the project in motion and get it done. Again, programming software is a good example. The downside of “doers” is that when they leave the company the skills leave with them. Doers are appropriate for one-off projects, that the company doesn’t need to have skill on staff to realize value from the project.

Teachers help to increase the skill and scope of the organization. While leading the project, they help people within the company contribute to the project. Usually teachers are temporary in nature, eventually backing away from the project as employees increase their ability to perform. When they leave, the skills they taught remain behind.

Decide how projects will be funded. How much will come from operating funds, how much from additional growth or profits. Set a budget to fund projects. Put that budget to use cycling through the list of priorities.