Topics
Solo operators don't need handoff coordination. They need the board to be a second brain that doesn't lie about what's actually in flight.

When you're a team of one, the board isn't there to coordinate handoffs. It's there to stop you lying to yourself about what's actually in flight.
Most production-board writing assumes a team: cards move from one person to another, owners-per-phase keep handoffs honest, the dashboard reads as a coordination view. For a solo operator - photographer, freelance editor, single-person workshop, sole proprietor running a small line - none of that applies. There's no handoff. There's only you, and the board has a different job.
The job becomes: keep an honest count of what's in flight, surface what's overdue, and block you from starting a fourth thing when three are open. The team-of-one failure mode is exactly this - pulling new work in before the old work is done, then losing track of which is which. The board exists to make that physically visible.
Owner-per-phase doesn't apply - it's always you. Don't bother filling it; the field becomes noise. WIP limits become more important, not less - solo operators are the worst at honoring "only one thing at a time" without a tool enforcing it. Set the cap to 1 for the active phase. Phase durations matter the most here - a solo operator's biggest blind spot is how long things actually take when there's no one to compare against.
A working solo board in {PRODUCT} has 3-5 phases reflecting the actual stages of your work, a WIP cap of 1 on the most active phase, no per-phase owners (the field is empty), durations on every phase set from observation, and the dashboard pinned to a tab. The whole point is that one open tab tells you what your day looks like - what's overdue, what's blocked, what's free to start.
Solo starter board
Phases: Briefing → Doing → Review → Delivered. WIP cap: 1 on Doing. Durations: measure for two weeks before setting any. Owner field: leave empty. That's the whole setup. Refine after a month of real use - not before.
Run this test once a week if you're solo. Open the board. Count cards across all in-progress phases (excluding backlog and done). If the count is over five, you're carrying more in flight than your real throughput - close some, formally pause others, or move them backward to backlog. The mental relief is immediate and the next week's work is faster as a result.
Three patterns. Phantom phases: phases you set up because the team-tutorial said to, but you never actually use - they sit empty and clutter the view. Delete them. Card hoarding: keeping every job in the backlog forever "just in case". The backlog is a working queue, not a museum; archive jobs that haven't moved in 60 days. Avoiding the overdue list: the dashboard shows overdues for a reason - looking at it daily is the discipline; not looking is how solo operators slowly lose the thread.
FAQ
Free plan, no credit card. We host in Germany. You can export and delete everything self-serve.

Written by
Co-Founder + CEO
Julia is one of the Co-Founders. She handles design, product direction, and most of the support replies that arrive in the morning.
Read next
WIP limits, plainly: why constraining work-in-progress speeds the team up
What WIP limits do, when to set them, and the numbers that work.
Read
Phase durations vs estimates: a different mental model for production work
Why production teams are better off measuring the phase, not the item.
Read
Production Board vs Trello
When sticky notes aren't enough.
Read