Prioritizing a project is inevitable
Projects are completed by people, that’s the obvious part that everyone knows. Here’s the part people working on projects don’t know or won’t accept:
Your projects will be prioritized.
Micromanagers and overreaching executives The manager who continually changes his mind about the work that you’ve done. The executive who decides to add 3 weeks of work that’s due in 3 days.
By entitled clients who “know what’s best.” The very same clients who treat your team with subtle condescension, as though you’re the “help” or your beneath them.
Well meaning creative, marketing, legal co-workers The designer who insists on following the new design standards he saw on Smashing Magazine.
People with agendas. People looking to make a name for themselves. Using your project to grab attention and accolades for themselves.
Or, if you handle it well, your project will be prioritized by you. Only that’s not what happens. Unsuccessful projects are dominated by detractors, the people I mentioned earlier.
All-star professionals don’t need to prioritize. Not true.
There’s this attitude with some professionals, the belief that prioritization is for amateurs and the inexperienced. “If you need to prioritize your projects you’re going about it all wrong.”
People argue about frameworks, About methodology. But they forget or ignore the why. The reasons they need to prioritize their projects.
Prioritizing decreases risk.
We didn’t know. This includes areas where you should have known but didn’t. Didn’t want to find out or were unwilling to do the work. This excuse seems legitimate until you realize this fact. You wouldn’t knowingly hire someone who didn’t know what they were doing, so why accept it as an excuse?
What all-stars need to prioritize well
Prioritizing depends on a system. When it comes to prioritizing projects, which one is most effective?