• Why I think ClickFraud is far greater than imagined. – Blog Maverick – www.blogmaverick.com _
  Dallas Mavs owner and Internet entrepreneur Mark Cuban on Click Fraud, a notorious member of the Internet Axis of Evil
  (tags: Email Technology Media Marketing)

• WSJ.com – Heard on the Street
  Amazon, Microsoft, and Google on big marketing spend
  (tags: Marketing Media Technology)

• Fractals of Change: Are You an Entrepreneur?
  Tom Evslin’s entertaining Top 10 Ways You Know You’re an Entrepreneur. Some may dovetail nicely if I ever write up my read of The Fountainhead through entrepreneurial lens!
  (tags: Entrepreneur VC)

• terrygold.com: Hiring Salespeople
  Good posting from Terry Gold of Gold Systems on his experiences over the years hiring and ramping up a sales team.
  (tags: Entrepreneur Sales Management)

• Seth’s Blog: Going to meetings
  A great posting about Vendor Love from Seth Godin!
  (tags: Entrepreneur)

• Feld Thoughts
  Brad has a good posting today about entrepreneur accountability — along the lines of my “Forecast Early and Often” theme. — /2005/11/notsocounter_cl.html
  (tags: VC Entrepreneur)

• Techdirt: India Says No Thanks To The $100 Laptop
  It’s kind of a “Let Them Eat Cake!” response — which kind of makes sense, given our recent trip to India.
  (tags: india Technology)

• Feld Thoughts: Falling Down and Getting Back Up
  Brad’s colorful, quick posting on “how running is like entrepreneurship.”
  (tags: Entrepreneur VC)

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.

The Gift of Feedback, Part III

I’ve written about our 360 Review process at Return Path a few times in the past:

• overall process
• process for my review in particular
• update on a process change and unintended consequences of that process change)
• learnings from this year’s process about my staff

And the last two times around, I’ve also posted the output of my own review publicly here in the form of my development plan:

• Here in 2008
• Here in 2009

So here we are again.  I have my new development plan all spruced up and ready to go.  Many thanks to my team and Board for this valuable input, and to Angela Baldonero (my fantastic SVP People and in-house coach), and Marc Maltz of Triad Consulting for helping me interpret the data and draft this plan.  Here at a high level is what I’m going to be working on for the next 1-2 years:

• Institutionalize impatience and lessen the dependency dynamic on me.  What does this mean?  Basically it means that I want to make others in the organization and on my team in particular as impatient as I am for progress, success, reinvention, streamlining and overcoming/minimizing operational realities.  I’ll talk more about something I’ve taken to calling “productive disruption” in a future blog post
• Focus on making every staff interaction at all levels a coaching session.  Despite some efforts over the years, I still feel like I talk too much when I interact with people in the organization on a 1:1 or small group basis.  I should be asking many more questions and teaching people to fish, not fishing for them
• Continue to foster deep and sustained engagement at all levels.  We’ve done a lot of this, really well, over the years.  But at nearly 250 people now and growing rapidly, it’s getting harder and harder.  I want to focus some real time and energy in the months to come on making sure we keep this critical element of our culture vibrant at our new size and stage
• I have some other more tactical goals as well like improving at public speaking and getting more involved with leadership recruiting and management training, but the above items are more or less the nub of it

One thing I know I’ll have to do with some of these items and some of the tactical ones in particular is engage in some form of deliberate practice, as defined by Geoffrey Colvin in his book Talent is Overrated (blog post on the book here).  That will be interesting to figure out.

But that’s the story.  Everyone at Return Path and on my Board – please help me meet these important goals for my development over the next couple of years!

Book short:  Life Isn’t Just a Wiki

One of the best things I can say about Remote: Office Not Required,  by Jason Fried and David Heinemeier Hansson, is that it was short.  That sounds a little harsh – part of what I mean is that business books are usually WAY TOO LONG to make their point, and this one was blessedly short.  But the book was also a little bit of an angry rant against bad management wrapped inside some otherwise good points about remote management.

The book was a particularly interesting read juxtaposed against Simon Sinek’s Leaders Eat Last which I just finished recently and blogged about here, which stressed the importance of face-to-face and in-person contact in order for leaders to most effectively do their jobs and stay in touch with the needs of their organizations.

The authors of Remote, who run a relatively small (and really good) engineering-oriented company, have a bit of an extreme point of view that has worked really well for their company but which, at best, needs to be adapted for companies of other sizes, other employee types, and other cultures.  That said, the flip side of their views, which is the “everyone must be at their cubicle from 9 to 5 each day,” is even dumber for most businesses these days.  As usual with these things, the right answer is probably somewhere in between the extremes, and I was reminded of the African proverb, “If you want to go fast, go alone. If you want to go farm go together” when I read it.  Different target outcomes, different paths.

I totally agree with the authors around their comments about trusting employees and “the work is what matters.”  And we have a ton of flexibility in our work at Return Path.  With 400 people in the company, I personally spend six weeks over the summer working largely remote, and I value that time quite a bit.  But I couldn’t do it all the time.  We humans learn from each other better and treat each other better when we look at each other face to face.  That’s why, with the amount of remote work we do, we strongly encourage the use of any form of video conferencing at all times.  The importance of what the authors dismiss as “the last 1 or 2% of high fidelity” quality to the conversation is critical.  Being in person is not just about firing and hiring and occasional sync up, it’s about managing performance and building relationships.

Remote might have been better if the authors had stressed the value that they get out of their approach more than ranting against the approaches of others.  While there are serious benefits of remote work in terms of cost and individual productivity (particularly in maker roles), there are serious penalties to too much of it as well in terms of travel, communication burden, misunderstandings, and isolation.  It’s not for everyone.

Thanks to my colleague Hoon Park for recommending this to me.  When I asked Hoon what his main takeaway from the book was, he replied:

The importance of open communication that is archived (thus searchable), accessible (transparent and open to others) and asynchronous (doesn’t require people to be in the same place or even the same “timespace”).  I love the asynchronous communication that the teams in Austin have tried: chatrooms, email lists (that anyone can subscribe to or read the archives of), SaaS project management tools. Others I would love to try or take more advantage of include internal blogs (specifically the P2 and upcoming O2 WordPress themes; http://ma.tt/2009/05/how-p2-changed-automattic/), GitHub pull requests (even for non-code) and a simple wiki.

These are great points, and good examples of the kinds of systems and processes you need to have in place to facilitate high quality, high volume remote work.