KENYA · GUIDE 0033 · EDITION 4.2
Chive growing in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- wilting
- labour-intensive small orders
Living pots can shift harvesting effort to a busy kitchen that expected a ready-to-use garnish, making a longer-lasting presentation commercially less convenient than cut packs.
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
Compare a cut-leaf pack with a living pot using one chef's feedback.
The pilot scope is: Compare cut chive packs with living pots for a kitchen whose garnish use is observable, asking how each option fits its available preparation and holding space.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Compare cut chive packs with living pots for a kitchen whose garnish use is observable, asking how each option fits its available preparation and holding space. |
| Output acceptable | Have the chef cut or portion both samples during normal service and note damaged tips, usable leaf quantity and convenience when a dish needs finishing. |
| Costs recorded | Include trimming and packing cut leaves separately from pot establishment and return handling, then compare earnings by actual kitchen orders rather than apparent plant productivity. |
| Buyer response recorded | Record service feedback, quantity used, tip damage, pot-care demands and repeat purchasing choice, allowing the preferred product form to emerge from the customer's real workflow. |
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 |
|---|---|---|
| Garlic flavour instead of onion | Check source-clump labels and approved sample | Hold substituted stock and restore the chosen type. |
| Hard stalks in leaves | Inspect flower-stalk removal at grading | Re-sort the lot before weighing. |
| Leaves kink and leak moisture | Inspect pack length and compression | Use a longer looser pack and validate the route before expanding. |
Outstanding go / hold conditions
- Local source identity and clump management require review.
- Packet weight and current delivered price unknown; no chopped-product process validated.
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.