Part 4: What This Transition Taught Me
Vibe coding isn’t a magic bullet for design teams. Lessons on governance, accountability, product strategy and documentation from a remote design team.

Part 3: What We Can Actually Claim Right Now
Measuring the ROI of a design team vibe coding is harder than it sounds. Here’s where we are on metrics, baselines and the design to engineering handover.

Part 1: How we started
How we started: a CTO vision, a business case full of open questions, and what we learned setting up our first repo.

Part 1: How we started
How we started: a CTO vision, a business case full of open questions, and what we learned setting up our first repo.

People often believe that building influence happens overnight, but it actually results from a series of cumulative moments. To do this strategically, one must be intentional in approach, starting with identifying key stakeholders and understanding their impact on design decisions and their familiarity with design. A stakeholder map can help categorize them based on design friendliness and influence, with different tactics for each quadrant. Focus on building relationships with those who understand design and have worked with you before, using case studies to influence others. For less familiar stakeholders, prioritize education about design and how you can support their challenges. When engaging stakeholders, understand their challenges and communication preferences to develop tailored strategies. Communicating broadly through channels like Slack, Teams, newsletters, and workshops can also amplify influence. Keep track of moments when your work makes a difference, both for team reflection and reporting to leadership, aligning your efforts with company goals.