🔎
Nov 23 2009

Powerpointless

Powerpointless

We tried an experiment last week at a Return Path Board meeting — and not just a regular Board meeting, but our once-a-year, full-day (~9 hour) annual planning session attended in person by all Board members, observers, and executives.  First, a little background.

We have been driving two important trends over the years at our Board meetings:

1. Focusing on the future, not the past.  In the early years of the business, our Board meetings were probably 75% “looking backwards” and 25% “looking forwards.”  They were reporting meetings — reports which were largely in the hands of Board members before the meetings anyway.  They were dull as all get out.  This past meeting was probably 10% “looking backwards” and 90% “looking forwards” and much more interesting as a result.

2. Focusing on creating a more engaging dialog during the meeting by separating out “background reading” vs. “presentation materials.”  We used to do a huge Powerpoint deck as both a handout the week before the meeting and as the in-meeting deck.  Then we separated the two things so people weren’t bored by the Powerpoint.  Then we started making the decks more fun and engaging and “zen.”  This meeting took the trend to its logical conclusion, which was that we sent out a great set of comprehensive reading materials and reports ahead of the meeting, and then…

…we didn’t have a single Powerpoint slide to run the meeting.  We thought that the best way to foster two-way dialog in the meeting was to change the paradigm away from a presentation — the whole concept of “management presenting to the Board” was what we were trying to change, not just what was on the wall.  The result was fantastic.  We had a very long meeting, but one where everyone — management and Board alike — was highly engaged.  No blackberries or iPhones.  Not too many yawns or walkabouts.  It was literally the best Board meeting we’ve had in almost 10 years of existence, out of probably 75 or 80 total.

I’m not sure this would work for all companies at all stages at all times, and we had a handful of graphics “ready to go” in case we wanted to shoot something up on the wall, as we likely will always have.  But I can’t say enough about how this evolution in meeting setup and execution changed the dynamic.

Aug 5 2008

Book Short: On The Same Page

Book Short:  On The Same Page

Being on the same page with your team, or your whole company for that matter, is a key to success in business.  The Four Obsessions of an Extraordinary Executive, by Patrick Lencioni, espouses this notion and boils down the role of the CEO to four points:

  1. Build and maintain a cohesive leadership team
  2. Create organizational clarity
  3. Overcommunicate organizational clarity
  4. Reinforce organizational clarity through human systems

Those four points sound as boring as bread, but the book is anything but.  The book’s style is easy and breezy — business fiction.  One of the most poignant moments for me was when the book’s “other CEO” (the one that doesn’t “get it”) reflects that he “didn’t go into business to referee executive team meetings and delivery employee orientation…he loved strategy and competition.”  Being a CEO is a dynamic job that changes tremendously as the organization grows.  This book is a great handbook for anyone transitioning out of the startup phase, or for anyone managing a larger organization.

I haven’t read the author’s other books (this is one in a series), but I will soon!

Feb 16 2012

Book Short: Steve Jobs and Lessons for CEOs and Founders

Book Short:  Steve Jobs and Lessons for CEOs and Founders

First, if you work in the internet, grew up during the rise of the PC, or are an avid consumer of Apple products, read the Walter Isaacson biography of Steve Jobs (book, kindle).  It’s long but well worth it.

