Pick a Plan, Any Plan

I'm fortunate enough to have not only a friend who writes business plans, but another friend who was a commercial lender. Thus I have friends on both the author and audience side of business plans. I myself am no expert on business plans, but these friends have given me valuable insights into what they must include to be effective.

My retired commercial lending friend recently suggested that one approach towards pitching a product to investors is to put together a simple, straw man business plan before spending too much time and effort fleshing it out. The idea is to put forth the basic value proposition and projections and use it to get feedback on how to refine it.

Of course, you will need to do some market research to end up with a compelling and credible plan. To some extent, the nature of this market research may depend on feedback you get from presenting your straw man business plan, however. So how do the business plan and the market research fit in with each other, given this cart-before-the-horse problem?

The answer is to iterate on both your market research and your business plan. Compose your business plan at the same time you hire a skilled product manager to research the market. Write the skeleton business plan, fleshing it out iteratively as the research findings and data collect. Start with formulas and metrics and plug guestimates into them, then put "real" numbers into it as data accumulates from the research.

Comments

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio

Cauvin

Search This Blog