ThemeKnowledge & Systems
CardCard 61 of 66
Questions5 to explore

Tools & Technologies

Digital and analog tools you rely on

The tools an organization uses shape how it thinks, and most teams have never made an intentional choice about their full stack.

Tools are not neutral. The project management system a team uses changes how it plans. The communication tool shapes what kinds of conversations happen. The analytics platform determines what questions get asked. Documenting the tool stack is partly logistics, but it is also a record of the choices that shape how the organization operates.

The practical problem with undocumented tool stacks is that they grow without anyone deciding they should. A trial subscription becomes permanent, a workaround tool becomes core infrastructure, and two teams end up using different systems for the same thing. A clear inventory makes those situations visible.

Tools documentation is also the foundation for onboarding. New people need to know what systems to access, what each system is for, and what the norms are for using it. That knowledge should not have to come from asking around.

What to capture

For this part of the company brain, what is worth writing down and keeping current. The goal is not a complete archive but a living record that new people can read and returning people can trust.

Tools inventory

A complete list of the digital and analog tools the organization uses, what each one is for, who uses it, and who owns the account or subscription.

Access & permissions

How new team members get access to each tool, who can grant permissions, and what happens to accounts when someone leaves. This is the most operationally urgent part to document.

When to use which tool

The intended purpose of each tool and the norms around it, so people know whether to put something in the project system or the knowledge base, and which tool wins when there is overlap.

Costs & contracts

What the organization pays for, renewal dates, and what is covered by each subscription. Especially important for tools that are purchased at a team level and may be invisible to finance.

Questions to explore

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

If a new person needed to access all the tools required for their role on day one, what is the exact process for that?
Are there tools being used by one team that another team does not know about, that could be shared or consolidated?
Which tools were introduced as temporary solutions that have since become permanent, and are they still the right fit?
What happens to tool accounts and passwords when someone leaves the organization?
Which tools does the organization pay for that fewer than half the intended users actually use?

Things to notice

Tool inventories go out of date quickly. Without a process for adding new tools and removing old ones, the list becomes inaccurate fast enough to be untrustworthy.
Access management is where most tool documentation fails. Who can grant access, what the offboarding process is, and where credentials are stored are often handled informally until something goes wrong.
A list of tools is not the same as documentation of how to use them. Point to the relevant how-tos or documentation for each tool rather than assuming people will find them.