Stage Gates, Go/No-Go & UAT

Big projects don’t run as one straight, unbroken dash from start to finish. That would be reckless — you’d commit all the money and time up front and only find out at the end whether it was a mistake. Instead, large projects are split into phases separated by stage gates: deliberate checkpoints where leadership pauses to decide whether the project still deserves to continue.

At each gate comes a Go/No-Go decision. Go means proceed to the next phase. No-Go means stop — the conditions to continue haven’t been met. A gate can also send work back for changes before it’s allowed through. The principle is the same one that runs through this whole course: spend a little to review before you spend a lot to continue. A gate is a chance to kill or correct a struggling project while it’s still affordable to do so.

What a gate actually checks

A gate isn’t a rubber stamp. The people at the table ask real questions: Did this phase deliver what it promised? Is the business case still true? Do we still have the budget and appetite? Have the risks changed? If the answers hold up, the project gets a “Go” and the next phase — and its funding — is released. If they don’t, better to find out now than after another quarter of spending.

This is why you’ll hear “we’re waiting on the gate.” It usually means the work is done but paused in front of decision-makers who haven’t yet said “Go.” The gate exists to make forward motion a conscious choice rather than a default.

UAT — User Acceptance Testing

UAT (User Acceptance Testing) is the stage where the actual end users — not the engineers who built the system, and not the QA team — test it against real-world scenarios and formally confirm it does what they need. The distinction matters. Engineers test whether the system works as built; users test whether it works for the job they actually do. Those aren’t the same thing, and plenty of technically flawless systems fail UAT because they don’t fit how real people work.

Passing UAT is usually the last gate before go-live. “UAT sign-off” is the formal statement that the users accept the system — it’s their signature saying “yes, this works for us, ship it.” Without that sign-off, going live means pushing software onto people who never confirmed it meets their needs, which is exactly how launches turn into disasters.

“Has it passed UAT?” really asks: have the people who’ll use this signed off that it works for them?

Gating on consulting projects

On consulting projects, this gating is often tied directly to milestones and payment. A consultant completes a phase, the client reviews it at the gate, and approval — the sign-off — releases both the next phase of work and frequently the next invoice. The gate is where value is confirmed and money changes hands.

This is why gates carry real weight on client work. “We’re waiting on the gate” can mean the project is paused for client approval, and that the consultant can’t bill — or safely start the next phase — until the client signs. Knowing where the gates sit tells you exactly when approvals (and cash) will happen.

A quick scenario

A vendor delivers a new HR system. Internally, everything passes the engineers’ tests. But during UAT, the HR team discovers they can’t run the one report they need every payday. That’s a No-Go at the go-live gate — not because the software is broken, but because it doesn’t yet do the users’ real job. The fix goes back in, UAT is re-run, sign-off is given, and then it goes live. The gate did its job: it caught a real-world gap before launch instead of after.

How to use it

When you hear “stage gate,” “Go/No-Go,” or “UAT,” translate them into plain questions. A gate asks should we keep going? UAT asks do the real users accept this? If you’re ever the user asked to sign off, take it seriously — your sign-off is a genuine decision, not a formality, and your best moment to catch problems while fixing them is still cheap. And if a project you care about seems “stuck,” check whether it’s really waiting at a gate for someone’s “Go.”

Spot the gate decision

Read each moment and decide what type of gate decision it is, then tap a card to flip it and check your answer.

Sort the gate types and responses

Drag each scenario into the correct gate moment — or tap a scenario, then tap a gate type. Hit Check placement when you’re done.