What this template helps you do
This page is written for operations managers, CI managers, Lean Six Sigma practitioners, supervisors and team leaders working in project and programme delivery. It focuses on a single search intent: step by step guide — simple cycle time log: step by step guide, so every section below is shaped around that question rather than offering generic background.
By the end of this guide you will know when to use the Simple Cycle Time Log, how to complete it section by section, the most common mistakes to avoid and the next practical step to take. The intended next action is to download the template and put it to work on a live piece of project and programme delivery improvement work.
The Simple Cycle Time Log is a working document, not a deliverable. It belongs at the workplace where the team can update it as decisions are made and evidence is captured, rather than sitting in a folder until a review meeting.
When to use this template
Reach for the Simple Cycle Time Log at the point in the work where decisions or evidence need to be captured in one shared place rather than scattered across notes, emails and spreadsheets. The right moment is usually earlier than people think.
- At the start of a piece of project and programme delivery improvement work, to agree scope and ownership before activity begins
- When the team needs a single source of truth that survives shift handovers and people changes
- Before a tier or steering review, so the conversation is about the work rather than about the document
- When a previous attempt drifted because the inputs and decisions were never written down in one place
- When new team members need to pick the work up without a verbal handover
If none of the situations above apply yet, save the template and come back to it — using it on work that is too small or too informal can make the work feel heavier without making it any clearer.
How to complete the template
Open the Simple Cycle Time Log, work through it section by section with the team, and sign off each step before moving on. Treat the document as a live working tool, not a one-off submission.
What to confirm before you start
- The scope of work the Simple Cycle Time Log applies to, agreed in writing with the sponsor
- The owner who will keep the Simple Cycle Time Log up to date between meetings
- Where the completed Simple Cycle Time Log will be stored and reviewed
- Which team members are involved in completing each section
- The cadence at which the Simple Cycle Time Log will be updated — usually weekly during active work
How to work through it
- Fill in sections in the order they appear; the order is part of the design
- Capture decisions and the reason for them, not only the outcome
- Keep entries short enough to be read at the workplace, not only in meetings
- Mark sections as draft, agreed or done so reviewers can see status at a glance
- Update the Simple Cycle Time Log as new evidence emerges rather than waiting for the next review
Worked example: a filled-in scenario
Filling in the Simple Cycle Time Log template for step by step guide in project and programme delivery, working section by section and signing off each step before moving on.
| Detail | Captured in the template |
|---|---|
| Detail | One Simple Cycle Time Log workbook covering project and programme delivery |
| Detail | completed by a team of 8 over 7 sessions |
| Detail | with 9 actions captured and 7 owners assigned. |
The point of the example is to show what a healthy first version of the Simple Cycle Time Log looks like — concise, dated, and clearly owned. Adjust the wording for your own work, but keep the level of detail roughly the same.
Download the templateCommon mistakes when using the template
- Filling in the Simple Cycle Time Log template after the fact rather than during the work
- Skipping sections of the Simple Cycle Time Log because they look optional
- Treating the Simple Cycle Time Log as a deliverable rather than a working document
- Sharing the Simple Cycle Time Log without naming an owner for each row
- Not reviewing the Simple Cycle Time Log at the next tier meeting, so it goes stale
Each of the points above appears repeatedly in real reviews. Catching them early is much cheaper than catching them after a change has been made on the floor.
Download and next steps
Download the Simple Cycle Time Log as an .xlsx workbook and start working through it with the team.
Download practical Lean and Six Sigma templates to structure the next stage of your improvement work.
Build the skills behind the work with practical training designed for operations people.
Use guided software to capture the data, structure the project and report progress with the team.
Frequently asked questions
How should the Simple Cycle Time Log be filled in for step by step guide in project and programme delivery?
Open the Simple Cycle Time Log, work through it section by section with the team, and sign off each step before moving on. In project and programme delivery, this keeps the step by step guide work auditable and stops the document drifting out of date.
What is the Simple Cycle Time Log for?
The Simple Cycle Time Log captures the decisions and data that a piece of improvement work depends on, in a format the next person can pick up without you. It is a working document, not a deliverable.
Who should own the Simple Cycle Time Log?
One named person per page, agreed at the start. They do not have to do all the work; they do have to make sure the Simple Cycle Time Log reflects what the team has actually decided.