People sometimes ask me this as if there’s a clever answer. A tool. A framework. A template. Something they can plug in and suddenly everything starts moving again. After years of working across iGaming platforms, regulatory programmes, product launches, and more recently data and AI implementations, I’ve learned that the answer is usually much less exciting.
It’s not a tool. It’s not a methodology. It’s not even more people. Most of the time, the one thing that would help your project right now is clarity. Not vague clarity. Not “we sort of know what we’re doing” clarity. Real, uncomfortable, specific clarity.
You can usually feel it before you can explain it. The team is busy. There are meetings. Updates are happening. Work is being done. But if someone senior asks, “Where exactly are we?” the answer isn’t clean.
You get a mix of:
“We’re making progress”
“Mostly on track”d
“A few dependencies”
“We just need one more thing from X”
I’ve walked into projects like this more times than I can count. On the surface, everything looks active. Underneath, things are slightly disconnected. No one is doing anything wrong. But no one has full clarity either.That’s when projects start to drift.
A story I’ve seen too many times
I was brought into a product and data initiative recently. It had elements of AI, some legacy systems, and a very real commercial deadline. Everyone involved was capable. The engineering team knew what they were doing. Product had a clear idea of what they wanted. Leadership was engaged. And yet, the project felt stuck. When I asked simple questions like:
“What exactly needs to be delivered for this to be considered done?”
“Which part of this is most at risk right now?”
“What would stop this from going live on time?”
The answers were… close, but not quite aligned. Different people gave slightly different versions of reality. That was the problem..
Clarity is so rare and so valuable
It sounds obvious. Of course projects need clarity. But in practice, it’s surprisingly hard to achieve. Because clarity forces decisions. It forces you to define success properly. To acknowledge constraints. To accept trade-offs. To say, “if we do this, we are not doing that.”
In a regulatory programme I worked on, there was constant pressure to “keep options open”. Which sounds sensible, until you realise it means nothing is truly prioritised. In an iGaming product launch, there were three different interpretations of what “ready for launch” meant. All reasonable. All slightly different. That alone was enough to create weeks of delay. Clarity removes that ambiguity. Which is exactly why people avoid it.
It’s not about more structure
When projects feel messy, the instinct is often to add structure. More tracking. More reporting. More process. I’ve seen this play out in Waterfall environments, Agile teams, Scrum setups, Kanban boards, you name it. The tools change, the pattern doesn’t. You can have the most beautifully organised Jira board in the world and still have no real clarity. Because structure without clarity just organises confusion.
Clarity looks like this in practice
It’s usually much simpler than people expect. It’s being able to answer, without hesitation:
- What exactly are we delivering?
- What does “done” actually mean?
- What are we not doing?
- What is most likely to delay us right now?
- Who owns each critical piece?
Not in a document somewhere. Not in a slide deck. But in a way that the people doing the work and the people making decisions would answer consistently. When that happens, things start to move.
The uncomfortable truth
Getting to that level of clarity is not always pleasant. It often exposes things people would rather not deal with. A dependency that’s been quietly ignored. A timeline that was never realistic. A supplier that is unlikely to deliver on time. A piece of scope that doesn’t fit. I’ve had conversations where, within 20 minutes, the mood shifts from “we’re mostly fine” to “we need to rethink this”. That’s when the project becomes visible for the first time.
Experience helps
This is the part that’s hard to explain without sounding like a sales pitch, so I’ll keep it simple. After working across different types of projects, regulatory, digital, product, data, AI, you start to recognise patterns quickly. You can tell when something is unclear even if everything looks organised. You know which questions to ask to surface the real issues. You know where things are likely to break before they actually do. That’s not something you get from a framework. PMP, Agile, Scrum, Kanban, they all help, but they don’t replace judgement. Clarity often comes from someone stepping slightly outside the day-to-day and connecting the dots.
If your project feels slow, heavy, or slightly out of control, the most useful thing you can do right now is to pause and get clear. Clear on what you’re actually delivering. Clear on what matters this week. Clear on where the real risks are. Clear on who is responsible for what. It sounds simple. It rarely is. But in my experience, it’s the fastest way to turn a project that feels stuck into one that starts moving again.
A small test to help you with this
If you’re not sure whether clarity is the issue, try this. Ask three people involved in the project the same question: “What does success look like for this?” If you get three slightly different answers, you’ve found your problem… and also, your starting point.