> For the complete documentation index, see [llms.txt](https://fuse-lab.gitbook.io/fuse-lab-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fuse-lab.gitbook.io/fuse-lab-docs/leadership-and-context/how-we-create-context.md).

# How We Create Context

Remote work, autonomy and cross-functional collaboration all depend on one thing: people being able to understand what is going on without needing to ask the same three people every time.

Context should survive meetings, handovers, holidays and resignations.

When knowledge will be useful more than once, write it down.

## Company Context

This handbook is the main introduction to how Fuse Lab thinks and operates. The opening pages explain why we exist and what we are trying to build. Culture explains the behaviors we want. The other sections explain how the company actually works.

For current reporting lines, use the Company Structure rather than copying names into multiple documents.

## Team Context

Each team should make the things that are specific to that team easy to find: what the team owns, who does what, how work flows, key tools and folders, common handoffs, and the standards that matter most.

Current team onboarding guides:

[CCW New Hire Onboarding Guide](https://docs.google.com/document/d/1LseeKmGCaHJzClQCLL-RXmbUKS9LfFnrlNFKo5r82Bw/edit?usp=drivesdk)

[CAV New Hire Onboarding Guide](https://docs.google.com/document/d/1ZMeIeIob7AWYucrwRSvZVXQ5Hi3bNylxI-DJgawAlmE/edit?usp=drivesdk)

[CDS New Hire Onboarding Guide](https://docs.google.com/document/d/1ugCuV4xT6XPxIm0aYxm8TKMdAhwh6YZFcda9RcVn4dc)

[RMT New Hire Onboarding Guide](https://docs.google.com/document/d/1wNIn5hwGO5bN8eC0IygPwnXLVkHkwtKSD3EnX0pLoWs)

These guides should get thinner over time, not thicker. If something is true for everybody at Fuse Lab, it belongs in the company handbook. Team guides should focus on what is actually different about the team.

## Client & Project Context

Every ongoing client or significant project should have a clear entry point for somebody joining the work.

Going forward, our preferred format is one living document per client rather than one giant sheet containing every account. If you are joining an account, you should be able to open one document and quickly understand the scope, people, current work, workflow, links, standards and important history.

[See Clients & Work for the current directory and documentation standard.](/fuse-lab-docs/clients-and-work.md)

## Personal User Manuals

A User Manual is a short practical guide to working with a person. It covers things like communication preferences, focused-work patterns, how somebody likes to receive feedback, what they appreciate from teammates and what overload can look like for them.

User Manuals are open to the whole team. Read the manuals of people you work with regularly. New hires should read their lead's manual and the manuals of their closest collaborators during onboarding.

A User Manual is context, not a contract. "I prefer feedback in writing" can help a teammate deliver feedback better. It does not mean feedback can no longer be given any other way.

[Browse Fuse Lab User Manuals](https://drive.google.com/drive/folders/1WLji9PbjUIknF7XS0j0fH1pOMiuuZWFC)