Buffer shows: a personal user manual needs to be easy to find

You start a new project with a colleague. There is a schedule, a shared folder and a first meeting. Only after an awkward feedback conversation do you discover that your colleague prefers to read comments beforehand. That preference was already written down somewhere. You just did not know where.

In Work Blueprints, Hailley Griffis describes how Buffer brought personal working manuals together in Notion. That raises a practical question: where does your colleague look when collaboration needs explaining?

Below, we explore that question for your own team. The examples and suggested agreements are our contribution, rather than a description of Buffer's current internal practices.

Being easy to find is part of being useful

A carefully written manual can still mean very little to someone else. If the link only appears in a welcome email, a colleague has to remember that the document exists and then search for it. Few people do that when a deadline moves.

Put the manual where people already look for working information, such as the team directory or a project's starting page. Explain what the link covers in everyday language: preparation, communication and feedback. That helps readers decide whether the document matters right now.

Make the most relevant agreement easy to read. “Send feedback one working day before our conversation so I can prepare examples” gives immediate direction. A longer introduction about your career can follow, if you want to share it.

When you create a personal user manual, answer two questions together: what does a colleague need to know, and where will they look for it?

A project kickoff gives people a reason to read

“Read each other's manuals” is an instruction without a clear outcome. One colleague reads everything; another opens the page and moves on. Neither knows what should happen differently afterwards.

Ask one specific question at the start of a project: which working preference could affect our first shared task? For a presentation, it might be preparation. For a customer request, availability. For a design, the point at which feedback can still change the result.

Suppose you want to develop a coherent proposal first, while your colleague wants to contribute early. Agree to share a rough outline on Wednesday with two questions. The developed version follows on Friday. Early discussion gets a place in the schedule, alongside independent work.

This is also the step explored in our article about Atlassian's personal manuals: connect a preference to an agreement you can use together.

One location does not mean access for everyone

Opening every manual to everyone may seem convenient. Yet a team agreement, a personal example and a note intended for your manager serve different purposes.

Discuss who needs the text. A project partner should be able to read your feedback agreement. Every colleague does not need access to personal background. Let the writer choose what to share and check the access settings of the chosen location.

Do not ask for a private explanation of a working preference. “I prefer to read beforehand” is enough to discuss preparation. People do not have to explain why. Managers can use a manager README to make their own expectations and responsibilities equally clear.

Update the agreement where readers find it

A circulated copy survives after its writer has changed the original. A colleague may then follow the wrong agreement in good faith. Where possible, link to the current version and date important changes.

After two weeks, review one work situation. Did the feedback arrive in time? Did everyone know whether the rough outline could still change? Was it clear when a call was necessary? Adjust the sentence that caused confusion and tell the colleague involved what changed.

The publication itself is not an evaluation of your team's results. Making a document available and reading it do not guarantee better collaboration. Start with what you can observe directly: could the other person find, understand and use the agreement?

Start with the next collaboration

Choose one colleague with whom you will deliver something this week. Share the link to your manual and point to one passage that matters for that work. Ask what context is missing and agree on a practical response together.

Keep that agreement where you follow the project. The manual can then answer a question that already exists in the work: what do we need from each other to complete this assignment well?