Book short:  Life Isn’t Just a Wiki

One of the best things I can say about Remote: Office Not Required,  by Jason Fried and David Heinemeier Hansson, is that it was short.  That sounds a little harsh – part of what I mean is that business books are usually WAY TOO LONG to make their point, and this one was blessedly short.  But the book was also a little bit of an angry rant against bad management wrapped inside some otherwise good points about remote management.

The book was a particularly interesting read juxtaposed against Simon Sinek’s Leaders Eat Last which I just finished recently and blogged about here, which stressed the importance of face-to-face and in-person contact in order for leaders to most effectively do their jobs and stay in touch with the needs of their organizations.

The authors of Remote, who run a relatively small (and really good) engineering-oriented company, have a bit of an extreme point of view that has worked really well for their company but which, at best, needs to be adapted for companies of other sizes, other employee types, and other cultures.  That said, the flip side of their views, which is the “everyone must be at their cubicle from 9 to 5 each day,” is even dumber for most businesses these days.  As usual with these things, the right answer is probably somewhere in between the extremes, and I was reminded of the African proverb, “If you want to go fast, go alone. If you want to go farm go together” when I read it.  Different target outcomes, different paths.

I totally agree with the authors around their comments about trusting employees and “the work is what matters.”  And we have a ton of flexibility in our work at Return Path.  With 400 people in the company, I personally spend six weeks over the summer working largely remote, and I value that time quite a bit.  But I couldn’t do it all the time.  We humans learn from each other better and treat each other better when we look at each other face to face.  That’s why, with the amount of remote work we do, we strongly encourage the use of any form of video conferencing at all times.  The importance of what the authors dismiss as “the last 1 or 2% of high fidelity” quality to the conversation is critical.  Being in person is not just about firing and hiring and occasional sync up, it’s about managing performance and building relationships.

Remote might have been better if the authors had stressed the value that they get out of their approach more than ranting against the approaches of others.  While there are serious benefits of remote work in terms of cost and individual productivity (particularly in maker roles), there are serious penalties to too much of it as well in terms of travel, communication burden, misunderstandings, and isolation.  It’s not for everyone.

Thanks to my colleague Hoon Park for recommending this to me.  When I asked Hoon what his main takeaway from the book was, he replied:

