Category: Management
This week I had two meetings with CEOs of companies we’ve recently invested in where the question of “what is an ideal board meeting” came up. I’m writing an entire book on it called Startup Boards: Reinventing the Board of Directors to Better Support the Entrepreneur so it’s easy for me to define my ideal board meeting at this point since my head is pretty deep into it intellectually.
One of the things I always suggest to CEOs is that they be an outside director for one company that is not their own. I don’t care how big or small the company is, whether or not I have an involvement in the company, or if the CEO knows the entrepreneurs involved. I’m much more interested in the CEO having the experience of being a board member for someone else’s company.
Being CEO of a fast growing startup is a tough job. There are awesome days, dismal days, and lots of in-between days. I’ve never been in a startup that was a straight line of progress over time and I’ve never worked with a CEO who didn’t regularly learn new things, have stuff not work, and go through stretches of huge uncertainty and struggle.
Given that I am no longer a CEO (although I was once – for seven years) I don’t feel the pressure of being CEO. As a result I’ve spent a lot of the past 17 years being able to provide perspective for the CEOs I work with. Even when I’m deeply invested in the company, I can be emotionally and functionally detached from the pressure and dynamics of what the CEO is going through on a daily basis while still understanding the issues since I’ve had the experience.
Now, imagine you are a CEO of a fast growing startup. Wouldn’t it be awesome to be able to spend a small amount of your time in that same emotional and functional detachment for someone else’s company? Not only would it stretch some new muscles for you, it’d give you a much broader perspective on how “the job of a CEO” works. You might have new empathy for a CEO, which could include self-empathy (since you are also a CEO) – which is a tough concept for some, but is fundamentally about understanding yourself better, especially when you are under emotional distress of some sort. You’d have empathy for other board members and would either appreciate your own board members more, or learn tools and approaches to develop a more effective relationship with them, or decide you need different ones.
There are lots of other subtle benefits. You’ll extend your network. You’ll view a company from a different vantage point. You’ll be on the other side of the financing discussions (a board member, rather than the CEO). You’ll understand “fiduciary responsibility” more deeply. You’ll have a peer relationship with another CEO that you have a vested interest in that crosses over to a board – CEO relationship. You’ll get exposed to new management styles. You’ll experience different conflicts that you won’t have the same type of pressure from. The list goes on and on.
I usually recommend only one outside board. Not two, not three – just one. Any more than one is too many – as an active CEO you just won’t have time to be serious and deliberate about it. While you might feel like you have capacity for more, your company needs your attention first. There are exceptions, especially with serial entrepreneurs who have a unique relationship with an investor where it’s a deeper, collaborative relationship across multiple companies (I have a few of these), but generally one is plenty.
I don’t count non-profit boards in this mix. Do as much non-profit stuff as you want. The dynamics, incentives, motivations, and things you’ll learn and experience are totally different. That’s not what this is about.
If you are a CEO of a startup company and you aren’t on one other board as an outside director, think hard about doing it. And, if you are in my world and aren’t on an outside board, holler if you want my help getting you connected up with some folks.
I continually refer people to the post I Don’t Hate Marketing which is a great example of a bunch of chocolaty goodness all rolled into one little post. Now, my friends at Haiku Deck have made it slick and pretty!
Don’t let your marketing suck. Set your story free with Haiku Deck.
My shift from manager hours to maker hours is officially over. I’ve learned a lot the past two months about how I work and the challenges of trying to both shift to maker hours as well as be effective in a blended manager / maker world.
I started out in June with a hard shift to maker hours. I only scheduled calls between 1pm and 4pm – the rest of my time was unscheduled. I was able to maintain this rhythm for about 30 days before my scheduled time expanded to 5pm, then 6pm, then noon. Ultimately the backlog of “other stuff” started to creep in and it was hard to ignore it.
My primary maker task was writing – I finished Startup Communities: Building an Entrepreneurial Ecosystem in Your City, the second edition of Venture Deals: Be Smarter Than Your Lawyer and Venture Capitalist, and made some, but not nearly enough, progress on Startup Life: Surviving and Thriving in a Relationship with an Entrepreneur (which I’m writing with Amy.) There was a lot of overhead associated with each book as I worked on the website (I’ll finally launch the Startup Revolution site later this week), some publisher stuff (which I knew about from before), and plenty of “edit cycle” stuff.
I discovered that I could only write effectively for four hours a day – any more than that and whatever I did was crap. If I did anything – even check my email – before I started writing, I got virtually nothing done that day. So – the ideal “writing day” was “get up early, have coffee, write for two hours, run, write for two more hours, switch into manager mode and deal with everything else.”
The magic lesson here is something I already knew – my best time for creative work is from 5am to 7am. This is my normal rhythm that I’ve had for a long time. Trying to change it was hard and when I reflect back on things I’m not sure I was any more productive than if I had simply decided to be incredibly disciplined for the past 60 days and just written every morning from 5am to 7am and then let the day be whatever it was.
As I shift back to manager mode, that’s the approach I’m going to take for August and see what it gets me.
I get asked all the time for a list of “tech reporters / bloggers” to contact around an announcement. A few weeks ago, I was pointed to a list on the web by Brownstein & Egusa titled the Tech Reporter Contact List. It’s actually seven lists.
- Top 100 Tech Blogs
- Top Tech Blog Reporters
- Top 100 Newspapers
- Reporters At Top 100 Newspapers
- Popular Bloggers
- Mobile Blogs
- SEO Blogs
As a bonus, there’s also a good Beginners Guide To PR up on the same site.
I just joined the Internet Defense League. Think of it as the cat signal for the Internet. You’ll see a signup at the top of this blog, or just go to the Internet Defense League site. If you are so inclined as I was, please donate to the launch of the cat signal.
Our goal is to help protect the Internet forever from bad laws, monopolies, and bad actions. When the internet is in danger and we need millions of people to act, the League will ask its members to broadcast an action. With the combined reach of our websites and social networks, we can be massively more effective than any one organization.
We are in the middle of a massive societal shift from a hierarchical world to a networked world. The Internet Defense League will be on the front lines of creating a massive network to keep the Internet safe forever. I’m proud to be a part of it.
Dave Jilk, my partner in Feld Technologies, recently dug up a bunch of old stuff. I blogged one of the documents recently – The Simple Formal Beginnings Of Feld Technologies – and have a few other fun ones coming.
Today, let’s look at another example of a contract that we signed in the context of “keeping it simple.” Over the seven years we were in business, we used a very simple form we referred to as a “Professional Services Agreement.” This was the document that we signed with almost all of our clients. Every now and then we had to deal with something more complicated, but even large companies typically were willing to sign this agreement in 1990.
Over the life of Feld Technologies, we were never sued. We had our share of difficult client situations and were fired a few times, but were always direct and straightforward in how we dealt with stuff. We tried to always keep it at a business level and have a personal relationship with our clients so that when projects got into a difficult place, we could get together and work them out directly. And even when the answer was to part ways, we were always graceful about it.
The PSA shown above is our standard, but listing us as the client and MaK Technologies as the vendor. I believe it’s the first piece of business for MaK Technologies, a company co-founded by my long time and close friend Warren Katz. Dave and I met Warren through his wife Ilana, who was the employee #7 at Feld Technologies.
One of our clients was Monitor Company, at the time a young but very rapidly growing consulting firm in Cambridge. They used a bunch of Sun Workstations for all of their presentations (this was in the time of Harvard Graphics – well before the ubiquity of PowerPoint – which was completely inadequate for what they did). Instead, they used the Sun’s and Interleaf running on Unix. While we had a lot of hardware and networking expertise, we didn’t do anything with Unix (we were all about DOS and Novell Netware) so we subcontracted Warren’s company to help us with the Unix stuff at Monitor.
Warren and I have done many things together – some that have worked and some that haven’t. Twenty-two years later we still do business with a handshake. Warren has a great chapter about this in Do More Faster. Remember – keep it simple.
I saw an email from a CEO the other day. In it, he said “I” over and over again. There were numerous places where he referred to “my company”, “my team”, “my product”, and “my plan.”
It bummed me out. I know the people on “his team” and they are working their asses off. The company is an awesome company and the CEO is a great leader. But there was a huge amount of “we” in the effort and when I read the note, all I could think about was how demotivated I would be if I was on “his team” and heard “I I I.”
Several years ago, my partners at Foundry Group had an intervention with me where they asked me, as politely as they could, to stop using the word “I” when I referred to Foundry Group. I asked them why. Their response was simple – we were a team and every time I talked in public and said “I” instead of “we” it was demotivating. While we each have our own distinct personalities and behavior, Foundry Group is a team effort (Becky, Dave, Jason, Jill, Kelly, Ken, Melissa, Ross, Ryan, Seth, Tracie, and me) and by saying “I” my speech and actions were undermining this.
They were completely, 100% correct.
Since that moment I’ve been very sensitized to this. I’m sure I fuck up occasionally, but I think I’ve gotten a lot better at saying “we.” Every now and then something really bizarre happens, like a national newscast where the interviewer cuts off the intro (e.g. “I’m one of the four partners at Foundry Group”) and then does a first person interview where it’s impossible not to say “I”, but I’m still trying.
If you are the CEO, recognize that there is a lot of “we” that is enabling you to be successful. Don’t get caught up in the “I” – it’s a trap that will only backfire on you over time. It’s often tough to get it right, but there’s so much power in the team dynamic when you do.
My first business partner, Dave Jilk, emailed me our original partnership agreement for Feld Technologies. It’s one page.
We incorporated a month later as an S-Corp. It cost us $99 to do this – I remember using an organization called The Company Corporation – we called an 800 number, gave them some information, and the documents were automatically generated and filed. A short letter agreement specifying the equity splits and the boilerplate legal docs were the only legal docs we had until we sold the company in 1993.
As my partner Jason Mendelson told me after I sent him this the other day, “If things go well, it’s fine. If they don’t, it’s a fucking disaster.” And he’s completely correct – in this case things went well so there were no issues.
I continue to try to do deals this way. I lay out the terms, will negotiate a little, but am clear about what I want. If it works, great. If it doesn’t, I move on. Once the simple terms are agreed to, I let the lawyers generate hundreds of pages of documentation to support the deal. I used to read every word on every page myself (I learned that from Len Fassler, who bought Feld Technologies). I still look through the documents, but I only work with lawyers who I deeply trust to do it right (like Mike Platt at Cooley) so I focus on the stuff that matters for the specific deal.
Trust matters more than anything else to me in a deal. Sure, I occasionally get screwed in a deal, but never more than once by the same person. And, for people like Dave Jilk and my dad, I’ll work with them over and over and over again because I trust them with my life.
Keep it simple. It’s much better.
Today’s guest post from Chris Moody, the COO of Gnip, follows on the heels of the amazing Big Boulder event that Gnip put on last Thursday and Friday. To get a feel for some of the speakers, take a look at the following blog posts summarizing talks from leaders of Tumblr, Disqus, Facebook, Klout, LinkedIn, StockTwits, GetGlue, Get Satisfaction, and Twitter.
- Transition at a Massive Scale with Ken Little of Tumblr
- From Monologue to Dialogue with Daniel Ha and Ro Gupta of Disqus
- Measuring Engagement on Facebook with Sean Bruich
- Measuring Influence Online with Joe Fernandez and Matt Thomson of Klout
- Data Science at LinkedIn with Yael Garten
- Industry-Focused Social Networks with Howard Lindzon of StockTwits
- Distributed vs. Centralized Conversations with Jesse Burros of GetGlue
- Engaging with Customers Online with Wendy Lea of Get Satisfaction
- Creating the Social Data Ecosystem with Ryan Sarver and Doug Williams of Twitter
The event was fantastic, but Chris sent out a powerful email to everyone at Gnip on Saturday that basically said “awesome job on Big Boulder – our work is just beginning.” For a more detailed version, and some thoughts on why The Work Begins When The Milestone Ends, I now hand off the keyboard to Chris.
We’ve just finished up Big Boulder, the first ever conference dedicated to social data. By all accounts, the attendees and the presenters had a great experience. The Gnip team is flying high from all the exciting conversations and the positive feedback. After countless hours of planning, hard work, and sleepless nights, it is very tempting to kick back and relax. There is a strong natural pull to get back into a normal workflow. But, we can’t relax and we won’t. Here’s why.
As a company it is important to recognize the difference between a milestone and a meaningful business result. Although it took us almost nine months to plan the event, Big Boulder is really just a milestone. In this particular case, it is actually an early milestone. The real results will likely begin months from now. All too often startups confuse milestones for results. This mistake can be deadly.
Milestones Are Not Results
Milestones represent progress towards a business result. Examples of milestones that are commonly mistaken for results include:
Getting Funded. Having someone make an early investment in your company is positive affirmation that at least one person (and perhaps many) believe in what you are trying to accomplish. But, the results will come based upon how effectively you spend the money; build your team/product, etc. Chris Sacca has tweeted a few times that he doesn’t understand why startups ever announce funding. Although I haven’t heard him explain his tweets, I assume he is making the point that funding isn’t a meaningful business result so it doesn’t make sense to announce the news to the world.
Signing a partnership. Getting a strategic partnership deal signed can take lots of hard work and months/years to accomplish. Once a partnership deal is finally signed, a big announcement usually follows. The team may celebrate because all the hard work has finally paid off. But, the obvious mistake is thinking the hard work has paid off. Getting the deal signed is a major milestone, but the results will likely be based upon the amount of effort your team puts in to the partnership after the deal is signed. I’ve never experienced a successful partnership that just worked after the deal was signed. Partnerships typically take a tremendous amount of ongoing work in order to get meaningful results.
Releasing a new feature. Your team has worked many late nights getting a new killer feature in to the product. You finally get the release out the door and a nice article runs in TechCrunch the next day. The resulting coverage leads to your highest site traffic in a year. But, have you really accomplished any business results yet? Often the results will come after lots of customer education, usage analysis, or feature iterations. If no customers use the new feature, have you really accomplished anything?
Is it okay to celebrate milestones? Absolutely! Blow off steam for a half-day or a long celebratory night. Take the time to recognize the team’s efforts and to thank them for their hard work. But, also use that moment to remind everyone that the true benefits will happen based upon what you do next.
Results Increase Value
Unlike milestones, results have a direct impact on the value of the company. Results also vary dramatically based upon different business models. Examples of common results include: increasing monthly recurring revenue, decreasing customer turnover, lowering cost of goods sold (increasing gross margin).
Announcing a new feature is a milestone because it adds no value to the company. On the other hand, having customers actually adopt a new feature might increase customer retention, which could be a meaningful business result.
The Work Begins When X Ends
When I worked at Aquent, there was a point in time when we were doing lots of tradeshows. We noticed a pattern of team members taking months to prepare for an event and then returning from the tradeshow declaring the event a success. They would put a stack of business cards on their desk and spend the next several weeks digging out from the backlog of normal work stuff. The business cards would begin to collect dust and the hot leads from the show would eventually become too cold to be useful.
In order to avoid this phenomenon, someone coined the expression “the work begins when the tradeshow ends”. This simple statement had a big impact on the way that I think about milestones versus results. Since that time, I’ve used the concept of this phrase hundreds of times to remind my team and myself that a particular milestone isn’t a result. You can substitute the word “tradeshow” for whatever milestone your team has recently achieved to help maintain focus.
The most recent example? The work begins when Big Boulder ends.