-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathmanager-readme.html
142 lines (135 loc) · 9.73 KB
/
manager-readme.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Manager README</title>
<link rel="stylesheet" href="./theme/css/main.css" />
</head>
<body id="index" class="home">
<header id="banner" class="body">
<h1><a href="./">The Train Station</a></h1>
<nav><ul>
<li class="active"><a href="./category/development.html">Development</a></li>
<li><a href="./category/general.html">General</a></li>
</ul></nav>
</header><!-- /#banner -->
<section id="content" class="body">
<article>
<header>
<h1 class="entry-title">
<a href="./manager-readme.html" rel="bookmark"
title="Permalink to Manager README">Manager README</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2020-04-07T10:00:00-05:00">
Published: Tue 07 April 2020
</abbr>
<address class="vcard author">
By <a class="url fn" href="./author/seth-buntin.html">Seth Buntin</a>
</address>
<p>In <a href="./category/development.html">Development</a>.</p>
<p>tags: <a href="./tag/management.html">management</a> </p>
</footer><!-- /.post-info --> <p>Hey, we are glad you are here. Take a couple of deep breaths, this will be fun. What you are about to experience in this place
will be different from any place you've worked before. There will be highs and there will be lows (there always is). But most
importantly, we are going to have fun. And you will help us make it great.</p>
<p>While you are here you will work with great people. Seriously, the people here are some of the best all around people you will get
an opportunity to be around. You will learn how we communicate, how we collaborate and how we build a product. All of this will take
time and we are here to provide that learning opportunity.</p>
<p>Before we get started we need to really define one thing well. That is, <em>our</em> relationship. While my title has the word "Manager" in
it I hope to show you my take on that word. Hopefully you will see that the managers on TV and in the movies aren't what we are in
reality. In reality my job is to make you the best <em>you</em> you can be. I'm your helper. I'm your guide. I'm your coach. Below
is sort of a guide to me. The things I find important and the things I value. I hope it helps you understand me.</p>
<p>Without further ado, buckle up and enjoy the ride.</p>
<h2>Our Average week</h2>
<p>We will for the first little bit of time meet 1:1 weekly. This meeting will change over time but for the first 3 or so months
we will focus heavily on our product and answering <em>any</em> questions you might have. After this period of time and when you have
developed a deeper understanding of Campaign Monitor we will switch to bi-weekly 1:1s.</p>
<p>Some weeks we have team meetings and some weeks we don't (see Principles below for more information on meetings). We have weekly
Engineering All Hands meetings that are a good place hear what is going on in the Engineering organization and various global
announcements. There will even be brand staff meetings that I encourage all of my teammates to attend.</p>
<p>You can Slack me whenever you want. I normally turn off notifications past 6 p.m. but if you feel I need to know you can notify
me anyways. I don't mind at all.</p>
<p>I sometimes work at weird hours. That is my choice. <strong>I do not expect you to work weird hours</strong>.</p>
<p>I take vacations and use my time-off. You should too. Being refreshed is one of the best ways to do our best job.</p>
<h2>My role</h2>
<p>My role mainly consists of three parts: People, Team, Technology. In that order.</p>
<h3>People</h3>
<p>Like I stated above my first responsibility is to enable you to be the best <em>you</em> you can be. But I can't do it without <em>you</em>.
I am dependent on you telling me what you want to do and then I get the opportunity to navigate all the situations we find
ourselves in and help you piece the puzzle together. This is one of my favorite things to do. Not because it is easy but because
we do this together.</p>
<p>As you've experienced I'm also in charge of hiring. This is another favorite thing to do. It is hard and tiring but in the end it
is rewarding.</p>
<p>I'm also active in compensation, promotions, reviews and all the "managery" things you might think of. These things come with
my role and I am eager to help where and how I can you navigate these conversations and situations.</p>
<h3>Team</h3>
<p>I get to be involved in a little bit of the day to day activities of the team. My main focus it to ensure that you all are able to
do you job and do it effectively together. I help coordinate conversations and collaboration. I help coach for the best outcome.
You will some times hear me say <em>"We win and lose as a team."</em> This is true, we can't do this without each other. The people that
sit with you and around you are your best allies. The analogy I like to use here is that of Steve Kerr, the head coach for the Golden
State Warriors. If you watch him during a game you'll notice that he is most often sitting comfortably on the bench letting the
team play. He may step up and adjust during the game but his actions show that the team is at work. I believe that the best coaching
happens through our 1:1 conversations and various team meetings and that the time for the team to shine is during the sprint. I may
help adjust along the way but this is game time for a product engineering team.</p>
<p>This is where process happens. One note about process and who I am at my core. I obviously care about process in that I have created
this document that details all of the things that mean something to me and I want to consistantly be communicating and enacting. But,
when it comes to the team I want the team to decide the tools and artifacts we use to help us be successful. I don't want that kind
of decision coming solely from me. I have opinions and will gladly share them but a process will never work if it doesn't have buy-in
from everyone. So we will decide process together.</p>
<h3>Technology</h3>
<p>I have had the opportunity over the years to be exposed to many problems that we face each day. This exposure enables me to help
where I can with some of the implementation. I've learned over the past couple of years what this actually looks like. For me
it looks a lot like 20 Questions. While I might have an idea or direction I tend to help you and the team navigate to the implementation.
This was hard at first but has become more and more fulfilling.</p>
<h2>Principles I care about</h2>
<p>I hold to a set of guiding principles. These principles are by far not perfect but I have found and seen a lot of success when
we as a team hold to them together. These principles are not my own. I intend to stand on the shoulders of giants who have done
this before and learn from their successes and failures.</p>
<h3>The 10 Commandments of Egoless programming</h3>
<ul>
<li>Understand and accept that you will make mistakes.</li>
<li>You are not your code.</li>
<li>No matter how much "karate" you know, someone else will always know more.</li>
<li>Don't rewrite code without consultation.</li>
<li>Treat people who know less than you with respect, deference, and patience.</li>
<li>The only constant in the world is change.</li>
<li>The only true authority stems from knowledge, not from position.</li>
<li>Fight for what you believe, but gracefully accept defeat.</li>
<li>Don't be "the guy or gal in the room."</li>
<li>Critique code instead of people – be kind to the coder, not to the code.</li>
</ul>
<h3>General</h3>
<ul>
<li>Facts over fear</li>
<li>Perfect is the enemy of Progress</li>
<li>A program that sells and makes money is better than one that doesn't</li>
<li>It is important to not stop questioning</li>
<li>Be introspective. If something goes wrong adapt the process that got you there.</li>
<li>Proactive is better than reactive</li>
<li>Respect goes a long way</li>
<li>Cinnamon Toast Crunch is the best cereal</li>
</ul>
<h3>Meetings</h3>
<p>To some this is a sore subject and if you were to survey a group of managers on what they think about meetings you will likely get
many differing responses. My care for meetings revolve around communication. I feel when teams are communicating well outside
of a meeting room there really is no need to go into a meeting room to communicate. This isn't always the case so sometimes a meeting
is the right place for certain conversations. I do my best to keep meetings on point and intentional. If you ever feel like a
meeting was a waste of time then let me know. Your time is the last thing I want to waste.</p>
<h2>My Expectations</h2>
<p>My main expectation is that when we are all doing our part the team runs like a well oiled machine. When we aren't we know it.
Conversation is my main reaction to when things aren't working well.</p>
<p>I also expect to have fun. We are here 8 hours a day. It isn't worth investing all that time when you can't have fun while doing it.</p>
</div><!-- /.entry-content -->
</article>
</section>
<section id="extras" class="body">
</section><!-- /#extras -->
<footer id="contentinfo" class="body">
<address id="about" class="vcard body">
Proudly powered by <a href="http://getpelican.com/">Pelican</a>, which takes great advantage of <a href="http://python.org">Python</a>.
</address><!-- /#about -->
<p>The theme is by <a href="http://coding.smashingmagazine.com/2009/08/04/designing-a-html-5-layout-from-scratch/">Smashing Magazine</a>, thanks!</p>
</footer><!-- /#contentinfo -->
</body>
</html>