Back to resources
    4 Mar 2026

    How to roll out team working manuals across your company

    Lynnsey Urquhart

    Founder · LinkedIn

    To build team working manuals across your company, start with one pilot team rather than a company-wide launch. Have each person write their own honest account of how they work best, store the manuals where people already do their work, and review them as roles and teams change. A rollout is something you build as a steady habit over time, and it lands best when it grows team by team.

    This guide covers what a company-wide rollout actually involves, from choosing a first team to keeping manuals current a year later. It is written for owners and leaders of small or growing teams who already understand what a working manual is and now want to put one in front of every person, without it turning into a stale HR exercise that nobody opens twice.

    The habit matters more than the document

    The document is the simple part. A manual takes most people half an hour to draft once they know what they are answering. The real work is making sure people read each other's manuals, refer to them in real situations, and update them when something changes.

    If you are still firming up the basics of the format, read what a working with me manual is first. This guide assumes you have that part settled and focuses on getting manuals into use across a whole company.

    Start with one pilot team before you go wide

    Pick one team to go first, ideally one led by someone who is open to it and whose people talk to each other often. A pilot lets you learn what questions land, what storage works, and what people stumble over, before you have committed the whole company to anything.

    When the pilot team can point to a real moment where a manual saved a misread or a clumsy handover, you have your proof. That story does more to bring the next teams on board than any internal memo. Roll out team by team, and let each group see the value before the next one starts.

    Keep each manual the person's own honest account

    A manual only works when the person wrote it themselves and meant it. It is their own account of how they work best, in their own words. It is not a form completed to satisfy a manager. The moment it feels imposed, people write what they think is expected and the whole thing loses its value.

    Give a light, shared set of prompts so manuals are comparable, then leave the answers to each person. A manual is not a score, a test or an assessment of anyone. It is a plain, honest description meant to make working together more straightforward.

    Make manuals simple to find and use day to day

    A manual nobody can find is a manual nobody uses. Store them where people already work, so reading a colleague's manual takes one click before a first meeting or a new project, rather than a hunt through a shared drive.

    A few small habits make the difference between a live tool and a forgotten folder:

    • Link a person's manual from wherever your team sees their name, so it is always one step away.
    • Ask people to skim a new joiner's manual before their first week, and the joiner to read the team's.
    • Bring manuals into real moments: handovers, project kick-offs, and when two people keep missing each other.
    • Keep each one short enough to read in a couple of minutes, so reading it never feels like a task.

    Keep manuals current as people and roles change

    People change jobs, take on new responsibilities, and learn more about how they work. A manual written eighteen months ago and never touched slowly stops being true, and once one is out of date people quietly stop trusting the rest.

    Set a light rhythm for review. A quick check when someone changes role, joins a new team, or at a fixed point each year is enough. Make updating a manual a normal, expected thing rather than a special event, and they stay honest on their own.

    The common mistakes that stall a rollout

    Three mistakes account for most rollouts that fade out. The first is treating it as a one-off HR exercise: manuals get written once, filed, and never referred to again. The second is over-templating, where so much structure is imposed that every manual reads the same and the person disappears from it.

    The third is letting manuals go stale because no one owns the rhythm of keeping them current. Each of these is straightforward to avoid once you name it. Keep the manuals personal, keep them in use, and keep them reviewed.

    It helps to pair manuals with a shared view of how the team works, covered in making working styles visible across a team and working styles at work. If you would rather not build the rollout from scratch, the Working With Me workshop builds your team's working manuals, priorities and rhythm with you in a day, and includes a four-week platform trial so they have a home from the start.

    Common questions

    How long does it take to roll out working manuals across a company

    Plan in waves rather than a single date. A first pilot team can have useful manuals within a week or two, and you then add a team at a time. Going wide all at once tends to produce filed-and-forgotten manuals, so a steady team-by-team pace usually lands better.

    Should everyone use the same template for their manual

    Use the same small set of prompts, but leave the answers entirely to each person. Shared prompts make manuals comparable and quick to read. Heavy templates make every manual sound the same and strip out the individual, which is the part that makes them useful.

    Who owns keeping the manuals up to date

    Each person owns their own manual, and a manager or team lead owns the rhythm of prompting reviews. Tie updates to natural moments such as a role change or a fixed annual check. Without a clear owner of that rhythm, manuals quietly go stale.

    What is the difference between this and a personality test

    A working manual is a person's own honest account of how they work best, written by them in their own words. It is not scored, rated or assessed by anyone. Where a test labels you, a manual simply describes how to work with you well.

    How do we stop manuals from being written once and ignored

    Bring them into real moments rather than leaving them in a folder. Ask people to read a colleague's manual before a first meeting, a handover or a new project. When a manual is genuinely useful in the work, people keep them alive without being chased.