Guides
A board only works if everyone reads it the same way. Here's the short walkthrough that gets a new person updating cards correctly on day one instead of guessing for a month.

Key takeaways
Explain the workflow left to right before any feature.
Make the exit criteria explicit and written down.
Light supervision on one genuine piece of work.
WIP caps + watch one board review before going solo.
The first thing a new person needs is not where the buttons are, it's how your work flows. Walk them left to right through the columns: what each stage means, what has to be true for a card to enter it, and who tends to own work there. The tool's features are obvious and discoverable; your team's specific pipeline is not, and getting that mental model right on day one prevents weeks of cards sitting in the wrong place. If your columns aren't yet clearly defined, designing them first makes onboarding much smoother.
This is the single biggest source of new-person confusion. When is a card ready to leave "in production" for "review"? Does "review" mean a glance or a sign-off? Every team has unwritten exit criteria, and a newcomer can't see them. Spend ten minutes making them explicit, ideally written somewhere everyone can point to. A shared definition of done per column is what stops a board from drifting into everyone-interprets-it-differently chaos.
Write the 'definition of done' on the board
The exit criteria for each column shouldn't live only in senior people's heads. A short note per stage (or a pinned card) means every new person, now and in a year, onboards from the same written source instead of absorbing folklore.
Skip the sandbox. Give the new person a small but real piece of work and have them move it across the board under light supervision: pick it up, update it as they go, hit the exit criteria, move it on. People learn a board by using it on something that matters, not by clicking around a fake demo. One genuine card moved correctly teaches more than an hour of explanation.
Two last pieces. If you use work-in-progress limits, explain why a column has a cap, otherwise a newcomer reads a full column as "I'm blocked" instead of "the system is telling us to finish before starting more". And have them watch one standup or board review before running their own updates solo. Seeing how the team reads the board together, what gets flagged, how blockers get raised, is the fastest way to absorb the unwritten etiquette. Production Board makes the state visible; this is how a new person learns to read it the same way everyone else does.
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, development, product direction, and most of the support replies that arrive in the morning.
Read next
Setting up your first production board: a five-step walkthrough
From empty board to running production in an afternoon.
Read
How to set up swimlanes for multiple product lines on one board
Keep product lines separate without splitting into separate boards.
Read
How to forecast a realistic delivery date from your board (instead of guessing)
Turn your board's past cycle times into a defensible delivery forecast.
Read