Now, This is What Blogs Are All About

In case you missed it, this article from Peggy Noonan in today’s Wall Street Journal is a great follow-up to my rant yesterday about how blogging isn’t going to eviscerate commercial email.  This is what blogging is all about, not replacing marketing tools and techniques.

Developer User Guide?

Tom Evslin wrote a two-part series this week called “Managing Programming for CEOs” (links here for Part I and Part II).  The first is pretty funny, and the second has some good thoughts in it, especially around milestone creation.

But if Tom’s had the experice he relays in Part I in real-life over and over, I have a suggestion for him:  get a great head of development he can trust, and work closely with him or her over the years to build a relationship of mutual trust so those issues are no different than they are with functional managers of other departments.  We are fortunate enough at Return Path to have two such individuals in Andy Sautins and Whitney McNamara (a fellow blogger).

Dumb Money

I don’t have a counter cliche to Fred’s two-for-one this week on Passing the Hat and Ponying Up, but I’ll counter with a different, somewhat related Fred cliche that I was reminded of today when reading Paul Graham’s essay entitled A Unified Theory of VC Suckage (form your own opinions of it, but it’s nothing if not thorough and experience-based).

There’s nothing worse than dumb money backing a dumb idea or management team.

The dumb idea or team can destroy an emerging sector pretty quickly, and the dumb VC behind the deal will just keep ponying up.  For the record, the converse is also true — there’s nothing better than smart money behind a great idea and solid team.

The classic dot com version of dumb money is the company who decides to give away its core service for free (the one where they compete with other players) in order to try to make money at something else.  It could take 2 years and a ton of VC money before that company is out of business, having figured out that they needed to charge for their core business — and that process can wash out other companies in the process who are being smarter and more conservative about things.

So instead of just cheering that your competitor is dumb, dig in and look at how smart the money is behind the company.  If the money is dumb, too, beware!

More on the Quick Flip

In case there’s anyone left that reads my blog but not Fred’s, he wrote a great follow-up posting today about the "quick flip," and how entrepreneurs and VCs have totally different (but reconcilable) views on these things.

But Hopefully More Fun Than Insurance

Return Path’s Chief Privacy Officer, Tom Bartel, has a great posting about the importance of focusing on privacy and data security within your organization, however large or small.  The lessons of the past quarter — ChoicePoint, B of A, etc., certainly lend a lot of credence to his argument.

As I mentioned in a previous post, I write 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. I recently posted George’s column on Staying Innovative as Your Business Grows (Part One). Below is a re-post of George’s second part of that column from this week, which I think my OnlyOnce readers will enjoy.

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

By George Bilbrey
Last month, as part of the Online Entrepreneur column, I shared some of Return Path’s organizational techniques we use to stay innovative as we grow. In this article, I’ll talk about the process we’re using in our product management-and-development teams to stay innovative.

The Innovation Process at Return Path
As we grew bigger, we decided to formalize our process for bringing new products to market. In our early days we brought a lot of new products to market with less formal process but also with more limited resources. We did well innovating one product at a time without that kind of process largely because we had a group of experienced team members. As the team grew, we knew we had to be more systematic about how we innovated to get less experienced product managers and developers up to speed and having an impact quickly.

We had a few key objectives when designing the process:

• We wanted to fail fast – We had a lot of new product ideas that seemed like good ones. We wanted a process that allowed us to quickly determine which ideas were actually good.

• We wanted to get substantial customer feedback into the process early – We’d always involved clients in new product decisions, but generally only at the “concept” phase. So we’d ask something like “Would you like it if we could do this thing for you?” which often elicited a “Sure, sounds cool.” And then we’d go off and build it. We wanted a process that instead would let us get feedback on features, function, service levels and pricing as we were going so we could modify and adjust what we were building based on that iterative feedback.

• We wanted to make sure we could sell what we could build before we spent a lot of time building it – We’d had a few “build it and they will come” projects in the past where the customers didn’t come. This is where the ongoing feedback was crucial.

The Process
We stole a lot of our process from some of the leading thinkers in the “Lean Startup” space – particularly Gary Blanks’ Four Steps to the Epiphany and Randy Komisar’s Getting to Plan B. The still-evolving process we developed has four stages:

