Only Once

• Share
• 0 comments

I Don’t Want to Be Your Friend (Today), part III

I Don’t Want to Be Your Friend (Today), part III

My first thought when my colleague Jen Goldman forwarded me a SlideShare presentation that was 224 pages long was, “really?”  But a short 10 minutes and 224 clicks later, I am glad I spent the time on it.

Paul Adams, a Senior User Experience Researcher at Google, put the presentation up called The Real Life Social Network.  Paul describes the problem I discuss in Part I and Part II of this series much more eloquently than I have, with great real world examples and thoughts for web designers at the end.

If you’re involved in social media and want to start breaking away from the “one size of friend fits all” mentality – this is a great use of time.

• Share
• 2 comments

Agile Marketing, Part II

Agile Marketing, Part II

I wrote about this years ago when I was temporarily running Marketing and was noting a lot of the similarities between running contemporary Product Development and Marketing efforts.

Nick Van Weerdenburg just put up a great post called Why Marketing is Becoming Like Software Development which you should read if you run or work in, or work closely with, a marketing department.

• Share
• 3 comments

Feature Requests

Feature Requests

Here are two new features I’d like to see in life:

1. Any time you hit “reply to all” when you are in the BCC line – a giant red alert should pop up and say “are you really sure you want to let all these people know that you were BCCd on this thread?”
2. Any time you place a call to a cell phone that’s outside of the person’s normal time zone – a giant red alert should pop up and say “are you sure you want to call this person at 3 a.m. in Singapore?” before completing the call

I’m not sure to whom these requests should be addressed, so I’ll just start with the open web.

• Share
• 1 comment

OnlyOnce, Part II

OnlyOnce, Part II

After more than six years, my blog starting looking like, well, a six-year old blog on an off-the-shelf template.  Thanks to my friends at Slice of Lime, OnlyOnce has a new design as of today as well as some new navigation and other features like a tag cloud and Twitter feed (and a new platform, WordPress rather than Typepad).  I know many people only read my posts via feed or email (those won’t change), but if you have a minute, feel free to take a look.  The site also has its own URL now – http://www.onlyonceblog.com.

With my shiny new template, I may add some other features or areas of content over time, as well.  There are still a couple things that are only 95% baked, but I love the new look and wanted to make if “official” today.  Thanks to Kevin, Jeff, Mike, Lindsay, and everyone at Slice of Lime for their excellent design work, and for my colleague Andrea for helping do the heavy lifting of porting everything over to the new platform.

• Share
• 1 comment

Automated Love

Automated Love

Return Path is launching a new mini feature sometime this week to our clients.  Normally I wouldn’t blog about this — I think this is mini enough that we’re probably not even saying much about it publicly at the company.  But it’s an interesting concept that I thought I’d riff on a little bit.

I forget what we’re calling the program officially — probably something like “Client Status Emails” or “Performance Summary Alerts” — but a bunch of us have been calling it by the more colorful term “Automated Love” for a while now.

The art of account management or client services for an on-demand software company is complex and has evolved significantly from the old days of relationship management.  Great account management now means a whole slew of new things, like Being The Subject Matter Expert, and Training the Client.  It’s less about the “hey, how are things going?” phone call and more about driving usage and value for clients.

As web services have taken off, particularly for small businesses or “prosumers,” most have built in this concept of Automated Love.  The weekly email from the service to its user with charts, stats, benchmarks, and links to the web site, occasionally with some content or blog posts.  It’s relatively easy (most of the content is database driven), it reminds customers that you’re there, working on their behalf in the background, it tells them what happened on their account or how they’re doing, it alerts them to current or looming problems, and it drives usage of your service.  As a bonus for you internally, usually the same database queries that produce a good bit of Automated Love can also alert your account management team when a client’s usage pattern of your service changes or stops entirely.

While some businesses with low values of any single customer value can probably get away with having a client service function based ENTIRELY on Automated Love, I think any business with a web service MUST have Automated Love as a component of its client service effort.

• Share
• 1 comment

I Don’t Want to Be Your Friend (Today), part II

I think Facebook is starting to get out of control from a usability perspective.  This doesn’t mean it’s not a great platform and that it doesn’t have utility.  But if the platform continues on its current path, the core system runs the risk of going sideways like its various predecessors:  GeoCities, MySpace, etc.  Maybe I’ll go in there to look for something or someone, but it won’t be a place I scroll through as part of a daily or semi-daily routine.

I wrote about this a year ago now, and while the site has some better tools to assign friends to groups, it doesn’t do any better job than it did a year ago about segregating information flow, either by group or by some kind of intelligence.

I don’t know why my home page, news feed, RSS feed, and iPhone app can’t easily show me posts from people I care about, but if it can’t do that soon enough, I will almost entirely stop using it.  Can’t Facebook measure the strength of my connections?  Can’t it at least put my wife’s posts at the top?  My usage is already way down, and the trend is clear.

