Sometimes, Things Are Messy

Many people who run companies have highly organized and methodical personality types – in lots of cases, that’s probably how they got where they got in life.  And if you work long enough to espouse the virtues of fairness and equality with the way you manage and treat people, it become second nature to want things to be somewhat consistent across an organization.

But the longer we’re in business at Return Path and the larger the organization gets, the more I realize that some things aren’t meant to fit in a neat box, and sometimes inconsistency is not only healthy but critical for a business to flourish.  Let me give a few examples that I’ve observed over the past few years.

• Our sales team and our engineering team use pretty different methodologies from each other and from the rest of the company in how they set individual goals, monitor progress against them, and compensate people on results
• The structure of our sales and service and channel organizations in Europe are very different from our emerging ones in Latin America and Asia/Australia – and even within Europe, they can vary greatly from country to country
• Although we have never been a company that places emphasis on job titles, our teams and leadership levels have become even more inconsistent over the years – sometimes a manager or director has a bigger span of control or more impact on the business than a VP does, sometimes individual contributors have more influence over a broad section of groups than a manager does, etc.

It’s taken me a while to embrace messiness in our business.  I fully acknowledge that I am one of the more hyper-organized people around, which means this hasn’t come naturally to me.  But the messiness has been very productive for us.  And I think it’s come from the combination of two things:  (1) we are a results-oriented culture, not a process-driven culture, and (2) we give managers a lot of latitude in how they run their teams.

I’m certainly not saying that striving for some level of consistency in organization is a bad goal – just that it’s probably not an absolute goal and that embracing messiness sometimes makes a lot of sense.  Or perhaps phrased more actionably, allowing individual managers to use their own judgment and creativity in setting up teams and processes, as long as they follow high-level guidelines and values can be an incredibly productive and rewarding way of maximizing success across an enterprise.

Solving Problems Together

Last week, I started a series of new posts about our core values (a new tag in the tag cloud for this series) at Return Path.  Read the first one on Ownership here.

Another one of our core values is around problem solving, and ownership is intrinsically related.  We believe that all employees are responsible for owning solutions, not just surfacing problems.  The second core value I’ll write about in this series is written specifically as:

We solve problems together and always present problems with potential solutions or paths to solutions

In terms of how this value manifests itself in our daily existence, for one thing, I see people working across teams and departments regularly, at their own initiative, to solve problems here.  It happens in a very natural way.  Things don’t have to get escalated up and down management chains.  People at all levels seem to be very focused on solving problems, not just pointing them out, and they have good instincts for where, when, and how they can help on critical (and non-critical) items.

Another example, again relative to other workplaces I’ve either been at or seen, is that people complain a lot less here.  If they see something they don’t like, they do something about it, solve the problem themselves, or escalate quickly and professionally. The amount of finger pointing tends to be very low, and quite frankly, when fingers are pointed, they’re usually pointed inward to ask the question, “what could I have done differently?”

The danger of a highly collaborative culture like ours is teams getting stuck in consensus-seeking.  Beware!  The key is to balance collaboration on high value projects with authoritative leadership & direction.

A steady flow of problems are inherent in any business.  I’m thankful that my colleagues are generally quite strong at solving them!

As I mentioned in a previous post, I’ve recently started writing a column for The Magill Report, the new venture by Ken Magill, previously of Direct magazine and even more previously DMNews. I share the column with my colleagues Jack Sinclair and George Bilbrey and we cover how to approach the business of email marketing, thoughts on the future of email and other digital technologies, and more general articles on company-building in the online industry – all from the perspective of an entrepreneur. Below is a re-post of George’s column from this week, which I think my OnlyOnce readers will enjoy.

Guest Post: Staying Innovative as Your Business Grows (Part One)

By George Bilbrey

As part of The Magill Report’s Online Entrepreneur column, I’d like to share some of Return Path’s learning about how to stay innovative as you grow. In Part One, I’m going to cover some of the organizational techniques we’ve been employing to stay innovative. In Part Two, I’ll talk about some of the practices we’re using in our product management and development teams.

