4 min read

When everything is important, nothing is

Growing organisations rarely suffer from a lack of opportunities. The real challenge is deciding what deserves attention — and what can wait.

A desk covered with competing priorities

Imagine a team discussing a possible new offer. The offer makes sense. Customers have asked for it, the team understands the work and the idea fits the direction of the business. Then another proposal arrives. It also makes sense. Each has a clear benefit when considered alone. The difficulty begins when both need the attention of the same people.

The discussion can quickly become a contest between persuasive cases. Someone describes the opportunity. Someone else explains the risk of waiting. Existing work remains in the background, although it will carry much of the cost. Agreement to proceed sounds positive in the meeting. The consequences become clearer when the people doing the work try to fit it into their day.

Follow the choice through

Take the proposed offer. Before approving it, the team needs to consider what preparing it would require. Customer questions need answers. People need to understand what can be promised. The organisation needs a way to handle problems once the offer is available. Work that looked contained now reaches into areas already occupied by other commitments.

What should take priority? The answer depends on what the organisation most needs to change and whether this offer can help change it. Customer interest matters, but it does not settle the choice. The team also needs to understand the effort required, the consequences of waiting and the work that would receive less attention if the offer went ahead.

Suppose the business is struggling to support what it already sells. Adding an offer could deepen that problem. There may still be a reason to proceed, but the reason has to account for the strain. If improving support is the immediate priority, postponing the offer becomes a decision that protects the work the organisation has chosen to do.

Now suppose the existing offer is losing relevance and support is steady. The balance changes. Exploring the new offer may deserve attention sooner. The idea itself has stayed the same. Its place in the organisation's priorities has changed because the surrounding problem is different. A convincing proposal needs to be read in that context.

Give waiting a reason

A decision to wait should be specific enough to revisit. The team might need to resolve a support problem, understand demand better or finish a commitment already under way. Recording that reason keeps postponement from becoming a quiet rejection. It also keeps an idea from returning to every meeting without anything meaningful having changed.

The work that continues needs the same clarity. People should be able to explain why it has priority and what would justify reconsidering that choice. This makes it easier to handle new requests. Instead of weighing each request against personal preference, the team can consider its effect on the commitment already made.

Priorities also need to show up in ordinary decisions. If every new request is accepted, the stated direction has little effect on the work. If people are told to focus but remain responsible for everything they were doing before, they have been given a problem to absorb. Something needs to be delayed, reduced or stopped.

The proposed offer may eventually go ahead. It may change as the team learns more. It may be set aside because the organisation has a stronger reason to spend its attention elsewhere. Each outcome can follow from careful judgement. The important part is that the choice remains visible, along with the work it makes possible and the work it asks to wait.

All insights