My User Manual
To set our relationship up for success, I've put together a cheatsheet for you to better understand how I work and how to best work with me.
What is a user manual?Hi, I'm Allen Hartwig. I'm based out of Washington State, but sometimes you'll find me working from Costa Rica.
I am excited to be working with you and building something great together!
Operational Approach
- I start my days early, usually around 6am and typically available until 8pm, Pacific Time. After 8pm my devices go into do-not-disturb mode and don't come back online until 6am the following day, including weekends. I highly value my sleep β my work and attitude suffer when I'm not well rested and I'm not my best self for you or my teams.
- Uninterrupted time for deep focus, thought, and work is something I value for both myself and you. I don't always check communications in real time and I don't expect you to either. If immediate attention is needed, use an @mention. If you need 1:1 time with me, please schedule it at least a day prior to avoid ad hoc meetings.
- I will meet with my teams quarterly to share short term vision, strategy, and targets. Providing visibility into the why? of your work is important to me. Knowing the reasoning behind what I ask you to invest your time and self in gives purpose and context, allowing you to produce a better work product and receive more fulfillment.
- I work out loud to give visibility into what I am doing and to make a habit of putting my thoughts into writing to better process my current focus. Having exclusively worked remotely since 2010, I find it builds trust and understanding, allowing my coworkers to virtually peak over my shoulder. By over verbalizing my work I can short circuit churn and rabbit holes.
- While I believe success comes from hard work, dedication, alignment, and focus, I also believe that there are a lot of variables outside of my control. Often, wins aren't as great as I think they are, and, at the same time, losses not as bad.Also, luck, happenstance, timing, and general externalities factor greatly into outcomes. Because of this, I operate with a low level of anxiety and stress, and, on the flip side, I am not quick to celebrate. However, this does not mean I am apathetic or not deeply invested in the dedication required to attain success. While I expect everyone I work with to give it their all, I also understand each of us can only bring so much to the equation.
How I make decisions
- When making a decision, I conduct thoughtful debate and market research to fully inform the matter at hand. Even if I have an opinion on which direction the outcome should go, I try to explore as many angles as possible and have a good grasp on what best practices within the space currently are. Good decisions are not made by the loudest voices or the most senior person, but by dedicated, deep thought, research, and discussion.
- With that said, I am also a big proponent of making decisions relatively quickly. People tend to over weigh the impact of making the wrong decision, when often, not making a timely decision results in a more significant negative impact. Decisions are rarely binary, and we rarely get them 100% right or 100% wrong. We always have the opportunity to re-evaluate decisions as more information comes to light. Opportunity cost is often a larger impact than that of imperfect decision.
- Throughout the decision making process, it is crucial to make sure that we fully understand, and remain focused on the root problem. During the process, it's possible to drift from this as the conversation unravels. I find it best to clearly and objectively define what we are deciding on and how we will be measuring the success of the decision very early in the conversation.
- Once a decision is made, we should be committed to it and execute fully. If we feel the decision should be revisited or re-evaluated, set up a time to discuss it with me. Until that time is reached, see the current decision through.
Management Style
π€² Hands-off
- I have a high degree of faith in you and your abilities. I am not a micro-manager. With that I maintain high expectations of you and your ability to self-manage, be a great teammate, and manage up to me as needed.
- You have been hired because you are exceptional at what you do. I will extend you a great deal of trust, latitude, and time to focus on your work to produce great things.
π€ Collaborative
- I enjoy participating where I can add value, regardless of the department or team. I am a big believer in cross-functional teams, applying a multi-disciplinary approach to problem solving.
- I understand having a senior voice at the table can be overbearing. If you are inviting me to collaborate, please make it clear to me what you are needing from me and what role I am playing in the conversation.
- Being that I often have a lot of plates spinning simultaneously, I find it valuable when teams utilize Lightweight Design Document (LDD) to frame the issue at hand, clearly outlining what is in and out of scope, the questions that need to be answered, and clear lines back to desired business outcomes.
πͺ’οΈ Accountability & Expectation Management
- I take milestones and deadlines seriously. In order to properly orchestrate work across the organization, it's essential that you commit to on-time delivery of your work. It is your responsibility to adequately manage expectations.
- With that, I defer to you and your team's best judgement on creating estimates of effort and time for work. I will notcreate arbitrary dates and deliverables without consulting you. I may challenge your estimates to be able to find compromise, negotiating on scope or ensuring we have alignment on what is truly needed.
- I understand that things don't always go to plan. Priorities shift, unforeseen circumstances emerge, actuals don't align with assumptions. However, when this occurs, I expect you to get a head of this, communicate the change, and reset my expectations.
- When setting my expectations, ensure you are taking into account all necessary components of the full delivery of your work, not just your step. When can the end user or stakeholder start receiving value?
π Outcome Driven
- There should be clear success metrics set on most everything we are doing. If you do not understand how to objectively measure the success of your work, let's discuss it immediately.
- My measures of success are based on the outcomes they drive, not work getting βdoneβ.
- I do not think in terms of βdoneβ and neither should you. Strive for incremental improvements towards outcomes. What is the next step to making a measurable increase in the direction we are heading toward?
- I do my best effort to create breadcrumbs back to business goals, big picture vision, and north star metrics.
- I appreciate when arguments are backed by data, utilizing dashboards and graphs to visualize things β however, I also understand how data can be contorted to tell inaccurate stories. Pressure test your data and make sure your assumptions are as accurate as possible and be ready to have your numbers interrogated.
Communication
π― 1:1s
- I don't pre-schedule a lot of 1:1s β as mentioned above, I value your time to focus on your work. If we do have one scheduled and you don't need it or having more pressing matters at hands, feel free to decline β it's for you.
- I keep my calendar availability accurate and up to date. If you need 1:1 time with me, by all means, book it.
- Use our 1:1 time for non-urgent items, or things that need more thorough discussion. Before hitting send in Slack, ask whether you need an answer immediately and if chat is the best medium for the conversation. If the answer is βnoβ, please add it to the agenda for our next 1:1.
ποΈ Meetings/Zoom
- If a topic pertains to multiple people, please make sure all parties are invited. If they simply need to be informed of the outcome, record the meeting and post to Rewatch so they can catch up async. Playing a game of telephone with meetings, or deferring meeting topics to 1:1, is expensive and error prone.
- Clearly define what the agenda of the meeting is in advance, what outcome you hope to achieve from the meeting, and what my role and responsibilities are at the meeting (as well as others you have invited).
- Focus meetings on the hard parts of the topic at hand. Route materials and get basic inputs in advance asynchronously.
π¬ Chat/Slack
- Chat is my preferred day-to-day communication channel, with Slack being used most. If I'm not available there and it is urgent, SMS/iMessage works as well.
- Use chat for quick feedback. While it should be approached as asynchronous, it's what I check most frequently and where you'll get the quickest response.
- I will use my Slack status as a way to indicate availability and to set expectations around response times.
- I will not use chat to assign you work, and please do not put important requests of me here. I often check messages throughout the day and once marked as read, it can be hard to find later. Do not brain dump your issue in a Slack channel and make it someone else's problem β we have task management solutions for this to ensure they get prioritized and completed.
π¨ Emails
- Email is not my preferred internal communication channel.
- If you do email me something as an FYI, I will see and read it, however I likely won't respond.
- If I do receive an email that requires a response, I will typically follow up within 48 hours.
βοΈ The Comments Section
- Many of the tools we use have the ability to add inline comments. This is great for quick feedback, however, it is not ideal for conversations. Please drive substantive discourse back to the appropriate channel.
Style
- I use humor quite a bit throughout my communications. I find it helps people let down guards and speak more openly, which is especially important in a remote work environment.
- I try to take an inquisitive approach to my feedback as I know I am not as close to some problems as you are, wasn't involved in all the discussions that lead to a decision, nor am I an expert in the things that you are. If I question your work, I truly am curious as to how you arrived at where you are β If I am requesting something to be changed, I will be direct.
- In order to fully explore a problem space, I will often play devil's advocate. I also like to take things to logical extremes on both ends of the spectrum to examine the issue at hand. If I am taking a position that challenges yours, it's not necessarily that I don't agree with you nor am I being divisive, I am trying to make sure our decisions are well thought through and we understand why we aren't doing alternatives.
You should know
- If I message you outside of your working hours, I do not expect you to respond. You may work a different timezone than me and my work hours span 14 hours. I will often follow up on Slack messages or drop thoughts outside of your work schedule. I don't expect you to respond until you are back on the clock.
- If you require my assistance, I highly appreciate if you take a giant step back and clearly articulate your ask in as much detail as possible. I often have many projects, topics, and efforts in flight at a given time and I am mostly likely not in the same headspace that you are. Give me as much context as possible, making it as unlikely as possible that I will have many (if any!) follow up questions. Not only will this allow me to get you an answer asynchronously when you may not be around, it often helps you better think through your ask and better frames the issue in your own mind. Forced rubber ducking.
- If you haven't received a response from me or I am blocking you on something, please follow up and repeat your request. It is my goal to make sure you are as equipped as possible at all times. I most likely have missed your message or it has slipped my mind.