Business Analysis

Stalled programmes usually aren’t a delivery problem. They’re a requirements problem.

You’ve got a programme that has lost the plot. The scope keeps moving. The vendor keeps quoting variations. The sponsor is starting to ask uncomfortable questions.

We unblock that — by getting back to what the business actually needs, what the tech can actually do, and what is safe to commit to next.

When to call us

  • A programme is stuck and the requirements keep moving.
  • You’re scoping a major investment and need to know what you’re really committing to.
  • The vendor is quoting variations faster than the project is moving.

Senior BAs with delivery scars

Our analysts have shipped real programmes. They aren’t workshop facilitators with a stack of post-its.

They have sat in the room when go-live went wrong, and they have fixed it. That experience shows up in how they shape requirements — and what they refuse to leave ambiguous.

Across the business and the tech

No translator needed. Our BAs talk to the CFO and the lead engineer in the same week, and neither one feels misunderstood. That’s how you avoid the requirements gap that kills most programmes.

Process improvement and automation

Sometimes the right answer isn’t a new platform. It’s fixing the process before you automate it, or automating the part that’s actually slowing you down. We’ll tell you which one you’ve got.

FAQs

What’s the difference between a BA and a workshop facilitator?

Different work, different people. A workshop facilitator runs the meeting; a senior BA shapes the requirements that come out of it — and refuses to leave the ambiguity that kills programmes later. Our analysts have shipped real programmes. They’ve sat in the room when go-live went wrong, and they’ve fixed it.

We already have a BA on the programme. How do you fit?

You don’t. We work alongside whoever’s in place — product managers, solution architects, vendor BAs, internal SMEs — and bring senior delivery experience to the room. Often the existing BA stays on requirements detail while we shape the bigger picture: what the business actually needs, what’s safe to commit to, and how to unblock what’s stuck.

Do you do process improvement, or just requirements?

It depends on what’s broken. We’ll tell you which one you’ve got — and we’ll tell you honestly. Sometimes the right answer is to fix the process before you automate it. Sometimes the platform is fine and the requirements are wrong. We start by understanding both before recommending either.

Stuck on requirements?

Bring us your messy programme. Thirty minutes, no slides, just a frank conversation about what’s really going on and what to do next.