{"id":342,"date":"2019-12-31T18:07:00","date_gmt":"2019-12-31T16:07:00","guid":{"rendered":"https:\/\/arc.dev\/employer-blog\/?p=342"},"modified":"2025-06-11T12:32:33","modified_gmt":"2025-06-11T04:32:33","slug":"manager-readmes-personal-user-manuals","status":"publish","type":"post","link":"https:\/\/arc.dev\/employer-blog\/manager-readmes-personal-user-manuals\/","title":{"rendered":"Are Personal User Manuals Useful for Managing Remote Teams?"},"content":{"rendered":"\n

An increasing number of tech managers around the world are using personal user manuals<\/strong> (or manager READMEs).<\/p>\n\n\n\n

Why? These documents are aimed at communicating the manager’s values, personality, style of leadership, and expectations to their direct reports. Thus, they intend to improve communication and productivity in the organization.<\/p>\n\n\n\n

This article delves into the recent trend of personal user manuals (manager READMEs). We will look at their potential benefits and drawbacks in the context of managing remote teams. <\/p>\n\n\n\n

Whether you’re a founder, a CEO, a manager, or a person on a remote team, you’ll be able to make the decision about whether a manager README is right for you.<\/p>\n\n\n\n

Looking for top talent fast? See how <\/em>Arc<\/a> can help you:<\/em><\/p>\n\n\n\n

\u26a1\ufe0f Find developers, designers, marketers, and more
\u26a1\ufe0f Freelance or full-time remote + fully vetted<\/em>
\u26a1\ufe0f Save up to 80% with global hires<\/em><\/p>\n\n\n\n

Hire top talent with Arc risk-free \u2192<\/strong><\/a><\/p>\n\n\n\n

What is a Manager README (Personal User Manual)?<\/h2>\n\n\n\n

A manager README\/personal user manual acts as a detailed guide that provides information about the\u00a0manager<\/em>, rather than the company. The name comes from README files \ud83d\udcc1 that you often find in a software folder. The file shows you exactly how to use the respective software.<\/p>\n\n\n\n

A manager README has a very similar purpose. It indicates the best ways to communicate with the manager and the principles that they stand for. It can be as professional or as personable as the manager chooses.<\/p>\n\n\n\n

The document helps employees to familiarize themselves with the organization and more senior personnel before ever interacting with them. Nevertheless, an exhaustive set of rules\u00a0should not<\/em>\u00a0be the basis of your personal user manual. Instead, we recommend that you treat it as a useful mechanism that can improve the efficiency of working relationships. <\/p>\n\n\n\n

Team-building groundwork and communication still need to be done the traditional way!<\/p>\n\n\n\n

Read More<\/strong>: How to Implement a Welcoming Software Developer Onboarding Process<\/a><\/p>\n\n\n\n

How Do You Write a Personal User Manual?<\/h2>\n\n\n\n

In a nutshell, your personal user manual \u2014 or manager README \u2014 should include any information that you think will help the working relationship between you and your remote developers. As they’re so new, there is no standard template. <\/p>\n\n\n\n

However, below are some of the areas you should look to cover, along with working examples from fellow managers.<\/p>\n\n\n\n

Introduction<\/h3>\n\n\n\n

A manager README will typically include a succinct description of who you are. Touch on why you are writing a personal user manual, what you hope to gain from it, and even how you got the position that you are in. Feel free to include an image or two: yourself, and maybe your pets!<\/p>\n\n\n\n

Your introduction should be short and easy to read without any waffle. Try to adhere to the\u00a0TL;DR (too long; didn\u2019t read) principle\u00a0to ensure it is not unnecessarily lengthy.<\/p>\n\n\n\n

Matt Newkirk\u2019s README<\/a>\u00a0gives a perfect example of an introduction, under the heading “Matt, as your manager.” The Senior Software Engineering Manager at Etsy includes less than five lines of text, introducing the intentions of his personal user manual and how he intends to support his employees.<\/p>\n\n\n\n

Explain your role<\/h3>\n\n\n\n

The next step is to explain your job role within the organization. You may include any information that you feel is most relevant. We recommend starting by outlining what your work style is and your broader goals within the business. This can include your typical working hours, along with any preferences relating to your work style.<\/p>\n\n\n\n

After that, it is often beneficial to implement some assurances that you intend to uphold with your remote developers. It shows that you’re willing to take some accountability, which is naturally more welcoming. This can come in the form of a “How can I help you?” section. Your aim could be to:<\/p>\n\n\n\n