KENYA · GUIDE 0589 · EDITION 4.2
Spreadsheet dashboard building in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- Wrong definitions
- broken references
- stale data
A colourful dashboard fails when revenue means invoiced sales on one page and cash received elsewhere, leading the owner to compare incompatible figures.
A risk list is useful only when it changes a decision. For each risk, write the observable warning, who checks it and the response before the next commitment. Do not treat a reserve of money as permission to continue unsafe or unauthorized work.
Use a small, measurable pilot
Create a small dashboard from fictional or authorized sample data.
The pilot scope is: Build the dashboard around decisions the owner makes, identifying approved data sources, metric definitions, refresh responsibilities, and how missing periods should appear.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Build the dashboard around decisions the owner makes, identifying approved data sources, metric definitions, refresh responsibilities, and how missing periods should appear. |
| Output acceptable | Ask the owner to trace selected figures to source records and explain the chart, checking filters, date boundaries, duplicates, and missing-data signals. |
| Costs recorded | Include data cleanup, calculation design, layout, source connections, documentation, and training, allowing for manual refresh work that remains necessary after delivery. |
| Buyer response recorded | Record metric definitions, source versions, reconciliation results, filter tests, missing periods, owner questions, and independent refresh attempts before accepting the completed dashboard. |
Stage the launch around prerequisites
First confirm the buyer specification and activity requirements. Then compare suppliers, establish suitable facilities and prepare the operating record. Run the bounded trial when those prerequisites are in place. Review actual costs, quality failures and cash collected before increasing the commitment.
This sequence is not a promise that the complete business cycle fits into 30 days. Growing periods, qualifications, approvals, seasonal access and customer buying cycles can require longer. Revise the schedule when a prerequisite changes rather than skipping it to meet a launch date.
Choose continue, revise, pause or stop
Continue only when the scoped result is accepted and direct costs and payment timing are workable. Revise one part of the offer if the problem is identifiable and affordable to test again. Pause when required information, permission, skills or resources are missing. Stop the affected work when safety, consent or lawful authority is uncertain.
Keep a maximum test loss and unpaid-balance limit suited to your actual funds. A successful single delivery is useful evidence, but it does not establish year-round demand or justify committing every available resource.
Tie launch milestones to observable checks
| Risk signal | Evidence to inspect | Response to test |
|---|---|---|
| New month missing | Check source-table expansion and chart range. | Extend the correct structured source and retest a new row. |
| Net double-subtracts refund | Compare signed amounts with metric definition. | Correct treatment and rerun base fixtures. |
| Zero appears for broken import | Check source row count and refresh errors. | Display missing/error state separately from a genuine zero period. |
Outstanding go / hold conditions
- Real source quality and metric definitions unverified.
- No financial assurance, dashboard execution or performance result claimed.
Assign an owner, evidence reference and review date to each unresolved condition. Do not give every milestone a fixed calendar date when it depends on a crop, production, approval or competence cycle. Run only a suitable limited trial, reconcile accepted output and actual cash, and record whether the evidence supports holding, revising, proceeding within the limit or stopping.