Prioritisation
How the work was prioritised
In one line
RICE is useful for comparing value, but it doesn't decide sequence. Dependencies do.
The method
No formal RICE sheet was kept in 2025, so the shipped initiatives below have been scored afterwards, using the best estimate of what was known at each decision. They show the reasoning, not a precise forecast.
RICE score=(Reach × Impact × Confidence)Effort
- Reach: share of Zigly's online customers affected in a quarter, from 0 to 100.
- Impact: 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal.
- Confidence: how sure the estimate was: 100%, 80% or 50%.
- Effort: person-months for a team of four developers and one QA engineer.
Shipped initiatives, scored afterwards
Scored afterwards, using the best estimate of what was known at each decision.
InitiativeReachImpactConfidenceEffortScore
- Fulfilment from storesReach100Impact2Confidence80%Effort2Score80
- ClickPost post-order automationReach100Impact2Confidence80%Effort2Score80
- Magento to Shopify replatformReach100Impact3Confidence80%Effort6Score40
- Calling and ticketingReach40Impact1Confidence100%Effort1Score40
- Vet and grooming bookingReach60Impact2Confidence80%Effort3Score32
- Rewards pointsReach100Impact1Confidence50%Effort2Score25
- E-pharmacyReach40Impact3Confidence50%Effort4Score15
- Webview mobile appReach30Impact0.5Confidence80%Effort1Score12
- Zoho CRM PlusReach40Impact2Confidence80%Effort6Score10.7
- Ringg.ai voice agentReach10Impact1Confidence50%Effort1Score5
Why these inputs, briefly:
- Store fulfilment: every shipment affected; mostly configuration.
- ClickPost: every order needs tracking; mostly integration work.
- Replatform: every visitor affected; a proven platform, but a full migration.
- Calling: only customers who contact care; off-the-shelf tools.
- Booking: a large services base; a custom VetBuddy integration.
- Rewards: whether points would change behaviour was uncertain.
- E-pharmacy: a new, regulated category across four systems.
- Webview app: low effort, low added value.
- Zoho: agent-facing; seventeen sources to integrate.
- Ringg.ai: narrow use, and new to the team.
Why the build order differs from the scores
The website foundation scores only 40. Yet the two initiatives ranked above it, and most of those below it, could not exist without it.
- E-pharmacy needed ClickPost, VetBuddy and the order system already working.
- Zoho was only worth doing once there were enough systems to bring together.
- Ringg.ai needed both the booking API and Zoho's appointment data.
So the scores helped compare value, and the dependency map set the order. The same thinking shapes what comes next (see What's next).