I know much has been written about the subject and the book, so I won’t be long or formal, but here are the things that struck me from my perspective as a founder and CEO, many taken from specific passages from the book:

  • In the annals of innovation, new ideas are only part of the equation. Execution is just as important.  Man is that ever true.  I’ve come up with some ideas over the years at Return Path, but hardly a majority or even a plurality of them.  But I think of myself as innovative because I’ve led the organization to execute them.  I also think innovation has as much to do with how work gets done as it does what work gets done.
  • There were some upsides to Jobs’s demanding and wounding behavior. People who were not crushed ended up being stronger. They did better work, out of both fear and an eagerness to please.  I guess that’s an upside.  But only in a dysfunctional sort of way.
  • When one reporter asked him immediately afterward why the (NeXT) machine was going to be so late, Jobs replied, “It’s not late. It’s five years ahead of its time.”  Amen to that.  Sometimes product deadlines are artificial and silly.  There’s another great related quote (I forget where it’s from) that goes something like “The future is here…it’s just not evenly distributed yet.”  New releases can be about delivering the future for the first time…or about distributing it more broadly.
  • People who know what they’re talking about don’t need PowerPoint.”  Amen.  See Powerpointless.
  • The mark of an innovative company is not only that it comes up with new ideas first, but also that it knows how to leapfrog when it finds itself behind.  This is critical.  You can’t always be first in everything.  But ultimately, if you’re a good company, you can figure out how to recover when you’re not first.  Exhibit A:  Microsoft.
  • In order to institutionalize the lessons that he and his team were learning, Jobs started an in-house center called Apple University. He hired Joel Podolny, who was dean of the Yale School of Management, to compile a series of case studies analyzing important decisions the company had made, including the switch to the Intel microprocessor and the decision to open the Apple Stores. Top executives spent time teaching the cases to new employees, so that the Apple style of decision making would be embedded in the culture.  This is one of the most emotionally intelligent things Jobs did, if you just read his actions in the book and know nothing else.  Love the style or hate it – teaching it to the company reinforces a strong and consistent culture.
  • Some people say, “Give the customers what they want.” But that’s not my approach. Our job is to figure out what they’re going to want before they do. I think Henry Ford once said, “If I’d asked customers what they wanted, they would have told me, ‘A faster horse!’” People don’t know what they want until you show it to them. That’s why I never rely on market research. Our task is to read things that are not yet on the page.  There’s always a tension between listening TO customers and innovating FOR them.  Great companies have to do both, and know when to do which.
  • What drove me? I think most creative people want to express appreciation for being able to take advantage of the work that’s been done by others before us. I didn’t invent the language or mathematics I use. I make little of my own food, none of my own clothes. Everything I do depends on other members of our species and the shoulders that we stand on. And a lot of us want to contribute something back to our species and to add something to the flow. It’s about trying to express something in the only way that most of us know how—because we can’t write Bob Dylan songs or Tom Stoppard plays. We try to use the talents we do have to express our deep feelings, to show our appreciation of all the contributions that came before us, and to add something to that flow. That’s what has driven me.  This is perhaps one of the best explanations I’ve ever heard of how creativity can be applied to non-creative (e.g., most business) jobs.  I love this.

My board member Scott Weiss wrote a great post about the book as well and drew his own CEO lessons from it – also worth a read here.

Appropos of that, both Scott and I found out about Steve Jobs’ death at a Return Path Board dinner.  Fred broke the news when he saw it on his phone, and we had a moment of silence.  It was about as good a group as you can expect to be with upon hearing the news that an industry pioneer and icon has left us.  Here’s to you, Steve.  You may or may not have been a management role model, but your pursuit of perfection worked out well for your customers, and most important, you certainly had as much of an impact on society as just about anyone in business (or maybe all walks of life) that I can think of.

Aug 14 2006

Book Short: Choose Voice!

Book Short:  Choose Voice!

I took a couple days off last week and decided to re-read two old favorites.  One –Ayn Rand’s The Fountainhead — my fourth reading — will take me a little longer to process and figure out if there’s a good intersection with the blog.  One would think so with entrepreneurship as the topic, but my head still hurts from all the objectivism.  The second — Exit, Voice, and Loyalty, by Albert O. Hirschman — is today’s topic.

I can’t remember when I first read Exit, Voice, and Loyalty.  It was either in senior year of high school Economics or Government; or in freshman year of college Political Philosophy.  Either way, it was a long time ago, and for some reason, some of the core messages of this quirkly little 125 page political/economic philosophy book have stayed with me over the years.  I remembered the book incorrectly as a book about political systems, and I think it was born consciously in the wake of Eugene McCarthy’s somewhat revolutionary challenge to a sitting President Johnson for the Democratic Party nomination in 1968.  But the book is actually about business; it’s just about businesses and their customers, not corporations as social structures (the latter being more of an interest to me).  Written by an academic economist (I think), the book has its share of gratuitous demonstrative graphs, 2×2 matrices, and SAT words.  But its central premise is a gem for anyone who runs an organization of any size.

The central premise is that there are really two paths by which one can express dissatisfaction with a temporary, curable lapse in an organization:  exit (bailing), or voice (trying to fix what’s wrong from within).  The third key element, Loyalty, is less a path in and of itself but more an agent that “holds exit at bay and activates voice.”

