IntermediateAgile & ScrumFree prompt

Kanban Board with WIP Limits and Flow Policies

Design a complete Kanban system with WIP limits and flow metrics.

Design a Kanban system that optimizes workflow, reduces bottlenecks, and increases delivery predictability using WIP limits and flow metrics.

At a glance

Access

Free prompt

Open to copy — no account or payment needed.

Prompt objective

Design a Kanban system that optimizes workflow, reduces bottlenecks, and increases delivery predictability using WIP limits and flow metrics.

Real use case

PixelCraft, a digital agency, has 3 teams (design, dev, QA) and work accumulates between phases. Items sit in queue for an average of 12 days before being pulled. The operations director wants to implement Kanban to reduce lead time from 22 to 10 days.

Customize these fields first

COMPANY NAMEDESCRIBE THE CURRENT WORKFLOW, E.G. BACKLOG → DESIGN → DEV → QA → DEPLOYNUMBER PER STAGEWORK ITEMS PER WEEKDAYSSTAGE WHERE WORK ACCUMULATES

Replace the placeholders with your own context before you run the prompt. That usually improves the first output more than adding more instructions later.

Prompt

Design a complete Kanban system for:

Organization: [COMPANY NAME]
Current process: [DESCRIBE THE CURRENT WORKFLOW, E.G. BACKLOG → DESIGN → DEV → QA → DEPLOY]
Team size: [NUMBER PER STAGE]
Weekly volume: [WORK ITEMS PER WEEK]
Current lead time: [DAYS]
Target lead time: [DAYS]
Main bottleneck: [STAGE WHERE WORK ACCUMULATES]

The system must include:
1) Kanban board design:
   - Columns with sub-columns (Doing/Done for each stage)
   - Expedite lane for urgent items
   - Blocked lane with unblocking policy
   - Buffer between stages (when necessary)
2) WIP limits per column:
   - Calculation based on capacity (explain the formula used)
   - System-wide WIP limit
   - WIP violation rule (when it is acceptable to break the limit)
3) Explicit flow policies:
   - Entry and exit criteria for each column
   - Service classes (Standard, Fixed Date, Expedite, Intangible)
   - SLA by service class
   - Prioritization policy (FIFO, WSJF, cost of delay)
4) Meeting cadence:
   - Daily standup (format: board-focused, not person-focused)
   - Replenishment meeting (backlog refilling)
   - Delivery planning
   - Service delivery review (with CFD)
5) Flow metrics:
   - Weekly throughput
   - Lead time and cycle time (with P50, P85, P95 percentiles)
   - Cumulative Flow Diagram (CFD) — how to read and interpret
   - WIP age and blocker clustering
6) Phased implementation plan (4 weeks)

Format: visual board layout in text, policy tables, metrics dashboard, and rollout plan.

Open directly in an AI — the text is pre-filled:

How to use this prompt

  1. 1Replace the key placeholders first: COMPANY NAME, DESCRIBE THE CURRENT WORKFLOW, E.G. BACKLOG → DESIGN → DEV → QA → DEPLOY, NUMBER PER STAGE, WORK ITEMS PER WEEK.
  2. 2Replace any bracketed placeholders like [this] with your own context.
  3. 3Add extra background information when you want more tailored results.
  4. 4Combine multiple prompts in one conversation when you need a richer output.
  5. 5Save your best-performing prompts so they are easy to reuse later.

Next best step

Open the guide first, then branch only if you still need more.

A guide for choosing prompts, tools, courses, and workflows without creating expensive tool sprawl.

If this prompt is close but not quite right, generate variants next. If the job is recurring, move into the course library after the guide.

Related prompts

View all

Explore other prompt categories

Move sideways into adjacent libraries when the current category is not the full answer.

Every prompt here is free. The course teaches the thinking behind them.

Copy as many prompts as you like. When you want to move from single prompts to a repeatable AI workflow, Learn AI in 30 Days walks through it, one day at a time.

Get the courseSee the 30-day curriculum first

Buy the course once ($15/$20 by length), or go all-access for $10/mo with a verifiable certificate.