What Kind of Entrepreneur Do You Want to Be?

I had a great time at Princeton reunions this weekend, as always.  As I was talking to random people, some of whom I knew but hadn’t seen in a long time, and others of whom I was just meeting for the first time, the topic of starting a business naturally came up.  Two of the people asked me if I thought they should start a business, and what kind of person made for a good entrepreneur.

As I was thinking about the question, it reminded me of something Fred once told me — that he thought there were two kinds of entrepreneurs:  people who start businesses and people who run business. 

People who start businesses are more commonly known as serial entrepreneurs.  These people come up with ideas and love incubating them but may or may not try to run them longer term.  They:

– generate an idea a minute
– have a major case of ADD
– are easily distracted by shiny objects
– would rather generate 1 good and idea and 19 bad ones than just 1 good one
– are always thinking about the next thing
– are only excited by the possibility of what could be, not what is
– are more philosophical and theoretical
– probably shouldn’t run the companies they start for more than a few months, as they will frustrate everyone around them and get bored themselves
– are really fun at cocktail parties
– say things like “I thought of auctions online way before eBay!”

The second type of entrepreneur is the type who runs businesses (and may or may not come up with the original idea).  These people:

– care about success, not just having the idea
– love to make things work
– would rather generate 1 idea and execute it well than 2 ideas
– are problem solvers
– are great with people
– are maybe less fun at cocktail parties, but
– you’d definitely want them on your team in a game of paintball or laser tag

Neither one is better than the other, and sometimes you get both in the same person, but not all that often.  But understanding what type of entrepreneur you are (or would likely be) is probably a good first step in understanding whether or not you want to take the plunge, and if so, what role you’d like to play in the business.

Book Short:  a Corporate Team of Rivals

One of the many things I have come to love about the Christmas holiday every year is that I get to go running in Washington DC.  Running the Monuments is one of the best runs in America.  Today, at my mother-in-law’s suggestion, I stopped i8n at the Lincoln Memorial mid-run and read his second inaugural address again (along with the Gettysburg Address).  I had just last week finished Doris Kearns Goodwin’s Team of Rivals:  The Political Genius of Abraham Lincoln, and while I wasn’t going to blog about it as it’s not a business book, it’s certainly a book about leadership from which any senior executive or CEO can derive lessons.

Derided by his political opponents as a “second-rate Illinois lawyer,” Lincoln, who arrived somewhat rapidly and unexpectedly on the national scene at a time of supreme crisis, obviously more than rose to the occasion and not only saved the nation and freed the slaves but also became one of the greatest political leaders of all time.  He clearly had his faults — probably at the top of the list not firing people soon enough like many of his incompetent Union Army generals — but the theme of the book is that he had as one of his greatest strengths the ability to co-opt most of his political rivals and get them to join his cabinet, effectively neutering them politically as well as showing a unity government to the people.

This stands in subtle but important contrast to George Washington, who filled his cabinet with men who were rivals to each other (Hamilton, Jefferson) but who never overtly challenged Washington himself.

Does that Team of Rivals concept — in either the Lincoln form or the Washington form — have a place in your business?  I’d say rarely in the Lincoln sense and more often in the Washington sense.

Lincoln, in order to be effective, didn’t have much of a choice.  Needing regional and philosophical representation on his cabinet at a time of national crisis, bringing Seward, Chase, and Bates on board was a smart move, however much a pain in the ass Chase ended up being.  There certainly could be times when corporate leadership calls for a representative executive team or even Board, for example in a massive merger with uncertain integration or in a scary turnaround.  But other than extreme circumstances like that, the Lincoln model is probably a recipe for weak, undermined leadership and heartache for the boss.

The Washington model is different and can be quite effective if managed closely.  One could argue that Washington didn’t manage the seething Hamilton and frothy Jefferson closely enough, but the reality is that the debates between the two of them in the founding days of our government, when well moderated by Washington, forged better national unity and just plain better results than had Washington had a cabinet made up of like-minded individuals.  As a CEO, I love hearing divergent opinion on my executive team.  That kind of discussion is challenging to manage — at least in our case we don’t have people at each other’s throats — but as long as you view your job as NOT to create compromises to appease all factions but instead to have the luxury of hearing multiple well articulated points of view as inputs to a decision you have to make, then you and your company end up with a far, far better result.

