Root cause analysis: getting past the first plausible answer
Root cause analysis works out why something went wrong deeply enough that fixing it prevents a recurrence. Its main difficulty is stopping too early, at an answer that sounds satisfying.
A business plan template is scaffolding, not an answer. The value is in three or four sections that force a real decision — the rest exists because a bank asked for it.
Reaching for a business plan template is usually the right instinct: a blank page is the worst possible place to think about a business, and the standard section list is a decent checklist of what a reader will ask. The mistake is treating the template as the work. A thirty-page plan assembled from prompts, none of which changed anyone's mind, is a document, not a plan.
Before filling anything in, be honest about who the reader is. A bank wants to know how the loan gets repaid. An investor wants to know why this becomes large. A grant body wants to see eligibility and delivery. And if the answer is that you are the only reader, most of the template can go — what you need is a few pages you will actually revisit.
The financial section is where plans are won or lost, and it is the one people copy least carefully. A reader with any experience goes to the cash-flow forecast first, checks whether the revenue line has an assumption behind it, and forms an opinion about the rest of the document from what they find there.
For most small businesses, a one-page plan plus a working cash-flow model beats a long document, and it gets updated. The long form is worth writing when an external reader demands it: a bank loan, a grant application, a visa or licence requirement, an investor process. Even then, write the short version first — the long one is easier to produce from a plan that already holds together than the other way round.
In Ettex, the document itself sits in Ettex Docs — templates and outlines, threaded comments with @mentions when a co-founder or an accountant reviews a section, and version history so the plan you sent the bank in March is still recoverable in September. The numbers belong in Ettex Sheets: an import of an existing XLSX with formulas intact, 150+ functions, charts from any range, and pivots when the model grows. If you present the plan rather than send it, Ettex Slides handles the deck, and anything that gets signed — a loan agreement, an investment document — goes through Ettex Signature.
To be clear: Ettex does not ship a library of ready-made business plan templates, has no plan wizard, and does no financial modelling for you. You get a document editor with comments and history and a spreadsheet with real formulas. The structure above is yours to build once — and a plan you built is worth more than a plan you filled in.
Executive summary, the business, market, competition, operations, team, financials, funding and risks. For internal use, the financials, operations and risks sections carry almost all the value.
As short as the reader allows. One page plus a cash-flow model is enough for most small businesses; banks, grant bodies and investors usually want the full form, typically ten to twenty pages plus appendices.
Monthly for the first year, then annually for two to three more. Beyond that, precision is invented — what matters is that the assumptions behind year one are visible and checkable.
Last, always. It is a summary of conclusions you do not have until the financials and the operations sections are done — but it is read first, so it deserves the most editing.
You need the thinking, not necessarily the document. A one-page plan and a working cash-flow forecast do the job, and being short is what makes them get updated.
Quarterly, or whenever a core assumption changes — price, channel, cost base, a key hire. A plan written once and filed has no way of being wrong, which is the same as having no way of being useful.
A business plan template is a good place to start and a bad place to stop. Build the numbers first, name the real competitors, cut everything that would be true of anyone — and keep it short enough that you will read it again in three months.
Root cause analysis works out why something went wrong deeply enough that fixing it prevents a recurrence. Its main difficulty is stopping too early, at an answer that sounds satisfying.
A code of conduct says how people here are expected to behave and what happens when they do not. Its value is not aspiration — it is having decided the hard cases before one arrives.
A project charter names the objective, the boundaries, the sponsor and the person authorised to run the work. Its main use comes months later, when people disagree about what was agreed.