A Kanban workflow shows the stages a task passes through and controls how much work the team takes on at once. Each task appears as a card on a board. Columns show its progress, from a new request to completed work.
The board might say a brochure is in Review. To get it delivered, the team also needs to know who is reviewing it, what needs approval and when to follow up.
Kanban uses a pull system: people take on the next task when there is capacity to handle it. The team limits unfinished work, watches for delays and adjusts the process as it learns. These practices are central to the Kanban Method.
A Kanban Workflow Example for Client Requests
Take a design team producing a client brochure. The designer needs an agreed brief, an internal check and client approval before sending the final files.
| Stage | What happens here |
|---|---|
| Requested | Confirm the brief, required files, deadline and client approver. |
| Ready | Select the request when design capacity is available. |
| In Progress | Finish the draft and attach the version that needs review. |
| Internal Review | Check the copy, design and file requirements. Resolve corrections. |
| Client Approval | Record approval and deliver the agreed final files. |
| Delivered | Keep the approval and delivery record with the completed task. |

In this workflow, a finished design waiting for client approval stays in Client Approval. The designer has completed their part, but the team still owes the client a delivery.
Give someone responsibility for that wait. For example, the account lead could send the review request, record the agreed response date and follow up if it passes. The card then shows the next action and its owner.
This is an example workflow. Adapt the stages and rules to your team.
How to Create a Kanban Workflow
1. Choose One Process and Define When Work Starts
Start with a process you can describe clearly, such as client design requests. Walk through a recent request with the people who handled it. Include the handoffs and approval waits that actually happened.
Then mark the start and finish points. For the brochure example, work starts when a designer pulls the card from Ready into In Progress. It finishes when the approved files reach the client.
Requests waiting in Ready sit outside those boundaries. Design, internal review and client approval sit inside them. Keep these definitions consistent when measuring delivery time.
2. Give Each Column a Clear Rule
Use columns for steps that change what happens next. A separate Client Approval stage makes sense when someone outside the team must respond. A column for every small design edit would make the board harder to scan.
Write a short rule for each handoff. For example:
Move to Internal Review when the draft, source files and review checklist are attached.
Agree on what “finished” means, too. In the brochure example, approval alone is not enough. The client must have the final files.
3. Put Enough Information on Each Card to Start Work
A card called “Brochure” leaves too much to guess. Use a title such as “Prepare the autumn product brochure” and include:
- The brief and a link to the current files.
- The person responsible for the next action.
- The deadline and named reviewer or approver.
- The requirements for completion, such as an approved print PDF and web PDF.

Keep revisions on the same card so the reviewer can find the latest version and earlier decisions.
If a request includes several separate deliverables, consider giving each its own card. A brochure, landing page and email campaign may have different owners and approval dates.
4. Set Work in Progress Limits
A work in progress limit, or WIP limit, caps the number of unfinished items in a defined part of the workflow.
Suppose this design team sets a limit of two cards in Client Approval. Two brochures are already there when a third passes internal review.
Under that rule, the third brochure waits in Internal Review, marked “Ready for client approval.” The account lead follows up on the existing approvals. The team checks the growing queue before starting another design.
Two is an example limit, not a standard. Choose limits with the people doing and reviewing the work, then check whether those limits help tasks finish. Raising a limit to hide a queue leaves the approval delay unresolved.

5. Review the Work That Needs Attention
In the team’s board review, start with blocked cards and the oldest unfinished tasks. Assign the next action before discussing new requests.
If internal reviews keep slipping, find out why. A reviewer may need time reserved in their schedule. Repeated corrections may point to a missing requirement in the brief.
Make a change that addresses the delay, then watch the next few requests to see whether it helps.
What to Do When a Task Gets Stuck
Keep blocked work visible where it stopped. If the brochure cannot proceed because the client has not supplied product images, mark that card as blocked. Record what is missing, who will request it and when they will follow up.
The task still counts as work in progress. Moving it into a separate holding area must not make unfinished work disappear from the count. Keeping a blocked card in its current stage also preserves the location of the delay, as ProKanban’s guidance on blocked work explains.
For revisions, return the card to the stage that needs work and keep its original start date. Resetting the date would hide time already spent on the request. Add the client’s feedback so the designer knows exactly what needs changing.
For urgent requests, agree on who can approve an exception to the WIP limit. Record which existing work will be delayed. An urgent label cannot create extra capacity.
How to Measure a Kanban Workflow
The Kanban Guide identifies four core flow metrics.
| Metric | What to measure |
|---|---|
| Work in progress | How many tasks have started and remain unfinished. |
| Throughput | How many tasks finish in a chosen period, such as a week. |
| Work item age | How much time has passed since an unfinished task started. |
| Cycle time | How much time passed between a completed task’s start and finish. |
Use the start and finish points you agreed earlier. If a brochure spends two days in design and four days awaiting approval, both periods belong in its cycle time. Counting only hands-on work would hide the wait.
Compare similar requests. A one-page flyer and a 40-page catalogue may share a board, but a change in that mix can affect delivery times. Check the work behind a number before deciding that the team has become faster or slower.
You can also set a service level expectation: a delivery forecast with a time and a probability. For example:
We expect 85% of brochure requests to finish within 10 calendar days of starting.
Those numbers are illustrative. Use your own delivery history to set the expectation. If you have no history, label the starting estimate and revise it as results arrive. It is a forecast, not a guaranteed deadline.
Kanban Workflow Examples for Other Teams
| Team | Example stages | Detail to define |
|---|---|---|
| Content marketing | Ready → Writing → Editing → Approval → Published | Name the final approver and specify who publishes approved content. |
| Purchasing | Submitted → Budget Review → Approved → Ordered → Received | Decide whether the request finishes when the order is placed or when the goods arrive. |
For either workflow, give tasks a clear owner and agree on capacity before pulling more work into active stages. Use a separate board when the process or completion rules differ enough to make a shared board confusing.
Manage Your Workflow in Skarya
Skarya combines Kanban boards with document management, collaboration and native timesheets. It also offers Gantt charts for projects that need a schedule view.
Bring one current project to the Skarya team. Ask how you can organise its tasks, manage review documents and record time in the platform.
Talk to Skarya about your team’s workflow.