To write a personal user manual for work, describe a few repeatable behaviors that help people coordinate with you, then agree what the team will do with them. Keep it to one page. The goal is a clearer working relationship, not a personality label or a list of rules for everyone else.
A page of preferences is only a first draft. A useful manual tells a colleague what to expect, what to do when a preference cannot be met, and what you will do in return. Every line should make the next move easier or invite a useful conversation.
Start with coordination, not self-description
Before writing, separate four kinds of information:
- A preference: a condition that usually helps you do the work, such as receiving a short written brief before a complex discussion.
- A request: a specific action you are asking a teammate to try, such as putting the decision needed at the top of a message.
- A limit: something people should not assume you can offer, such as being available after your posted work hours.
- A commitment: what others can count on you to do, such as flagging a deadline risk as soon as you see it.
Those distinctions keep the guide honest. A preference is not a rule until the people doing the work agree to it. A limit is more useful when it includes a route forward. A commitment keeps the manual mutual, so it does not read like a service menu for one person.
Use observable language. "A written outline helps me respond to multi-part questions" gives a teammate something to try. "I am a visual thinker" may be true, but it does not say what the work needs. Keep private details private. You do not need to disclose a diagnosis, family situation, or personal history to make a practical request.
How to write a personal user manual for work
Start with the people who need the guide and one real collaboration they share with you. Draft short answers to these five prompts:
- Conditions for good work. When do you make your strongest progress? What helps you start, focus, or hand work off? Write a condition and a practical request, not a universal rule about how work must happen.
- Communication and response. Which channel works for a quick question, a complex topic, or an urgent blocker? What response time can your teammates reasonably expect from you? Name a fallback for urgent needs.
- Decisions and uncertainty. What information helps you make a call? Which decisions can you own, and when should you bring in another person? Explain how you will surface a risk or a change of mind.
- Feedback and friction. How can someone raise a concern clearly? What kind of feedback helps you act on it? Say how you want to handle disagreement, and make room for people to tell you when your approach is not working for them.
- Reliability and support. What can others count on you to finish, communicate, or follow up? What specific help do you need from them? Include what you will do if the original commitment becomes unrealistic.
Keep each answer to one or two sentences. Add an example when a phrase could be read in more than one way. "I prefer direct feedback" is broad. "If a draft misses the brief, tell me which requirement it misses and what decision is blocked" gives the other person a clear opening.
If you want a team exercise to start the conversation, Atlassian's My User Manual play offers a set of prompts. Use a prompt only when it helps people coordinate on actual work.
Turn preferences into shared agreements
Share the draft with the people who will use it, then ask three questions: What is useful? What is unclear? What should I understand about working with you? The answers matter as much as your own page. A personal manual works best when preferences are discussed and adjusted across the relationship.
For example, "I prefer not to be interrupted" is hard to apply when the work has an urgent dependency. A more workable draft might be: "For non-urgent questions, send me a message and I will respond by the next workday. If a deadline or customer is blocked, call or message me with 'urgent' and the decision you need." Then ask your teammate what response window they need from you.
That exchange also reveals what belongs in a team-wide working agreement. If several people need the same escalation path or handoff rule, record it once where the team can find it. Do not make each person negotiate the same norm alone.
If a conversation stays vague, our guide to questions that move work forward can help turn a preference into a clear decision or request.
Share only what helps the work
A personal user manual, sometimes called a working with me guide, is voluntary context. Share it with close collaborators, a new manager, or a project team when it can make a real handoff or conversation clearer. A quiet one-to-one can be enough. You do not need a presentation or a company-wide profile.
Keep the audience in mind. A guide for a project partner may include response windows and decision ownership. A guide for a broad audience may not need details about your schedule or work environment. Include only information you are comfortable having those readers keep and revisit.
A personal user manual does not replace workplace policies or formal support channels. Use the appropriate process for a safety concern, access need, or other formal request. The guide can explain how to coordinate around a constraint; it cannot replace the process that governs it.
Make it useful after the first share
Test the manual during an upcoming handoff, project start, or feedback conversation. Did someone know what to do with the information? Did the guide help you meet a commitment, or did it create another expectation that needs discussion? Keep the parts that change the work. Rewrite the parts that sound polished but leave people guessing.
Update it when your role, responsibilities, or availability changes, and after a collaboration shows that an agreement is not working. A short check-in is enough: "Is this still accurate? What should we change for the next piece of work?" Keep an older version only if the change itself matters to the team.
Avoid filling the page with personality types, strengths adjectives, or absolutes such as "I never" and "I always." People change with the task and the context. Describe what tends to help, name exceptions, and invite a conversation when circumstances differ.
A copy-ready personal user manual template
Use these lines as a first draft, then edit them with the people who will work with you:
- How I do good work: I make the clearest progress when ____. It helps when ____.
- How to reach me: For ____, use ____. For an urgent blocker, use ____. You can expect me to ____.
- How I make decisions: I can decide ____. Please involve ____ when ____.
- How to give me feedback: The most useful way to raise a concern is ____. I will ____ in response.
- What you can count on: I will ____. If that changes, I will ____ by ____.
- What I need from you: I would like us to agree on ____ and revisit it when ____.
Keep what people can use and cut the rest. If writing the page is helping you avoid a conversation, take the draft to the person and write the agreement together.
Let the work stay human
A personal user manual is a practical way to make your working habits legible while leaving room for other people's needs. Share context, make a clear request, offer a commitment, and revise the agreement when the work changes. Self-made work is rarely made alone; the right people should be able to understand how to build with you.
If a repeatable uniform helps you mark the beginning of a work block, the Forged in Repetition Tee is one option from the collection. It is a visible cue, not a shortcut around the work. For more practical work guides, visit The Self Made Journal and read our piece on building a mentoring relationship through useful work.
0 comments