A room for Project teams

Risk Talk Without Fear

Name uncertain things early and decide what small signal to watch.

Why this might help

Every project has things nobody's sure about yet. Maybe a key person might leave. Maybe a supplier could be slow. Talking about those wobbly bits early isn't being negative — it's being smart. A friendly risk list is just a short, honest note of what might go sideways and one small sign that would tell you it's starting to happen. Your team doesn't need a fancy system. You just need a habit of saying 'what are we not sure about?' before it becomes a fire.

Does this feel familiar?

  • Someone on your team says 'I think that'll be fine' but can't explain why.
  • A deadline is coming up and you're still waiting on one person to confirm something.
  • Your team keeps skipping a topic in meetings because it feels awkward to bring up.
  • A task has been 'almost done' for two weeks in a row.

Try this together

  1. Set aside ten minutes at the start of a project and ask everyone: 'What's the one thing you're most unsure about?' Write every answer down, even the small ones.
  2. For each worry, agree on one tiny signal to watch — like 'if we haven't heard back by Thursday, that's our warning sign.'
  3. Keep your risk list somewhere the whole team can see it, not buried in someone's notes.
  4. Check the list briefly once a week — not to panic, just to see if any signal has shown up.
  5. When a risk goes away, cross it off together. Celebrating small wins keeps the habit going.

Friendly Risk List

  1. Open a shared doc or board your whole team can reach — something simple, like a table with three columns: Risk, Why It Worries Us, and Watch For.
  2. Go around the team and let everyone name one thing they're unsure about. No idea is too small. Write them all in the Risk column.
  3. For each risk, talk for one minute about why it matters. Keep it short — one sentence in the 'Why It Worries Us' column is enough.
  4. Agree on one concrete, everyday signal for each risk and write it in the 'Watch For' column. For example: 'If the design files aren't shared by Monday, that's our signal.'
  5. Review the list together once a week. Update it when things change, cross off risks that have passed, and add new ones as the project grows.

Questions worth talking about

What's the one part of this project that keeps you up at night, even a little?

If this project hit a wall next week, what would probably be the reason?

Is there anything we're all quietly hoping will work out but haven't actually checked on?

A few common questions

What if people feel like naming risks is being negative or pessimistic?

Reframe it as care, not fear. You're not predicting failure — you're looking out for the team. Try saying 'we're just being honest about what we don't know yet.' Most people relax once they see that naming a worry doesn't make it more likely to happen.

How many risks should we track at once?

Three to six is a comfortable range for most project teams. Too few and you're probably missing something. Too many and the list becomes noise that nobody reads. If you've got more than eight, group the similar ones together so the list stays useful and easy to scan.

Can Tindlo help us keep track of our risk list alongside the rest of our work?

Yes, in a practical way. You can create a work item in Tindlo for your risk list and attach the file or link directly to it, so it lives next to your schedule and tasks. That way the list doesn't get lost in a separate folder while the real work happens somewhere else.

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 teamsProject Managers' WorkshopProject managers