Working guide or company playbook?

Put stable organization-wide context in the playbook and job-specific procedure in the role guide. This keeps a change to company terminology from requiring a rewrite of every specialized workflow.

Compare the practical differences

Decision	Company playbook	Working guide
Best fit	Shared audience, terminology and general working rules	Role workflow, deliverables and quality checks
Useful property	Useful across different teammates	Keeps specialist instructions near the role
What to check	Should not contain task-specific source facts	Does not replace missing task inputs

A concrete choice

A rule about the approved product name belongs in shared context. Instructions for auditing spreadsheet formulas belong with the spreadsheet role.

Verify the choice

Start a new task after editing context and inspect whether both layers were applied. Existing tasks retain their saved context.

Write the reason for your choice into the task brief or setup notes. Then run a small representative task and compare the actual result with the requirement that drove the decision. Keep any unmet requirement visible rather than declaring the whole workflow ready from a single successful step.

Continue with the setup

The related desktop guide explains the relevant controls and limits. Use the current application state when applying this comparison; the presence of an option in a document does not mean every dependency on your computer is ready.