Drawing the LineWe are having a bit of a debate at the moment internally around our Sender Score deliverability business about how to handle clients who are in businesses that are, shall we say, not exactly as pure as the driven snow.  As a company that provides software and services to businesses without a vertical focus, we are often approached by all sorts of companies wanting our services where we don’t love what they do.  Examples include:

Gambling
Tobacco
Neutriceuticals
Guns
Adult content or products

Our challenges are along three dimensions, each of which is a little different.  But common threads run through all three dimensions. 

Dimension 1:  Our deliverability technology platform.   Our basic technology is used by mailers of all shapes and sizes to preview their campaigns, monitor their deliverability, and analyze their reputation metrics.  It doesn’t deploy campaigns.  Do we care who the users are?

Dimension 2:  Our full service deliverability practice that comes with consulting and high-touch account management.  This service offering has an additional layer of complexity in that our employees work closely with accounts and their web sites.  We already allow employees to opt-out of accounts where they find the work objectionable.  But is that enough?

Dimension 3:  Our whitelist, Sender Score Certified. This one is even trickier.  On the one hand, our program has fairly clear, published standards.  We do a thorough qualitative check of the client’s web site and email program to make sure, among other things, that the program is opt-in.  We monitor the client’s quantitative reputation metrics in real-time to make sure its complaint rate is low, signifying that its customers like (or at least don’t mind) receiving its email.  On the other hand, this program is supposed to signify the best of the best for email marketing and newsletters, which is why it’s used by so many ISPs and filters as their standard for defining “good mail.”  And yet on a third hand (perhaps there’s some sort of herbal remedy that can help me with that problem), for many ISPs, our program is their only whitelist, so clients who are above board, even if in a grey industry, may have no other option.

So is it our place to legislate morality, or should we just focus on what’s legal and what’s not legal?  How much accountability do clients bear for content that shows up in their emails from advertisers?  For example, and I’m making this up, what do we do if a men’s health magazine that’s a client has links in its email newsletters that are placed by an affiliate network that click through to a pornography site?  What if the pornography in question is legal in one country but not another?  How much time and energy should we spend vetting clients before we take them on?  Or monitoring them around these issues once they’re a client?  Does it matter which product they’re using?

I’d love feedback from the outside world (or the inside world) on how we should think about and handle these issues.

Jim Collins, in both Good to Great and Built to Last talked about the BHAG – the Big, Hairy Audacious Goal – as one of the drivers of companies to achieve excellence.  Perhaps that’s true, especially if those goals are singular enough and simplified enough for an entire company of 100-1000-10000 employees to rally around.

I have also observed over the years that both star performers and strong leaders drive themselves by setting large goals.  Sometimes they are Hairy or Audacious.  Sometimes they are just Big.  I suppose sometimes they are all three.  Regardless, I think successfully managing to and accomplishing large personal goals is a sign of a person who is driven to be an achiever in life – and probably someone you want on your team, whether as a Board member, advisor, or employee, assuming they meet the qualifications for the role and fit the culture, of course.

I’m not sure what the difference is between Hairy and Audacious.  If someone knows Jim Collins, feel free to ask him to comment on this post.  Let’s assume for the time being they are one and the same.  What’s an example of someone setting a Hairy/Audacious personal goal?  My friend and long-time Board member Brad Feld set out on a quest 9 years ago to run a marathon in each of the 50 states by the age of 50.  Brad is now 9 years in with 29 marathons left to go.  For those of you have never run a marathon (and who are athletic mortals), completing one marathon is a large, great and noteworthy achievement in life.  I’ve done two, and I thought there was a distinct possibility that I was going to die both times, including one I ran with Brad .  But I’ve never felt better in my life than crossing the finish tape those two times.  I’m glad I did them.  I might even have another one or two in me in my lifetime.  But doing 50 of them in 9 years?  That’s a Hairy and Audacious Goal.

For me, I think the Big goal may be more personally useful than the Hairy or Audacious.  The difference between a Big goal and a Hairy/Audacious one?  Hard to say.  Maybe Hairy/Audacious is something you’re not sure you can ever do, where Big is just something that will take a long time to chip away at.  For example, I started a quest about 10-12 years ago to read a ton of American history books, around 50% Presidential biographies, from the beginning of American history chronologically forward to the present.  This year, I am up to post-Civil War history, so roughly Reconstruction/Johnson through Garfield, maybe Arthur.  I read plenty of other stuff, too – business books, fiction, other forms of non-fiction, but this is a quest.  And I love every minute of it.  The topic is great and dovetails with work as a study in leadership.  And it’s slowly but surely making me a hobby-level expert in the topic.  I must be nearing Malcolm Gladwell’s 10,000 hours by now.

