- What I Believe & What I Expect
- What I say or do that some can misinterpret
- Getting ahold of me
- One on Ones
- ToDos for Version 2:
Context: We are a heavily async-based culture with an emphasis on writing our thoughts down, and Bo (Our Founder/COO) loves to communicate a via writing. Back in 2020 he started this letter (originally addressed to his team) about himself and how to work with him. This letter has been circulating throughout the company, is referenced a lot and played a major role for a lot of folks at CBH during their onboarding. It’s super enjoyable to read!
Context: I wrote this originally for people on my team, but after thinking about it realized it might help anyone at the company who might be interacting with me even if it’s infrequently. As always, would love any thoughts/reactions. My inbox is always open for your thoughts :)
Hello, and welcome. I'm very excited to work with you on our mission of improving the lives of Healthcare Workers and Healthcare Facilities. Day in and day out, my goal is twofold: to serve our customers, and to grow the careers of those around me. I know that a strong, clear, and productive working relationship between you and I will contribute greatly to the time both of us spend at work.
It's with this goal in mind that I write you this letter - to help both of us achieve that relationship with intentionality. I guess, first a little background about me. We'd likely have chatted about our childhoods over lunch if we sat in the same office. In lieu of that, I'll write it here so you get a sense of me as a person - and I want to hear about your childhood too! Email me!
I grew up on the campus of a Science and Engineering university in mainland China in the 80s, where both my parents were engineering professors - nerdiness is in my blood. I moved to West Virginia when I was in elementary school, and got picked on a lot as a kid for my accent and being terrible at sports… but being a nerd was respected in my elementary school! It took me forever to realize this was no longer the case in the US.
I went to college in the midwest, majoring in Computer Science at the University of Illinois at Urbana-Champaign, and ran for and won a seat in the Student Senate. So, rather than the movie version of college, I pretty much spent my days either in the windowless basement of the Digital Computing Lab or knocking on doors for votes. Life of the party, I am - sigh.
I spent the first 5 years of my professional life at Microsoft in Seattle as a Product Manager. I learned a ton about what to do as a product manager, and unfortunately also learned a ton about what not to do in running large organizations. I then spent the next ten years founding and CEO-ing a Silicon Valley startup that brought digital investment advice to families across the country, before joining BlackRock.
I learned an immense amount from that 10-year journey, and we were fortunate to have the “classic” Silicon Valley experience from going through the incubator Y Combinator to raising venture capital from the biggest names in the valley I’d only ever read about (Sequoia Capital, the founders of Yelp and YouTube, etc) to being acquired. Both in running my own company and at BlackRock, I learned a lot about how to run large(er) organizations that I'm excited to use as a foundation for continued improvement here at Clipboard Health.
Outside of work, I play as much tennis as my body will allow and mostly spend as much time as possible with our two kids (a newborn and a two-year-old). We are such nerds that we named our first child after a class of fundamental particles in quantum mechanics, and our second child after one of the five canonical nucleobases in biology. The saving grace is both names are normal-ish sounding, I think :). With that background, let me start with What I Believe, which also helps explain some of my general expectations.
What I Believe & What I Expect
i.e. thoughts that ring true to me that have stuck with me through the years, that may help you understand me better and what I expect from both you and me. I'd love to hear where you might agree or disagree, have questions, and what you believe that's not on this list! I believe...
- High Standards. First and foremost, I believe that setting high standards is the cornerstone of success. I have been the beneficiary of someone else's high standards time and again in my life, and seen myself achieve more than I thought I was capable of. Eventually, I got smart and just started setting very high standards for myself rather than waiting for someone else to do it for me. The last thing I want to do for you is to expect less.
- Enforce high standards in your organization. It’s easy to say “I want to work with exceptional people”… if you believe that (and you must since you work here) is every single person on your team truly exceptional? If you don’t answer with a resounding yes… then the answer lies in yourself. You’re the leader of your team, this is 100% on you. Usually, it’s because it’s easy to say “I want high standards” but hard to do the dirty, awkward, and emotionally painful yeoman’s work to get there. This means going to each person on your team that’s a great person, hardworking, but just not exceptional, and saying “you’re good but not great, and only great people work on my team”. It means actually following through and firing that person, even though he or she is working really hard. (Hard work is necessary but not sufficient for success here). High Standards apply to more than just talent. High standards mean rejecting good but not great work products even though you’re close to the deadline. High standards mean not hiring that good but not exceptional candidate when your team is severely understaffed. It’s this kind of hard tradeoff that actually makes High Standards a reality and not just a poster on the wall. I write on our internal blog about managing to High Standards as I think it’s the most important thing we do.
- Speed & self-sufficiency, loosely coupled. We are a small number of people working in a vast greenfield opportunity. Speed is underrated. Even though many blog posts have been written about going fast in a startup, it’s still massively underrated. To be fast you need self-sufficiency: as much as you can, we try not to take on dependencies (either internal or external) because we want to control our own timeline & quality. This means in practice if you can do it yourself don’t wait for someone else to do it because “it’s their job” or “it’s not my job”. Need to send an email newsletter? Fire up Mailchimp (or similar) and do it yourself. Need to write a Metabase query? Try it yourself first. We’re not a place where you hear phrases like “well, I had to wait for the BI team, and the User Research team, and coordinate the work” - we do the work here, we don’t coordinate other people doing work. Speed and self-sufficiency are supported by an organizational structure that is loosely coupled. If you’re client-facing, I hope that when a client comes to you with a problem you can fix it for them, immediately, rather than the common “let me open a ticket with department x”. If you’re in charge of a team, I hope your team has agency over accomplishing its goals. If I can do anything to help this be the case please come to me.
- Hardcore. We look at other people in our world, like those in the storied Navy SEALs, and see what they're willing to do to be the best in the world and say "they are hardcore". We are equally hardcore. People on this team have 1) spent many hours a day for days on end working on a single math problem because it was that hard. 2) worked 100 hour weeks when needed as a young attorney in the middle of one of the biggest corporate bankruptcies in the US (not "I estimated I worked 100 hours" but "I wrote down and billed a client for each 15-minute increment of my day and they add up to 100 hours"). 3) Been the actual best in the world, placing first in national or international science competitions. Unlike the Navy SEALs we don't risk our lives, but we are just as hardcore about what we do.
- We think from first principles. What's the goal? What constraints have we internalized that are unexamined? What assumptions have we made that are unexamined? For example, why do we "have no toes" in this company (as in, we never worry about stepping on someone else’s toes)? Because there's no customer problem to which the best solution is people in this company saying "I didn't do it because I didn't want to step on someone's toes". Thus toes don't exist, because we started with a clean slate and thought from first principles, rather than accept tradition or common practices unexamined. This helps us stay fearless and unencumbered - and yes, sometimes we have to discover best practices the “hard way” (from first principles) but I’m happy to pay that price. Something Elon Musk said in an interview stuck with me (paraphrased): I found out these rockets were crazy expensive, but when I looked up the cost of the raw materials it turns out only about 2% of the cost of the rocket is the raw material, so I thought 'well, almost all the cost is not in getting the atoms but arranging those atoms to form a rocket. So we just have to find a way to arrange those atoms more cheaply - that seems solvable'.
- Your job is not simply to do "what Bo wants". Think of me not just as a manager but as an investor, and you're the CEO of your part of the organization. Your job is to create and execute a convincing plan to achieve your goals. This is good practice for when we're a public company and part of the S&P 500 because then investors will expect that from each of us (see advice from Sequoia about Board Decks as an example). If you find yourself reacting to my questions, thinking "I've never thought of that, hmm, let me think of the answer" somewhat often then that's not good. Ask yourself your own questions, use your questions to push your own thinking, that's a success.
- Our company is like a minor league baseball team on its way to the World Series. As we get bigger (i.e. advance through the season) the problems get harder, the organization we manage gets more complex, and the competition will get more skilled, requiring each of us to get better quickly. This has been put articulately by others as “the same performance that earned an Outstanding last year will only earn an Okay this year”. To get better, great athletes do a lot of studying game film, training, and nutrition work off the field. For us, operating the business is "on the field", so we have to manage our own "off the field" work to make us great. This is not about the hours you work, but about doing the intentional efforts beyond just running the business to make ourselves better.
- Discipline. Something a friend who invests in startups said once stuck with me, and I'll quote it here (she eventually made that talk into a blog post): "After a founder sends me two or three update emails, I can immediately get a sense for whether or not that company will succeed. Some send an email and then you don't hear from them again for four months. Others use different formats or metrics every time. Or they say that revenue is the top priority in one meeting and then say they're focusing on engagement and redesigning the app in the next. That's not an update, that's an excuse. If revenue isn't where it needs to be, admit that you have an issue to your investors, your team, and above all yourself so you can start getting back on track." Each of us leads our own team and/or scope of initiatives, and holding ourselves (and each other) to a high standard of discipline is a key compounding effect that makes our organization stronger every day.
- Hard work. Each of us is given a limited and unknowable amount of time on Earth. This company is a collection of people who have each decided that they want to spend this phase of their lives becoming great business operators, and in so doing dramatically improve the lives of workers in the largest part of our economy: healthcare. We start with the nurses and nursing assistants who get paid very little to do the yeoman's work of caring for patients that is the foundation of good healthcare. As hard as any of us work, I'm constantly reminded that our customers, the nursing assistants, work far harder at far greater risk to themselves on the front lines, and get paid far less. That perspective reminds me to never complain, and get back to work. I constantly ask: can we be doing more for them? Can we do more today?
- Go faster. Speaking of our limited time on Earth, everybody gets the same 24 hours, but some people can get a lot more done than others. Every step we take in every project we do, every requirement we impose on others, has a Time Cost that oftentimes people don't account for correctly. Time Cost should show up on our credit card statement because it is a real cost. I believe in deciding proactively when to pay and when not to pay that cost, what I buy with that cost, and when to save others around me that cost.
- Touch the ball more. Years ago I read that the best soccer camps for developing youth prodigies into professional players focus every day on only one metric: how many times did the player touch the ball. Not number of goals scored, not number of games won. This stuck with me because it rings so true that the most foolproof way to get better at anything is to get more reps. For software engineers, reps are getting more code you wrote or bugs you fixed into the hands of customers to see what broke and what lessons you can take away. For P&L owners reps are getting more ideas into the marketplace more quickly to see which ones yielded the improvements to your core metrics you hoped for. The best way to write a good essay is to write ten bad ones in a row and then turn in the last one. What is it for you? Can you get faster tighter feedback loops? Can you "touch the ball" more? Get started. Nothing beats getting started. Right Now.
- Read, a lot. Here I'll quote from the memoir of a retired military commander. "Reading is an honor and a gift from a warrior or historian who—a decade or a thousand decades ago—set aside time to write. He distilled a lifetime of campaigning to have a "conversation" with you. We have been fighting on this planet for ten thousand years; it would be idiotic and unethical to not take advantage of such accumulated experiences. If you haven't read hundreds of books, you are functionally illiterate, and you will be incompetent, because your personal experiences alone aren't broad enough to sustain you. Any commander who claims he is "too busy to read" is going to fill body bags with his troops as he learns the hard way. The consequences of incompetence in battle are final. History teaches that we face nothing new under the sun." Mattis, Jim. Call Sign Chaos (p. 42). Random House Publishing Group. Kindle Edition. I also remind myself not to oversteer based on one or two books I read recently, no matter how much that book may have “really resonated” or seemed to mesh with my (limited) experience. I wouldn’t want to be led into an amphibious assault by a commander who only read one book on amphibious assault. By the same token, I know that my team (you) wouldn’t want to be led by someone who’s only read one book on management, hiring, or marketplaces. Your teams deserve the same.
- Metrics & Customer Conversations together are the ultimate Arbiter of Truth. I call this “Facts not Adjectives”. Metrics are the ultimate measure of whether you understand your business. Customer Conversations are the ultimate measure of whether you understand why your business is the way it is. Metrics tell you what is happening at scale, and may point the way to figuring out why. Customer Conversations driven by curious people revealing the actual root cause of exactly why something is happening and pointing the way to even deeper insights & ideas to fix it. And the two interweave to form a strong fabric: customer conversations can be backed up or disproved in the metrics; metrics can be corroborated or contextualized by customer conversations. The opposite of Metrics & Customer Conversations is… adjectives. Phrases like “major issue”, “substantial impact”, “is a well-oiled machine”, etc. are all adjectives. I don't trust adjectives. Adjectives obfuscate and overly simplify a nuanced and messy reality, and it's in understanding that nuance and messiness that real economic value is created. If you dig into the Metrics yourself, have the Customer Conversations yourself, you’re likely to notice specific subtleties and intricacies that others can't see that lead to specific solutions. Push through the phase where you think in adjectives and go directly to thinking in specific Metrics and specific Customer Conversations.
- Great leaders traverse multiple levels of abstraction and detail quickly and repeatedly. Nothing is "above" them, and nothing is "below" their notice. Have you talked to a customer lately? Tried to book them into a shift? Is your plan for your business ready for review by the Board of Directors? How about the public markets (i.e. can be included in our future filings with the SEC)? If we continue to succeed, we'll be there far before you think we're ready - no company is really ready for its IPO - so let's get started practicing now.
- Know your business cold, inside and out. There's a difference between 1) "I should know that, but I don't", 2) "I can't get at that info, but I have been pushing on the work needed from other teams [i.e. Engineering] to get it, and in the meantime here's what I was able to jury rig together to get a range for that number", and 3) "it's unknowable". Very very few things are in the 3rd category, and we should have intellectual honesty about that.
- I believe in asking lots of questions. What are we not thinking about that may limit our success? What will disappoint a customer? Asking pointed questions is how we push each other to ever higher standards of high-quality thinking. Our “The Working Backwards Document: Guide, Examples And How We Approve Initiatives” is a manifestation of this.
- Clear and precise goals. Not just for your organization for this quarter, but for everything we do. What's the goal of the meeting? What's the goal of this email? What's the goal of this blog post? The more precise our goals are, the more likely we are to actually get what we want. I believe in extremely high precision, and admitting what you don't know or haven't thought it through, rather than letting imprecise thinking hide behind imprecise language. Writing is thinking. Precise language is precise thinking.
- Think for the long term. What will you want to have done when it's 3 years in the future and you're looking back at this problem/opportunity/moment? Imagine the Ideal Impossible answer, and work backward from there. SpaceX realized that the Ideal Impossible way to make rockets cheaper was to make them reusable, even though entire nations had been unable to achieve this. Today, their rockets landing themselves is so routine it doesn't even make it onto the news.
- No plan survives first contact with reality. So, you know, run towards getting contact with reality!
- What got us here won't get us there. We experiment. This means the way we operate, even our org structures, are all experiments. Nothing is permanent. We start with how we can best improve the lives of our customers, and run whatever experiments are needed at every phase of this company to get there. For example, if I ask someone else to tackle a problem that I've also asked you to tackle, it's not because I don't believe in you. It's because I think the problem is big enough that it's worth running multiple experiments side by side. Imagine if in Physics or Chemistry the entirety of the human species ran only one experiment at a time...
- Self-awareness. I believe all of us, especially those of us in leadership roles, must work hard to cultivate high self-awareness. This means being curious about how you're being perceived and looking around you and outside the company for ways to improve yourself and your org. This means knowing your motivations, sharing that with others to help them understand you. Know your weaknesses, be brutally honest with yourself about them and how you're improving, and don't look away. Acknowledge your insecurities (at least to yourself, and ideally to others around you), and know when insecurities might be driving your thoughts or actions. Let's be honest, we all have insecurities. As a leader, it becomes hard to realize the way your voice seems to boom louder than every other voice in the room - so speak quietly. You get used to people withholding their opinions until they hear what you have to say - so try to speak last. People are afraid to bring ideas to you, afraid to dissent, afraid to engage - so you must proactively and intentionally help your organization counter-steer this tendency. All of these things can and do happen even to the most well-intentioned leaders. You have to work consciously and actively to fend off its corrosive effects - this is something I’d only give myself a C+ on, but I work on every day.
- Assume positive intent. If ever you or I find ourselves thinking "hmm… I could interpret what he or she just did in two ways" let us both strive to use the most positive intent interpretation. I will always assume you're a good person moving quickly, with a lot on your plate, doing your best. I hope you give me the same graciousness in interpreting my actions. That said, please tell me. The fact that something I did could be misinterpreted is very useful for me to know!
- Growth Mindset: it's not about whether you're good at something today, but about getting better quickly. When you get a numerical evaluation, whether by me (on our 1 to 5 scale), by our customers (i.e. NPS, CSAT), or by the market (i.e. Revenue, Churn) think of that first and foremost a feedback loop. Like seeing the answer key after you completed a math quiz - that you got the question wrong doesn't mean you're "bad at math" (i.e. a permanent judgment of talent or worth). That you got the question wrong just reveals an opportunity to practice, push harder, and get better (i.e. "that I missed this question about eigenvectors just means I need to practice, it's a temporary condition").
- Own the Outcome. This means don’t complain about another team without them present to hear it (thus it becomes feedback that helps them get better, not complaining behind their backs). This means don’t think your agency or control ends at the boundaries of your own team - you can have great influence on others and you should cultivate and wield that influence in service of our shared customers. And remember that your loyalty is to our mission and our customers, not to your direct reports. We stand shoulder-to-shoulder as if we are scientists in front of a chemistry experiment, not “depending on our people” when you get feedback from others or when an experiment didn’t work, but working together with your peers to figure out what will work and how to achieve success together.
- Solve a problem once, you've kicked the can down the road. Solve a problem and put systems in place to ensure it stays solved is better. Solve the problem, and put in place systems to guard against future problems of this general type or with a similar root cause is best.
- Speaking of finding root causes… I believe in asking "why" at least 5 times in a row. I pretend that I am explaining why something happened to a very inquisitive five-year-old (i.e. myself). After every sentence, she asks "yeah but why is that" or "ok but why then did that thing happen". It teaches me really quickly whether I have a deep understanding or not, And motivates me to go get that deep understanding.
- You'll hear me refer to the Rude Board Member on my shoulder - someone who's smart and speaks their mind without any sugarcoating. This is a way for me to constantly remind myself and those I work with that decisions need to make sense at the company level not just at the level of a person, team, or department. I oftentimes will say out loud in our meetings, "I think Rude Board Member might say..."
- You'll also hear me refer to the Busy Customer on my shoulder - a healthcare professional or healthcare facility employee who's super busy is really depending on us and speaks their mind. I want customers to be spiritually present in each conversation, in each of our minds, as we work on their behalf. Busy Customer reminds me that the reasons we make a decision or answers we give internally that would draw frowns from a busy customer if she was in the room are by default poor and deserve extra scrutiny. For example, we're not solving a problem right now because some other internal team is busy? Bad answer, busy customer doesn't care about your internal politics. We're making a product decision that's not ideal in anticipation of some future feature coming down the road? Bad answer, busy customer doesn't care about your future roadmap. Etc.
- Finally, I expect you to be great because I believe in you. I expect this list to be just the beginning of a much longer list you'll keep for yourself and hold yourself (and me!) accountable to. I believe you're capable of greatness - that's why you're here. My job is to be a helpful person on your professional journey. Okay, with that backdrop, let's talk about… things I say some folks might misinterpret.
What I say or do that some can misinterpret
i.e. What I mean, and what I don't mean, when I say certain things (which I say frequently).
- I sweat the details, a lot. The difference between Good and Great is often a collection of very small details. This means I’ll often ask very detailed questions or make very detailed suggestions. I’m not trying to micromanage you; I’m not telling you you have to do it my way. I am instead holding your work to a high standard (see #1 above) and using questions or suggestions as conversation starters. For example, during a spec review for an iOS mockup, I might ask “why does this button filter the Table View rather than jump to a place within the Table View”? Please don’t think to yourself “why is the COO getting involved in what this button does”… it’s because I care. What I’m hoping you’ll say is “I thought of that too, but what you’re missing Bo is that…” which helps me learn and helps ensure we’ve thought through the details on behalf of our customers. Please don’t take that as “Bo wants the button to do X” - you’ve been thinking about the spec for days, I’ve been thinking about it for minutes, how would I know? :)
- I have a lot of ideas, suggestions, and opinions. They are all conversation starters, that’s all. Things I say are not somehow more important because they happened to come from me. Treat it like you would input from any other internal stakeholder or customer, and filter it through your own judgment. You own the outcome, you're graded on judgment. Some of us have scars from working with past high ego bosses; you should be safe here. I try to have an extremely low ego, but I'm not perfect, please tell me when I'm not meeting my own standards.
- Some folks are more contemplative than others - if you are, and I pepper you with questions, it's okay to say "let me think about it and I'll get back to you" and write me something later (but tell me when to expect your response, and of course follow through) if that's how you think best.
- I sometimes swear. It's nothing except that I'm really passionate about something we're talking about, and a bad habit I picked up. I'm working on trying to tone it down.
- Want feedback? Ask me. My written feedback has been called more useful than my verbal feedback. I struggle with giving clear enough negative feedback in person, because I care about how you feel, so force me to give you a number/grade/rating on a numeral scale and that'll push through my weakness here. I'll also include a numerical rating in all written check-ins (i.e. if we do one at day 30, day 90, mid-year, end of the year), so remind me if I fail to do that.
- Me asking "when will this be done" is not necessarily me asking you to "do it faster". You set your own deadlines, just communicate your plan & schedule (written if at all possible). You drive. That said, I will sometimes think you can go faster, so our customers' lives improve earlier and you get more reps. In those cases I'll say simply "I think we can go faster"… but as mentioned above, as a conversation starter!
i.e. Methods to extract the most value out of working with Bo
Getting ahold of me
- Call me on Slack. Anytime. Seriously. No need to warn me or ask me, no need to first Slack me and say "can I call". A huge part of my job is to be here for you so that you can be here for our customers. I truly value each effort you make to reach out. We run a 24/7 company because patients get sick and need care without regard to what the clock on the wall says. We're also a distributed team hailing from seven countries and more than seven time zones. If you're afraid of calling me because "it's too late where Bo is"... don't be. I work weird hours, and it's my responsibility to turn off my ringer if I need to, not your responsibility to predict my schedule.
- If you call, Slack, or email I will try to get back to you the same day, though sometimes it'll be the next day. I return calls first, then slacks, then email, so feel free to use that to your advantage depending on urgency.
- You are always welcome to drop a meeting on my calendar. Anytime. Everyone in the company should be able to see my calendar - not just when I'm free and busy, but what exact meeting I'm in with whom (please tell me if you can't; then I must have inadvertently broken it).
- I very much appreciate your responsiveness and strive hard to be similarly responsive to you. That said, this is an Area of Growth for me. Please don't hesitate to tell me if I'm not being responsive enough to enable you to do your best work. I will not in any way take it personally.
One on Ones
- 1:1's are for you, to be driven by your agenda, and secondarily for me (I might have a few agenda items at the end). Think of 1:1's primarily as Board Meetings where you're the CEO and I'm a member of the Board. Your agenda, your plan, I'm here to help by whatever you need: a thought partner, by pushing your thinking, by helping you get access to talent/capital/other resources inside and outside the company.
- We might meet 1:1 daily, weekly, monthly, or quarterly. It's up to you. I won't be offended if you turn up or down the frequency, and vice versa please don't be offended if I do either. Usually, it'll be because other projects on my plate are consuming more or less time, and shouldn't be read as a judgment in any way of you or our working relationship.
- Don't wait for our 1:1 to roll around if there's a conversation we could have now that's urgent, or will enable you to do great work faster. Like I said earlier in this letter: touch the ball more, go faster, get more reps. I'm here to help you do that.
- I believe meetings are expensive, and get more expensive at the square of the number of people involved (more people get pulled from doing Deep Work to attend, still only one person can speak at once so less is learned from each attendee, every person in attendance becomes de facto unresponsive to customers).
- Meetings are a tool, like a hammer.
- Each meeting has a goal. The goal of a meeting is never "to have the meeting", just like the goal of a construction project is never "to hit something with this hammer".
- By the same token, I don't mean any offense if I ever decline a meeting, cut a meeting short, or propose that we don't have to meet and propose an alternative tool. I'm essentially saying "hey how about a drill for this project, not a hammer" not "I don't value your efforts" (which some people can interpret). No offense is meant.
- Our standard for meetings is high.
- Every Meeting Has A Document. "Document" can be a spec ready for review, a well-thought-through JIRA ticket, a full set of mockups, or a project on Asana where there are written updates to all or most Items. The key to all these is that the writing (and necessary thinking) has been done ahead of the meeting by the organizer. This is because writing engenders high-quality precise thinking, reading is a faster way to absorb deep content than listening, writing is more effective at "getting everyone on the same page" (I mean, literally), and written records keep us all accountable and can be easily disseminated broadly to those who couldn’t be there.
- If the meeting starts and not everyone has written their document (or section thereof), then we simply cancel and reconvene later. Better to have a high-quality meeting tomorrow than a low-quality meeting today (note I said tomorrow, not next week).
- Meetings have action items and should be judged by all attendees by the quality of the action items and their on-time completion rate. If a recurring meeting (literally the only type of meeting more expensive than a regular meeting) isn't getting a good completion rate on items, you should probably fix it or stop the meeting series and find another tool.
- A suggestion: if the meeting's only purpose is to "check-in" on an initiative, you can probably do it in written form. Haven't tried it? Try it! Would love to hear what you think.
- That said, want to bat an idea around? Call me. Call a friend. Rubber Ducking helps some people think (including me), and I'd love to help in any way I can.
I sometimes get behind on email/slack/returning phone calls. First, I never want anyone to interpret that as a signal of any kind - it’s always something else that’s causing me to be unresponsive, not “something you said”. I know the feeling because I have the same insecurity. Second, I’m never annoyed at being pinged again if you need me to get to something faster. On the contrary, I appreciate it, because if I can do something for you that will help you deliver more value to customers faster, then awesome.
In the other direction, some folks have had prior leaders equate being on email nights and weekends to doing good work. I do not and don’t expect that. If I send an email over the weekend, unless it’s a live issue (in which I’m probably slacking or calling), I’m expecting a response on Monday. Some weekends I work a lot, some weekends I don’t touch my computer, you do what helps you sustainably be your best. Again, I’m never annoyed if you email or slack me nights and weekends. Sometimes I’ll respond immediately and sometimes I won’t, most likely depending on how the baby is sleeping :). By and large, we are a group of people who care a lot about what we do. Folks who don’t care as much tend not to last here. But building a great business is a marathon, not a sprint. It’s very important to me that you don’t burn out.
We're going to build great stuff together. Let's get going. And I'd love a letter from you too (or a poem, or a call, or anything else), anytime! -Bo
ToDos for Version 2:
Risk is a real cost that's similarly oftentimes not accounted for.
Don't start small. Start Big! For example, want to get an initiative off the ground? Send an email to key stakeholders with a schedule - voila, it's now live.
Servant leadership. Leaders eat last.
How ideas die - the first person whom the idea generator mentions it to, when that idea is most fragile, misunderstands/dismisses/thinks it’s “already being worked on by [person x] in [project y]” or “how is this different than [other thing that looks related]. Years later, we’ve still not done it.
↓ Featured Articles