Trestle

A project board your team actually updates

One board per team, status fields that take five seconds, and reports built from what people already do. Setup in an afternoon; no consultants.

The board this week
Backlog In progress Review Done · W45 5 days quiet 31 cards finished median cycle 2.4 d One tap status · stale warnings · standard reports

The board

Four columns, kept honest

Status is one tap from the card; stale cards flag themselves before standup does.

12

Backlog

7

In progress

4

Review

31

Done this week

Work in progress is capped per team; the backlog holds the rest so the week stays honest.

The workspace in numbers

Adoption, cycle mix, and velocity

Computed from the demo workspace dataset shipped with this template.

Weekly active updaters (% of team)
Where cycle time goes (%)
Sprint: planned vs completed (points)

Why boards stay alive here

Three design decisions

Boards that stay honest

Status is one tap from the task, not a form. Stale cards amber themselves after five quiet days so the board shows truth, not intention.

Reports nobody has to build

Cycle time, carry-over, and workload come standard, computed from the moves your team already makes.

Setup in an afternoon

Import the backlog from a spreadsheet, invite the team, done. Migrations from the big trackers are one click.

Start a trial board All features

Getting started

Setup in an afternoon

  1. Bring the work

    Paste a CSV or connect the old tracker; tasks, owners, and due dates land on the board.

  2. Name the columns

    Start with three. Teams that begin simple keep their boards alive; teams that begin complex do not.

  3. Work the week

    Standup reads the board, not a document. Reports fill in behind the work, never ahead of it.

One sprint on the board

From Monday standup to Friday demo

Four checkpoints showing how the board carries a sprint without anyone becoming a project manager.

7

cards in flight, capped per team

Monday — The week is placed

Seven cards move into In progress; the rest wait in the backlog where they belong.

7 cards in flight, capped per team

Wednesday — The amber warning

A card sits untouched for five days; the board flags it before standup, not after the deadline.

5 days before a card ambers itself

Thursday — Review pulls

Review is a pull column: work moves when a reviewer takes it, so nothing queues invisibly.

4 cards waiting in review, visible

Friday — Demo and done

Thirty-one cards finished this week; cycle time updates itself for the retro.

2.4 d median cycle time