1
Define the scope and purpose before collecting data
Decide whether the assessment covers the whole business or a specific function. Clarify who commissioned it, who the audience is, and what decisions it will inform. A focused scope prevents scope creep and keeps the document usable.
π‘ Write a one-sentence 'purpose statement' at the top of your working document before touching any section β it anchors every editorial decision you make.
2
Gather financial data for at least three periods
Pull revenue, gross margin, EBITDA, and cash flow for the current period plus two prior comparable periods. Include the same metrics for industry benchmarks if available from trade associations or market databases.
π‘ Use actuals from your accounting system, not management estimates. Even small discrepancies between your assessment figures and audited accounts will undermine credibility.
3
Audit core operations with measured data
Interview process owners and pull system data β cycle times, error rates, capacity utilization, and support ticket volumes. Compare current performance to internal targets and industry norms.
π‘ If data doesn't exist for a process, note that in the assessment β 'no measurement currently in place' is itself a finding.
4
Map the competitive and market landscape
Identify at least three direct competitors and note their pricing, customer segments, and recent strategic moves. Use publicly available sources: press releases, LinkedIn, trade publications, and customer review platforms.
π‘ Date-stamp every market data point you include. Stale competitive intelligence is worse than no intelligence β it leads to wrong conclusions.
5
Conduct the organizational and team review
Pull HR metrics: headcount by department, voluntary turnover rate, time-to-hire, open roles, and any engagement survey scores. Note critical single points of failure β roles where one departure would severely disrupt operations.
π‘ Interview at least two to three managers directly, not just HR records. The real skill gaps and team dynamics rarely show up in a spreadsheet.
6
Build the risk register with likelihood and impact ratings
List every significant risk identified during the analysis. Rate each High, Medium, or Low on both likelihood and impact. Identify which risks have no current mitigation and flag them as requiring immediate action.
π‘ Limit the risk register to no more than 10β12 items. A list of 30 risks signals that nothing has been prioritized and readers will stop engaging.
7
Draft recommendations linked directly to findings
For each significant finding, write one specific recommendation with an expected outcome, a responsible owner, a timeline, and an estimated cost or resource requirement. Do not include a recommendation that cannot be traced back to a specific finding.
π‘ Rank recommendations by a simple priority matrix β high impact and low effort first. This gives leadership a clear starting point even if they only act on three items.
8
Write the executive summary last
Pull the three to five most important findings and the top two to three recommendations into a one-page summary. Write it as if the reader will not see any other section β because many won't.
π‘ Have someone outside the assessment team read only the executive summary and tell you what actions they would take. If they can't answer, the summary is not clear enough.