How Work Actually Flows
The path every idea travels — from a hallway conversation to something customers use.
What you'll learn
- See the full path from idea to live product
- Know which question each stage answers
- Place your own work inside the pipeline
Every idea runs the same gauntlet: prove it works, prove it's worth it, prove it holds up — or it drops out while it's still cheap.
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.
Each gate answers a sharper question than the last — and kills weak ideas while they're still cheap.
The three you’ll hear first
Three terms dominate early-stage conversations, and people often muddle them. Hold onto the distinction below and you’ll sound clear when others sound vague.
The five stages, in order
- Proof of Concept (PoC)
- Tests whether something is technically possible at all. Scrappy, often throwaway. Answers one question: can this even be built?
- Proof of Value (PoV)
- Assumes it works and asks the next question — is it worth the money and effort? — usually backed by real numbers like hours saved or revenue gained.
- MVP (Minimum Viable Product)
- The smallest genuinely usable version you put in front of real users, so you learn whether you’re building the right thing before you build all of it.
- Pilot
- A controlled trial with a limited group of real users, to check the thing holds up under real conditions before everyone gets it.
- Live
- Released to the full audience and supported as a real product.
The whole pipeline in one line
Prove it works → prove it’s worth it → build the smallest real thing → trial it → ship it.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?
The bottom line
Every idea travels the same path — PoC → PoV → MVP → pilot → live — and each gate exists to stop weak ideas cheaply. Spot which stage you’re in, and you’ll know exactly what your work needs to deliver.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.
Here's where each one goes:
- Prove the core idea is technically possible → Proof of Concept — that's the feasibility question.
- Scrappy and throwaway output is fine → Proof of Concept — PoC is allowed to be rough.
- Show the payoff in real numbers → Proof of Value — numbers convince budget holders.
- Aimed at the people who hold the budget → Proof of Value — PoV is for stakeholders and finance.
- Limited rollout to check it survives real use → Pilot & Live — the pilot tests under real conditions.
- Then roll out to everyone and support as live → Pilot & Live — live means full rollout and ongoing support.
Tip: drag with a mouse, or tap a statement then tap a bucket on touch screens. Get one wrong and the answer key appears.
Quick check
1. Which stage answers "can this even be built?"
2. A pipeline gate exists mainly to…
3. The smallest usable version shipped to learn from real users is the…