A room for Project managers

Project Managers' Workshop

Coordinate plans without losing the context behind changes, risks, and handoffs.

Why this might help

Projects fall apart quietly. Not because people stop caring, but because the reasons behind decisions get lost. Someone changes a deadline and nobody writes down why. A risk gets spotted in a meeting and never makes it into the plan. Then a new person joins the handoff and has to guess. This workshop is about one habit that helps: keeping a short, living record of the context behind your project — not just what's happening, but why, and what your team needs to watch out for.

Does this feel familiar?

  • A teammate asks why the launch date moved and nobody can remember the reason.
  • You hand a project to someone else and spend an hour on a call just explaining the backstory.
  • A risk you flagged two weeks ago surprises the whole team because it wasn't written down anywhere.
  • Someone makes a decision that contradicts an earlier one because they didn't know the earlier one existed.

Try this together

  1. Start a project context brief on day one — even a half-page is better than nothing.
  2. Every time a key decision changes, add one sentence explaining why it changed.
  3. Before a handoff, read the brief out loud with the person taking over and fill any gaps together.
  4. Keep a short 'risks we're watching' section and update it after every team check-in.
  5. When the project closes, spend ten minutes writing what future-you would want to know next time.

Project Context Brief

  1. Create a new work item in Tindlo and name it after your project — this becomes your context brief's home.
  2. Open the Brief field and write a short summary: what the project is, who it's for, and the one thing that must go right.
  3. Add your key files and links directly to the work item so the context and the materials live together.
  4. Use the Comments section to log decisions and changes as they happen — date each one so the timeline stays clear.
  5. Place the work item on the shared Week view so your whole team can see where the project sits alongside everything else.

Questions worth talking about

If someone new joined your project tomorrow, what's the one thing they'd struggle most to figure out from your current docs?

When was the last time a decision got made twice because the first one wasn't written down — and what did that cost you?

How does your team currently track the 'why' behind a change, not just the change itself?

A few common questions

How is a project context brief different from a project plan?

A project plan tracks tasks and dates. A context brief tracks the thinking behind them — why a deadline exists, what risks you're watching, and what someone needs to know to make good decisions. Think of the plan as the map and the brief as the notes you'd scribble in the margin.

How long should a project context brief actually be?

Short enough that people read it. One page is a good target. If it's longer, it usually means you're mixing in task lists or meeting notes that belong somewhere else. The brief should answer three questions: what's this project, what's changed, and what should we be worried about?

Can Tindlo help us keep the brief connected to the actual work?

Yes, in a practical way. Each Tindlo work item has a Brief field, a Comments section, and space for files and links. So your context note lives right next to the scheduled work on a shared timeline — not in a separate doc your team forgets to check.

Keep the story close to the schedule

A date makes more sense when you can also see the reason, the owner, and the work around it. Tindlo brings those pieces together when a calendar alone isn't enough.

See how Tindlo works →

Where would you like to go next?

Engineering Leadership ExchangeEngineering leadersProduct Operations CircleProduct operations teamsChief of Staff Operations RoomChiefs of staff