# Design the team handbook

Answer “how do I get this done?” for someone who does not know which team or
database owns the process. Make useful instructions approachable while giving
operators a clear place to maintain guidance and handle requests.

## Write labels employees can act on

Prefer “Procedures,” “Owners & reviews,” and “Requests” for the three main views.
Use specific route names such as “Getting started,” “Buying tools,” and “Client
handoffs” instead of broad verbs such as “Join,” “Buy,” and “Deliver.” Adapt them
to the actual procedures; keep established team labels when they are clear.
For new properties, “Procedure owner” explains “Steward,” and “Review status”
explains an ambiguous “Review.” Keep request responsibility distinct from the
person maintaining a procedure. Write instructions such as “Open a request to
see what to do next,” rather than describing records, relations, or execution.

## Orient the reader

Give the home a clear identity, team overview, and concise introduction. Use
headings and dividers to make procedures readable. Provide a browsable guidance
library and a separate maintenance view, adapted to the team and its work.

## Make the routes recognizable

Label entry points in plain language, such as “Set up a laptop” and “Buy software.”
Group a larger handbook by reader intent. Use a compact index and gallery cards
with enough context to identify the right procedure. Give sections distinct
headings and use a coherent accent palette, meaningful colored icons, and a
relevant cover to make the home feel considered and recognizable.

Keep the request desk accessible without making every employee read the queue.
Use its records to show current status, responsibility, due dates, and blockers.
Keep policy maintenance in a dedicated table so stewards can scan review state
without adding that full table to every reader's route.

## Make instructions dependable

Use a consistent reading structure: prerequisites, ordered steps, approval
checkpoints, exceptions, and completion checks. Distinguish draft guidance from
approved policy near text someone could act on. Preserve known sources and
uncertainty; do not invent authority to make a handbook look complete.

Connect onboarding to real procedures. Keep contact and escalation details near
the relevant steps when known. Avoid duplicating guidance as unrelated checklists.

## Check the design in use

Watch an employee find and use a procedure, then an operator handle a request.
Inspect the page hierarchy, library cards, maintenance columns, dates, and links
across those paths. Make each destination useful on its own and connected to the
rest of the system. Judge visual quality as well as successful navigation.