When we were starting our deliverability business at Return Path, staying innovative was relatively easy. With a total of four people (two employees, two consultants) involved in selling, servicing, building and maintaining product, the environment was very conducive to innovation:

• Every employee had good conversations with customers every day—We could see the shortcoming of our tools and got great, direct feedback from our clients.

• Every employee was involved in every other function in a very detailed way—This gave everyone a strong intuition as to what was feasible. We all knew if the feature or function that the client was asking for was within the realm of the possible.

• We were very, very focused on creating customers and revenue—We were a startup. If we drove revenue above costs, we got to take home a salary. Every conversation and decision we made came down to finding out what would make the service (more) saleable. It was stressful, but productively stressful and fun.

We were lucky enough to come up with good concept and the deliverability services market was born. Our business grew rapidly from those two full-time employees to where we are today with about 250 employees in eight countries supporting more than 2,000 customers.
Growing our business has been one of the most challenging and fun things I’ve ever had the chance to take part in. However, growth does have some negative impacts on innovation if you don’t manage it right:

• Supporting the “core” comes at the expense of the new—As you grow, you’ll find that more and more of your time is spent on taking care of the core business. Keeping the servers running, training new employees, recruiting and other internal activities start to take up more and more of your time as the business grows. Clients ask for features that are simple linear extensions of your current capabilities. You don’t have time to focus on the new stuff.

• Staying focused gets harder as the business get more intricate—As your business grows, it will become more complex. You’ll build custom code for certain clients. You’ll need to support your stuff in multiple languages. You find that you have to support channel partners as well as direct customers (or vice versa). All this takes away from the time you spend on “the new” as well.

• Creating “productive stress” becomes difficult—At the point our business became profitable, life became a lot better. There was less worry and we could invest in cool new innovative things. However, it’s hard to drive the same urgency that we had when we were a start-up.

Of course, a bigger profitable company has advantages, too. For one, there are the profits. They come in awfully handy in funding new initiatives. And while they can remove the “productive” stress that comes from needing revenue to keep a venture going, they can also remove the distracting stress of needing revenue to keep a venture going. Second is the ability to capitalize on a well-known brand—the result of many years of marketing, PR, and thought leadership within the industry. Third, we have access to a much broader array of clients now, which I’ll explain the importance of in a minute. Finally, back-end support and process—an accounting team that gets the invoices out, an HR team that helps make strategic hires—makes the folks engaged in product development more productive.

So what have we done to leverage these strengths while also combating the forces of inertia? We’ve done a lot of different things, but the major focus has been, well, focus. For the two to three key initiatives that we think are fundamental to growing our business, we’ve built a “company inside the company” to focus on the project at hand. A good example of this is our recent Domain Assurance product, our first product to address phishing and spoofing. Initially, we tried to run the project by assigning a few developers and part of a product manager’s time with some part-time support from a sales person. It didn’t work. We weren’t able to move forward quickly enough and some of our folks were getting fried.

Our answer was to create a dedicated team inside our business that focused entirely on the phishing/spoofing product space. The key components of the “company inside the company” were:

• Fully dedicated, cross-functional resources—Our team represented very much the kinds of folks you’d find in an early stage company: development, system administration, sales and marketing. This team worked as a team, not as individuals. Many of these resources were fully dedicated to this new initiative.
• Deadline-driven productive stress—When we launch new products, they go through four discrete stages (I’ll explain this in more detail in my next column). We set some pretty tight deadlines on the later stages.

• Customer involvement, early and often—The team involved customers in building our new product from the very beginning. From continuously reviewing early wireframes, prototypes and then beta versions of the product, we got a lot of client and prospective client feedback throughout the process.

We’re still working on the exact right formula for our “company inside a company” approach, but our experience to date has shown us that the investment is worth it.

Why CEOs Shouldn’t Mess with Engineers

