Writing a Manager’s User Manual
21 June, 2021
Something that I’ve adopted as a manager: the manager’s user manual. It documents how best to work with me.
A bit of background on me: I came to the States from China after grad school. My cultural heritage is quite different than many of those who I manage. A lot of times, I feel like people don’t understand me. I feel like I often need to supplement what I say with a lot of context in order to get my point across.
This has led me on this mission to figure out how to connect with those around me more directly. How can I make people understand me? How can I make working with me as clear and as simple as possible?
I found this solution online. The purpose of writing the manual is to carve out how I define success as a manager. In my own manual, I bring up the following:
- How do I view success?
- How do I best communicate?
- The things that I do that may annoy you or that may be misunderstood.
- The things that cause me to gain or to lose trust.
- My own personal strengths and weaknesses.
- My expectations for my direct reports.
- How I carry out my one-on-ones.
- My most direct channels of communication.
- How I prefer to give and to receive feedback.
This is my current list, but when I started, I really only had a few points. I have collected each point from feedback that I’ve received over the years. Some people thought that I was too direct. Some found that I am not direct enough. I have been told that my communication is much more clear in writing than in person. I have also learned to be more forthcoming with positive feedback, not just focusing on what needs to be improved.
Sometimes, I can be prone to jumping to conclusions myself. There have been times where communication did not go over as well as I had hoped that it would. I have reflected upon these experiences and summarized them here, as well. I have a caveat justifying my reasoning for sometimes not answering every question immediately. I explain that this is me respecting my employee’s autonomy, specifying only when necessary for them.
I keep this document on my internal company profile on our own personal social networking platform. This way, whenever somebody tries to set up a meeting with me, they will see it immediately. I have separate sections for my reports and for my cross-functional team members in other departments, as well.
- I created this when I first started. I realized that it sort of became this living document that changes with me. I am able to see how I change every quarter and every year.
- Now, when I am working with somebody new, they come to our first meeting very prepared. They are able to help me more directly with this additional source of context. This is especially useful in a post-COVID world. It has significantly scaled how I serve as the manager of a now remote team.
- Being transparent in how I communicate has benefited me both in the short term and in the long term. It has led to stronger relationships between myself and everybody who I work with.
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Supporting principles on why being data led (not driven) helps with the story telling.
Head of Engineering at Xero
Your Org Team may as well be a Sports team. Let's explore how this cohesive, multi-skilled team can be optimized for Great Group Playoff.
Google Cloud Practice lead at Contino
Why DevSecOps matter and what's really in it for you, the team and the organisation?
Head of Engineering at Xero
Mrunal Kapade, an Engineering leader, based in Silicon Valley, shares tips that helped reduce attrition in the remote engineering teams while leading multiple teams from startups to Fortune 500 companies.
Director of Engineering at Inspire Energy
Teams have tremendous impact on the products on they build. T.E.A.M definition - Together Everybody Achieves More is true. A collaborative and empowered team builds great product versus the good ones.
Senior Software Engineering Manager at Anaplan