🔎
Nov 7 2013

Getting the Most out of Your Investors

Getting the Most out of Your Investors

Fred Wilson has been a venture investor and director in Return Path since 2000, first with Flatiron Partners and then with Union Square Ventures.  We’ve been through a lot of wars together.  In a couple of weeks, he and I are team-teaching a class in Entrepreneurship at Princeton, and the professor gave us the assignment of writing two pairs of blog posts to tee up discussion with the class.  The first two posts were mine on selecting investors and Fred’s on selecting investments.  This is my second one
and Fred’s post on the other side of the topic is here.

Once you’ve done a venture financing and the smoke clears, you have to transition the relationship you have with your new investor from the courting phase to building a CEO-Director relationship for the long haul.  Here are a few thoughts on how best to do optimize the relationship once it’s established.

  1. Take onboarding seriously.  I always say that the hiring process for new employees doesn’t end when the employee starts
it ends 90 days later after some deliberate onboarding and a two-way review to check in and see how things are going.  Adding a new Board member is the same.  Onboard him or her with some of the same rigor and materials with which you’d onboard a new executive.  Touch base a lot early on.  Schedule an in-person 1:1 check-in after a few months to see how things are going
  2. Give news early and often.  CEOs who wait until Board meetings to share all news are missing out on the point of a good director relationship, as well as missing the point of how communications work in the 2010s.  This is especially true with bad news.  No one likes to get it, but the earlier people hear it, the more they can thoughtfully process it and provide help
  3. Ask for and give feedback early and often.  Though there are certainly some exceptions, venture investors are notoriously bad about giving and receiving feedback.  If you set the tone by asking for feedback regularly – then being sure to internalize and act on it and check back in to see if improvements are obvious – you can get even the most reticent director to speak up.  And there’s no reason you shouldn’t be providing feedback in near-real time as well.  Just because a director is your boss doesn’t mean he or she is meeting your expectations, and it’s a partnership, not a true hierarchical relationship
  4. Ask for help and give assignments.  As a friend of mine says to her kids all the time, You don’t A-S-K, you don’t G-E-T.  If Board members don’t have specific things to work on, they either do nothing, or they do things you don’t need help on.  Drive the work like you would with any team member
  5. Foster independent relationships with your team and other directors.  The hourglass model – where the CEO sits in between the Board and the management team and filters all dialog and data from one group to the other – is outdated.  A director will be much more able to add value to you and to the organization if he or she has an independent point of view as to what’s going on with your team and what other directors are thinking
  6. Encourage directors to speak their minds.  As awful as company politics are, Board politics are worse.  Try to create an environment where directors aren’t shy about saying what’s really on their mind.  You don’t want to get through a Board meeting and then have someone pull you aside and say “what I really think is
”  This means you need to ask them direct questions, not be defensive in your verbal or body-language reaction, and make sure you allow for Executive Sessions at Board meetings
  7. Hold directors accountable.  If you give a Board member an assignment, make sure it gets done on time and the way you asked for it.  If you have a director who is sitting in your Board meetings doing email the whole time, politely (and maybe privately, at least the first time) call him out on it.  If you don’t hold directors accountable, then just like your staff, they will learn that you don’t really mean what you say
  8. Use their time wisely.  No one likes to waste time – certainly not professional investors who sit on a dozen boards.  Get Board materials out early, run productive Board meetings, and while you include some social element like a dinner or outing, make sure even that has the right group and is at the right kind of venue
  9. Augment the Board with independent directors.  Venture directors can be amazingly helpful resources for you and your company.  But they typically have limitations as to their range of operating experience.  If you want to build a great Board and add some counterweights to your VCs, add one or more independent directors who are experienced business operators with experience serving on Boards as well

Year ago when we both first started blogging, Fred and I wrote a whole series of Venture ClichĂ© and Counter-ClichĂ© posts.  Writing these two makes me realize how much fun that was!  I’m looking forward to the class at Princeton next week and to seeing the kinds of questions these four posts inspire.

Dec 19 2013

5 Ways to Get Your Staff on the Same Page

5 Ways to Get Your Staff on the Same Page

[This post first appeared as an article in Entrepreneur Magazine as part of a new series I’m publishing there in conjunction with my book, Startup CEO:  A Field Guide to Scaling Up Your Business]