You need to read the book and apply it to your own circumstances to really get into it, but for me, it’s all about breeding loyalty as a means of making voice the path of least resistance, even when exit is a freely available option (few of us run totalitarian states or monopolies, after all).  That to me is the definition of a successful enterprise, both internally and externally.

With your customers:  make your product so irresistible, and make your customer service so deep, that your customers feel an obligation to help you fix what they perceive to be wrong with your product first, rather than simply complain about price or flee to a competitor.

With your employees:  make your company the best possible place you can think of to work so that even in as ridiculously fluid a job market as we live in, your employees will come to their manager, their department head, the head of HR, or you as leader to tell you when they’re unhappy instead of just leaving, or worse, sulking.

With your company (you as employee):  make yourself indispensible to the organization and do such a great job that if things go wrong with your performance or with your role, your manager’s loyalty to you leads him or her to give you open feedback and coach you to success rather than unceremoniously show you the door.

Ok, this wasn’t such a short book short — probably the longest I’ve ever written in this blog, and certainly the highest ratio of short:actual book.  But if you’re up for a serious academic framework (quasi-business but not exclusively) to apply to your management techniques, this short 1970 book is as valid today as when it was written.  Thanks to David Ramert (I am pretty sure I read it in high school) for introducing it to me way back when!

Jul 18 2013

Book Short: The Little Engine that Could

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.

Jun 5 2014

Book short: Life Isn’t Just a Wiki

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.

Apr 10 2014

Understanding the Drivers of Success

Understanding the Drivers of Success

Although generally business is great at Return Path  and by almost any standard in the world has been consistently strong over the years, as everyone internally knows, the second part of 2012 and most of 2013 were not our finest years/quarters.  We had a number of challenges scaling our business, many of which have since been addressed and improved significantly.

When I step back and reflect on “what went wrong” in the quarters where we came up short of our own expectations, I can come up with lots of specific answers around finer points of execution, and even a few abstracted ones around our industry, solutions, team, and processes.  But one interesting answer I came up with recently was that the reason we faltered a bit was that we didn’t clearly understand the drivers of success in our business in the 1-2 years prior to things getting tough.  And when I reflect back on our entire 14+ year history, I think that pattern has repeated itself a few times, so I’m going to conclude there’s something to it.

What does that mean?  Well, a rising tide — success in your company — papers over a lot of challenges in the business, things that probably aren’t working well that you ignore because the general trend, numbers, and success are there.  Similarly, a falling tide — when the going gets a little tough for you — quickly reveals the cracks in the foundation.

In our case, I think that while some of our success in 2010 and 2011 was due to our product, service, team, etc. — there were two other key drivers.  One was the massive growth in social media and daily deal sites (huge users of email), which led to more rapid customer acquisition and more rapid customer expansion coupled with less customer churn.  The second was the fact that the email filtering environment was undergoing a change, especially at Gmail and Yahoo, which caused more problems and disruption for our clients’ email programs than usual — the sweet spot of our solution.

While of course you always want to make hay while the sun shines, in both of these cases, a more careful analysis, even WHILE WE WERE MAKING HAY, would have led us to the conclusion that both of those trends were not only potentially short-term, but that the end of the trend could be a double negative — both the end of a specific positive (lots of new customers, lots more market need), and the beginning of a BROADER negative (more customer churn, reduced market need).

What are we going to do about this?  I am going to more consistently apply one of our learning principles, the Post-Mortem  –THE ART OF THE POST-MORTEM, to more general business performance issues instead of specific activities or incidents.  But more important, I am going to make sure we do that when things are going well…not just when the going gets tough.

What are the drivers of success in your business?  What would happen if they shifted tomorrow?

Jun 14 2012

Book Short: Alignment Well Defined

The Advantage: Why Organizational Health Trumps Everything Else In Business is Patrick Lencioni’s newest book.  Unlike most or all of his other books (see the end of this post for the listing), this one is not a fable, although his writing style remains very quick and accessible.

I liked this book a lot.  First, the beginning section is a bit of a recap of his Five Dysfunctions of a Team which I think was his best book.  And the ending section is a recap of his Death by Meeting, another really good one.  The middle sections of the book are just a great reminder of the basic building blocks of creating and communicating strategy and values – about driving alignment.

But the premise, as the subtitle indicates, is that maintaining organizational health is the most important thing you can do as a leader.  I tell our team at Return Path  all the time that our culture is a competitive advantage in many ways, some quantifiable, and others a little less tangible.

