Hybrid Teams
Decision-Making card, MethodKit for Hybrid Teams
Card 11 of 65 · MethodKit for Hybrid Teams
  • ThemeGetting work done
  • CardCard 11 of 65
  • Questions5 to explore
  • StepSet up how work flows
Getting work done

Decision-Making

Make & track decisions

In a hybrid team, a decision that lives only in someone's memory or a chat thread is a decision that will get lost or relitigated.

Decision-making is not just about reaching a conclusion. It is about who gets input, who decides, and where the outcome is recorded so it can be found later. In an office, decisions travel fast through hallways and side conversations. In a hybrid team, a decision made between two people on a call or in a chat disappears for everyone else.

Good hybrid decision-making is visible and documented. It means agreeing on how different kinds of decisions get made, who needs to be in the room (or the thread), and what gets written down afterward. When that is clear, the team stops revisiting closed questions and starts building on them.

Make it explicitWrite down your decision-making approach for this team: who decides what, how input is gathered, and where decisions are recorded after they are made.

How strong hybrid teams handle it

The same building block, handled well. These are patterns from teams that work well across locations, offered as illustrations to react to, not rules to copy.

Write decisions down, always

Strong hybrid teams treat a decision as not made until it is written somewhere findable: a shared doc, a task comment, a project update. The writing is not admin; it is the decision.

Separate input from deciding

Teams that work well async are clear about when they are gathering input (everyone can contribute) versus when a decision is being made (one person owns it). Mixing the two creates confusion and stalls.

Name a decision log

A simple shared list of decisions, the date they were made, and who made them saves hours of reconstructing context. Even a doc with bullet points beats nothing.

Set a time limit on async input

When a decision goes to the team for async comment, name a deadline for responses. Without one, the decision just hangs until someone follows up.

Questions for your team

Use these on your own or in a group. There are no right answers, only better conversations.

  1. Where do decisions from last month actually live, and could a new teammate find them today?

  2. How does your team gather input from people who were not in a meeting or did not see a message in time?

  3. Who has the authority to make different kinds of decisions, and is that clear to everyone?

  4. How often are decisions relitigated because people did not know they had already been made?

  5. What would it take for your team to trust that a decision is final rather than tentative?

Watch for

  • Decisions made in meetings without a written record tend to split the team: people who attended remember one thing, everyone else remembers nothing.
  • Consensus-by-default in hybrid teams often means the loudest voice in the meeting decides while remote people stay quiet, not because they agree but because the moment passed.
  • The absence of a decision is itself a decision, and in hybrid teams it quietly blocks other people's work without anyone realising it.