When a major issue arises, is everybody at your company serving the same interests? Or is one person serving the engineering team, another person serving the sales team, one board member serving the VC fund, another serving the early-stage “angels” and another serving the CEO? If that’s the case, then your team is misaligned. No individual department’s interests are as important as the company’s.

To align everyone behind your company’s interests, you must first define and communicate those goals and needs. This requires five steps:

  1. Define the mission. Be clear to everyone about where you’re going and how you’re going to get there (in keeping with your values).
  2. Set annual priorities, goals, and targets. Turn the broader mission into something more concrete with prioritized goals and unambiguous success metrics.
  3. Encourage bottom-up planning. You and your executive team need to set the major strategic goals for the company, but team members should design their own path to contribution. Just be sure that you or their managers check in with them to assure that they remain in synch with the company’s goals.
  4. Facilitate the transparent flow of information and rigorous debate. To help people calibrate the success, or insufficiency, of their efforts, be transparent about how the organization is doing along the way. Your organization will make better decisions when everyone has what they need to have frank conversations and then make well-informed decisions.
  5. Ensure that compensation supports alignment (or at least doesn’t fight it). As selfless as you want your employees to be, they’ll always prioritize their interests over the company’s. If those interests are aligned – especially when it comes to compensation – this reality of human nature simply won’t be a problem.

Taken in sequence, these steps are the formula for alignment. But if I had to single out one as the most important, it would be number 5: aligning individual incentives with companywide goals.

It’s always great to hear people say that they’d do their jobs even if they weren’t paid to, but the reality of post-lottery-jackpot job retention rates suggests otherwise. You, and every member of your team, “work” for pay. Whatever the details of your compensation plan, it’s crucial that it aligns your entire team behind the company’s best interests.

Don’t reward marketers for hitting marketing milestones while rewarding engineers to hit product milestones and back office personnel to keep the infrastructure humming. Reward everybody when the company hits its milestones.

The results of this system can be extraordinary:

  • Department goals are in alignment with overall company goals. “Hitting product goals” shouldn’t matter unless those goals serve the overall health of your company. When every member of your executive team – including your CTO – is rewarded for the latter, it’s much easier to set goals as a company. There are no competing priorities: the only priority is serving the annual goals.
  • Individual success metrics are in alignment with overall company success metrics. The one place where all companies probably have alignment between corporate and departmental goals is in sales. The success metrics that your sales team uses can’t be that far off from your overall goals for the company. With a unified incentive plan, you can bring every department into the same degree of alignment. Imagine your general counsel asking for less extraneous legal review in order to cut costs
  • Resource allocation serves the company, rather than individual silos. If a department with its own compensation plan hits its (unique) metrics early, members of that team have no incentive to pitch in elsewhere; their bonuses are secure. But if everyone’s incentive depends on the entire company’s performance, get ready to watch product leads offering to share developers, unprompted.

This approach can only be taken so far: I can’t imagine an incentive system that doesn’t reward salespeople for individual performance. And while everyone benefits when things go well, if your company misses its goals, nobody should have occasion to celebrate. Everybody gets dinged if the company doesn’t meet its goals, no matter how well they or their departments performed. It’s a tough pill to swallow, but it also important preventive medicine.

Mar 6 2014

Open Vacation

At Return Path, we’ve had an “open vacation” policy for years, meaning that we don’t regulate the amount of time off people take, and we don’t accrue for it or pay out “unused” vacation if someone leaves the company.  I get asked about this all the time, so I thought I’d post our policy here and also answer a couple follow-up questions I usually get about it.

First, here’s the language of our policy:

Paid Time Off

You’re encouraged to take as much time off as you can while maintaining high performance and achieving your goals. We don’t count the hours you work, so why should we count the hours you don’t? (Unless you’re a non-exempt employee, and only then because we have to!) Take what you need, when you can, and make sure to arrange coverage with your team. If you haven’t had a vacation in a while, you can expect to get a friendly nudge from your manager to get away from the office!

Use your Paid Time Off (PTO) for planned vacations, days off for appointments, religious, or personal holidays that are not offered in your country, community service days, or if you need an unanticipated, last-minute day off to care for a sick child or family member. Statutory or legally protected leaves of absence, such as medical leave, maternity/parental leave, family medical leave or unpaid leave, are governed by separate regulations that will not be affected by our PTO policy. See the Regional section for a list of statutory leaves of absence in your country.