The importance of open communication that is archived (thus searchable), accessible (transparent and open to others) and asynchronous (doesn’t require people to be in the same place or even the same “timespace”).  I love the asynchronous communication that the teams in Austin have tried: chatrooms, email lists (that anyone can subscribe to or read the archives of), SaaS project management tools. Others I would love to try or take more advantage of include internal blogs (specifically the P2 and upcoming O2 WordPress themes; http://ma.tt/2009/05/how-p2-changed-automattic/), GitHub pull requests (even for non-code) and a simple wiki.

These are great points, and good examples of the kinds of systems and processes you need to have in place to facilitate high quality, high volume remote work.

How to Get Laid Off – an Employee’s Perspective

One of my colleagues at Return Path  saw my post about How to Quit Your Job about 5 years ago and was inspired to share this story with me.  Don’t read anything into this post, team!  There is no other meaning behind my posting it at this time, or any time, other than thinking it’s a very good way of approaching a very difficult situation, especially coming from an employee.

In 2009 I was working at a software security start up in the Silicon Valley.  Times were exceedingly tough, there were several rounds of layoffs that year, and in May I was finally on the list. I was informed on a Tuesday that my last day was that Friday.  It was a horrible time to be without a job (and benefits), there was almost no hiring at all that year, one of the worst economic down turns on record.  While it was a hard message,  I knew that it was not personal, I was just caught up on a bad math problem.

After calling home to share the bad news, I went back to my desk and kept working. I had never been laid off and was not sure what to do, but I was pretty sure I would have plenty of free time in the short term, so I set about figuring out  how to wrap things up there.  Later that day the founder of the company came by, asked why I had not gone home, and I replied that I would be fine with working till the end of the week if he was okay with it.  He thanked me.

Later that week, in a meeting where we reviewed and prioritized the projects I was working on, we discussed who would take on the top three that were quite important to the future of the company.  A few names were mentioned of who could keep them alive, but they were people who I knew would not focus on them at all.  So I suggested they have me continue to work on them, that got an funny look but when he thought about it , it made sense, they could 1099 me one day a week.  The next day we set it up.  I made more money than I could of on unemployment, but even better I kept my laptop and work email, so I looked employed which paid off later. 

That one day later became two days and then three, however, I eventually found other full time work in 2010.  Layoffs are hard,  but it is not a time to burn bridges.   In fact  one of the execs of that company is a reference and has offered me other opportunities for employment.

I was trading emails a few weeks ago Elliot Noss from Tucows about the current state of the economy after being on a panel together about it, and he wrote:

The market is fascinating right now. Heated competition AND layoffs and hiring freezes. It feel like an old European hotel where there are two faucets, one is too hot and the other too cold.

While a quick rant about European hotel bathrooms could be fun…we’ll just stick to the sink analogy. As anyone who has ever tried to use one of these sinks that Elliot describes knows, they’re hard to use and illogical. Sure, sometimes you want freezing water and sometimes you want scalding water (I guess), but often, you want something in between. And the only way to achieve that is to turn on both freezing and scalding at the same time? That’s weird.

Then I was on another email thread recently with a group of CEOs, when John Henry from Ride With Loop said this:

Whatever the climate, we all surely agree there is no bad time to build a good business.

How true that is!

But here’s the worrisome part. It’s impossible to predict what’s going to happen next. We are in uncharted territory here with a land war in Europe, a partial global oil embargo of a top tier oil producer, a pandemic, supply chain problems, etc. etc. There are days and circumstances where everything feels normal. Plenty of businesses, especially in the tech sector, are kicking ass. And yet there are days and circumstances that feel like 2001 or 2009. It’s tough to navigate as a startup CEO. Yes, it’s obvious you should try to have a couple years of cash on hand, and that you should be smart about investments and not get too far ahead of revenue if you’re in certain sectors (presumably if you’re in an R&D intensive field and weren’t planning to have revenue for years on end, life isn’t all that different?). But beyond that, there’s no clear playbook.

And that’s where the worrisome line comes in. I saw Larry Summers on Meet the Press last weekend, who predicted that

a recession would come in late 2023.

Wait, what? Aren’t things messed up now? Yes, inflation is high, the stock market is down, and interest rates are creeping up. But the economy is still GROWING. Unemployment is still LOW. Summers’ point is a reminder that contraction is likely, but it may still be a ways off, it depends how the Fed handles interest rate hikes (and about a zillion other things), and it’s impossible to predict. That was more worrisome to me. If we’re navigating choppy waters now, it may not just be for a couple of quarters. It may be that 4-6 quarters from now, we are in for 2-3 quarters of contraction. That is a more than most companies are able to plan for from a cash perspective.

Frothy macro environments lead to bad businesses getting created, too many lookalike businesses popping up, or weak teams getting funded. When the tide goes out, as they say, you can see who is swimming naked. But if you’re building a good business, one that has staying power and a clear value proposition, with real people or clients paying real money for a real product or service, and if you’re serious about building a good company, keep on keeping on. Be smart about key decisions, especially investment decisions, but don’t despair or give up.

We’ll all get through this.

Ratcheting Up Is Hard To Do (or Boiling the Frog, Part II)

I’ve had to ratchet down business several times over the years at Return Path.  Times were tough, revenues weren’t coming as fast as promised, my investors and I were growing weary, the dot com crash, etc. etc.  We had layoffs, consolidated jobs, cut salaries multiple times, made people wear 8 hats to get the job done.  It’s an awful process to go through.

In the last year or so, business has finally started going much better.  We’ve been fortunate in many ways that we’re still around, with products that work really well, with a good customer base, and with good and patient investors and employees, as the business climate has improved.  We’ve grown from 22 people (at our low point) up to almost 75.  But what that has meant for our organization is that we’ve had to quickly "ratchet back up," adding people, adding new functions that were previously one of many hats worn by a single person, operating at a different level.  While ratcheting down is a nightmare, it turns out that quickly ratcheting back up is in many ways just as hard on the organization.

Some examples:

– IT (internal email and servers) has been run by a part-time resource and "off the side of the desk" of our product development engineering department.  Now it is almost completely broken, and it turned out we hired a very talented IT manager, probably about three months too late.

– Staffing up is particularly tough without a dedicated HR function and with a legacy of missed budgets.  HR has been done off the side of the desk of me and my executive assistant, and we can’t keep pace any more with all the recruiting, hiring, training, and development planning.  Now that we feel like we need and can afford more staff, we need to hire an HR manager to handle it all, but we need someone in place and trained today, not three months from now.

– A 22 person company can function brilliantly as a network of Individual Contributors who loosely coordinate with each other.  But now what we need at 75 is a a few hardcore Managers that can build systems and processes so that the whole machine runs smoothly.  We don’t necessarily have those people in-house, and if we bring them in from the outside, I’m left wondering if the Individual Contributors will feel like their years of hard work aren’t appreciated if there’s a new layer of management surrounding them.

I hope we never have to ratchet down again…but part of the reason why now is that I never want to have to ratchet back up, either!

Thanks to my COO and business partner Jack Sinclair for his help with this posting.

I’ve written a lot over the years about Return Path’s Core Values (summary post with lots of links to other posts here).  And I’ve also written and believe strongly that there’s a big difference between values, which are pretty unchanging, and culture, which can evolve a lot over time.  But I had a couple conversations recently that led me to think more philosophically about a company’s values.

The first conversation was at a recent dinner for a group of us working on fundraising for my upcoming 25th reunion from Princeton.  Our guest speaker was a fellow alumnus who I’ve gotten to know and respect tremendously over the years as one of the school’s most senior and influential volunteer leaders.  He was speaking about the touchstones in his life and in all people’s lives — things like their families, their faith, the causes they’re passionate about, and the institutions they’ve been a part of.  I remember this speaker giving a similar set of remarks right after the financial crisis hit in early 2009.  And it got me thinking about the origins of Return Path’s values, which I didn’t create on my own, but which I obviously had a tremendous amount of influence over as founder.  Where did they come from?  Certainly, some came from my parents and grandparents.  Some came from my primary and secondary education and teachers.  Some came from other influences like coaches, mentors, and favorite books.  Although I’m not overly observant, some certainly came from Hebrew school and even more so from a deep reading of the Bible that I undertook about 15 years ago for fun (it was much more fun than I expected!).  Some came from other professional experiences before I started Return Path.  But many of them either came from, or were strongly reinforced by my experience at Princeton.  Of the 15 values we currently articulate, I can directly tie at least seven to Princeton:  helpful, thankful, data-driven, collaborative, results-oriented, people first, and equal in opportunity.  I can also tie some other principles that aren’t stated values at Return Path, but which are clearly part of our culture, such as intellectually curious, appreciative of other people’s points of view, and valuing an interdisciplinary approach to work.

As part of my professional Reboot project, this was a good reminder of some of the values I know I’ve gotten from my college experience as a student and as an alumni, which was helpful both to reinforce their importance in my mind but also to remember some of the specifics around their origins – when and why they became important to me.  I could make a similar list and trade and antecedents of all or at least most of our Company’s values back to one of those primary influences in my life.  Part of Reboot will be thinking through all of these and renewing and refreshing their importance to me.

The second conversation was with a former employee who has gone on to lead another organization.  It led me to the observation I’ve never really thought through before, that as a company, we ourselves have become one of those institutions that imprints its values into the minds of at least some of its employees…and that those values will continue to be perpetuated, incorporated, and improved upon over time in any organization that our employees go on to join, manage part of, or lead.

That’s a powerful construct to keep in mind if you’re a new CEO working on designing and articulating your company’s values for the first time.  You’re not just creating a framework to guide your own organization.  You’re creating the beginning of a legacy that could potentially influence hundreds or thousands of other organizations in the future.

Pret a Manager

My friend James is the GM of the Pret a Manger (a chain of about 250 “everyday luxury” quick service restaurants in the UK and US) at 36th and 5th in Manhattan.  James recently won the President’s Award at Pret for doing an outstanding job opening up a new restaurant.  As part of my ongoing effort to learn and grow as a manager, I thought it would be interesting to spend a day shadowing James and seeing what his operation and management style looked like for a team of two dozen colleagues in a completely different environment than Return Path.  That day was today.  I’ll try to write up the day as combination of observations and learnings applied to our business.  This will be a much longer post than usual.  The title of this post is not a typo – James is “ready to manage.”

1. Team meeting.  The day started at 6:45 a.m. pre-opening with a “team brief” meeting.  The meeting only included half a dozen colleagues who were on hand for the opening, it was a mix of fun and serious, and it ended with three succinct points to remember for the day.  I haven’t done a daily huddle with my team in years, but we do daily stand-ups all across the company in different teams.  The interesting learning, though, is that James leaves the meeting and writes the three points on a whiteboard downstairs near the staff room.  All staff members who come in after the meeting are expected to read the board and internalize the three points (even though they missed the meeting) and are quizzed on them spontaneously during the day.  Key learning:  missing a meeting doesn’t have to mean missing the content of the meeting.

2. Individual 1:1 meeting.  I saw one of these, and it was a mix of a performance review and a development planning session.  It was a little more one-way in communication than ours are, but it did end up having a bunch of back-and-forth.  James’s approach to management is a lot of informal feedback “in the moment,” so this formal check-in contained no surprises for the employee.  The environment was a little challenging for the meeting, since it was in the restaurant (there’s no closed office, and all meetings are done on-site).  The centerpiece of the meeting was a “Start-Stop-Continue” form.  Key learning:  Start-Stop-Continue is a good succinct check-in format.

3. Importance of values.  There were two forms of this that I saw today.  One was a list of 13 key behaviors with an explanation next to each of specific good and bad examples of the behavior.  The behaviors were very clear and were “escalating,” meaning Team Members were expected to practice the first 5-6 of them, Team Leads the first 7-8, Managers the first 10, Head Office staff the first 12, Executives all 13 (roughly).  The second was this “Pret Recipe,” as posted on the public message board (see picture below).  Note – just like our values at Return Path, it all starts with the employee.  One interesting nugget I got from speaking to a relatively new employee who had just joined at the entry level after being recruited from a prominent fast food chain where he had been a store general manager was “Pret really believes this stuff — no lip service.”

I saw the values in action in two different ways.  The first was on the message board, where each element of the Pret Recipe was broken out with a list of supporting documents below it, per the below photo.  Very visual, very clear.

The second was that in James’s team meeting and in his 1:1 meeting, he consistently referenced the behaviors.  Key learning:  having values is great, making them come to life and be relevant for a team day-in, day-out is a lot harder but quite powerful when you get it right.

4. Managing by checklist.  I wrote about this topic a while ago here, but there is nothing like food service retail to demand this kind of attention to detail.  Wow.  They have checklists and standards for everything.  Adherence to standards is what keeps the place humming.  Key learning:  it feels like we have ~1% of the documentation of job processes that Pret does, and I’m thinking that as we get bigger and have people in more and more locations doing the same job, a little more documentation is probably in order to ensure consistency of delivery.

5. Extreme team-based and individual incentive compensation.  Team members start at $9/hour (22% above minimum wage that most competitors offer).  However, any week in which any individual store passes a Mystery Shopper test, the entire staff receives an incremental $2/hour for the whole week.  Any particular employee who is called out for outstanding service during a Mystery Shop receives a $100 bonus, or a $200 bonus if the store also passes the test.  The way the math works out, an entry level employee who gets the maximum bonus earns a 100% bonus for that week.  But the extra $2/hour per team member for a week seemed to be a powerful incentive across the board.  Key learning: team-based incentive comp is something we use here for executives, but maybe it’s worth considering for other teams as well.

6. Integrated systems.  Pret has basically one single software system that runs the whole business from inventory to labor scheduling to finances.  All data flows through it directly from point of sale or via manager single-entry.  All reports are available on demand.  The system is pretty slick.  There doesn’t seem to be much use of side systems and side spreadsheets, though I’m sure there are some.  Key learning: there’s a lot to be said for having a little more information standardized across the business, though the flip side is that this system is a single point of failure and also much less flexible than what we have.

7. Think time.  I’ve written a little about working “on the business, not in the business,” or what I call OTB time, once before, and I have another post queued up for later this summer about the same.  Brad Feld also very kindly wrote about it in reference to Return Path last week.  Working in retail means that time to work on IMPORTANT BUT NOT URGENT issues is extremely hard to come by and fragmented.  I suspect that it comes more at the end of the day for James, and it probably comes a lot more when he doesn’t have someone like me observing him and asking him questions.  But his “office” (below), exposed to the loud music and sounds and smells of the kitchen, certainly doesn’t lend itself to think time!  Key learning:  of course customers come first, but boy is it critical to make space to work OTB, not just ITB.  Oh, and James needs a new chair that’s more ergonomically compatible with his high countertop desk.

Years ago, I spent a few weekends working in my cousin Michael’s wine store in Hudson, NY, and I wrote up the experience in two different posts on this blog, the first one about the similarities between running a 2-person company and a 200-person company, and the second one about how in a small business, you have to wear one of every kind of hat there is.  My conclusion then was that there are more similarities than differences when it comes to running businesses of different types.  My conclusion from today is exactly the same, though the focus on management made for a very different experience.

Thanks to James, Gustavo, Orlanda, Shawona, and the rest of the team at the 36th & 5th Pret for putting up with the distraction of me for the bulk of the day today — I learned a lot (and particularly enjoyed the NYC Meatball Hot Wrap) and now have to figure out how to return the favor to you!

Was anyone else as appalled as I am by the contents of Connie Loizos’s recent article, Coming out of COVID, investors lose their taste for board meetings? The stories and quotes in the article about VCs reducing their interest and participation in Board meetings, not showing up, sending the junior associate to cover, etc. are eye opening and alarming if widespread. 

The reasons cited in the article are logical—overextended VCs, Zoom fatigue, and newbie directors. Connie’s note that “privately, VCs admit they don’t add a lot of value to boards” is pretty funny to read as a CEO who has heard a ton of VCs talk about how much value they add to boards (although the good ones DO add a lot of value!).  

For the most part, everything about the substance of this article just made me angry.  

Disengaged or dysfunctional boards aren’t just bad for CEOs and LPs; they’re bad for everyone. If the world has truly become a place where the board meeting is nothing more than a distraction for CEOs, and investors think it’s a tax they can’t afford, then it’s time to hit the reset button on boards and board meetings. 

Here are four things that need to happen in this reset:

VCs need to do their job well or stop doing it. The argument that investors did too many deals in the pandemic so now they don’t have any time is a particularly silly one, since the pandemic reduced the amount of time VCs needed to spend on individual board meetings as well. I used to have four board meetings each year with directors who were traveling for the meetings, having dinners, spending time with the team and sitting in on committee meetings. 

Today, boards are lucky to have one in-person meeting a year (more on that later). And as everything else takes less time, and there’s little transit, any given VC should have doubled the time they spend on board meetings.

Serving on a board post-investment is a central part of the VC role. They have obligations to the founders they back and to the LPs they represent. The entire role is “find deals, execute deals, manage the portfolio.” 

If they no longer have time for the third job, they need to admit that to both founders and LPs before stepping down. If a VC can’t be bothered to focus on minding their investments and adding value, they should work with the company to find their replacement.  

CEOs need to take their job as leader of the board seriously. Would a good CEO just throw their hands up if they found management team meetings boring or a waste of time? No. They’d fix the structure of the team or meetings. If not, they shouldn’t be the CEO. 

It’s no different with boards. Whether or not the CEO is the board chair, they’re the leader of the organization. So, one of the few “must do” items in their job description is leading the board. The board is part of the CEO’s team, just like the management team. 

CEOs get to call the meetings, run the meetings, and insist on attendance. The CEO’s obligation is to make it easy and meaningful for everyone so the board isn’t a tax but rather a secret weapon for the company’s success. As my long-time independent director Scott Weiss used to tell me, boards consume whatever you put in front of them. Garbage in, garbage out. That means paying careful attention to the board materials, to meeting etiquette, and everything in between.

If the CEO doesn’t know how to do that, they should find a CEO mentor who can teach them, observe some well run boards in action through their network, or read Startup Boards: A Field Guide to Building and Leading an Effective Board of Directors, a book I just published along with co-authors and VCs Brad Feld and Mahendra Ramsinghani.

Here’s one tip on making Board prep more efficient: work your Operating System and your Board Book formats so you do one set of reporting for the company and management team that is 95% reusable without any changes for your board.

The format for Board meetings needs to evolve. Board meetings need to evolve in our world of hybrid work just as office work needs to evolve. The format that works for in-person can’t just “lift and shift” to Zoom as is, indefinitely.

Here’s how I’m steering my board:

• I insist on one or two “old school” meetings per year, meaning in-person attendance required, half a day long, and including a meal and even an activity. If I’m only going to see my directors together infrequently, I make it mandatory, but I also make it worthwhile and fun.
  
• Remote meetings that happen between the in-person meetings are becoming shorter and tighter. I still send out a lot reading material beforehand, but I make sure to keep the focus on a fixed number of major topics to keep the discussion engaging.
  
• We need a new set of expectations around Zoom meeting etiquette for long meetings. It’s okay to ask people to close their email, browser, and Slack before the meeting starts. If a meeting is more than two hours long, a 15 minute break in the middle is important. Use breakout rooms to mix up topic discussions and working sessions.
  
• I am trying a new meeting format to maximize director conversation and team development. I start every meeting with a director-only session for half an hour that’s not exactly an Executive Session but is more fun and social—usually including a nonwork discussion topic, as if we were sitting around the dinner table having a cocktail. That gets the conversational juices flowing. Then when my team and observers join the meeting, I ask those people to turn their video off, and I ask directors to adjust their Zoom setting to “hide participants not on video” to keep the number of Zoom squares down to the bare minimum. Any time a team member or observer wants to engage in a particular topic, they turn their video on. Then we follow the meeting with Executive Session and Closed Session and a single-director debrief with me. That is a lot of moving pieces to manage, I find that but doing so keeps the meeting fresh and well paced.
  
• Finally, I’m following Fred Wilson’s advice and running a very short survey post-meeting to ask directors basic questions so they can summarize their thinking for me and the team: What are we doing well? What do we need more work on? And did the meeting meet your expectations?

Companies need to Follow the Rule of 1s

The secret to engaged and diverse boards is to mix up their membership more than most companies do. Our Board Benchmark study at Bolster indicates that the vast majority of private company boards have no independent directors at all—only founders and investors—and every year, the vast majority of the “open independent seats” specified in those companies’ charters go unfilled. 

It’s hard work hiring a new independent board member, and it rarely rises to the top of the CEO’s priority list. But the more independent the board is, and the more diverse the board is in every way (in terms of demographics as well as experience and background), the more robust the conversations around the table become, and the more valuable the board is to the CEO.

My Rule of 1s for building highly effective boards is simple:

• Add independent directors to your board on Day 1
• Try to limit your Board to 1 founder/team member
• Then, for every 1 investor on your board,
• Add 1 independent director

A great board is one of a company’s greatest assets. A weak board can kill a company. A mediocre board is just a waste of time. There’s no question that running an effective board, or serving as an effective director, takes serious time and energy and diligence. But that’s not a reason not to try.

(This post first ran on TechCrunch+ and is also running on the Bolster blog)

Call Me

A fine song by Blondie from 1980 and from the soundtrack of the movie American Gigolo.  And also something that reminded me about the importance of not relying too much on email this past month. 

 I had surgery on my left wrist in early March to hopefully fix a nagging tendonitis problem.  And while I could still write and type post-op, I got sore pretty quickly every day, so I tried to keep those activities to a minimum.  As you might imaging, I do an awful lot of email and IM in my line of work.  So what was my short response to a huge number of emails and IMs for a few weeks?  “Call me.”

 My communications, especially with remote employees, not only didn’t suffer while I couldn’t type a lot – they were stronger than ever.  Even short, two-minute phone conversations – the remote equivalent of someone sticking their head in my office – are preferable to IM or email in many cases.  There’s nothing like the sound of someone’s voice to add real texture to a dialog and to avoid misunderstandings.

I just said this to a fellow little league coach, and it’s certainly true for baseball.  I’ve coached games with sloppy and/or blowout wins in the past.  You take the W and move on, but it’s hard to say “good game” at the end of it and feel like you played a good game.  And I’ve coached games where we played our hearts out and made amazing plays on offense and defense…and just came up short by a run.  You are sad about the L, but at least you left it all out on the field.

Is that statement true in business?

What’s an example of a “bad” win?  Let’s say you close a piece of business with a new client…but you did it by telling the client some things that aren’t true about your competition.  Your win might not be sustainable, and you’ve put your reputation at risk.  Or what about a case where you release a new feature, but you know you’ve taken some shortcuts to launch it on time that will cause downstream support problems?  Or you negotiate the highest possible valuation from a new lead investor, only to discover that new lead investor, now on your Board, expects you to triple it in four years and is way out of alignment with the rest of your cap table.

On the other side, what’s an example of a “good” loss?  We’ve lost accounts before where the loss was painful, but it taught us something absolutely critical that we needed to fix about our product or service model.  Or same goes for getting a “pass” from a desirable investor in a financing round but at least understanding why and getting a key to fixing something problematic about your business model or management team.

What it comes down to is that both examples – little league and business – have humans at the center.  And while most humans do value winning and success, they are also intrinsically motivated by other things like happiness, growth, and truth.  So yes, even in business, sometimes a good loss is better than a bad win.

Debunking the Myth of Hiring for Domain Expertise vs. Functional Expertise

As a CEO scaling your business, you’ll invariably want to hire in new senior people from the outside.  Even if you promote aggressively from within, if you’re growing quickly enough, you’ll just need more bodies.  And if you’re growing really fast, you will be missing experience from your employee base that you’ll need to augment.

For years, I’ve thought and heard that there’s a basic tradeoff in hiring senior people — you can hire someone with great domain expertise, or you can hire someone with great functional expertise, but it’s almost impossible to find both in the same person, so you need to figure out which is more important to you.  Would I rather hire someone who knows the X business, or someone who is a great Head of X?  Over the course of the last year, I’ve added four new senior executives to the team at Return Path, and to some extent, I’ve hired people with deep functional expertise but limited domain expertise.  Part of that has been driven by the fact that we are now one of the larger companies in the email space, so finding people who have “been there, done that” in email is challenging.

But the amount of senior hiring I’ve done recently has mostly shown me that the “domain vs. functional” framework, while probably accurate, is misleading if you think of it as the most important thing you have to consider when hiring in senior people from the outside.

What’s more important is finding people who have experience working at multiple growth stages in their prior jobs, ideally the scaling stage that you’re at as a business.  It makes sense if you stop and think about it.  If your challenge is SCALING YOUR BUSINESS, then find someone who has DONE THAT before, or at least find someone who has worked at both small companies and larger companies before.  I suppose that means you care more about functional expertise than domain expertise, but it’s an important distinction.

Looking for a new industrial-strength CFO for your suddenly large business?  Sure, you can hire someone from a Fortune 500 company.  But if that person has never worked in a startup or growth stage company, you may get someone fluent in Greek when you speak Latin.  He or she will show up on the first day expecting certain processes to be in place, certain spreadsheets to be perfect, certain roles to be filled.  And some of them won’t be.  The big company executive may freeze like a deer caught in the headlights, whereas the stage-versatile executive will invariably roll up his or her sleeves and fix the spreadsheet, rewrite the process, hire the new person.  That’s what scaling needs to feel like.

I always thought that spam blacklists were well intentioned but problematic for the email ecosystem, since they are vigilantes in action and have no accountability and trackability. Periodically, I’ve even pondered whether or not they violate someone’s first amendment rights. It’s maddening to know you’re a good guy in the email world, you can get put on a blacklist because some anti-spam zealot decides he or she doesn’t like you on a whim, you can’t complain or get off of the list, you may not even know you’re on the list, then you’re downloaded thousands of times by naively trusting or equally zealous sysadmins, and boom — your emails aren’t getting through any more.

Then yesterday, I was looking at what’s probably the first blacklist for blog comment spam, dubbed by Brad Feld as BLAM. I immediately found myself using it myself to prevent my blog from getting overrun by the newest Internet evil. (Of course, I should be so lucky…my fledgling blog has all of one comment on it, but I’m sure there are scores of people ready to comment at a moment’s notice.)

So here we are at the dawn of a new era: the beginning of the blacklist for blam. I’m an early adopter of Jeff Nolan’s pioneering list and proud of it, which made me rethink my view of email blacklists for about five minutes. It didn’t ultimately change that view — email blacklists still have all the problems I mentioned above and have run amok — but it does make me hope that there’s a better long-term solution for stopping blam than the one the world of email has ended up with. Fred Wilson has some good thoughts on better tools for this as well.

Necessity, as always, is the mother of invention, but hopefully the blam blacklist situation won’t get out of control before someone tries to fix it, which may be too late. What I think we need now to solve the blacklist problem is a blacklist of blacklists, but that’s another story for another posting.