How Work Actually Flows

Almost everything you hear in a corporate setting — the acronyms, the meetings, the status updates — is really describing one process: how an idea becomes something real that customers actually use. It rarely happens in a single leap. Instead, the idea travels down a pipeline, and at each stage someone asks a harder question before agreeing to spend more time and money. Once you can see that pipeline, most of the jargon stops being intimidating. You start hearing it as shorthand for “which stage are we at, and what does this stage need from me?”

The delivery pipeline

Think of the pipeline as a series of filters, not a conveyor belt. A conveyor belt moves everything to the end no matter what. A filter is allowed to stop things. Each stage exists to answer one specific question before the organisation commits more resources — and if the answer is “no,” the idea stops there, cheaply, instead of failing expensively after launch.

That “fail cheap” logic is the whole point. A bad idea caught at the sketch stage costs an afternoon. The same bad idea caught after a full build costs months of salaries, a frustrated team, and sometimes a public flop. So the gates aren’t bureaucracy for its own sake — they’re a way of spending small amounts to avoid spending large ones.

The three you’ll hear first

Three terms dominate early-stage conversations, and people often muddle them. Hold onto the distinction and you’ll sound clear when others sound vague.

A Proof of Concept (PoC) tests whether something is technically possible at all. It’s scrappy, often throwaway, and answers a single question: can this even be built? A Proof of Value (PoV) assumes the thing works and asks the next question: is it worth the money and effort? — usually backed by real numbers like hours saved or revenue gained. An MVP (Minimum Viable Product) is the smallest genuinely usable version you put in front of real users, so you can learn whether you’re building the right thing before you build all of it.

Prove it works → prove it’s worth it → build the smallest real thing → trial it → ship it.

After the MVP comes a pilot — a controlled trial with a limited group of real users to check the thing holds up under real conditions before everyone gets it. Pass that, and the work goes live: released to the full audience and supported as a real product.

A quick scenario

Say someone suggests an AI tool that reads incoming invoices. The PoC is a weekend script proving a model can extract the right numbers. The PoV shows it would save the finance team forty hours a month — worth funding. The MVP is a rough but working tool five people use daily. The pilot rolls it out to one department for a month. Go live means the whole company gets it. Same idea, five very different conversations.

How to place your own work

Wherever you sit — engineering, design, sales, operations, finance — your work plugs into this flow somewhere. When you’re handed a task, quietly ask: what stage is this at? A PoC task wants speed and a clear yes/no, not polish. An MVP task wants something real users can touch. A go-live task wants reliability and support. Matching your effort to the stage is one of the fastest ways to look like you “get it.”

It also helps you read the room. If leadership keeps asking “but is it worth it?”, you’re at a value gate, and a slicker demo won’t help — they need numbers. If they ask “does it actually work end to end?”, you’re near go-live, and reassurance about edge cases matters more than new features. The question every team quietly asks is always the same: what stage are we at, and what does this stage need?

Spot the pipeline stage

Read each situation and decide for yourself, then tap a card to flip it and check your answer.

Sort the gates

Drag each statement into the bucket it belongs to — or tap a statement, then tap a bucket. Hit Check placement when you’re done.