<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Manager Documentation on cjcodes</title>
    <link>https://cjcodes.com/manager-docs/</link>
    <description>Recent content in Manager Documentation on cjcodes</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 28 Dec 2021 11:33:56 -0800</lastBuildDate><atom:link href="https://cjcodes.com/manager-docs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PRs Welcome</title>
      <link>https://cjcodes.com/manager-docs/prs-welcome/</link>
      <pubDate>Tue, 04 Jan 2022 19:58:28 -0800</pubDate>
      
      <guid>https://cjcodes.com/manager-docs/prs-welcome/</guid>
      <description>Even though these docs are a reflection of my personal style, I am very open to feedback, suggestions, corrections, questions, and challenges to my opinions. The source of this site is open-source on GitHub. File an issue or open a PR!</description>
    </item>
    
    <item>
      <title>1-on-1s</title>
      <link>https://cjcodes.com/manager-docs/1-on-1s/</link>
      <pubDate>Tue, 04 Jan 2022 09:38:08 -0800</pubDate>
      
      <guid>https://cjcodes.com/manager-docs/1-on-1s/</guid>
      <description>A 1:1 is always your meeting. My meetings are performance reviews and formal calendar invites. As always, others have written with more eloquence than I on the topic, so I picked one for you that summarizes my approach.
Format of a 1:1 doc I like to have these categories in my 1:1 docs:
 Prioritized topic backlog Action items Dated summary of items discussed  1. Backlog The topic backlog is a dumping ground for things that come up during the week that you or I would like to discuss together.</description>
    </item>
    
    <item>
      <title>Expectations of Me</title>
      <link>https://cjcodes.com/manager-docs/expectations-of-me/</link>
      <pubDate>Tue, 28 Dec 2021 20:57:42 -0800</pubDate>
      
      <guid>https://cjcodes.com/manager-docs/expectations-of-me/</guid>
      <description>To be written. This page will outline what you can expect from me as your manager. Below is my working list that I&amp;rsquo;ll add to over time.
 Radical transparency Thorough performance reviews and 100% clarity on the factors that impacted your performance review Estimate with a 1 year margin of error of when you&amp;rsquo;ll be ready for your next promotion. (The precision decreases as you go beyond Staff level.) 24 hour response SLA to emails &amp;ldquo;Next free time&amp;rdquo; commitment to acknowledge Slack messages (SLA &amp;lt; 4 business hours) Evidence- and example-driven feedback No feedback sandwiches Ad-hoc feedback when requested within 48 business hours &amp;hellip; more to come, along with better formatting  </description>
    </item>
    
    <item>
      <title>Working Hours</title>
      <link>https://cjcodes.com/manager-docs/working-hours/</link>
      <pubDate>Tue, 28 Dec 2021 18:58:02 -0800</pubDate>
      
      <guid>https://cjcodes.com/manager-docs/working-hours/</guid>
      <description>I try very hard to adhere to an eight hour schedule, and I do this for a very specific reason that&amp;rsquo;s not just to protect against burnout. Stretching my working hours to accommodate more responsibilities than I have time for allows understaffing to perpetuate itself, and doesn&amp;rsquo;t let my team or organization easily identify what our staffing gaps are. Folks like me who are capable of wearing many hats fall into this trap very easily, and the workday limit gives me the tool I need to trade off what the highest priority for me is.</description>
    </item>
    
    <item>
      <title>No Hello</title>
      <link>https://cjcodes.com/manager-docs/no-hello/</link>
      <pubDate>Tue, 28 Dec 2021 18:57:57 -0800</pubDate>
      
      <guid>https://cjcodes.com/manager-docs/no-hello/</guid>
      <description>I don&amp;rsquo;t have many pet peeves aside from chewing with your mouth open. However, in a professional setting, I do admit to having one pet peve:
The Hello. So with that vague introduction, I send you over to nohello.net, where some other random internet stranger has articulated the problem and solution.</description>
    </item>
    
    <item>
      <title>Management Books</title>
      <link>https://cjcodes.com/manager-docs/books/</link>
      <pubDate>Tue, 28 Dec 2021 12:23:28 -0800</pubDate>
      
      <guid>https://cjcodes.com/manager-docs/books/</guid>
      <description>I&amp;rsquo;ve assembled a list of books that have helped me formulate my leadership and management style. I&amp;rsquo;ve roughly ordered them based on how formative I believe them to be on my style.
Management  Leading Snowflakes Oren Ellenbogen Turn the Ship Around! L. David Marquet Start with Why Simon Sinek Leadership and Self-Deception The Arbinger Institute The Manager&amp;rsquo;s Path Camille Fournier Predictably Irrational Dan Ariely Thinking, Fast and Slow Daniel Kahneman The Back of the Napkin Dan Roam Switch Chip and Dan Heath Linchpin Seth Godin Radical Candor Kim Scott The Power of Habit Charles Duhigg Made to Stick Chip and Dan Heath The Five Dysfunctions of a Team Patrick Lencioni Drive Daniel H.</description>
    </item>
    
    <item>
      <title>Feedback</title>
      <link>https://cjcodes.com/manager-docs/feedback/</link>
      <pubDate>Tue, 28 Dec 2021 11:33:56 -0800</pubDate>
      
      <guid>https://cjcodes.com/manager-docs/feedback/</guid>
      <description>Throughout my career, my process and standards for feedback have remained pretty consistent. So this page attempts to distill down the key points into a relatively short guide.
Types of Feedback Let&amp;rsquo;s start by breaking feedback down into two categories: developmental and performance. Each one has different implications for the recipient.
Developmental Developmental feedback is the feedback that you provide to your peers, up to your manager, and down to those that you don&amp;rsquo;t directly manage (eg.</description>
    </item>
    
  </channel>
</rss>