The reason someone sets out on a personal quest is unclear to me.  Some people are more goal-driven than others, some just like to Manage by Checklist, others may be ego-driven, some love the challenge.  But I do think that having a personal quest can be helpful to, as Covey would say, Sharpen the Saw, and give yourself something to focus personal time and mental/physical energy on.

Just because someone isn’t on a personal quest doesn’t mean they’re not great, by the way.  And someone who is on a quest could well be a lunatic.  But a personal quest is something that is useful to look for, interesting and worth learning more about if discovered, and potentially a sign that someone is a high achiever.

Book Short:  The Little Engine that Could

Authors Steven Woods and Alex Shootman would make Watty Piper proud.  Instead of bringing toys to the children on the other side of the mountain, though, this engine brings revenue into your company.  If you run a SaaS business, or really if you run any B2B business, Revenue Engine:  Why Revenue Performance Management is the Next Frontier of Competitive Advantage, will change the way you think about Sales and Marketing. The authors, who were CTO and CRO of Eloqua (the largest SaaS player in the demand management software space that recently got acquired by Oracle), are thought leaders in the field, and the wisdom of the book reflects that.

The book chronicles the contemporary corporate buying process and shows that it has become increasingly like the consumer buying process in recent years.  The Consumer Decision Journey, first published by McKinsey in 2009, chronicles this process and talks about how the traditional funnel has been transformed by the availability of information and social media on the Internet.  Revenue Engine moves this concept to a B2B setting and examines how Marketing and Sales are no longer two separate departments, but stewards of a combined process that requires holistic analysis, investment decisions, and management attention.

In particular, the book does a good job of highlighting new stages in the buying process and the imperatives and metrics associated with getting this “new funnel” right.  One that resonated particularly strongly with me was the importance of consistent and clean data, which is hard but critical!  As my colleague Matt Spielman pointed out when we were discussing the book, the one area of the consumer journey that Revenue Engine leaves is out is Advocacy, which is essential for influencing the purchase process in a B2B environment as well.

One thing I didn’t love about the book is that it’s a little more theoretical than practical. There aren’t nearly enough detailed examples.  In fact, the book itself says it’s “a framework, not an answer.”  So you’ll be left wanting a bit more and needing to do a bit more work on your own to translate the wisdom to your reality, but you’ll have a great jumping off point.

As I mentioned in last week’s post, I’m rebooting my work self this year, and this quarter in particular.  One of the things I am doing is getting back to basics on a few fronts.

Over the holiday break, as I was contemplating a reboot, I emailed a handful of people with whom I’ve worked closely over the years, but for the most part people with whom I no longer work day in day out, to ask them a few questions.  The questions were fairly backward looking:

1.       When I was at my best, what were my personal habits or routines that stand out in your mind?

2.       When I was at my best, what were my work behaviors or routines that stand out in your mind?

3.       When our EC was at its best, what were the team dynamics that caused it to function so well?

I got some wonderful responses, including one which productively challenged the premise of asking backward-looking questions as I was trying to reboot for the future.  (The answer is that this was one of several things I was doing as part of Rebooting, not the only thing, and historical perspective is one of many useful tools.)

Although the question clearly led itself to this, the common theme across all the answers was “back to basics.”  Part of evolving myself as a CEO as the company has grown over the years has been stopping doing particular things and starting others intentionally.  I try to do that at least once a year.  But what this particular exercise taught me is that, like the proverbial boiled frog, there were a slew of small and medium-sized things that I’ve stopped doing over the years unintentionally that are positive and productive habits that I miss.  I have a long list of these items, and I probably won’t want or need to get to all of them.  But there are a few that I think are critical to my success for various reasons.  Some of the more noteworthy ones are:

