Behind the “Screens”

A glimpse into my process as a designer

Sprint Demos & Design Presentations: part UX update, part live improv.

Every 2 weeks, I took the “virtual” stage to share UX updates with developers, product owners, and QA - not just walking through what I designed but why it mattered, to align the team, spark discussion, and refine the product with cross-functional feedback.

Bonus: I became very good at screen sharing, storytelling, and spotting bugs mid-demo.

Workshop Facilitation

I led a 3 part cross-functional workshop series with my product partner with 25+ stakeholders to define the Rewards roadmap for the AIR MILES Rewards Program. We identified target collector segments, and collector pain points based on data and analytics, brainstormed solutions, and evaluated them based on effort and impact.

I built the FigJam workshop structure, shared data-packed pre-read, and kept the team engaged with creative activities and interactive user scenarios.

Despite the questionable FigJam playlist attempting to set the mood, the workshops were a hit!

The Result: A prioritized roadmap and solid alignment across cross functional stakeholders.

Designer-Developer Collaboration

“When I logged the 142 bug, thats when I realized the importance of QA’ing designs as they’re being built - not just during UAT.”

To make the handoff process more efficient and build trust, I work closely with developers to co-create a process that works for both sides. We established a shared workflow, with consistent communication and a refined approach to documentation that fits how they like to work.

I provide detailed specs at both the screen and component level, including:

  • design states and edge cases

  • example use case scenarios

  • Accessibility considerations

Every two weeks, we sync in UX-dev refinement sessions to walk through designs, clarity logic and flag potential dev or UX gaps before they become JIRA tickets.

And the QA doesn’t stop there - I continue to test and review builds as components and screens are being developed, ensuring the final experience matches the intent.

Leveraging AI (Copilot)

Me + Copilot = Smarter, Faster, Funnier UX. Co-pilot helps me think sharper and design better. Here’s how I put it to work:

  • Stress-testing designs by exploring edge cases I hadn’t considered

  • Prepping stakeholder-proof rationale by anticipating the tough questions

  • Challenging assumptions with alternative perspectives

  • Heuristic checking using Nielsen Norman principles

  • Content polishing for tone, clarity, and UX voice

  • Writing usability testing questions tailored to specific flows

  • Speed-researching patterns and best practices across domains

  • Grabbing legit resources (Baymard, NN/g) without the tab chaos

  • Development handoff help, like:

    • Translating design decisions into developer-friendly terminology.

    • Flagging key logic and behaviours

    • Highlighting accessibility requirements (e.g. color contrast, focus states, ARIA roles).