Why a Prioritisation Workshop Should Be Your First Move on Any New Project

By a project manager who’s learned (sometimes the hard way!) just how important this is.

There’s that moment at the start of every new project where excitement is high, ideas are flying, and everyone is itching to get stuck into the work. Designers are sketching on napkins, developers are exploring new tools, and project stakeholders are dreaming up features faster than you can write them down.

This moment is exciting, but it’s also high risk.

In these early days, before all of the potential features have been discussed and before anyone has fully defined what ‘success’ looks like, this is when the first seeds of scope creep, misaligned expectations, and left-field surprises begin to sprout.

That’s exactly why the very first structured step to take on any project is to run a prioritisation workshop. It consistently proves to be one of the simplest, quickest, and most effective ways to set a project up for success.

So, if you’re leading, commissioning, or contributing to a new website build, here’s exactly why a prioritisation workshop isn’t just helpful - it’s essential.

1. It brings clarity to the discussion

At the start of a project, everyone has a list (sometimes unspoken) of what they think should go into the website.

• The comms team would like advanced search.

• The marketing team needs a blog

• The sales team want a leads pipeline

• The creative team would like animated content

• The legal team wants disclaimers

All valid. All potentially important. All could potentially derail the project.

A prioritisation workshop forces the team to put every feature, idea, and expectation on the table and categorise them accordingly. It’s important that you think about this in terms of your MVP (Minimum Viable Product). At the very top of the list are the absolutes; the things that mean the site/platform can actually function, and at the bottom of the list, you will have the ‘nice-to-haves’.

Traditionally this is a MoSCoW:

• Must-Have - Essential to launch

• Should-Have - High priority but not launch-critical

• Could-Have - Nice to include if time/budget allow

• Won’t-Have (at the moment) - Out of scope for now

However, through trial and error, I’ve found that the language used can be counter productive in terms of keeping the scope agile and flexible. If half of your list is assigned as a ‘Must’ then the project is very likely to go very over budget. By reframing your features into priority levels, everyone can see the project for what it is; a structured set of priorities with a clear path forward, rather than a bottomless wishlist.

1. High - First priority

2. Medium - Next priority

3. Low - Last priority

It’s hard to overstate how much confusion, and potential future frustration this simple activity prevents.

2. It prevents unexpected costs (on both sides)

Expectation misalignment is one of the biggest causes of project derailment, and it always costs more to fix later than to identify out of scope items early on.

Before we started embedding prioritisation workshops into our process, projects often started with what felt like alignment… but really it wasn’t. These are some of the common issues and questions that might arise:

• Why certain features weren’t being delivered

• Why timelines were longer than expected

• Why things were added or removed

• Why the final site didn’t match someone’s ideas

A prioritisation workshop prevents these misunderstandings by making every decision visible, discussed, and agreed collectively so that when you walk out of the room, you have a shared, collaborative and visible understanding.

Expectations aren’t just aligned, they’re aligned publicly, which creates accountability, trust, and transparency for the rest of the project.

3. It protects the project from scope creep

Scope creep isn’t usually a major project curve ball, but a slow drip feeding of ‘minor’ tweaks:

E.g. ‘Could we just add…’

Before long, your timeline is stretched, your budget is strained, and your team is quietly panicking behind the scenes. The beauty of a prioritisation workshop is that it creates a pre-agreed reference point for all future decisions. Any new requests later in the project can be held up against the original prioritisation:

• Is this truly a requirement for the MVP?

• Does adding this mean something else goes?

• Should this be captured as a Phase Two item?

Suddenly, scope management stops being emotional or confrontational. It becomes a logical conversation grounded in a decision-making framework that everyone already bought into.

This is how you keep projects on track without ever needing to say the dreaded, relationship-damaging words: ‘We can’t do that.’

4. It reveals risks early, when you can still do something about them

A prioritisation workshop is one of the fastest ways to expose these risks early, because as you prioritise, you naturally begin to ask:

• Why is this feature a high priority?

• What makes this complex?

• What could stop us doing this?

• What assumptions are we making?

• What do we need before we can start this?

• What could go wrong?

These conversations lead to early risk visibility and, even better, early mitigation planning. When risks are identified at the beginning, they’re manageable, predictable, and can be scoped out. When they are discovered mid-project, they’re expensive, stressful, and often damaging.

5. It builds trust

Clients don’t just want a good website; they want to feel confident, informed, heard, and involved.

A prioritisation workshop demonstrates from day one that you’re transparent, providing strategic guidance and involving the client with decision making.

This sets the tone for the entire relationship. When things get tricky later (and there’s always a moment), the trust and approach that you established in the prioritisation workshop becomes the difference between a productive conversation and a tense escalation.

6. It empowers teams to deliver with focus and confidence

When the team knows exactly what the priorities are, they can design, plan, and build with clarity.

The team understands:

• Where to invest time and energy

• Which decisions matter most

• Where compromises can be made if needed

• What ‘done’ actually means

In a world where teams are often over-stretched and juggling multiple projects, that level of clarity is invaluable.

Teams do their best work when the target stops moving.

So, is a prioritisation workshop worth it? Absolutely.

It’s an hour or two of structured conversation that can save days of debates later, weeks of lost development time, thousands in unexpected costs and an entire client relationship. I wouldn’t start a website build without one.

It’s where clarity begins, trust forms, risks are flagged, and targets are aligned.