Free Kanban Board Template
A UI/UX design kanban board covers intake, audit, flows, wireframes, UI work, and prototype handoff, with each step broken into cards.
Share template
A product design job can look finished in Figma and still fall apart in the build, because the edge cases, missing states, and handoff details never got decided. This Stuart Street Studio - Kanban Board keeps the work moving in an order that forces those calls early, so the buyer can see what’s getting checked before the screens get polished.
The board moves from Intake through Prototype & Handoff, with cards that prompt scope and screen count checks, a heuristic audit, flow mapping with edge cases, and wireframe iteration before the UI kit and specs get locked in. The layout pairs an olive green base with violet accents under Space Grotesk headings and Roboto body text, so the work reads like labeling and documentation, not a mood board.
- Intake This column holds the triage and kickoff cards, covering scope and screen count, plus the access and assets the work needs to start.
- Audit This column captures the heuristic review and the audit report work, including quick wins and technical risks that affect design decisions.
- Flows This column carries the flow-mapping cards, including edge cases and the review step with stakeholders and developers.
- Wireframes This column covers low and mid-fidelity wireframes, plus the interaction details and states that usually get missed until build.
- UI & Kit This column holds the high-fidelity UI work and the component kit work, with accessibility notes and specs alongside the screens.
We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.
What is on this board
6 columns carrying 19 cards. Adding it builds the whole thing as a project in your workspace, with every column and card in place.
| Column | What is in it |
|---|---|
Intake | This column holds the triage and kickoff cards, covering scope and screen count, plus the access and assets the work needs to start.
|
Audit | This column captures the heuristic review and the audit report work, including quick wins and technical risks that affect design decisions.
|
Flows | This column carries the flow-mapping cards, including edge cases and the review step with stakeholders and developers.
|
Wireframes | This column covers low and mid-fidelity wireframes, plus the interaction details and states that usually get missed until build.
|
UI & Kit | This column holds the high-fidelity UI work and the component kit work, with accessibility notes and specs alongside the screens.
|
Prototype & Handoff | This column finishes the job with a prototype, a usability test plan and script, and a developer handoff package that leads into sign-off and closeout.
|
What happens when you install it
- A project is created with its board, 6 columns and 19 cards already there.
- Nothing carries a due date, because a board holds the order the work runs in rather than a calendar. The dates go on once you know when the job starts.
- Every card opens as a task with its own description, assignee, dates, subtasks and files, and columns are renamed, reordered or deleted like any other.
Who it is for
UI/UX designers and product design studios doing app or web interface work that needs a clear path from scope through developer handoff.
Questions about this project template
What’s the difference between a kanban board and a design process checklist?
A kanban board tracks work as it moves through columns, so everyone can see what’s in progress and what’s next. A checklist can say what to do, but it doesn’t show the current state of each piece of work.
How do you keep scope and screen count from drifting during UI work?
Scope control starts with an intake step that confirms scope and screen count before deeper design work begins. The board keeps that check as the first set of cards, so later work ties back to an agreed baseline.
Do developers need to be involved before the UI screens are finished?
Developers usually need to weigh in during flows and wireframes, because technical constraints and missing states show up there first. The board includes a review step with stakeholders and developers before the UI and kit work gets finalized.
What does a heuristic UI audit include?
A heuristic audit is an expert review of an interface area against usability principles. The board’s audit step includes compiling findings and calling out quick wins and technical risks that affect what gets designed next.
What should a developer handoff package contain for product design?
A handoff package typically includes the final screens, component usage, and the interaction states and specs developers need to build accurately. The board’s last column also includes sign-off, so the handoff closes out cleanly.
Do you need usability research for every UI/UX project?
Not every project runs user testing, but many benefit from planning for it early. The board includes a usability test plan and script as part of the prototype and handoff stage, so testing can happen when it’s needed.
Start free today
Your entire business, one login away
No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.
No credit card required
