First day at Techstars:  Where do you start?

I’m a new mentor this year at Techstars, a program in its third or fourth year in Boulder (and this year also in Boston for the first time) that provides a couple dozen companies with seed capital, advice and mentorship, and summer “incubation” services in a really well conceived for-profit venture started by David Cohen in Colorado.

Yesterday was my first day up there with my colleague George Bilbrey, and we met with three different companies, two of which we will tag team mentor through the summer.  I won’t get into who they are at the moment, mostly because I’m not sure what the confidentiality issues are offhand, but I’ll make the first of a series of posts here about observations I make from doing this work.

Yesterday’s thought was:  Where do you start?

It was so interesting to meet with in some cases pretty raw companies.  They weren’t exactly “a guy with an idea,” but for the most part they were <5 person teams with a working code base and some theories about who would buy the product. 

So where do you start on the question of business planning.  Do you dive into the deep end of details?  (What should we charge?  How do I get my first 5 beta customers?  What about this new feature?)  Or do you wade into the shallow end of methodical planning?  (Who is our target market?  What problem are we solving?  How much is it worth to the prospect?  What will it cost us to produce, sell, and support the product?)  We heard both of those approaches yesterday across the three companies. 

My conclusion isn’t that there’s a single correct answer.  For most mortals, it’s probably the case that while it’s good to have a product and an inspiration behind it, there’s a long road between that and a successful company that requires careful articulation of the basics and a good grip on potential economics before incremental investments of time or money. 

But there are the occasional companies whose ideas are so perfectly timed for such a large market or user base that some of the method can be ditched up front in the name of getting to market (think Twitter or eBay) — provided that the company circles back to those basics down the road in order to grow smartly over time.

Anyway, it was a thought-provoking day and great to see new entrepreneurs and ideas take root.  George and I have a series of six sessions set up with these companies as well as the full Techstars Demo Day in early August.  I’ll try to blog some thoughts after each session.

The Acquisition (a parody of a parody)

I just spent a great 4th of July with my brother Michael, one of the finer and funnier people I know.  Among other things, we treated ourselves to about the 18th viewing of Mel Brooks’ History of the World, Part I on DVD.

One of our favorite moments in the movie is the Broadway musical version of “The Inquisition” (lyrics, download MP3).  Since both of us work in the online marketing industry (Michael is a marketing manager at search agency Did-It), Michael came up with the brilliant idea of a parody of a parody…so here goes, all in good fun.

The acquisition, what a show
The acquisition, here we go
We’re on a mission, have you heard the news?

The acquisition, serve those ads
The acquisition, we’re so glad
We’ll make an offer, that they can’t refuse

Google, don’t be boring
WPP, don’t feel set
Yahoo seems to be ignoring:
It’s better to lose your market cap than your market!

Hey, Steven Ballmer, what do you say?
“I just got back from Avenue A”
“Avenue A?  What’s Avenue A?”
“It’s what I ought not have bought, but I bought anyway!”

The acquisition, what a show
The acquisition, here we go
We know you’re wishin’ that we’d go away.
But the acquisition’s here and it’s here to stay!

Happy 4th, everyone!

Techstars:  One Pitfall to Avoid

George and I met with our Techstars “mentee” companies again yesterday.  As was the case with the last meetings, the sessions were energizing and fun and great to see new companies unfolding. One lesson I was reminded of yesterday with both companies is a timeless one, since at least the beginning of the commercial internet:

I call this the Pointcast problem, after the mid-90s service that pulled headlines into screensavers and clogged corporate networks until the fad passed. 

One of the companies we’re working with has this challenge looming in front of them.  They have a very cool concept and technology.  It’s clear that it solves some problems, but there are many possible problems it solves, for many different people.

The key to get past this hurdle in the development of a business is to force yourself to articulate one or more very clear, crisp definitions of “it solves THIS problem for THIS person who is willing to pay THIS amount of money to have the problem solved.”  Even if you end up with two or three of these statements to then go concept test in the market, at least you will be able to shape your product and messaging development towards getting into the revenue jetstream somewhere, to quote my friend David Kidder from Clickable.

On the Other Hand…

A couple days ago, I wrote about how crummy the customer service experience was with Clear going out of business with no notice and no apology. 

Today my inbox revealed the exact opposite experience:

Greetings from Amazon.com.

You saved $1.40 with Amazon.com’s Pre-order Price Guarantee!

The price of the item(s) decreased after you ordered them, and we gave you the lowest price.

I didn’t even know Amazon had a Pre-order Price Guarantee.  They could have gotten away with not giving it to me, and I would have never even thought about it.  Great experience!

What if There’s No Reason to Eat the Dog Food?

There’s an expression in software about producing a product and market testing it — “seeing if the dogs will eat the dog food.”  I’ve heard it mangled many times around the employees of a software company using the software their own company produces as “seeing if the dogs will eat their own dog food.”  This is always true in consumer software and service companies. 

