└── readme.md /readme.md: -------------------------------------------------------------------------------- 1 | 2 | This is my version of the so-called "leadership readme" or a "how I lead" reference for anyone that works directly with me. 3 | 4 | ### About Me 5 | 6 | I've been in technology for almost two decades and I am still tying to figuring it all out. I've advanced my career in engineering primarily through the lens of a [site reliability](https://en.wikipedia.org/wiki/Site_Reliability_Engineering) and "devops engineer" (not a real job title, ask me more!) but have also played Software Engineer, Architect, Technical Product/Program Manager, and any other duties as required. I'm used to looking at complex systems and figuring out why the cogs are misaligned and providing a simple but effective solution. 7 | 8 | Also, I'm a huge fan of Star Wars, Lego & reality tv cooking shows. 9 | 10 | ### My Role 11 | 12 | My role is to be accountable for the decisions, progress and general success. I am **not** here to make all the decisions nor should I or should you let me. 13 | 14 | Everyday I work to guide, advise and facilitate the growth of our team and our impact on the products we build and support. 15 | 16 | ### How I Lead 17 | 18 | #### My style 19 | 20 | I lead projects and endeavors using 3 sequential modes: visioning, demonstrating, stewarding and typically ask 5 sequential questions: what, why, how, who & when on any scaled effort. 21 | 22 | #### I trust my team 23 | 24 | I trust each and every member of our team. Trust isn't earned, it's lost. 25 | 26 | #### I like to be challenged 27 | 28 | I would like to think I know everything but that just isn't the case. I hire smart people because I like to surround myself with opinionated, passionate, hard-working people. Please challenge my ideas, thoughts and feedback. If you're not comfortable doing it in a group setting please make sure to voice your thoughts in our 1o1. 29 | 30 | #### I embrace a work/life balance 31 | 32 | I typically work between 8am and 6pm, and unless there's an emergency, I don't expect to communicate with you (about work) outside of these hours. As such, I **never** expect you to respond to me outside these hours either unless it is an emergency. 33 | 34 | #### I want you to be and feel productive 35 | 36 | Regardless of where you work, our success relies on your independence and autonomy. My role is to provide a framework and support so you can be productive and *feel* productive. If our processes or procedures don't enable you to be productive or feel productive make sure to tell me. 37 | 38 | #### I want our team to add value 39 | 40 | I love talking technology and can do so for hours on end; but technology is rarely the only component an engineering team produces or supports. I expect the team to focus on adding business value and making decisions that ensure we can and do deliver on our commitments to the business and our customers. 41 | 42 | #### I want you to grow 43 | 44 | I expect the team to have a passion for learning and growing and I will do my best to challenge and entice you to learn new and exciting things. 45 | 46 | #### I want your feedback 47 | 48 | "Feedback is a gift" 49 | 50 | #### Culture 51 | 52 | Every company has one, even if it isn't codified, but a codifed one is almost always better. 53 | 54 | A few places I've worked have well documented cultural pillars; like Rocket Mortgage's [ISMs](https://www.myrocketcareer.com/About-Us/Our-Philosophies). 55 | 56 | These philosphies help ensure we're all aligned to the right direct, our interactions are governed by an appropriate compass, and our mission is clear. 57 | 58 | ### Your Role 59 | 60 | A team's success is not defined by any one person's achievements or failures. 61 | 62 | > Each and every member of our team needs to help positively influence, guide, change, and improve our product, technology & processes. 63 | 64 | That is your role and the role of everyone on the team. At times you will need to be able to change the mindsets and beliefs of your team; this give and take, these professional debates, are not optional. They **will** make you a better engineer and leader, but they can be trying and often difficult. I'm here to provide guidance and course correct the conversation if need be, but I cannot and will not speak for you. 65 | 66 | 67 | #### 1 on 1 Meetings 68 | 69 | If you directly report to me, you should schedule a weekly, 30 minute conversation with me. I prefer that you schedule the meeting, so you can pick a time (and place) that works for you, your schedule, and avoids interrupting your flow. 70 | 71 | Our chats should be less about the status of your work, and more about *how* work is going. These are **your** meetings, but if you need a few ideas of things we can talk about, here is a brief list: 72 | 73 | - new ideas you have that you need a sounding board for 74 | - if there is something I can do to guide you, coach you 75 | - if you're having a problem and you don't know how to attack it 76 | - if you want to discuss something and need someone to listen 77 | 78 | Our initial conversation *will* be a bit different. Here are a few of the questions I typically ask during that session (h/t to [Lara Hogan](https://larahogan.me/)) 79 | 80 | - What makes you grumpy? 81 | - How will I know when you're grumpy? 82 | - How can I help you when you're grumpy? 83 | 84 | - How do you prefer feedback? (in scheduled 1o1, as-it-happens, via text, phone, smoke signal?) 85 | - How do you prefer to receive recognition (publicly or privately) 86 | 87 | - How do we make 1o1s value to you? 88 | 89 | - Human learning and growth requires the right amount of four things: new challenges, low ego, space to reflect and brainstorm, and timely and clear feedback. How are these four going for you? Is there one you need more or less of? 90 | 91 | - What's your favorite way to treat yourself? 92 | 93 | 94 | 95 | --------------------------------------------------------------------------------