Swiftio supports aged care teams across Australia: GPs moving between patients, and nurses and facility managers coordinating from a desk. I joined from Kaizer Studios as the embedded design partner, working directly with the founding and engineering team across all three portals.
The doctor app, nurse portal, and facility manager portal had each grown one feature at a time, on a shared generic AI design and an early platform vendor chosen to move fast in the beginning. As the product needed to scale and prepare for larger partner capability, staying on that path risked slowing the team down just when speed mattered most.
Watching all three roles work made the gap obvious. Doctors move in short bursts, one ticket, one decision, moving on. Nurses and facility managers work in longer sessions, reconciling across a whole facility. A single generic template, on a platform not built for the team's pace, served none of them well.
I revamped the interface across all three portals, tailoring each to how that role actually works, and pushed as product manager to leave the early platform vendor for a codebase the team could own and control outright. Staying on the original platform would have cost the team speed at exactly the point they needed it most, right as two larger partner integrations were coming into view. My designs, originally built for the old platform, were structured cleanly enough to carry over without a redo.
Leaving the early platform meant pausing feature work to migrate, at a point when the product surface was still small enough to move cleanly. Waiting until later, once more features and two partner integrations had landed on top of it, would have made the same migration far more expensive. The cost was paid early and on purpose, while it was still cheap to pay.
Two confidential partner integrations were in early conversation during this work. I'm now the design lead on one of them. There's no outcome to share yet since it's pre-launch, and that gap is intentional rather than glossed over.