I went to the Vasa Royal Warship Museum in Stockholm the other day, which was amazing – it had a breathtakingly massive 17^th century wooden warship, which had been submerged for over 300 years, nearly intact as its centerpiece.  It’s worth a visit if you’re ever there.

The sad story of its sinking seems to have several potential causes, but one is noteworthy both in terms of engineering and leadership.  The ship set sail in 1628 as the pride of the Swedish navy during a war with Poland.  It was the pride of King Gustavus Adolphus II, who took a keen personal interest in it.  But the ship sank literally minutes after setting sail.

How could that be?  While the king was quick to blame the architect and shipbuilder, later forensics proved both to be mostly blameless.

Likely cause #1:  after the ship was designed and construction was under way, the King overruled the engineers and added much heavier cannons on the upper armament deck.  The ship became top-heavy and much less stable as a result, and while the engineers tried to compensate with more ballast below, it wasn’t enough.

Likely cause #2:  the King cut short the captain’s usual stability testing routines because he wanted to get the ship sailing towards the enemy sooner.

Let’s translate these two causes of failure into Internet-speak.  #1:  In the middle of product development, CEO rewrites the specs (no doubt verbally), overruling the product managers and the engineers, and forces mid-stream changes in code architecture.  #2:  In order to get to market sooner, the CEO orders short-cuts on QA.  I’m sure you’ll agree the results here aren’t likely to be pretty.

So product-oriented leaders everywhere…remember the tale of Gustavus Adolphus and the Vasa Royal Warship and mind the meddling with the engineers!

Backwards

I came to an interesting conclusion about Return Path recently.  We’re building our business backwards, at least according to what I have observed over time as the natural course of events for a startup.  Here are a few examples of what I mean by that.

Most companies build organically for years…then start acquiring others.  We’ve done it backwards.  In the first 9 years of our company’s life, we acquired 8 other businesses (SmartBounce, Veripost, Re-Route, NetCreations, Assurance Systems, GasPedal Consulting, Bonded Sender, Habeas).  Since then, we’ve acquired none.  There are a bunch of reasons why we front loaded M&A:  we were working hard to morph our business model to achieve maximum success during the first internet downturn, we knew how to do it, there was a lot of availability on the sell side at good prices.  And the main reason we’re not doing a lot of it now is that there’s not much else to consolidate in our space, though we’re always on the lookout for interesting adjacencies.

Most companies tighten up their HR policies over time as they get larger.  We’ve gotten looser.  For example, about a year and a half ago, we abolished our vacation policy and now have an “open” system where people are encouraged to take as much as they can take while still getting their jobs done.  Or another example is an internal award system we have that I wrote about years ago here.  When we launched this system, it had all kinds of rules associated with it — who could give to whom, and how often.  Now those rules have faded to black.  I’d guess that most of this “loosening up” over time is a vote of confidence and trust in our team after years of demonstrated success.

Most companies start by investing heavily in product, then focus on investing in sales and marketing.  Here we haven’t exactly gotten it backwards, but we’re not far off.  Two years ago, one of our major company-wide initiatives/priorities was “Product First.”  This year, we decided that the top priority would be “Product Still First.”  The larger we’ve gotten, the more emphasis we’ve placed on product development in terms of resource allocation and visibility.  That doesn’t mean we’re not investing in marketing or the growth our sales team — we are — but our mentality has definitely shifted to make sure we continue to innovate our product set at a rapid clip while still making sure existing products and systems are not only stable but also improving incrementally quickly enough.

I don’t know if there’s a single generalizable root cause as to why we’ve built the company backwards, or if that’s even a fair statement overall.  It might be a sign that my leadership team is maturing, or more likely that we didn’t know what we were doing 11-12 years ago when we got started — but it’s an interesting observation.  I’m not even sure whether to say it’s been good or bad for us, though we’re certainly happy with where we are as a company and what our prospects look like for the foreseeable future.

But it does lead me to wonder what else we should have done years ago that we’re about to get around to!

