Cancer Council Victoria was replacing the digital foundation behind Quit while establishing the basis for a national cessation platform: a more accessible and flexible way for Australians to find evidence-based support to stop smoking or vaping.
My role was to lead delivery from solution design through launch, creating enough clarity for the client, designers and engineers to keep making good decisions as the plan changed around us.
The constraint
The broader Quit ecosystem included more than 25 disconnected websites and tools, legacy technology, manual content workflows and a large stakeholder group spanning digital, research, clinical, content, communications and technology.
The foundational platform also had a fixed contractual launch commitment in December 2025.
At the same time, content was still being rewritten and migrated, third-party services were being integrated and provisioned, and major product decisions were continuing to emerge through real content entry and testing.
I had only recently joined Inlight, so I was learning a new organisation, multidisciplinary team and client environment while helping the project establish its delivery rhythm.
The question I kept coming back to was:
What genuinely needs to be true for launch, and what can safely improve afterwards?
Creating clarity around the work
As more of the platform became tangible, the amount of feedback naturally increased.
Without a clear process, a new suggestion could easily look as important as something genuinely blocking launch.
I introduced a consolidated ClickUp workflow with CCV so feedback came through nominated people, was triaged at agreed points, and was explicitly classified as launch-critical or post-launch, as well as by type.
The mechanics were simple, but the purpose was product-focused: give design and engineering enough space to finish the most important work while making sure useful feedback was not lost.
By the final stages of delivery, content migration had become part of the critical path into UAT. That changed how I assessed new requests. A theoretically better solution was not necessarily the better product decision if implementing it stopped the content team moving.
Decision 01 — Stop waiting for the ideal forms integration
One of the first major risks appeared around forms.
The intended custom form solution depended on Salesforce work that was not ready. Continuing to wait would have put the wider delivery plan at risk.
I made the call to move forward without the custom implementation for Phase 1. Instead, we embedded the existing form experience within the new platform.
It was not the architecture we ultimately wanted, but it protected the user journey and removed an external dependency from the critical path. The deeper integration could be revisited later without holding up the rest of the platform.
Decision 02 — Choose the pragmatic content architecture
A second decision arrived much closer to launch.
During content migration, CCV discovered that informational pages needed functionality originally designed for Articles, including references, sharing, tags and better content discovery.
There were two reasonable options.
We could substantially rework the Article template. It was the more complete solution, but it required significantly more design and engineering effort and would have delayed content entry by at least two weeks.
Or we could enhance the Page template that already existed, allowing the content team to continue immediately while deferring some richer listing and filtering behaviour.
I worked with our Design Lead and Engineering Manager to estimate both approaches, then wrote the recommendation for CCV's leadership team setting out the effort, trade-offs and impact on the December deadline.
I recommended the second option.
It was not the most complete solution. It was the right solution at that point in the product's lifecycle.
It kept content migration moving, protected time for QA and launch, and avoided introducing unnecessary late-stage effort into an already constrained engagement.
The outcome
The foundational National Cessation Platform launched in December 2025 against the contractual delivery commitment.
Phase 1 established a new platform foundation spanning structured content and reusable components, search, analytics, personalisation foundations and interactive cessation tools including the Quit Plan, Cost Calculator and Health Effects experience.
My Quit Plan turns a difficult personal goal into a clear, guided series of steps.
The platform brought practical services including My Quit Plan, the Cost Calculator and the interactive Health Effects experience into a consistent, accessible product ecosystem.
The Health Effects experience makes a complex evidence base easier to explore by product and area of the body.
The work then moved into structured handover and managed support rather than an extended build phase. The selected article-to-page migration was completed after launch, validating the decision to keep content moving rather than pause for a larger template rebuild.
The platform has continued to be used at national scale. In September 2026, Google Analytics showed approximately 40,000 users over the previous 30 days, with the Quit Plan, support pathways and health tools among the most-visited experiences.
What I learned
This project reinforced that complex delivery is often an exercise in product judgement rather than plan adherence.
Dependencies fail. New information arrives late. The best solution on paper is not always the right solution at that moment.
The useful skill is making the consequence of each option clear enough that a team and client can keep moving with confidence.
Sometimes that means adding structure. Sometimes it means making a deliberate compromise. And sometimes good leadership is recognising that “not yet” is a better decision than allowing perfect to put the outcome at risk.