Cycle time — how to see the flow of work from idea to value
Most organisations talk about ideas. Fewer talk about the value that comes from those ideas. Almost none talk about the invisible journey between the two. Cycle time makes that journey visible.
Cycle time — how to see the flow of work from idea to value
Most organisations talk about ideas.
Fewer talk about the value that comes from those ideas.
Almost none talk about the invisible journey between the two.
Cycle time is a simple way to see that journey.
It tells you how long an idea takes to become something real — something shipped, experienced, and valuable.
Not in theory.
In practice.
In Cultivated terms, cycle time is not a productivity hack.
It is a lens on, and in, the Idea → Value system.
It shows you where ideas stall, where energy dissipates, and where work quietly accumulates friction.
Editor's note — where this sits
This essay sits in the Physics layer of the Idea to Value system — the diagnostic system for understanding what sits between an idea and the value it creates. Cycle time is one of the most practical lenses inside that system: a way of making the invisible journey from idea to outcome visible, and the friction within it observable rather than merely felt.
The Idea to Value system — five layers
What Is Cycle Time (in Human Terms)?
Cycle time is the time it takes for something to move from one meaningful state to another.
For example:
- From idea to shipped product
- From customer request to resolution
- From proposal to decision
- From draft to published work
It is not about speed for speed’s sake.
It is about flow.
Every organisation has a hidden story about how ideas move.
Cycle time makes that story visible.
Variation Is the Signal
Average cycle time matters.
Variation matters more.
If something usually takes three days but sometimes takes three weeks, the system is speaking.
Delays often hide in:
- Governance and approval chains
- Dependencies between teams
- Unclear ownership
- Fear of making decisions
- Reporting rituals that exist to protect people rather than serve customers
- Single points of failure
Cycle time turns organisational folklore, rumours, myths and opinions into observable reality.
Quick reference — where delays hide
The physicsCommon sources of cycle time variation
When something usually takes three days but sometimes takes three weeks, the system is speaking. Variation almost always hides in one of these places.
Governance and approval chains
Work waiting for sign-off from people who are not close to it, do not fully understand it, and are needed only because no one lower has been trusted with the decision.
Look for: decisions that travel upward before moving forward.
Dependencies between teams
Work sitting in a queue waiting for input from another team — often one with its own priorities, its own backlog, and no shared understanding of urgency.
Look for: handoffs that happen without conversation.
Unclear ownership
Nobody is certain whose responsibility it is to move something forward. Work sits in a shared space where everyone assumes someone else is accountable.
Look for: work that exists in group inboxes or shared documents with no named owner.
Fear of making decisions
Work paused while people wait for more information, more consensus, or more certainty — often because making a wrong decision carries more personal cost than making no decision.
Look for: work described as "pending alignment" for weeks.
Reporting rituals
Status updates, dashboards, and governance meetings that consume the time of the people doing the work — without accelerating the work itself.
Look for: time spent describing work rather than doing it.
Single points of failure
Work that can only be done by one person — and stops whenever that person is unavailable, overloaded, or simply the bottleneck in an unexamined system.
Look for: queues that form in front of one person consistently.
The key distinction: Not all delays add cost. Some waiting is genuine — design review, drying time, legal check. The question is which delays are structural (built into the system's design) and which are accidental (nobody chose this, it just accumulated). Cycle time makes both visible.
Cycle Time Is a Signal, Not a Target
This is important.
Cycle time should not become a KPI to chase.
Forcing speed often destroys quality, creativity, and meaning.
Making it a target will morph behaviours to meet the target, and that may not necessarily improve the work.
Cycle time is a diagnostic lens.
It tells you where the system is healthy and where friction erodes value.
In Cultivated language:
It helps you see the potential cost between idea and value.
A Practical Example
In one organisation, we measured recruitment cycle time — from first candidate contact to offer or rejection.
It averaged more than 50 days.
By studying the flow, we removed unnecessary steps, clarified ownership, and simplified decision-making.
Cycle time dropped to around 10 days.
Nothing magical changed.
The system became visible
—and then intentional.
The organisation didn’t just hire faster.
It hired better, with less frustration and lost talent.
Cycle Time Beyond Product Teams
Cycle time applies everywhere:
- Writing and publishing
- Marketing campaigns
- Strategy decisions
- Learning initiatives
- Personal creative projects
I track cycle time in my own work
from idea to script,
from filming to publishing,
from draft to book.
Not to optimise myself into a machine
—but to see where energy leaks and costs add up.
Closing Thought
The questions worth sitting with are simple: how long does it take for an idea to become something real here? Where does work wait, and why? Which delays add value — and which exist out of habit or fear?
Cycle time is not about efficiency.
It is about honesty.
It shows you how your organisation really operates and moves — not how people claim it does.
And once you can see the journey from idea to value, you can begin to cultivate it with intention.
From the Cultivated library
Idea to Value System
Guidebook + video series · Digital
The full system this essay draws from — cycle time is one lens inside a broader diagnostic framework for understanding where ideas stall and how to design systems that move work toward value.
From £19.99
Explore the system →Workshops & Keynotes
In-person or virtual · Bespoke
For teams who want to map their actual cycle time — making the hidden journey from idea to value visible in their own system, and identifying where the real delays are.
Enquire
Start the conversation →
