Brian Rhea Brian Rhea

You Need a Plan, Just Not a “Business Plan”

If you’re early stage and small, take advantage of those strengths with an equally small and nimble business plan.

Emulating the enterprise approach to business planning makes as much sense as emulating their tedious approach to software development.

A common mistake small businesses make is thinking they need to operate the same way as massively scaled enterprises with thousands of people on the payroll.

“If the big, fancy, successful companies are doing it, then it must work!”

But, your biggest advantage as a startup is that you’re able to make local decisions and change course quickly! In fact, it’s common for a well-functioning team to dig into a customer problem in the morning, brainstorm a solution, and ship an improvement that same afternoon.

Mature companies with years or decades of bolted on processes and code debt can’t match that sort of responsiveness!

And so, in the same way that you should ignore the engineering practices of large companies and embrace your small, nimble nature; ignore the business planning practices of the big guys and adopt an equally nimble approach to planning.

An approach that many startups have used is the Business Model Canvas developed by Steve Blank, and adapted by Ash Maura as the Lean Canvas.

Each of these tools have their pros and cons, and neither are perfect. But one thing they have in common is that whatever you write in them on Day One is very unlikely to be what is written down on Day One-hundred and One.

The temporary nature of the Business Model Canvas is a feature, not a bug.

Your plan should be able to adapt to what you learn from your customers as you build, test, observe, repeat. If you spend weeks or months working on and revising a forty-page “Business Plan” in the early days, you’ll be subconciously invested in proving it right to convince yourself all that time wasn’t a waste.

With a Business Model Canvas, you can hammer out Version 0.1 in an afternoon at your favorite coffee shop and look forward to revising and improving it upon first contact with your customers.

If a conventional Business Plan holds any value for a typical startup, it’s that it forces the founders to think through the many challenges they’re likely to face. That’s a good thing, but instead of investing a boat-load of time on bizspeak prose in a Business Plan, jot a couple bullet points down on your Canvas and spend the rest of that time testing your hypothesis in the real world.

JTBD App Now in Beta!

I'm working on a JTBD app to help you build better products!

JTBD is an amazing tool, but it can be pretty confusing. I'm working on a product to help teams like yours conduct Jobs to Be Done research you can actually use.

Request early access today!

Related posts

If you're still reading, you'll probably like these.

Never Ask Your Customers: Would You Use This?

“Would you use this?” is probably the worst and most expensive question you could ask a customer.

Product Risk and Market Risk

Understanding the difference between these two types of risk should change how you approach customer research.

Focus On the Problem

One of the most common mistakes people make early on is jumping to a solution too quickly and getting attached.

Customer Interview Tips & Tricks to Save Time & Money

If you haven’t heard this nugget of truth yet, you will soon: “You’ve got to get out of the building.”

Early-stage Startups and Uncertainty Go Hand in Hand

I was a guest on a podcast talking about early-stage startups recently and the host asked: "We know most startups fail, but the number one reason is they don't meet a market need. Why is that?"

Pretend the Stakes Are Low Even If They Aren't

When you're kicking off customer interviews to collect feedback on a design or prototype, one of the most important things you should say is:

Is Your Market Leader Susceptible to Disruption?

Do you find yourself in a market with a long-standing, dominant player, and you’re wondering:

Using a JTBD Survey to Quantify Unmet Customer Needs

In this post, I’ll show you step-by-step how I’ve used the approach described in Tony Ulwick’s book, "What Customers Want" to help my clients get a much better handle on what to build, what to improve, what to leave alone, and what to ignore.

How to Write Jobs to Be Done Example Statements

If you're trying to integrate Jobs to Be Done into your design process, you've probably found yourself looking for some concrete examples of Jobs to Be Done statements to be sure you're on the right track.

Start Over with Simplicity or Reduce Complexity?

I was having a conversation with a client recently and they’d more or less come to the conclusion that they needed to do a hard reset on the company and rebuild their application.

Kano Model (Part 2): Creating Your Survey

Using a Kano-based survey, you can avoid false positives (“Oh, sure I'd totally use that!” ... never uses it) and identify the features your product actually needs to have to satisfy and delight your customers.

Kano Model (Part 1): Understanding the Kano Model

What is the Kano Model?

Ready to know what your customers actually want? Get in touch.