Refund Policy Risk Review & Beta Program

Risk Analysis & User Research · Bachcare Holiday Homes
Project Overview
When the New Zealand Government imposed COVID-19 lockdown restrictions, the company's cancellation and refund policy suddenly faced situations it was never written for.
My Contributions
On my own initiative and in my own time, analyzed the refund policy, identified the legal and reputational exposure, and recommended revised terms and conditions to the executive team and board. Separately, planned and led the company's first-ever beta testing program, for the Contractor Portal used by cleaners and hospitality staff.
~$45K
saved by testing in-house
68%
fewer post-release incidents
4.7/5
ease-of-use rating
38
issues caught before release
120+
user insights gathered
How the beta ran

Bachcare’s first beta program, in three phases

1
Plan
Test plan, Jira workflow, and 10–20 internal testers.
→
2
Pilot · 1 week
Caught show-stopper issues early and cheaply.
→
3
Full beta · 2 weeks
Interviews, surveys, and heatmap analytics.
→
4
Closure · 1 week
Analyzed 38 issues and 120+ insights.
→
5
Release
React.js portal shipped with 68% fewer incidents.
Bachcare Holiday Homes
Junior Technical Business Analyst
2019 – 2021

Refund policy review: the analysis showed the existing refund policy exposed the business to legal risk and public backlash during the lockdowns. I presented the findings and a redefined set of terms and conditions to executives and board members.

Beta program: the beta validated the Contractor Portal after its migration from PHP to React.js. Until then, Bachcare had relied only on developer-led checks. I ran it in three phases: a one-week pilot, a two-week full beta, and a one-week closure. 10–20 internal staff and contractors logged 38 issues and produced 120+ qualitative and behavioral insights through interviews, surveys, and heatmaps.

Results: 68% fewer post-release incidents than earlier rollouts, a 4.7/5 ease-of-use rating, and about $45,000 saved by testing in-house instead of hiring external QA contractors. The test plan and Jira workflow became the standard for future releases.

Also at Bachcare: ran the Scrum ceremonies for the development team and built scalable workflows and automation on Salesforce.

Lesson learned: a short pilot surfaces the show-stopper issues cheaply, and reusable templates make every later beta faster to set up.

Before and after

What changed for releases

Before
Releases were checked only by developers
The Contractor Portal was moving from PHP to React.js
Hiring an external QA contractor was the alternative
No repeatable testing process to reuse
After
A structured beta program, run in-house
38 issues caught before release
68% fewer post-release incidents and a 4.7/5 rating
The test plan and Jira workflow became the standard
Methods and tools

Built with

Jira
Salesforce
Scrum
User interviews
Surveys
Heatmap analytics