Category: Management
I love Paul Graham’s Maker vs. Manager schedule concept. At Feld Technologies, we used to call this “programmer time vs. phone/meeting time” and my partner Dave Jilk and I spent a lot of time figuring out how to make it work since we each had programming work throughout the life of the business but an increasing amount of phone/meeting time as our business scaled up. Near the end I was in almost 100% phone/meeting time, which I hated, but at least I knew why.
As a VC, I’ve created a very tight approach to dealing with my manager schedule. I get up a 5am every morning, read/write online until Amy wakes up (usually between 630am and 7am), go for a run, and then switch into manager mode until 6pm. I try to schedule everything (including phone calls) – I use 30 minute increments so I have lots of “air” in my schedule since many things never take more than 10 minutes. At 6pm, I either go out to a business-related dinner, hang out with Amy, or lay on the couch and catch up on email and other random stuff.
For the points in time when I need to be on a maker schedule, I go away for a week or two. To the outside world it often doesn’t seem different, except I’m not available to get together physically and I’m not traveling anywhere. But I still blog, do email, and spend time on the phone with companies we’ve invested in. However, I control the schedule tightly, usually giving myself a several hour block of time in the afternoon for this.
I’ve decided to spend the entire summer in maker mode. The first five months of the year have been intense – tons of travel, lots and lots of stuff going on, and very little time for me. I fucked myself up by doing the 50 mile run so I was more emotionally drained than normal and I didn’t really give myself time and space to recover from it. On top of it, I don’t feel like I’ve spent enough time with Amy the first half of this year, nor do I feel like I’ve had enough me time as I feel like I’ve been spending too much time doing things for other people rather than spending time on things I want to spend time on.
Through labor day, I’m not going to travel at all, except for a few marathon weekends and a few trips to Boulder for a few days. Amy and I are holed up at our place in Keystone and I’ve decided to only have a manager schedule between 1pm and 4pm each day. That leaves me from when I wake up until 1pm to be on maker time, followed by 4pm until when I go to bed.
This rhythm starts tomorrow. It’ll be interesting to see if I can hold it for the full summer given all of the other pressures on my time. It’ll also be interesting to see the external perception of my responsiveness changes at all.
Either way, I think the only real way to learn about this type of thing is to experiment, so the experiment begins now.
Chris Moody, president and COO of Gnip, is back with a guest post in his Moody on Management series. Following are Chris’ thoughts on negotiating compensation with a prospective employee. Enjoy and comment freely!
In my last post, I provided a few tips for job candidates when interviewing at a startup. This week I wanted to cover a simple process for hiring managers to follow when communicating with candidates about salary requirements.
There is the old saying that people spend more time planning their vacation than they spend planning their retirement. I’ve found the same concept sometimes applies to job candidates when thinking about their compensation requirements. As the hiring manager, you need to ensure that a candidate has fully considered their compensation needs before you make an offer. Over the years, I’ve refined a simple and effective approach to facilitating this discussion. I’ve used this technique countless times with great results. The process starts with an email to the candidate:
“Dear Candidate,
From a skills and values standpoint, it seems like we are both excited about the possibility of you joining our company. If you agree, the next step in the process from my perspective is to determine if we are aligned from a compensation standpoint. As such, it would be helpful to get the following information from you:
– Current compensation. Please breakout your base salary from any variable compensation if applicable.
– Your view of your current compensation as it relates to your next opportunity. It is particularly helpful if you provide this feedback by selecting from either
a) I believe I’m fairly compensated and would anticipate making the same salary at my next opportunity
b) I’d be willing to take less for the right opportunity
c) I feel I’m currently under valued and looking for an increase of $x in order to be excited about my next opportunity.
If it works for you, I’d prefer to have this communication via email. Over time I’ve found that putting this stuff in writing helps people think about it more before responding.
Love,
Chris”
Of course there are no right or wrong answers. The goal here is simply to get a clear understanding of how the candidate is thinking about their future compensation by using their current compensation as a frame of reference. Best case, the candidate’s expectations align with yours and the offer moves forward with a high probability of success. Worst case your expectations don’t align but you now have a thoughtful starting point for negotiations if you still want to move forward with an offer.
A couple of additional points:
1) Even if the candidate has expressed salary requirements during the screening process or during your discussions, I strongly recommend you have this written conversation as the final step before you make an offer. For example, perhaps your conversations along the way changed their perspective on salary requirements for the position.
2) The key to this approach is to do this communication in writing. I know it can seem silly or impersonal, but it makes a huge difference in terms of requiring people to give thoughtful answers instead of answering on the spot.
Before using this approach I had more than a few occasions where candidates indicated verbally that they wanted $x, we offered $x, and then they responded with “I was thinking about it more and I really need $y to feel good about joining”. Once you hit this situation, it puts both parties in an awkward position and it can be hard to recover. You can avoid this potential pitfall with one simple email.
Oh, by the way, Gnip is hiring!
Monthly Financials, Quarterly Board Meetings, Continuous Communications
I’ve been writing about boards of directors some lately – both changing my behavior as well as thinking out loud as I explore reinventing how boards work for the book “Startup Boards” that I’m working on with Mahendra Ramsinghani. All fit in the context of continuous communications as I believe three things about early stage companies and their boards.
1. Board members should be actively engaged with the company on a continuous / real time basis.
2. Existing board meeting dynamics are often an artifact of how they’ve been done for the past 30 years.
3. The way most board meetings are currently conducted is a waste of time for management, significantly inefficient, and generally ineffective.
One of the very simple tactical things I’m shifting to is a totally different board rhythm. Historically, many of the companies I’m involved in have been on a board rhythm of meetings every four to six weeks. As they become more mature, these board meetings shift to quarterly, although many of them have mid-quarter update calls. The board meetings themselves are long affairs (even the monthly ones) – often lasting three or more hours.
At some point I’ll dissect one of these board meetings and explain all the things that are artifacts of the past. These artifacts are a result of the communication methods that existed 30+ years ago that required paper and face to face meetings and resulted in very structured communications. But for now, I’ll give you three specific things to change.
1. Separate the monthly financials from the board meeting. Send out monthly financials (Income Statement, Balance Sheet, Cash Flow) with a written analysis of them. This written analysis should be done by the CEO (or president / COO), not the CFO, and should be in English, not accounting-ese.
2. Have quarterly board meetings. These should be in person meetings with no laptops, smartphones, or iPads in the room. Give the people pads of paper to write on if they don’t bring their own (I don’t carry paper). 100% attention for the meeting. Arrange the meeting so you can have a dinner the night before or after the meeting. The meeting shouldn’t last more than four hours but should be fully engaged.
3. Provide regular weekly CEO updates, to all board members. The best entrepreneurs I know communicate regularly with everyone in the company and have a structured update process of some sort. The best CEOs send out short but focused weekly updates to their boards. These are not “templated updates” – they don’t necessarily fill in a set of things that they update each week. Often they are just a “sit in front of the computer and send out an email update” type of update full of substance, whatever is on the CEO’s mind, and requests for help. My favorites have typos and look like a blog post of mine (e.g. it looks like someone just wrote it rather than struggled over it for hours to get it just right.)
While my 2012 board meeting schedule is locked in, I plan to shift to quarterly meetings in 2013 for every board I’m on. I’m sure some of my co-investors will still want monthly meetings, but that’ll be up to the CEO to ultimately decide and I’ll commit to being in person for one a quarter, but fully engaged on a continuous basis (like I try to always be.)
Over the past year, I’ve been systematically trying to change the way the board meetings work for the companies that I’m on the boards of. I’ve done a bunch of experiments and continue to learn what works and what doesn’t work.
Ever since I started investing in the mid-1990’s I’ve been exposed to a concept called “board observer rights.” When we did investments at Mobius Venture Capital, in addition to a board seat, we always got board observer rights. This was a way for us to bring another person to the board meeting other than the board member (usually an associate or a principal but sometimes another partner), or have someone sit in for the board member if the board member wasn’t available.
Early in the life of a company, this often seems manageable. But after several rounds of financings with new investors, I’ve often found myself in board meetings with ten or more people. I think the most I’ve ever seen was about 25 people in the room for a board that had five board members. As you’d expect, there was very little critical thinking or real discussion in these board meetings; instead, the management team just presented to the mass of people in the room. And, in this context, the board members rarely formed a tight and effective working relationship.
Over the last few years, I’ve become very anti-board observer. I’ve been on several boards where the CEO didn’t allow board observers in the meeting. I’ve been on several boards where there were observers in the room, but they weren’t allowed to sit at the board table and could only “observe”. In both cases, the quality and level of discussion in the board meeting was dramatically higher.
I’ve come to believe that formal board observer rights shouldn’t exist. Instead, they should be voluntary and controlled by the CEO. In some cases, the CEO will want observers at the meeting; in other cases he won’t. But it should be up to him.
The best board meetings I’ve been at have been ones that only have the board members and select participants from the management team in the room. Casual discussion, either through dinner the night before or lunch after the board meeting, with an extended group including people from the management team and any other investors, is an effective way to engage everyone else. But the 25 person board meeting is rarely effective.
My long time friend Chris Moody, president and COO of Gnip, has offered to write some guest posts on management – we’ll call the series Moody on Management. In addition to being an outstanding early stage / high growth executive, Chris has made a study of management in startups and is extremely thoughtful about what does and doesn’t work.
His first post is aimed at anyone looking to get a job in a startup and talks about how to be effective at interviewing for a job. Feel free to weigh in if you have other “Stop, Don’t, Nevers” or “Pleases”
I love interviewing people to work at Gnip. Unless I’m having a really crappy day, I enter each interview full of hope and optimism. I’ve done countless interviews in the last 20+ years and I can easily slip into autopilot mode if I’m not careful. In order to avoid this trap, I mentally prepare by reminding myself “today could be the day I’ll meet the next great team member.” I’ve found this mental pep talk helps remind me that there is no better use of my time than investing in the interviewing process. In other words, the next interview could be a company game changer and I need to be 100% engaged.
Most interviews don’t directly lead to someone joining our company. Often the person doesn’t have the right skills or experience. There are plenty of cases where it becomes clear to the candidate that we can’t provide them an opportunity that meets their interest/needs. Both of these outcomes are normal and healthy. Unfortunately, I often find another outcome can occur which is frustrating and deflating. This situation occurs all too often when a person is so poor at interviewing that we’re unable to determine if there is a potential match. I’ll invest up to an hour in an interview trying to peel back the layers. However, I’m frequently unable to get to a substantive layer of discussion that will help both parties determine if there is a potential match. I’ll leave these interviews thinking, “Maybe that person was great, I’ll never know”. Over time, I’ve started to referring to these as the “who knows?” interviews.
The good news is that I think job candidates can follow some simple guidelines when interviewing at a startup that will help avoid the “who knows?”
Stop, Don’t, Never
- Stop selling and start engaging. In order for this to work, we both have to determine if there is a match. The best way for us to determine the match is to have a thoughtful/engaging discussion. If the interview process only involves me asking questions and you giving answers that you think will impress me, we’re going to waste a perfectly good hour.
- Don’t talk in sound bites and buzz words. You might think they make you sound smart, but they don’t because they lack substance. We need to have a real discussion. If you find yourself rehearsing answers before the interview even starts, we’re almost certainly going to have an unproductive meeting. Speak from your heart and your experience not from a script.
- Don’t agree with everything I say. I’m wrong… A LOT. I once went on an all beer and water diet for a week. Challenge me. Startups thrive when each person hired is smarter than the person hiring them. If you agree with everything I say in the interview, I’m left wondering how are you going to contribute when we are working together trying to solve tough problems.
- Avoid talking about past individual results. I know this sounds unconventional, but as the interviewer is often very hard to contextualize how these results might translate to our business. I’m much more interested in discovering what you learned in your last job that we might leverage at our company. For example, telling me you increased sales by 300% isn’t that helpful. Telling me how you learned to handle customer objections around price could prove to be very useful.
Please
- Be honest
- Ask lots of questions about stuff that matters to you. Reviewing a company’s web site before the interview will give you some reasonable background. But, I can assure you that no company web site answers all the questions about a business. It is often the case that an interviewer can learn more about the way someone thinks from the questions they ask than from the answers they give.
- Ask tough questions. You are considering investing a huge portion of your waking hours at our company. Think about the risks and the downsides of the company or the role and freely express any concerns.
- Figure out if our company is a good culture and values fit for you by asking tough situational questions based upon your past experiences. Questions like “Can you give me an example of how the company handled a situation where a customer had a bad experience with the product?” can be very revealing about how the company acts/thinks.
Ask CEOs of successful startups about their biggest challenge and they’ll often cite the inability to hire great people. My theory is there are plenty of great people, but many are just terrible at interviewing. Hopefully these few tips help lead to more great matches down the road. By the way, Gnip is hiring!
Once again we are in a zone where hiring software developers is incredibly challenging. The market is fully employed and while there is some movement between companies, great developers tend to be decided to what they are doing for a while, especially in an entrepreneurial context.
Last night I was at Angel Boot Camp in Boston. It was a dinner for about 50 angel investors – a mix of experienced ones and new ones – organized by Jon Pierce. A few of us (including me) gave short talks and there was a long, vibrant room wide group conversation.
Angus Davis followed me for the short talks. He had a bunch of great ideas, but one stood out. He said something like:
“If you want to recruit great software developers, show up at the computer science lab with a bunch of pizza the night before a major project is due.”
While he said this in the context of recruiting software developers, I think this is true of building relationships with anyone in college you are interested in working with. Just show up and bring pizza. Just show up and do something memorable that is helpful in the moment. Just show up and be generous with your time. Engage and go to where the people are, rather than wait for them to come to you, because they won’t.
This afternoon I’m teaching a class at Harvard with Jeff Bussgang and then tonight I’m teaching a class at MIT with Ken Zolot. I haven’t decided what version of pizza I’m bringing, but Angus’ line made me think about always showing up with something that everyone will remember, in addition to simply showing up in the first place, which is probably the most important point of all.
I get to work with a lot of great CEOs. When I reflect on what makes them great, one thing sticks out – they are always building their muscles. All of them.
As a marathon runner, I’ve got massive legs. Marathoner legs. They’ll look familiar to anyone who runs a lot. In contrast, I have a wimpy upper body. I’ve never enjoyed lifting weights. So I don’t spend any time on it.
Dumb.
I’d be a much better marathon runner if I worked on a bunch of other muscles as well. I’m starting to get into a swimming regimen, I’m riding my new bike around town and this summer I’ve got pilates three days a week as a goal of making it a habit. By the end of summer I hope to have a bunch of other muscles developing and a set of habits that enables me to finally maintain them.
The key phrase above is “I’ve never enjoyed lifting weights.” When asked, I say I’m bad at it. Or that I simply don’t like it. Or, when I’m feeling punchy, that jews don’t lift weights.
Of course, these are just excuses for not working on another set of muscles. If I don’t like lifting weights, surely there are things I like doing instead. I’ve always been a good swimmer – why don’t I have the discipline to go to the pool three days a week and swim? Most hotels I stay in have a swimming pool or have a health club nearby. Swimming is as easy as running – you just get in the pool and go.
“I’m bad at it and I don’t like it.” That’s what runs through my head when I lift weights. For a while, I used this narrative with swimming. But when I really think about swimming, the narrative should be “I’m ok at it and I like it.”
So why don’t I do it? I don’t really know, but I think it’s because the particular muscles I use when I swim are intellectually linked to the weight lifting muscles, which gets me into a loop of “I’m bad at it and I don’t like it.” So rather than break the cycle, I let my muscles atrophy.
Yoga is the same way. I struggle with Ashtanga Vinyasa Yoga. It’s too fast for me, I struggle to remember the poses, and my glasses constantly fall off, and I can’t follow what’s going on. So I say “I’m bad at it and I don’t like it” and then don’t do it. But I do like Bikram Yoga. It’s slower, there are the same 26 poses, and I like the heat. So why don’t I do it? Once again, the narrative gets confused in my mind and it turns into “I don’t like yoga.”
All of this is incredibly self-limiting. Rather than fight with “I’m bad at it and I don’t like it” how about changing it to “I’m not good at it but I’m going to try new approaches and find something I like.” There are many different approaches to building a particular muscle so rather than use a one-size fits all approach (e.g. I must go lift weights, which I hate), search for a different approach that you like.
If you want to be a great CEO, you need to be constantly building all of your muscles. There are going to be a lot of areas you think you aren’t good at. Rather than avoid them, or decide you don’t like them, figure out another way to work on these muscles. You’ll be a better, and much more effective CEO as a result.
Why I’m Joining The Application Developers Alliance Board of Directors
I spend all of my working time in the domain of software, Internet, and entrepreneurship. Over the past few years I’ve gotten increasingly involved in a handful of political situations – local, state, and national – that directly impact companies either in the ecosystem I’m part of or that I’ve invested in. Many of these political situations stifle entrepreneurship, innovation, or opportunities for these companies.
I’ve come to appreciate the importance of organizations of like-minded individuals working together to advocate clear positions and help acceleration entrepreneurship and innovation. Historically I’ve been very reticent to formally join anything, preferring to help as much as I can as an individual contributor. Recently, I’ve stepped up my involvement in some non-profits, adding Startup Weekend and Startup Colorado to the list of non-profits I’m working with in addition to my longstanding role as chair of the National Center for Women & Information Technology.
When my long time friend Don Dodge reached out and asked me to join the board of the Application Developers Alliance, I said yes. Developers are at the heart of the universe I work in and central to many of the things I do. Making sure they have a voice in the rapidly evolving software / Internet ecosystem on a global scale is important to me. Hopefully I can be helpful.
In the mean time, if you are a company that develops applications or provides ecosystems for application developers, take a look at the current member list and consider joining our effort.
I love getting post board meeting emails that are retrospectives from execs in the meeting. This one came a week ago from Jeff Malek, the CTO and co-founder of BigDoor. They’ve been on a tear lately and are in the process of a massive set of Q1 launches for new customers.
We had a solid board meeting, but I suggested they were being too casual about a couple of things, including communication about what was going on. This is NOT a casual group and I knew using the word casual would press a few buttons. And they did – the right ones. Jeff’s retrospective is awesome and he was game to have me share it with you to get a sense of what’s inside a CTO’s head during and after a board meeting.
I have a retrospective addiction. But as a result of looking back at our meeting today Brad, words like ‘casual’ still ringing in my ears, I recognized I’d let some of my own assumptions drive away potential opportunities, maybe even creating some problems along the way. I’ve always run under the assumptions that :
- your inbox is an order of magnitude more onerous than mine (quite)
- the best way to respect and value your time would be to limit email/communication
- you and Keith have regular communications complete with bits about what I’m up to and thinking
- you know even in the absence of communication from me that I’m working like a madman, doing everything I can to make it happen
- you also know through some process of osmosis how much I value you, Foundry, your approach, feedback, etc
Just so you don’t get the wrong idea, it’s not that I took your feedback and concluded that I needed to give you more BigDoor insight, or that you needed more info in general to get a better picture – that’s what the numbers are for.
So while all of the above assumptions are probably true to some degree, here’s the new protocol I’m going to start optimistically running under:
- thanks to your candor and aversion to BS, you’ll tell me to STFU as needed
- you’d like a concise ping about whatever, whenever from me
- you’ll give me feedback if/when it makes sense to, and I won’t expect a reply otherwise, unless I’m asking a direct question
- doing so is likely to benefit both of us, one way or another – hopefully more candid feedback will ensue
- you know that I value your time highly, and mine specifically in the context of devoting most waking hours to making BigDoor a success
- you know that I am incredibly grateful to know you and have you as an investor
Those are my new assumptions. I felt like giving this topic some time and thought, glad I did, will keep it (mostly) short going forward but hopefully you know a bit more about where I’m coming from, out of this.
Thanks again for the time today, I thought it was an awesome f-ing meeting. I always leave them on fire.