Paid Time Off scheduling is subject to approval by your manager, who has sole discretion to approve or deny requests under this policy. Requests of greater than two consecutive weeks or more than two weeks in one three-month period require approval of your Executive Committee member.

The first question I always get is, “Wow – does that really work?  What issues have you had with it?  My response:

No issues with it at all, other than it’s a little weird to apply internationally, where we have 50 people across 7 countries, since most of those countries have significantly more generous vacation policies/customs than the US.  But we generally make it work.

The second question I get is whether people abuse it or not:

In all the years we’ve done it, we only ever had one person attempt to abuse the policy, one time.  People do still have to ask their managers if it’s ok to take time off, and they do still have to get their jobs done.

Finally, people ask me for general advice on implementing this kind of policy:

Continue to track days off and generate reports for managers every quarter so they at least know whether their people are taking not enough or too much – generally people will take not enough, and you will need to encourage them to take more.  Also, our managers were *really* worried about launching this, so we had to do some hand-holding along the way. 

The results of this policy for us have generally been great.  People take about the same amount of true vacation they used to take, maybe a little more.  They definitely take more half-days and quarter-days where they probably still get a full day worth of work done, without worrying about counting the hours.  Best of all, there’s a strong signal sent and received with this kind of policy that we trust our team members to do what they need to do in order to live their lives AND get their jobs done.

Jun 28 2018

Feedback Overload and Confusion – a Guide for Commenting on Employee Surveys

We run a massive employee survey every year or so called The Loop, which is powered by Culture Amp.  We are big fans of Culture Amp, as they provide not only a great survey tool but benchmarks of relevant peer companies so our results can be placed in external context as well as internal context.

The survey is anonymous and only really rolled up to large employee groups (big teams, departments, offices, etc.), and we take the results very seriously.  Every year we run it, we create an Organization Development Plan out of the results that steers a lot of the work of our Leadership team and People team for the coming year.

I just read every single comment that employees took the time to write out in addition to their checkbox or rating responses.  This year, that amounted to over 1,200 verbatim comments.  I am struggling to process all of them, for a bunch of reasons you’d expect.  Next year we may give employees some examples of comments that are hard to process so they understand what it’s like to read all of them…and we may reduce the number of places where employees can make comments so we try to get only the most important (and more detailed) comments from people to keep the volume a little more manageable.

But I thought it might be useful to give some general advice to people who write comments on anonymous surveys.  Your company may have every good intention of following up on every last comment in an employee survey (we do!), but it’s difficult to do so when:

  • The comment is not actionable.  For example, “The best thing about working at Return Path is…’I can afford to live nearby.'”  That doesn’t do much for us!
  • The comment is too vague.  For example, “I’m not the engineer I was a year ago” – we have no idea what that means.  Is it a plus or a minus?  What is behind it?
  • The comment is likely to be in conflict with other comments and doesn’t give enough detail to help resolve conflicts.  40 positive comments about the lunch program in an office and 40 negative comments about the lunch program in the same office kind of get washed out, but “Lunches are good, but please have more gluten-free options” is super helpful.
  • The comment lacks context.  When the answer to the question “What would be the one thing we could do right away to make RP a better place to work?” is “Investing in some systems,” that doesn’t give us a starting point for a next step.
  • The commenter disqualifies him or herself.  Things like “Take everything I’m saying with a grain of salt…I’m just an engineer and have no real idea of what I’m doing” that punctuate a comment are challenging to process.
  • The commenter forgets that the comments are anonymous.  “I have serious problems with my manager and often think of leaving the company” is a total bummer to hear, but there’s not a lot we can do with it.  I hope with something like this that you are also having a discussion with someone on the People team or your manager’s manager!

We’re doing everything employees would expect us to do – reading the ratings and comments, looking at trends over time, breaking them down by office and department, and creating a solid Organizational Development Plan that we’ll present publicly and follow up on…but hopefully this is useful for our company and others in the future as a guide to more actionable commenting in employee surveys.

Mar 26 2014

Book Short: Internet Fiction

Book Short:  Internet Fiction

It’s been a long time since I read Tom Evslin’s Hackoff.com, which Tom called a “blook” since he released it serially as a blog, then when it was all done, as a bound book.  Mariquita and I read it together and loved every minute of it.  One post I wrote about it at the time was entitled Like Fingernails on a Chalkboard.

