Do you canary deploy your new features using a spreadsheet?

Canary deployments let you release new features or updates to a small group of users first, gather feedback, and reduce the risks of a global rollout. At SSW, we track all our canary testers, their onboarding dates, OS, test status, feedback, and environment in a single spreadsheet.

Figure: Example canary deployment spreadsheet – track who is testing, the environment, and their feedback

Using a structured spreadsheet ensures transparency and consistency, so no one is missed and feedback can be actioned quickly.

Practical use case

Scenario: You’ve built a new feature and are eager to roll it out to everyone.

❌ Figure: Bad example – No clear plan, no single source of truth, no tracked outcomes

✅ Figure: Good example – A single, consistently updated spreadsheet for your canary rollouts

Steps to implement a canary spreadsheet

1. Create your spreadsheet
   • Include columns for User, Date Onboarded, Status, Mark /10, OS, Environment, and Notes
   • Store it in a central location (e.g. Microsoft 365, Google Sheets) accessible to all stakeholders, testers and developers
   • If relevant, feel free to add as many columns as needed
2. Identify your canary testers
   • Start with a small, diverse set of users
   • Include at least one “power user” who knows the system deeply and one “fresh perspective” user
3. Onboard each tester
   • Give them clear instructions (including any known limitations or the environment’s URLs)
   • Direct them to fill in or confirm their details in the spreadsheet
4. Record feedback
   • Ask each tester for a rating (Mark /10) and to log outcomes under Status (Test Passed, Test Failed, etc.)
   • Document any showstoppers or usability issues in Notes
5. Iterate quickly
   • If someone logs a “Test Failed,” address the issue before inviting more testers
   • If changes are requested, update the environment or instructions, then retest
6. Go wider
   • After successful canary feedback, roll out your feature to all users
   • Keep the spreadsheet as a living record of the rollout process

Possible statuses

• N/A – Not started or not applicable yet
• ✅ Test Pass (with changes requested) – Feedback is positive, with small tweaks needed
• ❌ Test Failed – Showstopper or critical bug prevents completion

Avoid confusion

A canary deployment spreadsheet is your single source of truth. If a tester isn’t responding or is blocked, assign another tester rather than stalling the rollout. Record these changes so it’s clear who tested and when.