Employees are often the best users, the power users, and the source of the best feedback to the organization about the product and competition.  We certainly saw this phenomenon in spades at MovieFone, where I used to work before starting Return Path.  There was no more of a power user to be found than Andrew, the CEO, and there was a frenzy every Thursday and Friday as employees called into 777-FILM to buy their own tickets for the upcoming weekend.

But what if there’s no reason to eat your own dog food?  What if your software company develops a specific business application that only one or two people inside your company even care about?  Our services are a great example.  One or two people in Marketing, maybe one or two people in Technology, are users.  When I think about some of the web applications we as a company use, the same must be true of their companies as well.

If this is the case with your company, how do you make sure you get that same level of raw feedback from passionate users inside the four walls of your office, and not just from user groups, which are ok but have some inherent problems in terms of their objectivity and representation. 

I’m not sure I have a good answer to this – it’s more of a question to my readers than a prescription.  I’ll happily reblog the best responses!

The Gift of Feedback, Part III

Last week, I posted about my new development plan.  I thought I’d also share a “team development plan” that we crafted this year for the entire Executive Committee at Return Path (basically me and my direct reports), coming out of all of our 360 live reviews taken as a whole.

1.  Push each other harder and be continuous in our effort to provide the team and each of us feedback and further develop:  Improve ability to handle conflict as a group; Drive this work deeper into the organization; “Eyes/ears/mouth open;”  Explore how to better serve as role models to the rest of the organization, especially our direct reports/the next level of management; How do we get the Level II to function in the way that we do?
2. Getting messaging out/improve our communications as a team to the rest of the organization
3. Be more hawkish with underperformers:  Exert a discipline in dealing with problems; Making tough calls that don’t feel very good; Do we accept mediocrity?
4. Take responsibility for everyone as a group
5. Do we have a team of A+ players?  How do we recruit them as we get bigger?  Can we attract the best?  Or pay differently?  Revisit incentive comp plan if we don’t feel like it’s working as intended?
6. At least 2x/year comprehensively evaluate next level management to assess bench strength
7. Goal: to have this executive team be the outlier and be able to grow and each and as a team be able to manage a $100MM company

Thanks to our friend Marc Maltz at Triad Consulting as always for facilitating these great sessions and distilling the learnings down into bite-sized pieces for us!

Learning How to Stop

This is my last post about thoughts I had coming out of the NYC Lean Startup Meetup that I spoke at a couple weeks ago.  Being lean, the discussion went at this event, means not doing extraneous things.  While it’s true for startups that it’s important to make great decisions about what to do up front, it’s also true — especially as companies get larger and more important older — that organizations and individuals have to be vigilant about stopping activities that become extraneous over time.

This is HARD.  Once things — product features, business processes, reports, ways of communicating or thinking about things — get ingrained in an organization, there’s never a natural impetus to stop doing them.  Even the smartest and most thoughtful individuals often find themselves doing things that once made sense but no longer do. 

We encourage people at Return Path to create space to work OTB (on the business), not just ITB (in the business).  Take time not just to perfect what you’re doing and do it, but take time to reexamine what you’re doing and ask whether or not it needs to be done.  My staff is going to start doing an exercise at least quarterly around pruning/simplifying activities.  

Focus is not just about saying “no” to new tasks.  It’s also about saying “no longer” to old ones.

From Founder/Builder to Manager/Leader

After I spoke at the Startup2Startup event last month, one of the people who sat with me at dinner emailed me and asked:

I was curious–how did you make the transition from CEO of a startup to manager of a medium-sized business? I’m great at just doing the work myself and interacting with clients, and it’s easy for me to delegate tasks, but it’s hard to have the vision and ability to develop my two employees into greater capacity…

I’d be interested in reading a blog post on what helped you make that transition from founder/builder to manager/leader

It feels like the answer to this question is about a mile long, but I thought I’d at least start with five suggestions.

1. Hire Up!  The place where I see most founders fumble the transition is in not hiring the best people for the critical roles in the organization.  Sometimes this is for cash flow reasons, but more often it is either due to subconscious fear (“will I still be able to control the organization if this person is in it?”) or due to bravado (“I can do engineering way better than that guy”).  Lose that attitude and hire up for key positions.  Even if you COULD do every role better than anyone you’d ever hire, you only have so many hours in the day.
2. Learn the magic of delegation and empowerment.  You can never get as much work done on your own as you can if you get work done THROUGH others.  Get comfortable delegating work by setting clear expectations up front in terms of timing and quality of deliverables and giving your high level input.  And never be a bottleneck.  If people are waiting on you for decisions or comments, that means they’re not working…or at least that they’re not working on the highest value or most urgent things they could be working on.
3. Don’t fear some elements of larger organizations.  Larger organizations require some process so they don’t fall apart.  Make sure you pick your battles and accept that some changes, even if they feel bureaucratic, are critical to ensure success going forward.  I still get a queasy feeling in my stomach half of the times I see a new form or procedure or a suggestion from a lawyer, but as long as they are lightweight and constantly reviewed to make sure they’re having their intended impact AND ONLY their intended impact, some are inevitable.
4. At the same time, don’t lose the founder/builder mentality.  Your company may have grown larger, but if you’re still running it, people will naturally look to you and other founders for much of the energy, vision, and drive in the business.  You will also likely be more inclined to be scrappy and entrepreneurial, which are good traits for any business.  Don’t lose those qualities, even as you modify them or add others.
5. Look to the outside for help.  In my case, I’ve consistently done three things over the years to learn from others and to prevent myopia.  First, I have worked on and off with a fantastic executive coach, Marc Maltz from Triad Group. Second, I have always had one or two “CEO mentors,” e.g., guys who have built larger businesses than Return Path, on my Board, at all times, as resources.  Finally, I do a lot of CEO peer networking, some informal (breakfasts, drinks meetings), and some more formal (a CEO Forum group that I established) to make sure I’m consistently sharing information and best practices with others in comparable situations.