The essence of that post was “I liked it, but the truth of the parts of the Internet bubble that I lived through were painful to read,” applies to two “new” works of Internet fiction that I just plowed through this week, as well.

Uncommon Stock

Eliot Pepper’s brand new startup thriller, Uncommon Stock, was a breezy and quick read that I enjoyed tremendously. It’s got just the right mix of reality and fantasy in it. For anyone in the tech startup world, it’s a must read. But it would be equally fun and enjoyable for anyone who likes a good juicy thriller.

Like my memory of Hackoff, the book has all kinds of startup details in it, like co-founder struggles and a great presentation of the angel investor vs. VC dilemma. But it also has a great crime/murder intrigue that is interrupted with the book’s untimely ending.  I eagerly await the second installment, promised for early 2015.

The Circle

While not quite as new, The Circle  has been on my list since it came out a few months back and since Brad’s enticing review of it noted that:

The Circle  was brilliant. I went back and read a little of the tech criticism and all I could think was things like “wow – hubris” or “that person could benefit from a little reflection on the word irony”
 We’ve taken Peter Drucker’s famous quote “‘If you can’t measure it, you can’t manage it” to an absurd extreme in the tech business. We believe we’ve mastered operant conditioning through the use of visible metrics associated with actions individual users take. We’ve somehow elevated social media metrics to the same level as money in the context of self-worth.

So here’s the scoop on this book.  Picture Google, Twitter, Facebook, and a few other companies all rolled up into a single company.  Then picture everything that could go wrong with that company in terms of how it measures things, dominates information flow, and promotes social transparency in the name of a new world order.  This is Internet dystopia at its best – and it’s not more than a couple steps removed from where we are.  So fiction
but hardly science fiction.

The Circle  is a lot longer than Uncommon Stock and quite different, but both are enticing reads if you’re up for some internet fiction.

May 8 2014

Book Short: Like Reading a Good Speech

Book Short:  Like Reading a Good Speech

Leaders Eat Last, by Simon Sinek, is a self-described “polemic” that reads like some of the author’s famous TED talks and other speeches in that it’s punchy, full of interesting stories, has some attempted basis in scientific fact like Gladwell, and wanders around a bit.  That said, I enjoyed the book, and it hit on a number of themes in which I am a big believer – and it extended and shaped my view on a couple of them.

Sinek’s central concept in the book is the Circle of Safety, which is his way of saying that when people feel safe, they are at their best and healthiest.  Applied to workplaces, this isn’t far off from Lencioni’s concept of the trust foundational layer in his outstanding book, Five Dysfunctions of a Team.  His stories and examples about the kinds of things that create a Circle of Safety at work (and the kinds of things that destroy them) were very poignant.  Some of his points about how leaders set the tone and “eat last,” both literally and figuratively, are solid.  But his most interesting vignettes are the ones about how spending time face-to-face in person with people as opposed to virtually are incredibly important aspects of creating trust and bringing humanity to leadership.

My favorite one-liner from the book, which builds on the above point and extends it to a corporate philosophy of people first, customer second, shareholders third (which I have espoused at Return Path for almost 15 years now) is

Customers will never love a company unless employees love it first.

A couple of Sinek’s speeches that are worth watching are the one based on this book, also called Leaders Eat Last, and a much shorter one called How Great Leaders Inspire Action.

Bottom line:  this is a rambly book, but the nuggets of wisdom in it are probably worth the exercise of having to find them and figure out how to connect them (or not connect them).

Thanks to my fellow NYC CEO Seth Besmertnik for giving me this book as well as the links to Sinek’s speeches.

Oct 9 2014

Book Short: Way, Way Beyond Books

Book Short:  Way, Way Beyond Books

The Everything Store: Jeff Bezos and the Age of Amazon, by Brad Stone, was a great read.  Amazon is a fascinating, and phenomenally successful company, and Jeff is a legendary technology leader.  The Everything Store is a company and personal biography and totally delivers.

Forget about the fact that Amazon is now almost $100B in revenues and still growing like mad.  I find it even more amazing that a single company could be the largest ecommerce site on the planet while successfully pioneering both cloud computing services and e-readers.  The stories of all these things are in the book.

