A company can usually survive a busy season. It can survive a demanding customer, an unexpected issue, a delayed project, or some sudden opportunity that needs immediate attention. What becomes harder to survive is the habit of treating every new issue as the new most important thing. The “flavor of the week” if you will.
You can usually feel it long before anyone says something out loud. A team is working on one priority, then an executive meeting creates another. A customer concern arrives and becomes insanely urgent. A sales opportunity appears and becomes “the most important thing” and “we could make a million dollars!” A compliance item is discovered and becomes non-negotiable (Although I’d argue those are probably legitimately urgent). A project that was already approved suddenly gets paused because something else now has everyone’s attention. Nobody is lazy, or trying to be irresponsible. In fact, the problem is usually the opposite: everyone is trying very hard to respond to everything. Almost everyone I’ve worked with is willing and motivated to work on the most important thing. What they tire of is hearing that everything is the most important thing.
The result is an organization that is constantly moving but rarely gaining momentum. It’s circular movement, like spinning wheels in mud, or riding an escalator up and down. Lots of movement, no progression.
And as the old saying goes, “when everything is important, nothing is important.” The phrase is familiar because most people have lived through it. If every request receives the same level of urgency, teams lose the ability to distinguish between strategic work, operational work, reactive work, and noise. Everything becomes a fire drill. The organization starts rewarding responsiveness more than judgment, and motion more than progress.
Productivity research has warned about this for years. The American Psychological Association notes that task switching creates mental blocks, and that even brief shifts between tasks can cost as much as 40 percent of productive time. That matters because organizational priority switching is so much more than just a calendar problem. It creates cognitive drag across teams that are repeatedly asked to stop, restart, re-explain, re-plan, and re-align.
A favorite author of mine, Jim Collins, is often quoted more bluntly: “If you have more than three priorities, you don’t have any.” In an Inc. interview, Collins connected that idea to the discipline of maintaining a “stop-doing” list alongside major priorities. That is the part organizations often miss! Prioritization is not simply choosing what matters, it’s also choosing what will not receive attention right now. Making a deliberate point to say no.
Peter Drucker’s familiar warning also applies here: “There is nothing quite so useless as doing with great efficiency, something that should not be done at all.” It is possible for a team to work hard, communicate well, manage tasks, and still waste comically enormous effort if the work itself should not have been allowed to compete for priority in the first place.
This is why priority planning should never be reduced to asking which idea sounds best in the moment. The loudest issue is not always the most important issue. The loudest person is probably not the most important person. The newest flavor of the month is almost never the most strategic issue. And the most anxious or most whiney person in the room should not automatically define the organization’s next priority.
I help address this through a structured prioritization planning process that makes priority decisions more objective, consistent, and transparent. The Pye Advisory Group Priority Model evaluates potential projects through four main categories: Strategic Alignment, Operational Impact, Feasibility, and Financial benefits. Rather than relying on urgency, opinion, or the loudest voice in the room, it creates a repeatable way to compare projects against the factors that matter most to the organization.
That kind of structure is crucial because many competing ideas are individually reasonable, but collectively need objective prioritization. A project may improve operations but have weak strategic alignment. Another may support strategy but be unrealistic with current capacity. Another may be financially attractive but create operational strain. Without a consistent model, these conversations almost always become subjective. With a model, leaders can discuss the same criteria, score the same factors, and make better decisions about what should receive attention first.
Good prioritization does not mean the organization ignores urgent issues; it means that urgency is handled in context. Some things must be handled immediately, while other things should be planned. Some things should be deferred, and other should be removed completely. The discipline is in knowing the difference before the organization burns time, attention, and trust because they’re too busy reacting—or overreacting—to everything.
Proper priority planning shouldn’t be treated as administrative overhead, but rather as the discipline that protects strategy from being slowly dismantled by urgency.