• Blogging, which I mentioned in last week’s post as an important way for me to reflect and crystallize my thinking on specific topics
• Ensuring that I have enough open time on my calendar to breathe, think, keep current with things.  When every minute of every day is scheduled, I am working harder, but not smarter
• Be more engaged with people at the office.  This relates to having open time on the calendar.  Yesterday I sat in our kitchen area and had a quick lunch with a handful of colleagues who I don’t normally interact with.  It was such a nice break from my routine of “sit at desk, order food in” or “important business lunch,” I got to clear my head a little bit, and I got to know a couple things about a couple people in the office that I didn’t previously know
• Get closer to the front lines internally.  Although I’ve maintained good external contacts as the company has grown with key clients and partners, our multi-business-unit structure has had me too disconnected from Sales and Engineering/Product in particular.  This one may take a couple months to enact, but I need to get closer to the action internally to truly understand what’s going on in the business
• Get back to a rigorous use of a single Operating System.  I’ve written a lot about this over the years, but having a David-Allen style, single place where I track all critical to do’s for me and for my team has always been bedrock for me.  I’ve been experimenting with some different ways of doing this over the last couple years, which has led to a breakdown in Allen’s main principle of “put it all in one place” – so I am going to work on fixing that
• Reading – while I have been consistently and systematically working my way through American history and Presidential biographies books over the years, I’ve almost entirely stopped reading other books for lack of time.  A well-balanced reading diet is critical for me.  So I’m working in some other books now from the other genres I love – humor (Martini Wonderland is awesome), architecture (see last week’s post on The Fountainhead), current events (I’m in the middle of Michael Lewis’ The Undoing Project and next up is Tom Friedman’s Thank You For Being Late), and business books (about to start Kotter’s A Sense of Urgency)
• Like reading, doing something creative and unrelated to work has always been an important part of keeping my brain fresh.  Coaching little league has helped a lot.  But I need to add something that’s more purely creative.  I am still deciding between taking guitar lessons (I halfway know how to play) and sculpting lessons (I don’t know a thing about it)

That’s it for now.  There are other basics that I never let lapse (for example, exercise).  But the common theme of the above, I realize now that I am writing it all out, isn’t only “back to basics.”  It’s about creating time and space for me to be fresh and exercise different muscles instead of grinding it out all day, every day.  And that’s well worth the few minutes it took me and my friends to work up this list!

Hopefully I’ll have more to say on the general topic of rebooting in another week or two as January craziness sets in with our annual kickoff meetings around the world.

Book Short:  Scrum ptious 

I just finished reading Scrum: The Art of Doing Twice the Work in Half the Time, by Jeff Sutherland and JJ Sutherland. This reading was in anticipation of an Agile Facilitation training my executive team and I are going through next week, as part of Return Path’s  Agile Everywhere initiative. But it’s a book I should’ve read along time ago, and a book that I enjoyed.

Sutherland gets credit for creating the agile framework and bringing the concept scrum to software development over 20 years ago. The book very clearly lays out not just the color behind the creation of the framework, and the central tenets of practice again, but also clear and simple illustrations of its value and benefits.  And any book that employs the Fibonacci series and includes Theodore Roosevelt’s “Man in the Arena” quote — my all-time favorite — is off to a good start by me.

I’ve always appreciated a lot of the underlying philosophy of Agile, such as regularly checking on projects, course correcting in response to feedback from customers or other stakeholders, and working hard to remove any impediments to progress in real time.

One of the author’s most poignant points is that “multitasking makes you stupid.”  I hadn’t focused in the past how agile allows you to clear away context shifts to focus on one task at a time, but that’s another great take away from the book.

Our Agile Everywhere initiative, which is designed to improve productivity across the organization, as well as increase accountability through transparency, is even more critical in my view after having read this book.

The thing that I am left struggling with, which is still very much a work in progress for us, and hopefully something that we will address more head on in our training next week, is the application of the agile framework to teams that are not involved in the production of a tangible work product, such as executive or other leadership teams.  That is something that our Agile Everywhere deployment team has developed a theory about, but it still hasn’t entirely sunk in for me.

I can’t wait for next week’s training session!  If you have any experience applying the agile framework to different types of teams in your company I’d love to hear more about it in the Comments.

Today marks Return Path’s 16^th anniversary.  I am incredibly proud of so many things we have accomplished here and am brimming with optimism about the road ahead. While we are still a bit of an awkward teenager as a company continuing to scale, 16 is much less of an awkward teen year than 13, both metaphorically and actually. Hey – we are going to head off for college in two short years!

In honor of 16 Candles, one of my favorite movies that came out when I was a teenager, I thought I’d mark this occasion by drawing the more obvious comparisons between us and some of the main characters from the movie.  My apologies to those who may have missed this movie along the way.

Why we are like Samantha (Molly Ringwald):  No, no one borrowed our underpants. But we can’t believe that people forgot our birthday either.

Why we are like Farmer Ted / The Geek (Anthony Michael Hall):  Meet my co-founder, George Bilbrey. I mean that with love.