And I won’t really comment on Facebook COO Sheryl Sandberg’s inane remark last week that “email is dead because young people don’t use it” other than to paraphrase two things I read on a discussion list I’m on:  “Just checked, and you still need an email address to sign-up for a Facebook account,” and “Most teens don’t buy stocks so Wall Street has no future.”  More entertaining analogies from Loren McDonald of Silverpop are listed here.

• Share
• 0 comments

Why I Love Our New Product

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.

• Share
• 2 comments

From Founder/Builder to Manager/Leader

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?

• Share
• 2 comments

Pivot, Don’t Jump!

Pivot, Don’t Jump!

I spoke last night at the NYC Lean Startup Meetup, which was fun.  I will write a couple other posts based on the experience over the next week or so.  The Meetup is all about creating “lean startups,” not just meaning lean as in cheap and lightweight, but meaning smart at doing product development from the perspective of finding the quickest path to product-market fit.  No wasted cycles of innovation.  Something we are spending a lot of time on right now at Return Path, actually.

My topic was “The Pivot,” by which the group meant How do you change your product idea/formation quickly and nimbly when you discover that your prior conception of “product-market fit” is off?  I talked a bit about the pivots we’ve done over the years here, not just the corporate ones, but some of the essential product ones as well.  One of the comments a member of the Meetup made that really stuck with me was that you have to “Pivot, Don’t Jump” when making changes to your business or product.

This has been true of Return Path’s pivots over the years.  Our pivots have all had two very solid foundation points — the company’s deep expertise in email, and our customer base.  Every pivot we’ve done has been in some way at the request/urging of our clients, and the new directions have always been in line with our core capabilities.  While we have a talented team that probably could execute lots of different businesses well, it’s hard to see us being successful in other areas that are farther afield.

People over the years, for example, have suggested that we should get into SMS deliverability — isn’t that going to be a hot topic?  We don’t know.  We don’t spend our lives immersed in text messaging.  What about getting into measurement of social media messaging — isn’t that related?  Maybe, but it’s not in our wheelhouse.  Expanding from email deliverability software and analytics, into services, into data, into whitelisting on the other hand – those were pivots, not jumps.

One other note of course, is that the larger your business is, and the more investors have a stake in it, the harder it is to make BIG pivots or any kind of jumps.  Innovation is still critical, but innovating from a well-protected core is what it’s all about, not chasing new shiny objects.

• Share
• 10 comments

Techstars Roundup: Why I Mentor Other Entrepreneurs

Techstars Roundup:  Why I Mentor Other Entrepreneurs

Yesterday was Demo/Investor day at Techstars in Boulder, Colorado.  A lot of people have written about it – Fred, Brad, and a great piece by Don Dodge on TechCrunch listing out all the companies.  My colleague George and I co-mentored two of the companies, SendGrid and Mailana, and we really enjoyed working with Isaac and Pete, the two entrepreneurs.

I posted twice earlier this summer on the TechStars experience.  My first post on this, Where do you Start?, was about whether to be methodical in business planning for a startup or dive right into the details.  My second post, One Pitfall to Avoid, was about making sure you don’t create a whizzy solution looking for a problem, but that you start with a problem that needs solving.

Rather than rehash what others have written about yesterday — yes, it was great and fun and energizing — I thought I’d focus on why I spend time mentoring new entrepreneurs.  I did it this year at TechStars, but I’ve done this informally for probably a dozen different entrepreneurs over the years in the community in general. 

Anyway, there are four main reasons I spend time mentoring other entrepreneurs (in no particular order):

It sharpens the saw.  This is Stephen Covey’s language from both The 7 Habits of Highly Effective People and The 8th Habit:  From Effectiveness to Greatness, and it simply refers to an activity that puls you out of the day to day and refreshes your brain because it’s different.  Running, playing guitar, mentoring sessions with entrepreneurs — they all clear the head and are just plain fun.

I get good specific ideas for my own business.  I think I came away from every single meeting I had with either entrepreneur this year with at least one new “to do” for myself and my team at Return Path.  There’s nothing quite like seeing how another company or entrepreneur operates to spur on good thinking, and in this case, both teams we worked with were working in the email space, so they were very relevant to our day-to-day.

I crystallize my own thoughts and ideas.  Much like writing this blog, problem/solution sessions with other entrepreneurs forces me to take a cloud of ideas down to a simple sentence or paragraph. 

I learn a lot about my colleagues.  This is a specific case for this year because I co-mentored these companies with George, although I guess bits and pieces of it have come up over the years as I’ve roped other colleauges into other situations.  George and I brought different ideas and frames of reference to our sessions with SendGrid and Mailana, and it was fun for me and a good learning experience as well to see how George approached the same problems I did.  Call it a “peek inside George’s brain.”

Hopefully I will get invited back to TechStars again next year as a mentor – it was great fun, and I’m incredibly proud of Pete and Isaac and their teams with how well they presented their companies yesterday!