Company

Honor

Role

Product Design Director

Year

2023

Cultivating Culture

When I joined the team, my priority was trust.

I set up one-on-ones with every teammate, not just to learn their skills, but also to understand the work they enjoy most and how they approach their tasks.


Photo with two past direct reports

Project Story

At the same time, I dove into product demos and asked questions everywhere I could—curiosity became my way into the team’s culture and product.

To maintain a steady pulse, I introduced monthly health surveys that measure happiness, balance, and productivity. The patterns that emerged became our compass, revealing where we were thriving and where structure was lacking.

From there, I turned feedback into action. I publicly tracked leadership initiatives in Jira—everything from evolving design levels and clarifying roles, to refining critique and launching Data+Design share-outs. That visibility built confidence while showing the team what accountability looked like. One of the most impactful changes was the leveling process: clarifying the difference between Principal and Lead Designer finally answered a question that had lingered across the organization.

With clarity in place, I turned to growth. I facilitated “Design Quality Upskilling” sessions, pairing frameworks with active learning so designers could stretch into new skills and raise the quality bar together. As leadership priorities shifted, I also led cross-functional workshops to strengthen remote collaboration and explore new opportunities.

Project Story

At the same time, I dove into product demos and asked questions everywhere I could—curiosity became my way into the team’s culture and product.

To maintain a steady pulse, I introduced monthly health surveys that measure happiness, balance, and productivity. The patterns that emerged became our compass, revealing where we were thriving and where structure was lacking.

From there, I turned feedback into action. I publicly tracked leadership initiatives in Jira—everything from evolving design levels and clarifying roles, to refining critique and launching Data+Design share-outs. That visibility built confidence while showing the team what accountability looked like. One of the most impactful changes was the leveling process: clarifying the difference between Principal and Lead Designer finally answered a question that had lingered across the organization.

With clarity in place, I turned to growth. I facilitated “Design Quality Upskilling” sessions, pairing frameworks with active learning so designers could stretch into new skills and raise the quality bar together. As leadership priorities shifted, I also led cross-functional workshops to strengthen remote collaboration and explore new opportunities.

My Contributions

  • Built trust through 1:1s and curiosity-driven product deep dives

  • Introduced monthly team health surveys to track happiness, balance, and productivity

  • Translated feedback into transparent initiatives (levels, critique, Data+Design share-outs, problem-solving frameworks)

  • Modeled accountability by publicly tracking leadership projects in Jira

  • Clarified design leveling, removing org-wide confusion about roles (Lead vs. Principal)

  • Facilitated “Design Quality Upskilling” sessions with frameworks and active learning

  • Led cross-functional workshops to improve remote collaboration and align with shifting leadership priorities

Team Photo
JTBD Framework
Screenshot of the design file
Screenshot of the design file

My Impact

The result: a healthier, more confident team with clear roles, stronger skills, and a culture of transparency that carried into how we worked across the org.

Project Stats

  • 12+ monthly team health surveys run, capturing trends in happiness, balance, and productivity

  • 5 new initiatives launched from feedback (levels, critique evolution, problem-solving frameworks, Data+Design share-outs, structured rituals)

  • 30% improvement in clarity of roles and responsibilities after leveling framework rollout (placeholder % — swap in with actual if you have it)