Stage 1: Confirm Need

Key Elements

• Understand economic value and size of problem through intense client Interaction
• Briefly define the size of opportunity and rough feasibility estimate – maybe with basic mockups
• Key Question: Is the need valid? If yes, go on. If no, abandon project or re-work the value proposition.

Stage 2: Develop Concept

Key Elements

• Create a high fidelity prototype of product and have clients review both concept and pricing model
• Where applicable, use data analysis to test feasibility of product concept
• Draft a more detailed estimate of effort and attractiveness, basically a business model
• Key Question: Is the concept Valid? If yes, go on. If no, abandon project.

Stage 3: Pilot

Key Elements

• Build “minimum viable product” and sell (or free beta test with agreed to post beta price) with intense client interaction and feedback
• Develop a marketing and sales approach
• Develop a support approach
• Update the business model with incremental investment requirements
• Preparation of data for case studies
• Key Question: Is project feasible? If yes, go on. If no, abandon project or go back to an earlier stage and re-work the concept.

Stage 4: Full Development and Launch

Key Elements

• Take client feedback from Pilot and apply to General Availability product
• Create support tools required
• Create sales collateral, white papers, lead generation programs, case studies and PR plan.
• Train internal teams to sell and service.
• Update business model with incremental investment required
• Go forth and prosper

There are a several things to note about this process that we’ve found to be particularly useful:

• A high fidelity prototype is the key to getting great customer feedback – You get more quality feedback when you show them something that looks like the envisioned end product than talking to them about the concept. Our prototypes are not functional (they don’t pull from the databases that sit behind them) but are very realistic HTML mockups of most products.

• Selling the minimum viable product (MVP) is where the rubber meets the road – We have learned the most about salability and support requirements of new products by building an MVP product and trying to sell it.

• Test “What must be true?” during the “Develop Concept” and “Pilot Phases” – When you start developing a new product, you need to know the high risk things that must be true (e.g., if you’re planning to sell through a channel, the channel must be willing and able to sell). We make a list of those things that must be true and track those in weekly team meetings.

• This is a very cross functional process and should have a dedicated team – This kind of work cannot be done off the side of your desk. The team needs to be focused just on the new product.

While not without bumps, our team has found this process very successful in allowing us to stay nimble even as we become a much larger organization. As I mentioned in Part 1, our goal is really to leverage the strengths of a big company while not losing the many advantages of smaller, more flexible organizations.

Counter Cliche:  Good Choices Are Made From Good Options

The Counter Cliche to Fred’s VC Cliche of the Week this week, the Walk Away,  is that Good Choices Are Made From Good Options.  Fred’s right — sometimes you do have to walk away from a deal where you’ve invested a lot of time, energy, and emotion.  But as an entrepreneur, you can mitigate the number of times you have to Walk Away by developing good alternative options to a particular deal.  That way, if one option doesn’t pan out as you’d hoped, another very good option is waiting in the wings.

There’s a very business school-sounding term called the BATNA, which stands for the Best Alternative to a Negotiated Agreement.  Quite frankly, it’s just a fancy way of saying Plan B.  I wrote about the importance of the BATNA once before in How To Negotiate a Term Sheet with a VC (item 3). 

Dying to get a deal with a good VC?  If you negotiate with one of them, you may or may not end up with a deal you like, and it could suddenly change on you at the 11th hour.  If you negotiate with two or three of them, you’ll have a great backstop and won’t let the emotional investment in the deal get the best of you.  Trying to sell a company?  You’d better have a couple of acquirers in mind to maximize price. 

Sometimes, developing a good BATNA, or Plan B, can take as much time as working on Plan A.  But it’s well worth it if it ensures that you will have multiple Good Options at the end of the process — which will invariably result in a Good Choice.

I think the lesson of the BATNA is more broadly true in life, not just in business, although it may be a little bit less universally applicable to VCs looking to put money to work unless there are multiple strong companies in a sector all looking for VC around the same time.

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.

