KENYA · GUIDE 0605 · EDITION 4.2
Computer keyboard repair in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- Hidden liquid damage
- Wrong layouts
Repair is poor value when several hidden failures remain or a superficially fixed key becomes unreliable during normal typing after a brief counter demonstration.
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
Test a supported keyboard and compare repair with a traceable replacement before quoting.
The pilot scope is: Repair supported keyboards after identifying whether faults involve keys, connectors, contamination, or the host device, agreeing repair feasibility and replacement alternatives before work.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Repair supported keyboards after identifying whether faults involve keys, connectors, contamination, or the host device, agreeing repair feasibility and replacement alternatives before work. |
| Output acceptable | Test every key and relevant shortcut after repair, checking intermittent behaviour, repeated characters, connection stability, and whether the customer's original symptom genuinely disappears. |
| Costs recorded | Include diagnosis, replacement mechanisms or assemblies, cleaning supplies, disassembly time, failed repair attempts, and the commercial comparison with a suitable complete keyboard replacement. |
| Buyer response recorded | Record key-level symptoms, host-device checks, contamination observations, replaced parts, full typing tests, intermittent faults, and the customer's decision between repair and replacement options. |
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 |
|---|---|---|
| Only one application fails | Check shortcuts/settings. | Resolve software cause before parts purchase. |
| Repeated spaces remain | Compare same test on second device. | Escalate hardware diagnosis; do not claim fixed. |
| Keycap unfamiliar | Check model instructions. | Stop removal and seek appropriate service. |
Outstanding go / hold conditions
- No keyboard inspected or successful repair 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.