As a CEO, I enjoyed reading more of the vignettes behind the things that Amazon is reputationally known for in the tech world – doors as desks, their unique meeting formats, the toughness of the culture, the extensive risk taking of growth over profits, and what works and does not work about Bezos’ authoritative and domineering style.  And it’s always great to be reminded that even the biggest and best companies had to cheat death 10 times over before “arriving.”

This is good fun and learning for anyone in the business world.  It reminded me most of Walter Isaacson’s biography of Steve Jobs ,which I wrote about here, although it’s more of a company history and less of a biography than the Jobs book.

Sep 17 2015

The Playbook

As Return Path gets older, we are having more and more alums go on to be successful senior executives at other companies – some in our space, some not.  It’s a great thing, and something I’m really proud of.  I was wondering the other day if there’s effectively some kind of “RP Playbook” that these people have taken with them.  Here’s what I learned from asking five of them.

People-related practices are all prominent as part of the Playbook, not surprising for a People First company.  Our Peer Recognition program, which is almost as old as the company and has evolved over time, was on almost everyone’s list.  Open Vacation is also part of the mix, as was a focus on getting Onboarding right so new employees start off on the right foot.  Live 360s were on multiple lists, too, as were Skip-Level 1:1s.

Beyond People-related programs, though, there was general agreement among the five that the mentality of trust in management was something they brought with them in this mythical Playbook.  Specific examples include fostering a culture of idea sharing, having difficult conversations, driving as much self-management as possible, focusing on managing high performers as opposed to spending all our cycles on managing low performers, balancing freedom and flexibility with performance and accountability, and going above and beyond and bending rules for sick employees and their families.

Connections and networking – both internal and external – made the cut as well.  A lot of those, especially external ones, are used to foster benchmarking, best practices sharing, and “leveling up” to help teams and organizations scale by learning from others.

Finally, there were some specific execution-related Playbook items from establishing a vision, to translating it into goals and fostering alignment across the organization, to instituting processes and systems instead of throwing bodies at problems.  One important element of execution cited is the importance of giving new and existing managers the tools to grow as the company grows.

This is hardly an exhaustive Playbook and unscientific in its construction, but I thought the “top of mind” answers from five senior people I respect was an interesting list and probably the beginning of something broader.

Thanks to the following friends for their contributions to this post:  Jack Sinclair, CFO of Stack Overflow; Angela Baldonero, SVP Human Resources for Kimpton Hotels; Tom Bartel, CEO of ThreatWave; Chad Malchow, CRO for Gitlab; and Dennis Malaspina, CRO for Parsley.

Feb 9 2017

Book Short: Why Wait?

A Sense of Urgency, by John Kotter, is a solid book – not his best, but worth a read and happily short, as most business books should be.  I originally was going to hold off on writing this post until I had more time, but the subject matter alone made me think that was a mistake and that I should write it while it’s fresh in my mind.  <g>

The three tools to fight complacency are the organizing framework for the book — bring the outside in, behave with urgency every day, and turn crises into opportunities — are all good thoughts, and good reminders of basic management principles.  But there were a couple other themes worth calling out even more.

First up, the notion that there is a vicious cycle at play in that urgency begets success which creates complacency which then requires but does not beget urgency.  The theme is really that success can drive arrogance, stability, and scale that requires inward focus — not that success itself is bad, just that it requires an extra level of vigilance to make sure it doesn’t lead to complacency.  I’ve seen this cycle at different times over the years in lots of organizations, and it’s one of the reasons that if you look at the original companies on the Dow Jones Industrials index when it was expanded from 12 to 30 around 100 years ago, only one of them (GE) still exists.

Second, that busy-ness can masquerade as urgency but actually undermines urgency.  A full calendar doesn’t mean you’re behaving with urgency.  Kotter’s example of an Indian manager is great:

If you watch the Indian manager’s behavior carefully and contrast it with the hospital executive’s, you find that the former relentlessly eliminates low-priority items from his appointment diary. He eliminates clutter on the agenda of the meetings that do make it into his diary. The space that is freed up allows him to move faster. It allows him to follow up quickly on the action items that come out of meetings. The time freed up allows him to hold impromptu interactions that push along important projects faster. The open space allows him to talk more about issues he thinks are crucial, about what is happening with customers and competitors, and about the technological change affecting his business.

