Less Rework Workshop

Why this might help

Rework is exhausting. You finish something, share it, and then find out the other person had a completely different picture in their head. Suddenly you're starting over. This room is about catching that gap before it costs you time. The fix isn't more meetings — it's asking the right questions earlier. When your team checks expectations out loud, small misunderstandings stop turning into big do-overs. Think of it like confirming a restaurant order before the kitchen starts cooking.

Does this feel familiar?

Someone delivers work and hears 'this isn't what I meant' — but nobody said what they meant at the start.
A task gets passed along and the next person does it completely differently than the first person expected.
Your team has a meeting, everyone nods, and then three people go off and do three different things.
A deadline arrives and two teammates realize they were each waiting on the other to go first.

Try this together

Before starting any task, ask out loud: 'What does done actually look like here?' Write the answer down somewhere everyone can see.
When you hand work to someone, spend two minutes describing what you're handing over and what you expect back — don't assume they'll figure it out.
After a decision gets made in a meeting, have one person read it back in plain words before the call ends.
Pick one upcoming task this week and run a quick expectation check with whoever's involved — just five minutes, no agenda needed.
When something gets repeated or redone, pause and ask 'where did our pictures stop matching?' — that answer helps you catch it earlier next time.

Expectation Check

Pick one piece of work that's about to start — something real, not hypothetical.
Ask everyone involved to write down, in one or two sentences, what they think the finished result will look like.
Read the answers out loud together and circle any spots where the descriptions don't match.
Agree on one shared description of done and write it somewhere the whole team can find it later.
After the work is finished, take two minutes to check whether what you delivered matched what you agreed — and note anything to adjust next time.

Questions worth talking about

When was the last time we redid something — and what did we actually disagree about?

Do we usually know what 'finished' looks like before we start, or do we figure it out at the end?

Is there one handoff on our team right now where nobody's totally sure what the other person expects?

A few common questions

This sounds like more process. Won't it slow us down?

It feels that way at first. But a five-minute check at the start almost always takes less time than fixing work that went the wrong direction. You're not adding a step — you're moving a conversation from the end of the task to the beginning, where it's much cheaper.

What if people feel awkward saying they don't understand the expectations?

That's really common. It helps to make the check a team habit rather than a personal question. When everyone does it together, it stops feeling like an admission and starts feeling like normal preparation. Nobody's singled out — the whole team is just getting on the same page.

Can Tindlo help with this?

It can support it. Tindlo lets you attach a Brief, files, and comments directly to a work item, so the agreed expectation lives right next to the task. When your team can see the context alongside the schedule in one shared view, it's easier to spot when something's missing before work begins.

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 leaders Product Operations CircleProduct operations teams Project Managers' WorkshopProject managers