Two Teams Becoming One

Why this might help

When two teams merge, you don't just share a calendar — you share a whole way of working. Words mean different things. Meetings run differently. Even a simple task like 'send the update' can mean five different things to five different people. This room helps your team slow down, compare notes, and pick shared habits together. Nobody has to forget where they came from. The goal is to build something new that actually works for everyone in the room.

Does this feel familiar?

Someone uses a word like 'standup' or 'brief' and half the room nods while the other half looks confused.
A task gets marked done on one side, but the other side is still waiting for something they expected to come with it.
Two people schedule the same kind of meeting in completely different ways, and nobody notices until it causes a problem.
One team shares updates in a doc, the other sends a message, and things keep falling through the gap between the two.

Try this together

Pick one small routine — like how you kick off Monday — and have both teams describe how they used to do it. Just listen first.
Make a short list of words your teams use differently. Even five words is a great start. Agree on what each one means going forward.
Try one shared habit for two weeks before deciding if it works. Don't overhaul everything at once.
When something feels awkward or slow, say it out loud. Friction is useful information, not a complaint.
Celebrate small wins together — like the first week everyone used the same check-in format. It sounds small, but it builds trust fast.

Shared Habits Map

Draw two columns on a shared page — one for each team. List how each team currently handles a routine, like sharing weekly updates.
Circle the habits that overlap or feel similar. These are your starting points — they're easier to agree on.
Mark the habits that are very different. Don't judge them yet. Just notice where the gaps are.
Together, pick one habit from each side that the whole team wants to keep, and write it in a third column called 'Ours'.
Review the map after two weeks. Add what's working, cross out what isn't, and keep building from there.

Questions worth talking about

What's one habit from your old team that you'd really miss if it disappeared?

Is there anything we do right now that feels confusing or unclear to you — even if you haven't said it yet?

If we could only agree on one shared way of working this month, what would make the biggest difference?

A few common questions

What if one team feels like their way of working is being erased?

That feeling is real and worth taking seriously. The shared habits map helps because it makes both teams visible side by side — nobody starts as the default. When people see their habits written down and considered, it feels less like a takeover and more like a real conversation.

How long does it take before a merged team actually feels like one team?

Honestly, it varies a lot. Some teams find a rhythm in a few weeks; others take a few months. What speeds it up is having small, regular moments where you work through differences together — not one big offsite and then silence. Consistency matters more than speed.

Can Tindlo help a merged team stay coordinated while they're still figuring things out?

Yes, in a practical way. Tindlo lets both teams see work across time in one shared view — tasks, schedules, and context all in one place. That shared visibility helps a lot when you're still learning each other's rhythms and need to know what's happening without asking someone every hour.

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