There’s been much coverage in the news of Saturday’s passing of President Ronald Reagan, but I will add a new wrinkle by trying to distill down what I know and remember of The Great Communicator’s leadership style into a few simple lessons of note for CEOs.

Lesson 1: Sunny optimism motivates the people you lead, but only when it’s balanced with hard-headed realism. Reagan’s message that tomorrow can be a better day than today was powerful and timely for the American psyche, but he didn’t just assume that because he said it, it would be true. He backed up his message with (a) an understanding that the American economy itself was in the doldrums in the late ’70s, and (b) policies designed to fix the economy. Whether you agree with those policies or not, you have to respect the fact that Reagan as a leader wasn’t just talk — he combined the talk with reality-based action. That’s super important when communicating key messages to a company of any size.

Lesson 2: Simplicity of messaging beats out measured intellectualism in broad-based communications. Reagan’s view of the 40-year-old Cold War when he took office was “we will win, and they will lose.” Much easier to rally around than messages of detente and containment (this quote came from an editorial by former Reagan staffer Peter Robinson in today’s Wall St. Journal). Similarly, the bigger and more diverse the group you’re talking to inside your company or in a speech or in the press, the more important it is to boil your key message down to something people can easily take away with them and repeat at home later to their spouse or friends.

Lesson 3: Nobody’s perfect, and you don’t have to be perfect either. He may have been, electorally, the most popular president of our generation, but Reagan certainly had his many and sometimes glaring faults. History will acknowledge his faults but overall judge him on his performance. It was noted (also in today’s Journal, I think) that Reagan got a lot of little things wrong, but in the end, he will be remembered because he got a few big things very, very right. Perfection is something that most mortals can’t achieve, certainly not in a high profile position like President or CEO of anything, whether a 10-person startup or a nation.

Love him or hate him, the man was one of the most prominent leaders of our time. I’m sure there are more lessons from Reagan’s legacy than these three for CEOs, but this is a start, anyway.

Book Short:  Which Runs Faster, You or Your Company?

Leading at the Speed of Growth, by Katherine Catlin at the Kauffman Center for Entrepreneurial Leadership is a must read for any entrepreneur or CEO of a growth company.  It’s one of the best books I’ve ever read targeted to that audience – its content is great, its format is a page-turner, and it’s concise and to the point.

The authors take you through three stages of a growth company’s lifestyle (Initial Growth, Rapid Growth, and Continuous Growth) and describe the “how to’s” of the transition into each stage:  how you know it’s coming, how to behave in the new stage, how to leave the old stage behind.

I didn’t realize it when I started reading the book, but Brad had one of the quotes on the back cover that says it all:  “There are business books about starting a company, but they tend to deal with the mechanics of business plans and financing.  Then there are books about ‘how to be the CEO of a Fortune 500 company.’  This is the first book I’ve seen that details the role of the CEO of a small but growing company.”  Thanks to my colleague George Bilbrey for pointing this one out to me.

UPDATE:  Brad corrects me and says that I should mention Jana Matthews, who co-wrote the book with Katherine Catlin and is actually the Kauffman Center person of the duo.

I haven’t done a book review yet on this blog because I haven’t found a very relevant one. I will do more as I go here — I’ve actually read a few pretty useful business books lately — but there’s no better book to kick off a new category of postings here than the one I just finished: The MouseDriver Chronicles: The True-Life Adventures of Two First-Time Entrepreneurs.

The book details how two freshly-minted Wharton MBAs skipped the dot com and investment banking job offers to start a two-person company that produced the MouseDriver (a computer mouse shaped like a the head of a golf club) back in 1999-2000. It’s a great, quick read and really captures the spirit of much of what I’m trying to do with this blog, which is talk about first-time CEO issues, or company leadership/management issues in general.

Although it’s not about an internet business, the book also has an interesting side story, which is the powerful impact that email had on the MouseDriver business, with an email newsletter the entrepreneurs started that developed great readership and ultimately some viral marketing. Sort of like a blog, circa 1999.

Thanks to Stephanie Miller at Return Path for giving me the book!

