ThemeTools, space & tech
CardCard 6 of 65
Questions5 to explore

Cloud Storage

Established places for shared content

Shared cloud storage only works if everyone knows where things live and trusts that the folder structure will hold.

A cloud drive is where the team's work exists when it is not in someone's head. When it is organised, anyone can find what they need without asking. When it is not, the drive becomes a place where things go to get lost, and people quietly start keeping their own copies.

In hybrid teams, cloud storage carries more weight than in a colocated one because you cannot just shout across the desk. A missing file means a blocked task, not a five-second conversation. Naming conventions, folder hierarchies, and access permissions all need to be decided explicitly.

The goal is a structure that survives turnover and does not require the person who built it to be online to navigate it.

Make it explicitAgree on a folder structure, a file-naming convention, and who is responsible for keeping the top-level organisation clean.

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.

One drive, one source of truth

Strong hybrid teams pick one primary storage tool and resist the drift toward parallel copies in personal drives or local folders. Shared means shared: if it is not in the agreed place, it does not officially exist.

Naming conventions in writing

Teams that write down their naming convention (date format, project prefix, version numbering) save hours of confusion. It does not have to be elaborate, just consistent and findable.

Quarterly folder review

Some teams add a short 'tidy the drive' task each quarter to archive old projects and update the top-level structure before it calcifies into something nobody wants to touch.

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 know where to save a new document without having to ask?
How do we handle files that exist in multiple versions, and which one is the current one?
Are permissions set so people have access to what they need, without access to things they should not see?
What happens to files when a project ends or someone leaves the team?
How long would it take a new team member to find an important document from six months ago?

Watch for

Folder structures that only make sense to the person who built them create a single point of failure, especially when that person is on leave or leaves the team.
Duplicate files with similar names but different versions are one of the most common sources of errors in hybrid teams working on shared deliverables.
Storage tools often have generous permission defaults that mean outside collaborators can see more than intended; permissions are rarely reviewed after the initial setup.