{"id":29,"date":"2018-06-02T14:09:19","date_gmt":"2018-06-02T18:09:19","guid":{"rendered":"https:\/\/patrickv.info\/?p=29"},"modified":"2018-06-02T14:09:19","modified_gmt":"2018-06-02T18:09:19","slug":"user-manual","status":"publish","type":"post","link":"https:\/\/patrickv.info\/index.php\/2018\/06\/02\/user-manual\/","title":{"rendered":"A User&#8217;s Manual For YOU"},"content":{"rendered":"<p>I ran across an interesting concept, creating a user&#8217;s manual for how you operate. This can be very simple, or very elaborate, but the idea is to create a document for your co-workers that informs that about how you operate, what your issues are, what&#8217;s expected of them, and even your own short-comings. This is obviously most useful to people who report to you, especially new hires that will feel like they&#8217;re struggling to catch up and fit in, but could also be insightful for your peers and those you report to.<\/p>\n<p>When I first heard about it from an article posted by FirstRound.com [note]<a href=\"http:\/\/firstround.com\/review\/the-indispensable-document-for-the-modern-manager\/\">FirstRound.com: The Indispensable Document For The Modern Manager<\/a>[\/note], I was intrigued. It turns out this isn&#8217;t an original idea. In 2003, there was an article from The Wall Street Journal [note] <a href=\"https:\/\/www.wsj.com\/articles\/SB1041881615563021064\">The Wall Street Journal: Job Candidates Get a Manual From Boss<\/a>[\/note], in 2010 a presentation from Dattner Consulting [note]<a href=\"http:\/\/dattnerconsulting.com\/presentations-files\/usersmanual.pdf\">Dattner Consulting: Do you have a user manual<\/a>[\/note], and another article on The Military Leader [note]<a href=\"https:\/\/www.themilitaryleader.com\/your-own-user-manual\/\">The Military Leader: How To Write Your Own User Manual<\/a>[\/note].<\/p>\n<p>I think this idea is genius on several levels. Most obviously it will help anyone reporting to you to work and communicate most effectively with you, while avoiding hot-buttons. Think about the difficult bosses you&#8217;ve had, and how much time and energy a document like this would have saved in figuring them out.\u00a0 But, there are some side benefits:<\/p>\n<p>[su_list icon=&#8221;icon: chevron-right&#8221; icon_color=&#8221;#0545ed&#8221;]<\/p>\n<ul>\n<li>It makes you examine yourself in some ways that most of us aren&#8217;t accustomed to. The key is being honest with yourself.\u00a0 If you&#8217;re not prepared for honest self-assessment, then this isn&#8217;t the exercise for you.<\/li>\n<li>It encourages feedback. You never know how people really experience your actions, this encourages people to say &#8220;you should add this to the manual&#8221;, or &#8220;that&#8217;s not what you put in the manual&#8221;. Encourage people to call you out right in the manual.<\/li>\n<li>It fosters accountability. If you put it in the manual, you&#8217;re more likely to follow-through.<\/li>\n<li>It creates continuous improvement. You&#8217;ll start to say to yourself, &#8220;that&#8217;s something that needs to go in the manual&#8221; or &#8220;I have to work on this so I can take it out&#8221;.<\/li>\n<li>It can create a closer team. If done right, you&#8217;ll be sharing not just your good points, but also some things that maybe you don&#8217;t like so much. Does someone not answering your Emails within an hour make you literally scream? That&#8217;s extremely important for people to know, but maybe it&#8217;s not your proudest moment.<\/li>\n<li>Knowing some of these intimate details in your behavior could make you more relatable and less intimidating.<\/li>\n<\/ul>\n<p>[\/su_list]<\/p>\n<p>It&#8217;s a concept that&#8217;s infinitely flexible. Put whatever you like in it.\u00a0 But, I recommend you try to keep it concise. Your manual may get out of control and need to be re-organized, or pruned, as it grows. Depending on your level and responsibilities, maybe some things can be taken out or added. Here are some ideas:<\/p>\n<p>[su_list icon=&#8221;icon: chevron-right&#8221; icon_color=&#8221;#0545ed&#8221;]<\/p>\n<ul>\n<li>Communication &#8211; How do you communicate? How do you prefer others to communicate with you. What expectations are there on how often and what form communication takes?<\/li>\n<li>First 90 days &#8211; What should someone expect from their onboarding?<\/li>\n<li>First 6 months &#8211; What should someone expect from the &#8220;new hire&#8221; period.<\/li>\n<li>Work Style &#8211; How do you like to work, do you like to have worked knocked out ahead of schedule? What don&#8217;t you like? Do you dislike when someone comes to you with problems without looking at possible solutions?<\/li>\n<li>Feedback &#8211; How you like to give and get feedback.<\/li>\n<li>Team expectations &#8211; What ground-rules do you have for your teams, and how they interact with each-other and the customers?<\/li>\n<li>Professional development &#8211; How can you help people develop, what development plans do you have for yourself?<\/li>\n<li>Personal quirks or issues &#8211; Are you grumpy if interrupted before you&#8217;ve had your first cup of coffee and read your Email?<\/li>\n<\/ul>\n<p>[\/su_list]<\/p>\n<p>I personally think this is a document that you may never finish. It&#8217;s something that could be reviewed and updated often, a tool for continuous self-discovery and growth.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I ran across an interesting concept, creating a user&#8217;s manual for how you operate. This can be very simple, or very elaborate, but the idea is to create a document for your co-workers that informs that about how you operate, what your issues are, what&#8217;s expected of them, and even your own short-comings. This is &hellip; <a href=\"https:\/\/patrickv.info\/index.php\/2018\/06\/02\/user-manual\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;A User&#8217;s Manual For YOU&#8221;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-29","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/patrickv.info\/index.php\/wp-json\/wp\/v2\/posts\/29","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/patrickv.info\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/patrickv.info\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/patrickv.info\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/patrickv.info\/index.php\/wp-json\/wp\/v2\/comments?post=29"}],"version-history":[{"count":0,"href":"https:\/\/patrickv.info\/index.php\/wp-json\/wp\/v2\/posts\/29\/revisions"}],"wp:attachment":[{"href":"https:\/\/patrickv.info\/index.php\/wp-json\/wp\/v2\/media?parent=29"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/patrickv.info\/index.php\/wp-json\/wp\/v2\/categories?post=29"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/patrickv.info\/index.php\/wp-json\/wp\/v2\/tags?post=29"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}