Kanban by the book: pull instead of push, flow instead of jams
WORKSPACE.PM carries the Kanban practices as the method describes them: make work visible, pull when capacity frees up, manage flow with data and improve in a steady cadence - embedded in your organisation’s portfolio and reporting.
Where Kanban sits on the spectrum
And which methods are in the neighbourhood
Kanban: flow-based, continuous, evolutionary
Kanban sits at the outermost agile edge of the spectrum - continuous flow instead of fixed iterations, evolutionary improvement instead of big upheaval. In WORKSPACE.PM a flow team works next to timeboxed and classically run workstreams in the same initiative - and teams that want a timebox find Scrum next door.
Where Kanban gets stuck in practice
Four patterns from teams that have a board - but not yet a method
The board exists, the method is missing
Columns are there, but “pulling” means assigning in practice - and the working rules are written nowhere.
Flow is gut feeling
Nobody sees where work sits idle - until a deadline bursts. Measuring happens only afterwards.
Cadence without consequence
The weekly takes place, but open items trickle away between meetings - starting over every week.
An island board next to the project
The team flows, but none of it reaches status report and portfolio - there, data is maintained by hand again.
The Kanban practices - and their home in WORKSPACE.PM
Six practices of the method, each with the tools that carry it in daily work.
Make work visible
The first Kanban practice: every piece of work is a card on a board that mirrors the process.
A board that mirrors your process - down to the card layout
Columns are freely configurable, including a marked done column. Cards show exactly the fields your process needs - from priority via effort with buffer to labels, set up in the layout designer. Swimlanes, filters and selectable sorting make every view of the work visible.
Pull principle and commitment
Work is pulled when capacity frees up - and whoever pulls takes visible responsibility.
Pull by drag, commitment by the accountable person
Cards move through the columns individually or in bulk by drag and drop. Every card has exactly one accountable person - and the commitment, open, committed or declined, can only be set by them: enforced server-side on every change.
Manage flow
Kanban manages the flow of work with data - bottlenecks show up in numbers before deadlines tip over.
Every status change is recorded - flow becomes measurable
Every movement of a card lands in the status transition history - the day-accurate basis for cumulative flow and cycle time on the metrics page. Due dates are watched by an hourly reminder sweep, and on every move the column default duration sets the next due date automatically.
Make policies explicit
Good Kanban systems write their working rules down - visible and binding for everyone.
Rules the server enforces - events that start processes
Commitments only by the accountable person, estimates in the project-wide unit, the done flag following the closing column - the server checks such rules on every change. And every card reports its events, from being moved to a due date approaching, as triggers for automated workflows.
Feedback cadences
Fixed rhythms keep the system honest: look together, decide, refine.
Series with memory - from the weekly to the series evaluation
Meeting series create their follow-up dates themselves; open items move to the next agenda via a click marker, and the series evaluation shows open tasks and decisions across all dates. Recurring work is created by the system as series cards in the rhythm of the rule - with a preview of the next three occurrences.
From team flow to portfolio
Kanban does not end at the team board - the flow carries into the organisation’s steering level.
The same card on every level - with its own rank per board
A card lives simultaneously in the personal inbox, the team, project, program or portfolio board - with its own order per board. Due dates can be coupled to container end dates, and workstreams measure their progress “derived from Kanban” - visible all the way into health indicators and status reports.
Flow in the team, reliability in the report
The flow does not end at the board: through the progress method “derived from Kanban” and the coupling of due dates to container dates, team work feeds health indicators, status reports and the portfolio - while the team simply keeps pulling, card by card.
Where Kanban is at home
Teams and project worlds where continuous flow plays to its strengths
Frequently asked questions about Kanban in WORKSPACE.PM
The tools behind board, pull, flow and cadence
WORKSPACE.PM carries the Kanban practices end to end: freely configurable boards with swimlanes, filters and four views, pull by drag with a binding commitment, a recorded status transition history as the data basis for flow metrics, and fixed cadences via meeting series. The team works by the method - in the same system the organisation reports in.
Cards are pulled through the columns individually or in bulk by drag and drop. Every card has exactly one accountable person, and only they can set the commitment - open, committed or declined, enforced server-side. The personal inbox “My Kanban” bundles everything that flows to you from projects, teams and meetings.
Cumulative flow and cycle time are built from the day-accurate status transition history of every card - plus burndown and velocity on the metrics page. You see where work piles up and how long it really travels - measured, card by card.
Every card reports its events - created, moved, commitment changed, checklist changed, due soon - and each of them can start a workflow: notification, status change, follow-up task. In addition, an hourly reminder sweep watches due dates, and the column default duration sets the next due date automatically on every move.
Series cards are born from a rule - daily, weekly or monthly, with interval, weekdays, time and time zone - and the system creates them automatically in the rhythm of the rule, with a live preview of the next three occurrences. Meeting series create their follow-up dates themselves and evaluate open tasks and decisions across the whole series.
Yes - the bridge is built in: card due dates couple to container dates, a card can be converted into a project container, the Gantt view shows cards with dependency arrows, and workstreams measure their progress “derived from Kanban” - directly visible in health indicators and status reports.
Related methods
When your team changes rhythm or extends the frame
Bring your work into flow - method included
Create the board, set the rules, pull - ready in minutes.