My podcast with OnBoards is live, talking with Raza and Joe about the importance of adding independence, first-time directors, and diversity to startup boards, and how Bolster helps companies achieve that quickly and inexpensively.

I’m writing a lot about Boards at the moment on the Bolster blog. We’re compiling all of those posts into a couple of eBooks. Once all of that is done, I’ll put some digests up here on StartupCEO.com as well as make the eBooks available for download.

But the gist of it is that we are working hard to break the logjam of diversity on startup boards, and we’re starting to meet with some great success with our clients.

The Direct Marketing Association (DMA) has long been a leading voice for direct marketing for nearly 100 years – back when direct marketing was really only about postal. It has evolved in that time to include phone, fax (for the nanosecond that was relevant), and then interactive tactics, including email. While the DMA has not always incorporated the new technologies in the most elegant way – the tendency has been to apply previous best practices, even when consumers have demanded a new way of thinking – the organization has made tremendous strides in recent years to re-shape itself into an organization that will be relevant for another 100 years.

And one way it is doing that is by supporting and recognizing achievements among start-ups and new ventures, they’ve announced a new award called the Early Stage Innovation Award.

As a DMA Board member and mentor of TechStars/SeedCamp companies, I am happy to see my two interests coming together in this way. Return Path’s own history of innovation and supporting new companies that are at the leading edge of the progress of direct marketing (including email) is well documented.

I’ve said that marketing is like eating French fries (and ice cream— I like snack-based analogies) and it’s hard to know when to stop grabbing for just one more. There’s always one more thing you can do to position your company and gain awareness. But I can give you a tip. This award? It’s a fry worth eating.

Awards don’t just make you feel you great; they can provide credibility in a crowded marketplace. What’s important about this Early Stage Innovation award is the exposure. Being industry-acknowledged as a company that makes new rules or changes the game? That’s the kind of ROI and opportunity that a growing company can really run with.

The other thing I love about awards and the shows where they are presented is the chance to learn about what’s new and interesting. Attending these shows helps link me to companies who may be creating tools that I didn’t even realize I was lacking and may not have heard about otherwise. I get the opportunity to learn more about problems other companies may be facing as well as seeing the solutions being proposed. For a smaller, new company, this chance to connect may lead to the support they need to grow and eventually be eligible for accolades in growth and long-term success.

If your young company is doing something new and innovative in direct marketing, consider submitting for an award. But hurry! Entries are due by May 15. Finalists will be selected and showcased during our ALL FOR ONE Marketing Summit June 20-21 in New York NY. I’m looking forward to hearing about these exciting new companies at the Summit.

My dad (one of my main CEO/entrepreneur role models) and I team-teach a business school class in entrepreneurial leadership every year at USD where a friend of his is the professor.  Sometimes I go in person, usually I just do it by video.  We did this a few weeks ago, and my dad talked through a decision-making framework that I’d never heard him mention before.

I sketched it out and really like it and am already using it internally, so I thought I would share it here as well:

To walk through it, delegating decision-making to someone on your team can be as simple as understanding where a decision falls along two different spectrums.  On the vertical axis is “How familiar is the person with this type of decision?” – meaning, has the person seen and made this kind of decision before?  This could be something like firing an employee, signing a contract, negotiating a vendor agreement.  On the horizontal axis is “What are the consequences of getting the decision wrong?” – which is really self explanatory…how big a deal is this?

The primary, upper right quadrant of “The person has made this decision before, and it’s not a huge deal” is an easy one – delegate the decision-making authority.  The two middle quadrants of “big deal, but familiar with the decision” and “never seen this before, but not a big deal” are ripe for the old adage of ask forgiveness later, not permission first, meaning it’s ok to delegate decision-making authority, but hold the person accountable for letting you know about decisions like that so you can be on the lookout for potential required clean-up.

But what I love most is the way my dad framed the final quadrant (lower left here), which is “high stakes decision, never seen this situation before.”  It can be tempting for a senior manager or CEO to just take this quadrant over and remove decision-making authority from a team member.  But it’s also a perfect teaching/coaching moment.  So the rule of thumb for this quadrant is “make the decision with me, but please come to me with a proposal on it.”

And that’s why my dad is such a great business mentor!