A telling point in the book is when Lencioni is relaying a conversation he had with the CEO of a client company who does run a healthy organization – he asked, “Why in the world don’t your competitors do any of this?” And the client responded, “You know, I honestly believe they think it’s beneath them.” Lencioni goes on to say, “In spite of its undeniable power, so many leaders struggle to embrace organizational health because they quietly believe they are too sophisticated, too busy, or too analytical to bother with it.”  And there you have it.  More examples of why “the soft stuff” is mission critical.

Lencioni’s “Recipe for Organizational Health” (the outline of the book):

–          Build a Cohesive Leadership Team

–          Create Clarity

–          Overcommunicate Clarity

–          Reinforce Clarity

And his recipe for creating a tight set of “mission/vision/values” (the middle of the book):

1. Why do we exist?

2. How do we behave?

3. What do we do?

4. How will we succeed?

5. What is most important, right now?

6. Who must do what?

While there are lots of other good frameworks for doing all of this, Lencioni’s models and books are great, simple reminders of one of the CEO’s most important leadership functions.  We’re recrafting our own mission and values statements at the moment at Return Path, and we’re doing it using this 6-Question framework instead of the classic “Mission/Vision/Values” framework popularized a few years back by Harvard Business Review.

The full book series roundup as far as OnlyOnce has gotten so far is:

Dec 19 2013

5 Ways to Get Your Staff on the Same Page

5 Ways to Get Your Staff on the Same Page

[This post first appeared as an article in Entrepreneur Magazine as part of a new series I’m publishing there in conjunction with my book, Startup CEO:  A Field Guide to Scaling Up Your Business]

When a major issue arises, is everybody at your company serving the same interests? Or is one person serving the engineering team, another person serving the sales team, one board member serving the VC fund, another serving the early-stage “angels” and another serving the CEO? If that’s the case, then your team is misaligned. No individual department’s interests are as important as the company’s.

To align everyone behind your company’s interests, you must first define and communicate those goals and needs. This requires five steps:

  1. Define the mission. Be clear to everyone about where you’re going and how you’re going to get there (in keeping with your values).
  2. Set annual priorities, goals, and targets. Turn the broader mission into something more concrete with prioritized goals and unambiguous success metrics.
  3. Encourage bottom-up planning. You and your executive team need to set the major strategic goals for the company, but team members should design their own path to contribution. Just be sure that you or their managers check in with them to assure that they remain in synch with the company’s goals.
  4. Facilitate the transparent flow of information and rigorous debate. To help people calibrate the success, or insufficiency, of their efforts, be transparent about how the organization is doing along the way. Your organization will make better decisions when everyone has what they need to have frank conversations and then make well-informed decisions.
  5. Ensure that compensation supports alignment (or at least doesn’t fight it). As selfless as you want your employees to be, they’ll always prioritize their interests over the company’s. If those interests are aligned – especially when it comes to compensation – this reality of human nature simply won’t be a problem.

Taken in sequence, these steps are the formula for alignment. But if I had to single out one as the most important, it would be number 5: aligning individual incentives with companywide goals.

It’s always great to hear people say that they’d do their jobs even if they weren’t paid to, but the reality of post-lottery-jackpot job retention rates suggests otherwise. You, and every member of your team, “work” for pay. Whatever the details of your compensation plan, it’s crucial that it aligns your entire team behind the company’s best interests.

Don’t reward marketers for hitting marketing milestones while rewarding engineers to hit product milestones and back office personnel to keep the infrastructure humming. Reward everybody when the company hits its milestones.

The results of this system can be extraordinary:

  • Department goals are in alignment with overall company goals. “Hitting product goals” shouldn’t matter unless those goals serve the overall health of your company. When every member of your executive team – including your CTO – is rewarded for the latter, it’s much easier to set goals as a company. There are no competing priorities: the only priority is serving the annual goals.
  • Individual success metrics are in alignment with overall company success metrics. The one place where all companies probably have alignment between corporate and departmental goals is in sales. The success metrics that your sales team uses can’t be that far off from your overall goals for the company. With a unified incentive plan, you can bring every department into the same degree of alignment. Imagine your general counsel asking for less extraneous legal review in order to cut costs
  • Resource allocation serves the company, rather than individual silos. If a department with its own compensation plan hits its (unique) metrics early, members of that team have no incentive to pitch in elsewhere; their bonuses are secure. But if everyone’s incentive depends on the entire company’s performance, get ready to watch product leads offering to share developers, unprompted.