Finally, Kotter’s theme of “Urgent patience” is a wonderful turn of phrase.  As he says,

It means acting each day with a sense of urgency but having a realistic view of time. It means recognizing that five years may be needed to attain important and ambitious goals, and yet coming to work each day committed to finding every opportunity to make progress toward those goals.

How true is that?  It’s not just that big ships take a long time to turn…it’s that big opportunities take a long time to pursue and get right.  If they didn’t…everyone would do them!  Urgent patience is what allows you to install a bias for action in your team without causing panic and frenzy, which is never productive.

Thanks to my friend Chad Dickerson for recommending this book, a great read as part of Operation Reboot Matt.

Oct 17 2019

The Nachos Don’t Have Enough Beef in Them!

(This is an excerpt from Chapter 23 of Startup CEO, “Collecting Data,” in which I write about the importance of observing and learning from customers and friends of the firm, as well as employees.)

Here’s a story for you that happened 10+ years ago. I’m sitting at the bar of Sam Snead’s Tavern in Port St. Lucie, Florida, having dinner solo while I wait for my friend Karl to arrive. I ask the bartender where he’s from, since he has an accent. Nice conversation about how life is rough in Belfast and thank goodness for the American dream. I ask him what to order for dinner and tell him a couple of menu items I’m contemplating. He says, “I don’t know why they don’t listen to me. I keep telling them that all the people here say that the nachos aren’t good because they don’t have enough beef in them.”

I order something else.

Five minutes later, someone else pounds his hand on the bar and barks out, “Give me a Heineken and a plate of nachos.”

The bartender enters the order into the point-of-sale system.

What’s the lesson? Listen to your front-line employees—in fact, make them your customer research team. I have seen and heard this time and again. Employees deal with unhappy customers, then roll their eyes, knowing full well about all the problems the customers are encountering and also believing that management either knows already or doesn’t care. There’s no reason for this! At a minimum, you should always listen to your customer-facing employees, internalize the feedback and act on it. They hear and see it all. Next best prize: ask them questions. Better yet: get them to actively solicit customer feedback

Aug 22 2013

Unknown Unknowns

Unknown Unknowns

There are known knowns. These are things we know that we know. There are known unknowns. That is to say, there are things that we know we don’t know. But there are also unknown unknowns. There are things we don’t know we don’t know.”   –Donald Rumsfeld

Say what you will about Rumsfeld or the Iraq war, but this is actually a great and extensible quote.  And more to the point, I’d say that one of the main informal jobs of a CEO, sort of like Connecting the Dots in that it’s not one of the three main roles of a CEO) is to understand and navigate known unknowns and unknown unknowns for your organization (hopefully you already understand and navigate the known knowns!).  Here’s what I mean:

  • An example of a known unknown is that a new competitor could pop up and disrupt your business from below (e.g., the low end) at any minute.  Or let’s say your biggest partner buys one of your competitors.  These are the kinds of things you and your team should be cognizant of as possibilities and always thinking about how to defeat
  • While I suppose unknown unknowns are by definition hard to pin down, an example of an unknown unknown is something like a foreign leader deciding to nationalize the industry you’re in including your local subsidiary, or a young and healthy leader in your organization dying unexpectedly, or September 11.  I suppose these are “black swan” events that Nassim Nicholas Taleb made famous in his book.

Helping your team identify potential known unknowns and think three steps ahead is critical.  But helping your team turn unknown unknowns into known unknowns is, while much harder, probably one of the best things you can do as CEO of your organization.  And there are probably two ways you can do this, noting that by definition, you’ll never be able to know all the unknowns.  As you might expect, the way to do that comes down to increasing your pool of close-at-hand knowledge.

First, you and your executive team can have as broad a view of your industry and corporate ecosystem, and of the economy at large, as possible.  It’s critical for business leaders to read diverse publications, to share insights with teammates, and to network with experts both inside and outside your space.
Second, you can design a culture so that information flows freely up, down, and sideways — so that people in your organization want to share information instead of hoard it.  That’s easier said than done, and there’s more than a blog post worth of what has to go into making that a reality.  But think about the CIA and all the flak they got about failure to connect the dots around September 11.  To close this post where I opened it, you can be the chief connector inside your organization…but you need to get your organization connecting the dots itself.