Why we are like Jake (Michael Schoeffling):  Meet my other co-founder, Jack Sinclair. The shy, good looking one.

Why we are like Long Duk Dong (Gedde Watanabe):  We have only been in our newest business, Consumer Insight, for five minutes, but we already have a whole bunch of dates.

Why we are like Grandpa Fred (Max Showalter):  We’ve been around long enough to know the ways of the world, not to mention all the good wisecracks in the book.

There you have it. Year 17, here we come!

The Value of a Break

I’ve written before about our sabbatical policy as well as my experience with my first sabbatical five years ago.

I just got back from another sabbatical. This one wasn’t 100% work-free, which breaks our rule, but after a few false starts with it, when I realized a few weeks before it started in January that I either needed to postpone it again or work on a couple of things while I was on a break, I opted for the latter.  The time off was great. Nothing special or too exotic. A couple short trips, and lots of quality time with Mariquita and the kids.

Re-reading my post from my last sabbatical now, I realize I have re-learned those same three lessons again — that I love my job, my colleagues, and what we are working on.

But I also recognized, in three different ways, the value of a break this time around maybe more than last time.  Maybe it’s that I’m five years older or that I’ve been doing the job for five more years.  Maybe it’s because the last couple of years at work have been incredibly intense and both physically and mentally taxing.  But regardless of cause, the outcome is the same — I return to work today rested, healthy, a little tanner, a few pounds lighter, and with more clarity, resolve, and ideas for work than I’ve had in a long time.

Not only did I recognize this with Return Path on my sabbatical, but during my sabbatical, I also reengaged with two organizations (Princeton and the Direct Marketing Association) where I sit on boards and used to be extremely active but have been pretty dormant for a couple of years. The perspective I gained from that dormant time not only gave me new energy for both, but I think very focused and creative energy that I hadn’t seen in a couple of years.

Even with a little work sprinkled in, 6 weeks off and disconnected from emails, the office, and regular meetings is a blessing that I hope everyone gets to experience at some point in his or her career.

Sources of Urgency

Sometimes I wish we were in the hardware business.  Why?  It’s not the margins, that’s for sure.  It’s because hardware businesses usually have externally-imposed deadlines that create urgency in an organization around deliverables.

If you are making a chip that Dell is putting in all of its boxes, and your contract with Dell stipulates that the chip will be ready for testing on X Date and for shipping on Y Date, you darn well better hit the deadline.  If you are making software that gets installed or pre-loaded on all Samsung TVs, same thing.  Maybe it’s not the hardware business per se, but you certainly don’t see this kind of mentality in SaaS businesses very often, either because of the lack of true OEM and ship dates, or because of the now fluid nature of agile software development.

Without that kind of externally-imposed deadline, instilling true urgency gets a lot harder for a leader.  Sure, you can stick an arbitrary deadline out there and rally people to work towards it, but it’s much harder to define the consequences of missing the deadline.  Since there are in many cases no tangible and immediate business consequences, it feels a little more hollow for a leader to say “Why?  Because I said so.”  Yes, you have firing as the ultimate accountability tool in your toolkit, but again, it’s hard to feel good about using that tool when the deadline is arbitrary.

Probably the default method most companies like ours have settled on over the years is around quarterly goals.  That kind of cadence removes the arbitrary part of the problem, but it doesn’t remove the tangible business consequences part of the problem – and often, it doesn’t align with actual project deadlines.  Public companies probably can use quarterly financial results as something more tangible, but those often don’t align with deliverables quarter for quarter.  Customer conferences or marketing events can be other deadlines as well, which are less arbitrary.

I realize my blog is usually more about sharing stories than asking questions, but in this case, I’d love to hear from any reader who has a good answer to this very important management challenge.  If I get a great response, I will reblog it!

I gave a presentation to a few hundred Return Path employees in January at an all-hands conference we did called “How to Manager Your Career.”

The presentation has three sections — The Three Phases of a Career, How to Get Promoted, and How to Wow Your Manager.

While it’s not as good without the voiceover and interactivity, I thought I’d post it here…see the presentation on Slideshare.

As I said to my audience, if there’s one thing to take away from the topic, it’s this:

Managing your career is up to one, and only one person – you. 

It doesn’t matter how great a corporate culture you have, or how supportive your manager is.  You’re the only person who cares 100% of the time about your career, and you’re the only person with a longitudinal view of what you love, what you’re great at, where you’ve been, and where you want to go.