What is Cycle Time?
Cycle time is the elapsed time it takes to complete a single task from the moment you start working on it until it’s finished. It’s a simple, measurable way to see how long work actually takes in practice.
Cycle time measures the real work duration for an item — for example, from when you open a draft to the moment you hit send, or from starting to prep dinner to the dish being finished. It differs from lead time (which often counts from when a task is requested or recorded) because cycle time begins when active work begins. Tracking cycle time can be as simple as timestamping a task’s start and end, then calculating averages, medians and distributions to spot slow or unpredictable work stages.
Usage example
A freelance writer notices emails about article edits sit idle for days. They start logging times and find the cycle time for ‘revise draft’ is typically 6 hours across many small sessions. By batching editing into a single 90‑minute block, their median cycle time drops to 1.5 hours and they deliver faster.
Practical application
Why it matters: cycle time reveals where time leaks and friction live. For busy people juggling many commitments, knowing the typical cycle time for recurring tasks helps with realistic planning, reduces decision fatigue (you can choose tasks that finish quickly when energy is low), and guides habit design (break long tasks into reliably short cycles for momentum). On a team or for repeatable personal workflows, cycle-time trends highlight bottlenecks, inform better scheduling, and improve forecasting. Tools that capture timestamps or estimate task durations (including AI helpers) can automate tracking and suggest the next task to minimise friction and maximise momentum — a helpful complement to systems that prioritise and nudge you toward achievable next steps.
FAQ
How is cycle time different from lead time?
Lead time usually measures from request or idea to delivery (including waiting and queuing). Cycle time starts when active work begins and excludes time spent waiting in a backlog or on someone else. Both metrics are useful but answer different questions.
How do I measure cycle time for short personal tasks?
Use simple start/stop timestamps: note when you begin and when you finish. Track enough instances to calculate a median and typical range rather than relying on a single example. Even approximations (e.g., rounding to 5 or 10 minutes) are useful for spotting patterns.
What counts as a 'good' cycle time?
There’s no universal target — it depends on task complexity and value. Aim to reduce unnecessary variability and to align cycle times with realistic slots in your day (e.g., short tasks under 15 minutes, deep tasks in 60–90 minute blocks). Improvements are meaningful when they lower stress, increase predictability, or free up mental space.
Can AI tools help with cycle-time insights?
Yes. AI can estimate durations from past behaviour, auto-capture start/finish events, and surface tasks that historically complete quickly when you need momentum. These insights are most powerful when paired with simple human habits like explicitly starting and stopping work.