ThemeGetting work done
CardCard 48 of 65
Questions5 to explore
StepSet up how work flows

Tools

Software used for work & collaboration

Your tools are not neutral: the ones your team agrees to use, and how it uses them, shape who can participate and who gets left behind.

Tools are the software a hybrid team uses to do work and work together: chat, video, project management, document collaboration, file storage, and more. Most teams have more tools than they need and fewer agreements about how to use them than they think. In a hybrid team, the tool stack is the workplace. If someone cannot access a tool, does not know a file lives there, or uses a different tool for the same job, they are partially cut off from the team.

The goal is not to minimise the number of tools but to make sure the team has genuine shared agreements about which tools they use, what each one is for, and how to keep them accessible for everyone regardless of location or device.

Make it explicitList the tools your team uses, what each one is for, and confirm that everyone has full access to each one they need to do their job.

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.

Assign a job to each tool

Strong hybrid teams avoid tool overlap by giving each tool a clear purpose and not using three apps for the same kind of work. When everyone knows that decisions go in the project tool and quick questions go in chat, things get lost less often.

Check access, not just invites

Sending someone an invite is not the same as confirming they can use it. Practical onboarding checks that new team members have working access to every tool before they need it.

Choose async-friendly defaults

Tools that require everyone online at the same time create problems for distributed teams. Where there is a choice, tools that work well async (shared docs, comment threads, recorded demos) include more of the team more of the time.

Audit occasionally

Tools accumulate. A short annual check of which tools the team actually uses, which are abandoned, and whether anything is missing prevents tool sprawl and ensures nobody is still relying on something that was quietly discontinued.

Questions for your team

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

Does everyone on the team have full working access to every tool they need, including people in different locations or on different devices?
Where does tool overlap create confusion about where things live or where to post something?
Which tools does your team rely on most, and what happens if one of them goes down?
Are there team members who have informal workarounds because the official tools do not quite work for them?
When did you last check whether your tool stack is still the right one for how the team works now?

Watch for

A tool that works well in the office (on the same network, with the same setup) may be painful for remote team members. Office-centric tools create two-tier experiences.
Teams often add tools without retiring old ones. After a while nobody knows where things are supposed to live, and important things end up scattered across all of them.
Free tiers and personal accounts sound like a reasonable shortcut until someone leaves the team and takes the access with them.