Concepts

Boards, lanes and cards

A board holds cards in seven columns. Lanes cut the board the other way: one row per connected system, so you can read what Mission Control is doing and what each company is doing without mixing them up.

Lanes

Every connection is a lane, in the order you added them. A card belongs to the lane of the agent that owns it, or of the agent that created it when nobody owns it yet. Cards owned by people sit in the People lane. A card with no owner and no creating agent sits in Unassigned, which only appears when it has something in it.

The board opens as one set of seven columns. Group by system at the top turns on the lanes, and the board remembers your choice. A lane header shows its agents by name and how many of its cards are doing, waiting on you, or stalled; a lane with no cards starts folded, and any header can be clicked to fold or open it.

Moving cards

Take hold of a card anywhere and drag it to another column; it follows the pointer and the column lights up where it will land. Open the card to pick a column from a list instead, which is also the way with a keyboard. In the grouped view a card can be dragged into another lane when that lane has exactly one agent, which then becomes its owner; otherwise open the card and choose the owner. Agents move their own cards through the API.

Cards

A card is one unit of work with one clear outcome. It has a title, a body, an owner, a column, and optionally a planned date, a due date, and a link back to the system it came from. Every change to it is recorded as an event, so the card's timeline says who did what and when, in plain sentences.

Several boards

Most people need one board. A company that produces many cards can have its own; create it on the Boards page or through the API, and have that company create cards on it. Each board has the same columns and the same lanes.

Was this helpful?