During a quiet period with limited incoming work, I took the initiative to create a reusable design system for Power Apps — a platform often seen as visually restrictive and under-designed.

I started by gathering screens from past client-facing Power Apps projects, many of which had been delivered with minimal design polish due to time or budget constraints. I redesigned these screens using a cohesive, component-based system to demonstrate how much more refined and usable these experiences could be — even within Power Apps’ limitations.

This self-led effort caught the attention of another team, leading to several new opportunities — including the Vector Substation Keys Rebuild, where the design system played a key role in accelerating delivery and improving the final outcome.

The Power Apps design system I built includes:

• A robust component library designed to work within Power Apps’ constraints

• Scalable design patterns across devices and resolutions

• Visual hierarchy, spacing, and accessibility rules

• Quick brand customisation options for different clients

• Clean documentation and file structure to support developer collaboration

I used my Power Apps design system to transform low-fidelity wireframes into a cohesive, branded high-fidelity interface — adapting Vector’s identity to create a clear, usable experience within the platform’s limitations.

Vector is a major electricity and gas provider in Aotearoa New Zealand. This project focused on rebuilding their Substation Keys Register — a tool used to manage access to critical infrastructure. I worked closely with Vector’s in-house UX designer to bring the tool to life, using my system to enhance efficiency and consistency throughout.

Despite the challenges of working within Power Apps’ rigid structure, I delivered a solution that aligned with the client’s vision, brand, and technical limitations — proving that even utility tools can feel polished and intentional.

Designing within the tight constraints of Power Apps required creative thinking and deep platform understanding. I learned how to push visual quality and usability without compromising feasibility.

Presenting my system to new teams and advocating for its adoption also taught me how to lead with clarity and quiet confidence — especially when working with stakeholders unfamiliar with design systems or the platform itself.

This work reminded me that design leadership doesn’t always mean visibility. Sometimes, it’s the systems you build behind the scenes that change the way a team works.