Here's a sobering statistic: 73% of new hires say unclear manager expectations are their biggest early frustration—yet most leaders never document how they actually work. The cost? Weeks of unnecessary confusion, eroded trust, and talent that could be contributing from day one instead of getting lost in translation.

Picture this familiar scene: a new developer joins on Monday, you're knee-deep in quarter-end reporting, and the Slack pings begin. "Do you prefer a quick call or should I write this up?"... "Is it OK to update the roadmap doc without you?"... "Have you seen my holiday request?" None of these questions is unreasonable, yet by Friday both of you feel like you're talking past each other.

That early friction is rarely about competence—it's about unspoken expectations. An operating manual (also known as a manager README or leadership user manual) makes those expectations explicit before misunderstandings ignite. In short, it's a concise guide to working with you.

"A Manager README is a document that outlines your management style, expectations, and preferences," writes engineering leader Ryan Rodemoyer, adding that publishing his own was one of the best career decisions he's made.

What an operating manual actually looks like

Think of it as the readme.md for you-the-manager rather than for a codebase. The most effective manuals I've seen cover five core areas:

Purpose and values – the principles that steer your decisions. For example: "I believe in transparency over politics. If you're wondering about a decision, ask directly rather than speculating with teammates."

Communication norms – how, and how fast, you respond across channels. Be specific: "I check Slack every 2 hours during core hours (9-5 GMT) and aim to respond within 4 hours. For urgent matters, text me at [number]. I prefer async updates over status meetings."

Working preferences – how you run one-to-ones, review work, and make calls when data is incomplete. Detail your rhythms: "Our weekly 1:1s are sacred time—I won't reschedule except for genuine emergencies. Come with your agenda; I'll add mine 24 hours beforehand."

Support and growth – what "good" looks like, how you delegate, and the coaching you enjoy giving. Get concrete: "I delegate outcomes, not tasks. Tell me what success looks like, then own the how. I'm here for rubber-ducking problems, not micromanaging solutions."

Availability and boundaries – core hours, emergencies, and what happens when you're on holiday. Set clear expectations: "I'm offline 6 PM-8 AM GMT unless there's a customer-impacting outage. On holiday, contact [deputy] unless the building is literally on fire."

The most successful manuals follow this "how I like to work" approach, focusing on practical guidance that speeds up the getting-to-know-you phase. Keep it to two or three pages and write in plain English—no one needs a novella.

Five reasons it's worth the investment

The benefits extend far beyond smoother onboarding:

1. Faster trust – New joiners land on their feet because the guard rails are visible from day one. Instead of the usual month-long ramp-up, team members can start contributing meaningfully within weeks when they understand your expectations upfront.

2. Fewer micro-frictions – You remove guesswork about response times, feedback style, or what warrants a meeting. No more "sorry to bother you" messages or anxiety about whether that 3 PM Slack was too pushy.

3. Self-awareness on tap – Drafting the manual forces you to articulate (and sometimes refine) your leadership beliefs. You might discover you're unconsciously favouring one communication style over another, or that your assumptions about "urgent" don't match your team's reality.

4. Built-in accountability – Once published, your team can call you on any gap between words and deeds. It's humbling and incredibly valuable.

5. Signalling effect – It tells the wider organisation you take clarity and psychological safety seriously, often inspiring other leaders to follow suit.

The upshot? More time spent on the work that matters, less on decoding the boss.

Common mistakes to avoid

The concept has its critics, and they raise valid concerns. James Stanier, CTO and author of The Engineering Manager, describes writing several drafts that felt "trite" and worries a manual may shift the burden of adaptability onto the team. He's right on two counts:

Tone can drift into "my way or the highway" – A manual is a starting point for discussion, not a set of commandments chiselled into granite. Frame preferences as "this typically works well for me" rather than "you must do this."

Mismatch hurts more than silence – If you claim to welcome blunt feedback and then bristle the first time someone tries, trust evaporates faster than gin on a summer's day. Your actions must match your manual, or the whole exercise backfires.

Other traps include using the document as a substitute for real conversations, or as an excuse for problematic behaviour ("I'm just forgetful—it's in my manual!"). Remember: the manual enables better conversations, it doesn't replace them.

A lightweight creation process

Here's the approach I've refined over multiple iterations:

1. Reflect – List moments when you feel deeply effective and deeply irritated at work. Patterns reveal your genuine preferences, not just your aspirational ones.

2. Draft in bullets – Aim for ~1,000 words maximum. This is a field guide, not your memoirs. Use concrete examples rather than vague principles.

3. Sleep on it, then stress-test – Hand it to a peer and ask, "If you'd read this on day one, what would still be unclear?" Fresh eyes catch assumptions you've missed.

4. Publish and discuss – Share with direct reports during their first week and invite questions. The conversation matters more than the PDF itself.

5. Iterate – Schedule a six-monthly review. Your style evolves as you grow; so should the document.

Pro tip: Encourage team members to write their own one-page "how to work with me" sheets. Reciprocity keeps power imbalances in check and gives you the intel you need to flex your style for each individual.

How to implement your manual

Once you've drafted your manual, these tactics help it become a living tool rather than shelf-ware:

Onboarding integration – Drop the manual into the welcome folder alongside IT logins and org charts. New starters will thank you for the clarity.

Team resets – Use it to open strategy off-sites or post-reorganisation kick-offs. It grounds the conversation in how you'll work before diving into what you'll accomplish.

Performance reviews – Revisit the manual with each report during quarterly check-ins. Where have you lived up to it and where have you slipped? That meta-conversation deepens trust and accountability.

Share great examples – When you stumble across an excellent README (Buffer's Katie Womersley or Slack's Michael Lopp are classics), share it with your team and discuss what resonates. It normalises the practice and sparks valuable conversations.

AI coaching integration – Here's a modern twist: encourage your team to use your manual as context for AI tools. When drafting emails, reports, or presentations, they can provide the LLM with your manual and ask it to review their work against your preferences. For example: "Review this project update email against my manager's communication preferences in the attached manual—does it hit the right level of detail and tone?" This creates a feedback loop that helps team members internalise your working style faster whilst ensuring their output aligns with your expectations from day one.

Quick self-assessment: how clear are your management expectations?

Rate yourself on these five areas (1 = unclear, 5 = crystal clear):

  • Communication: Do your team members know when and how to reach you? ___/5
  • Decision-making: Is your approval process transparent and predictable? ___/5
  • Feedback: Do people understand how you give and receive input? ___/5
  • Priorities: Can your team predict what you'll care about most? ___/5
  • Boundaries: Are your availability and limits clearly defined? ___/5

Score 20-25: You're already operating with high clarity Score 15-19: An operating manual would eliminate remaining friction Score below 15: Your team is likely spending significant mental energy guessing your preferences

The bottom line

An operating manual won't transform a mediocre leader into a great one, nor will it magically erase every misunderstanding. What it will do is replace tacit assumptions with explicit agreements so your team can focus on meaningful work sooner, and with less stress.

The leaders I most respect aren't the ones who expect others to figure them out—they're the ones who do the work to make collaboration effortless. Your operating manual is that work made visible.