How to Set Priorities a Small Team Can Actually Finish

Why small teams struggle with priorities more than big ones

It's tempting to assume a small team should find prioritisation easier than a big company, since there's less bureaucracy and fewer people to align. In practice the opposite often happens: a small team has no spare capacity to absorb a scattered set of priorities, so the cost of trying to do six things at once shows up immediately as everything moving slowly, rather than being hidden in a large organisation's slack.

The founder is usually the source of the scatter, not the team. New opportunities, new anxieties and new ideas arrive constantly when you're close to the business, and each one feels urgent in the moment it occurs to you. Without a discipline for deciding what actually displaces what, a founder's enthusiasm becomes the team's whiplash — everyone drops what they were doing to chase the newest thing, and very little gets finished.

The case for three priorities, not ten

A useful constraint for a team of five or fewer is to cap active priorities at three at any one time. This isn't an arbitrary rule for its own sake — it reflects the reality that most small teams don't have dedicated capacity sitting idle, so anything beyond a handful of live priorities is really just a list of things nobody has time to properly start.

Capping the number forces a genuinely useful conversation: what matters enough to be one of the three right now, and what has to wait. That conversation is uncomfortable, because it means explicitly deprioritising things that still feel important, but it's far better to have that discomfort openly than to pretend everything can happen simultaneously and then quietly watch none of it get finished.

Write priorities as checkable outcomes, not themes

'Grow the business' or 'improve customer service' are themes, not priorities — they don't tell anyone what to do differently on a Tuesday morning, and they can't be marked done because there's no defined finish line. A workable priority is written as a specific, checkable outcome: what will be true when this is done, by roughly when, and who owns making it happen.

Compare 'improve customer service' with 'cut average email reply time from two days to four hours by the end of the quarter, owned by [name]'. The second version tells everyone what changes, gives a deadline to work towards, and can be unambiguously checked as done or not done. This clarity is what actually changes daily behaviour — the first version just sits on a wall doing nothing.

• State the outcome, not the activity: what will be different, not what will be worked on
• Attach a rough timeframe, even an approximate one, rather than leaving it open-ended
• Name a single owner, even if several people contribute
• Make it checkable: someone should be able to say definitively whether it happened
• Keep the wording short enough that people can actually remember it without looking it up

The real cost of changing priorities mid-quarter

Founders often underestimate how much churn costs compared to simply having a slightly wrong priority for a set period. Every time a priority changes, the team has to mentally close down what they were doing, often losing partially finished work and the context that went with it, then re-orient to the new thing. Do this three or four times a quarter and very little actually reaches completion, even though everyone has been busy throughout.

This doesn't mean priorities should never change — genuinely new information (a client leaving, a serious operational problem, a real opportunity with a tight window) can justify it. The discipline is to treat a mid-cycle change as a deliberate, visible decision with a stated reason, rather than a quiet drift that happens because something newer caught your attention. If you find yourself changing direction more than once a quarter without a clear external reason, that's worth examining as a pattern in itself.

A good test before changing a priority mid-cycle: would you make the same call if you had to explain the reason to the whole team out loud? If not, it's probably enthusiasm, not necessity.

Setting priorities on a fixed cadence

A quarterly cycle works well for most small businesses: long enough that a priority can actually be finished rather than abandoned half-done, short enough that you're not locked into a stale direction for a year. At the start of each quarter, review what was achieved, what wasn't and why, and set the next three priorities deliberately rather than letting the previous quarter's leftovers simply roll over by default.

Involve the team in this conversation where you can, even briefly. People are more likely to stay committed to a priority they had some input into, and they often have direct, ground-level information about what's realistic that a founder, working from a slight distance, doesn't have.

1. Look back: what got finished last quarter, what didn't, and why
2. List candidates for the next quarter, including anything genuinely urgent that's emerged
3. Cut the list to three, explicitly deciding what waits
4. Write each as a checkable outcome with an owner and rough timeframe
5. Share it with the whole team in writing, not just verbally in passing
6. Put a mid-quarter check-in on the calendar to catch drift early

Making priorities visible day to day

A priority that exists only in a document nobody looks at again does little good. Keep it visible somewhere the team actually sees regularly — a shared document referenced in weekly meetings, a line at the top of a team update, a fixed agenda item in one-to-ones. The point is that the priorities should be doing active work shaping decisions, not just sitting as a record of a conversation that happened once.

It also helps to explicitly connect day-to-day requests back to the priorities. If someone brings you a new task or idea mid-quarter, a useful habit is to ask out loud: 'does this help one of our three priorities, or is it something else that should wait?' This keeps the discipline alive between formal review points, rather than only surfacing at the quarterly reset.

What to do when priorities conflict with each other

Even three well-chosen priorities can end up competing for the same limited time, particularly in a team where most people wear several hats. When this happens, resist the temptation to simply add more hours or ask people to somehow do both — that's usually a route to burnout rather than genuine progress on either front.

Instead, force an explicit trade-off conversation: which priority genuinely needs attention this fortnight, and which can afford to move more slowly. Naming the trade-off out loud, and being honest that something is deliberately slowing down rather than pretending everything is proceeding equally, tends to produce far better outcomes than an unspoken scramble that leaves both things half-finished.