On Wed, 9 Dec 1998 Tom Bryant wrote Re: Business Plans
[...]look at the roles of planning in entrepreneurial
>behavior. Amar Bhide, at Harvard has done some provocative work debunking
>our control-oriented predilection for pushing entrepreneurs through things
>called Business Plans (articles in HBR, 1986, 1994). His work shows pretty
>clearly that the presence of a formal plan is not a success indicator.
>
[...]
>Can we revisit the "controlled chaos" discussion a bit? What do we know
>about managing the degree of chaos we unleash with learning exercises?
>When is "a little knowledge"' simply not enough? Why does curiosity
>sometimes overwhelm us? How do we, really, pace a learning process?
First, I think that there are Business Plans and *Business Plans*.
Business Plans focus on financial spreadsheets while *Business Plans* focus
on actions, enabled by resources and producing value. In consonance with
Mr. Bhide, in my experience (current, unfortunately) Business Plans have
little correlation to success. The Visions expressed are but unrecognized
Hallucinations and the numbers are fictional stories. Conversely, *Business
Plans* include spreadsheets but only as expressions of expected results
(rather like the speedometer, gas gauge and radar detector) and not as the
steering wheel, accelerator, brakes nor map. For what its worth, the *BP*
answers the following questions:
1. What do we do for a customer?
What needs do we meet, what problems do we solve (from their viewpoint)
What are their key characteristics that creates this need
-- that makes them our customers
What role do we play (on the customer's team)
What tasks do we perform
What are the deliverables (what we leave behind)
2. What does our Value Added do to the Customer's "System"?
-- before we do it
What they do, how they do it, and the economic structure of the
game they are in.
-- after we do our thing.
What will they do, how will they do it, and what changes will they
be able to make to the economic structure of the game they are in.
3. What results will they get?
Benefits they can expect
Performance changes to their system --
Performance changes in their business --
Competitive edge enhancements --
Collateral Impacts (what costs and pain to them will we
cause) --
Value they can realize:
The economic leverage they can gain plus the new rate of learning
and adaptation they can enjoy minus the cost of collateral impacts --
4. Why will our technology and approach work -- and be accepted?
5. How we do it?
Our skills
Customer Project Scenarios
Key Ideas and Concepts
How we mitigate their pain of change.
Results (e.g. Quick implementation, Low risk (high foresight)
projects, Low cost implementation, Self-sustaining staff)
6. What will we learn from each "project"
and how will we apply that to building a better company?
7. How we will qualify prospects?
criteria
decision process
8. How we will attract prospects?
How we find them. Better yet, how we help prospects find us
9. How we will Sell and Manage Accounts?
What Information, process, techniques, tools, effort?
10. Why we will win?
Why they should prefer us
Why we will be successful
11. What else is important?
12. How big could this market be?
-- driving forces
-- who are immediate targets
-- who are likely followers
-- who are the unknown 90%
13. What is our Development and Intro Plan for information, services
and products?
Key Technologies, Critical Resources, Steps, Method
14. How big could our business become?
Our limits of Management Competency and Cohesion
Competitors and Rivals
Price Elasticity
Our Readiness and Image
What share can we expect
What are our other limits to growth
15. Outlook -- our L-M-H scenario?
Revenue
Costs
Staff
Profits
Cash Flow
Note that not until #12 - #15 do spreadsheets beging to come into play.
In light of this, I am not surprised that your students are cavitating.
There are simply too many variables and n(n-1)/2 interreletionships.
Especially if they start only at the financial view of the business,they
have no basis for deciding any specific parameter or relationship. I can
still remember the first time I had to help prepare a business plan without
a guru. We had five person teams and were still floundering after a week.
Then we got back to the basics of what a business does rather than what it
looks like. It still took another week to create a very simple plan.
Now I coach supposed CEO's through the process and it takes the better part
of three months. Of course we are examining all the variables but it is
still very complicated.
I suggest looking at the problem as follows:
*Business Planning* is a larger form of Project Planning. (A business is
but 63 projects which must be orchestrated. If the orchestration is sloppy
the financial results will be low and if perfect, the financial results
will maximize.)
Accordingly, the students should start with a Project Planning assignment
(develop a product) followed by a second (produce a product) and a third
(bring 100 propects to the point of salivation in two months) and a fourth
(make 100 quotes and close/negotiate 50 Purchase Orders within two weeks of
the onset of salivation) and a fifth, hire and train the 5 people required
to support the 50 new customers, with a lead time of four months). Now
have the students integrate the five projects (and the costs) and estimate
the subsequent revenue that the 50 customers will pay depending on sale vs.
lease assumptions.
Easy for me to say, aye?
Jack Ring
32712 N. 70th St.
Snottsdale, AZ 85262-7143
sendmail:
jring@amug.org
602-488-4615
Cell) 602.418.8784
F)602-488-4616