This approach can only be taken so far: I can’t imagine an incentive system that doesn’t reward salespeople for individual performance. And while everyone benefits when things go well, if your company misses its goals, nobody should have occasion to celebrate. Everybody gets dinged if the company doesn’t meet its goals, no matter how well they or their departments performed. It’s a tough pill to swallow, but it also important preventive medicine.

Jul 9 2010

Book Short: Multiplying Your Team’s Productivity

Book Short:  Multiplying Your Team’s Productivity

No matter how frustrated a kids’ soccer coach gets, he never, ever runs onto the field in the middle of a game to step in and play.  It’s not just against the rules, it isn’t his or her role.

Multipliers: How the Best Leaders Make Everyone Smarter by Liz Wiseman and Greg McKeown (book, Kindle) takes this concept and drives it home.  The book was a great read, one of the better business books I’ve read in a long time.  I read a preview of it via an article in a recent Harvard Business Review (walled garden alert – you can only get the first page of the article without buying it), then my colleague George Bilbrey got the book and suggested I read it.  George also has a good post up on his blog about it.

One of the things I love about the book is that unlike a lot of business books, it applies to big companies and small companies with equal relevance.  The book echoes a lot of other contemporary literature on leadership (Collins, Charan, Welch) but pulls it into a more accessible framework based on a more direct form of impact:  not long-term shareholder value, but staff productivity and intelligence.  The book’s thesis is that the best managers get more than 2x out of their people than the average – some of that comes from having people more motivated and stretching, but some comes from literally making people more intelligent by challenging them, investing in them, and leaving them room to grow and learn.

The thesis has similar roots to many successful sales philosophies – that asking value-based questions is more effective than presenting features and benefits (that’s probably a good subject for a whole other post sometime).  The method of selling we use at Return Path which I’ve written about before, SPIN Selling, based on the book by Neil Rackham, gets into that in good detail.  One colorful quote in the book around this came from someone who met two famous 19th century British Prime Ministers and noted that when he came back from a meeting with Gladstone, he was convinced that Gladstone was the smartest person in the world, but when he came back from a meeting with Disraeli, he was convinced that he (not Disraeli) was the smartest person in the world.

Anyway, the book creates archetypal good and bad leaders, called Multipliers and Diminishers, and discusses five traits of both:

  • Talent Magnet vs. Empire Builder (find people’s native genius and amplify it)
  • Liberator vs. Tyrant (create space, demand the best work, delineate your “hard opinions” from your “soft opinions”)
  • Challenger vs. Know-It-All (lay down challenges, ask hard questions)
  • Debate Maker vs. Decision Maker (ask for data, ask each person, limit your own participation in debates)
  • Investor vs. Micromanager (delegate, teach and coach, practice public accountability)

This was a great read.  Any manager who is trying to get more done with less (and who isn’t these days) can benefit from figuring out how to multiply the performance of his or her team by more than 2x.

Jun 6 2013

Book Short: Like a Prequel to My Book

Book Short:  Like a Prequel to My Book

How to Start a Business, by Jason Nazar, CEO of our client Docstoc, is a great and quick (and free) eBook that feels a lot like a prequel to my book Startup CEO:  A Field Guide to Scaling Up Your Business (original outline here). My book is about scaling a business once you’ve started it.  Jason’s book is a really practical guide to starting it in the first place.

The thing that’s particularly good about this book is that it’s as much a resource guide as it is a book.  At the end of each of its 24 chapters (and within them as well), Jason adds a series of external links to other resources, from videos to checklists to templates.  The book answers a lot of really practical questions that are easy for product-focused entrepreneurs to gloss over or ignore, from corporate structures to insurance, from trademark registration to pitching VCs, from payroll to tax planning.

It’s great to see so much more being written for entrepreneurs these days.  Ash Maurya’s Running Lean: Iterate from Plan A to a Plan That Works (which I blogged about last week) is another related book that focuses on how to bring a new product to market.  But Jason’s eBook is a must read for anyone in TechStars or any accelerator program, or anyone contemplating starting a business.