01 · The challenge
Create a path from uncertainty to contribution.
AI was changing the boundaries of product design, but the team’s experience and confidence were uneven. We had no shared definition of AI fluency, no consistent workflow, and no safe path from experimentation to meaningful contribution.
My leadership challenge was to create the conditions for people to learn quickly, take thoughtful risks, and carry design intent closer to implementation.
02 · The strategy
Make learning part of how the team works.
I built a system of reinforcing interventions. Each addressed a different barrier to adoption: getting started, finding time, sharing learning, contributing safely, and understanding what growth looked like.
Lower the cost of starting
A hands-on, two-day Cursor bootcamp gave designers space to practice prompting, evaluate output, recover from errors, and decide when AI was useful.
Protect experimentation
AI Days provided dedicated time. A GitLab sandbox gave people a safer place to try unfamiliar workflows and learn at their own pace.
Make learning reusable
A weekly sharing thread surfaced successes, failed experiments, prompts, and tools. A prompt library turned individual discoveries into shared team knowledge.
Set a shared direction
Engineering partnership established a path to reviewed contributions. An AI fluency rubric made expectations and growth explicit.

03 · The workflow
Carry design intent closer to implementation.
I partnered with Engineering to give designers a responsible path into coded prototypes and established development workflows, using Cursor, Claude Code, GitHub, and GitLab.
We moved away from static Figma handoffs in this workflow. Designers could test ideas in code, uncover implementation constraints earlier, and contribute through Engineering review.
Engineering review provided technical guardrails while designers brought their judgment about interaction, quality, and the customer experience directly into implementation.

04 · The expectations
Define fluency beyond any single tool.
I developed an AI fluency rubric and embedded it in the Product Design competency and leveling framework. That gave the team a shared language for growth and made AI fluency part of performance calibration.
The expectations covered recognizing where AI adds value, providing useful context, critically evaluating output, protecting quality and security, applying human judgment, and sharing reusable learning.
This made AI an ongoing organizational capability with clear expectations for development.

05 · The impact
Broader contribution.
Stronger shared ownership.
increase in designer code contributions within three months
Alongside that increase, the team showed greater confidence and autonomy, higher-fidelity coded prototypes, earlier implementation learning, and closer collaboration with Engineering.
Designers expanded their contribution from concept through implementation within the broader Product, Engineering, and Design organization.
06 · From capability to delivery
AI-native experiences.
Three weeks, not three months.
to ship AI-native experiences rather than three months
The AI-enabled design processes helped us ship AI-native experiences in three weeks rather than three months. Working directly in code brought design exploration, implementation learning, and Engineering review into a tighter loop.
The AI dashboard and scheduled-task experiences below show what that capability enabled the team to deliver. My role was to build the conditions for faster contribution; delivery was a shared effort across Design, Product, and Engineering.


What I learned
Adoption depends on the conditions you create.
People adopt change at different rates. Durable progress came from combining psychological safety, protected time, practical infrastructure, shared expectations, and cross-functional trust.
AI expanded where designers could create value—and made their judgment even more important.