Anything Worth Doing is Worth Doing Well, Part II

I posted Part I a really long time ago — it’s pretty self explanatory.  I was given a related gem today from fellow blogger Hawaiian leadership coach Rosa Say:

"If you don’t have the time to do it right, when will you have the time to do it over?"

Now there’s something to keep in mind every time you’re doing something halfway!

Blogiversary

Next week will mark the one year anniversary of my blog (and for that matter, Brad’s blog).  It’s been a lot of fun, so I think I’ll celebrate by taking two weeks off and going to Europe with Mariquita (well, ok, I was planning on doing that anyway).

Even if no one read OnlyOnce, I’d be happy I’m writing it for all of the reasons I expressed here back in June.  But lots of people do read it, more and more every day.  In fact, an executive at Yahoo! who I met earlier this week actually quoted it to me — as Bruno Kirby said in When Harry Met Sally, “the first time someone has ever quoted me back to me before.”

In my very first posting, which explains the blog’s title and mission, I said I’d try not to be too extraneous with the material I post.  So I took a look through some stats this morning about the last year of blogging:

– Including this, I’ve written 131 postings, about one every three days

– Typepad doesn’t keep stats on blog topics/categories, so this is an estimate (and postings can be associated with multiple categories), but it looks like I’ve posted 6 times about books, 10 times about current events, 4 times about travel, 7 times about blogs, 9 times about “business” (whatever that means), 52 times about email/web/tech, 40 times about entrepreneurship, and 38 times about leadership/management.  So at least I stayed more or less on point.

– I’ve received a total of 125 comments, or less than one per posting (this is NOT a truly interactive medium!)

– I have about 1,000 regular readers, roughly 70% via RSS feed, 20% via email subscription, and 10% via live alerts or just regular web visitors

– My Amazon Associates link has generated about 150 sales for a total of $2,700 and about $170 in affiliate fees to me, which basically covers the cost of my Typepad subscription

Thanks to everyone who reads and comments.  Feedback is always welcome for year two!

What a View

We’ve done 360-degree reviews for five years now at Return Path.  Rather than the traditional one-way, manager-written performance review, we instituted 360s to give us a “full view” of an employee’s performance.  Reviews are contributed by the person being reviewed (a self assessment), the person’s manager, any of the person’s subordinates, and a handful of peers or other people in the company who work with the person.  They’re done anonymously, and they’re used to craft employees’ development plans for the next 12 months.

The results of 360 are a wonderful management tool.  Mine in particular have always been far more enlightening than the one-way reviews of the past.  The commonality in the feedback from different people is a little bit of what one former manager of mine used to say — when three doctors tell you you’re sick, go lie down.

I know a lot of companies do 360s, but we had two great learnings this year that I thought were worth noting.  First, we automated the process (used to manual in Excel and Word) by using an ASP solution called e360 Reviews from Halogen Software.  It was GREAT.  The tool must have saved us 75% of the administrative time in managing the process, and it made the process of doing the reviews much easier and more convenient as well.  I strongly recommend it.

Second, we started a new tradition of doing Live 360s for the senior staff here.  All people who filled out a review for a senior staff member were invited into an hour-long meeting that was moderated by a great organizational development consultancy we work with, Marc Maltz and Nancy Penner from Triad Consulting.  The purpose of each meeting was to resolve any conflicting comments in the reviews and prioritize strengths as well as development objectives.  We also did a very quick session where the senior staff did “speed reviews” in person of the rest of the company’s leadership team that tried to accomplish similar objectives in a much more compressed time frame and format.

So far (we’re in the middle of them — actually, the team is doing my review as I write this), the results are wonderful.  We’re going to end up producing MUCH crisper and more actionable development plans for our senior staff this year than we ever have in the past.  And the tone of the meetings has been incredibly supportive and constructive.  Having an outside moderator made a huge difference.

And yes, just in case you’re wondering, it is a little bit unnerving to know that a room full of 15 people is discussing you.  Especially when you can hear them all laughing through the wall.  🙂