Skip to content

Ontario Electricity Support Program

A coded prototype as the decision artifact

The client couldn't see how a web-standards mandate would land on their real site. I built the working experience instead of a style guide, and fixed the UX along the way.

Role
Product strategy, UX design, front-end prototyping
When
2024
Scope
Full applicant journey, authenticated dashboard, design system in code

The problem wasn't the standards. It was imagining them.

The Ontario Electricity Support Program had a mandate: bring the applicant experience in line with the Ontario Design System. The team had the standards. They had a style guide. What they didn't have was any way to see what their own site would become once the standards were applied — and without that, every review meeting turned into a debate about hypotheticals.

A static style guide answers "what does a button look like." It doesn't answer "what does our eligibility form look like, with our questions, when someone on a phone hits the third screen and realizes they picked the wrong household size."

What I built instead

Rather than annotate mockups, I built the applicant journey as a working site: eligibility, application, document upload, and a state-driven authenticated dashboard where an applicant could see where their case stood. Hand-coded in Eleventy, deployed to Netlify, clickable by anyone with the link.

Three things made this the right call rather than a flex:

  • The standards had to be seen in context. The question stakeholders were actually asking was "will this still feel like our program," and the only honest answer was a page they could use.
  • State mattered. The dashboard changes depending on where an applicant is in the process. That's hard to convey in a flat mockup and trivial to convey in a prototype that actually changes.
  • Review cycles were the bottleneck. A link beats a deck. People reviewed on their own time, on their own devices, and came to meetings with specific feedback instead of general unease.

The UX fixes rode along

Building the real flow exposed problems the mandate hadn't asked about: questions ordered for the back office rather than the applicant, dead ends when eligibility failed, no way to save and return. I fixed them in the same pass. The prototype shipped as a better product, not just a compliant one.

What this is evidence of

I use coded prototypes when the decision hinges on how something behaves, not how it looks — and I don't use them when a sketch would do. The judgment about which situation you're in is the senior part of the job. Here, the code was the decision artifact, and it ended the debate.