Any other entrepreneurs who have made the leap have other advice to offer?

Getting Good Inc., Part II

It was a nice honor to be noted as one of America’s fastest growing companies as an Inc. 500 company two years in a row in 2006 and 2007 (one of them here), but it is an even nicer honor to be noted as one of the Top 20 small/medium sized businesses to work for in America by Winning Workplaces and Inc. Magazine.  In addition to the award, we were featured in this month’s issue of Inc. with a specific article about transparency, and important element of our corporate culture, on p72 and online here.

Why a nicer honor?  Simply put, because we pride ourselves on being a great place to work — and we work hard at it.  My colleague Angela Baldonero, our SVP People, talks about this in more depth here. Congratulations to all of our employees, past and present, for this award, and a special thanks to Angela and the rest of the exec team for being such awesome stewards of our culture!

Why I Love Our New Product

Return Path officially announced a new product today called Domain Assurance, which I blogged a little bit about here.  It’s a very exciting product that will help reduce and ultimately eliminate phishing emails – spam’s even more evil cousin that leads to identity theft, malware, further propagation of spam through botnets, and all sorts of other goodies.  The product is in beta now with a bunch of top ISPs and brands.

Those are a lot of reasons to love our new product.  But for me, there’s more.

For starters, this is the first new product (entirely new product, not just a feature or extension) that we’ve launched in years.  While we’ve made some acquisitions and done a ton of product development, they’ve always been right in our strike zone of deliverability.  This is a nice, deeply interrelated adjacency.  It’s fun to branch out a little bit and do something new.

Second, this product is a great example of operating leverage.  Many of the necessary ingredients for it were already in house – most notably customers and partners, but also a lot of data.  That’s what adjacencies should be about.  Building it, while a significant effort (and one that’s not completely done yet) was significantly easier than building, say, the original deliverability tool set or reputation database.  Let’s hear it for scale!

Finally, the product showcases Return Path’s commitment to open standards, which is fundamental to the Internet’s success.  We hope our new Domain Assurance product encourages more and more mailers to authenticate all of their outbound mail, and we hope the product also encourages the use of ADSP and ultimately some productive enhancements to both ADSP and DKIM.  Authentication does not equal reputation, but we’ve said for years it’s the fundamental underpinning of it.

Mental Maps

I recently went grocery shopping at a store I’d never been to before, Stew Leonard’s, and, no offense to Stew, I am unlikely to be a repeat customer.  While there were some things about the store that were better than most grocery stores, the experience drove me nuts.  Here’s why.

The store is laid out completely differently from standard grocery stores.  Most stores, even unusual ones like Whole Foods or Trader Joe’s, have a nearly identical layout.  One side is produce, frozen foods in the middle, meats in the back, dairy around the other side, standard aisles have bread, baking stuff, cans, cereals, drinks and snacks, etc.  Go shopping enough, and you can generally find your way around any store in your sleep.

Stew Leonard’s decided to break the model.  The store has no aisles and is linear – you just keep walking in one direction/flow and hit every single section of the store before you reach the end of the maze at the cashiers.  One bonus is that they merchandise some things well and put logical items next to each other (burgers next to buns).  But you can’t really go back if you missed something, you have no idea what’s coming up next, you can’t tell if you’ve seen all of a given class of item yet since different elements of every category keep popping up.

Sometimes that kind of a risk can pay off in a breakthrough new product design.  Maybe people buy more items at Stew’s because things are set up differently.  But the experience was very disorienting, the shop took twice as long as usual, and I couldn’t find a bunch of things so I still had to go to A&P afterwards – basically, the costs outweighed the benefits.

The obvious comparison here to our professional world is UI design.  Breakthrough redesigns are always risky.  They can produce better user experiences, but they can also confuse new visitors or less sophisticated users, and they risk an immediate reaction of “I can’t figure this site out, goodbye.”

UPDATE:  Comments aren’t working today on the new blog, but my friend Pete Warden just emailed me a great comment about this post:

Your post reminded me of an incident at Apple that I wanted to share…One of the engineers was advocating for a UI change to an existing product. It clearly made the interface more elegant and logical, but our designer was pushing back hard. Finally the designer said “If you put that change in, I’m going to sneak into your house tonight and move all your furniture to different positions”. That analogy stuck with me; familiarity is what enables us to use a tool without having to stop and think, and so you need a really strong reason to change the structure of an interface.