Biweekly strategies for product designers ready to move from execution to influence. Learn frameworks for stakeholder management, getting ideas approved, and advancing to senior roles.
|
Hey Reader, A designer I mentored in September wrote back a month later with a list of seven changes she’d made. Her title was the same and nobody had promoted her. She’d simply stopped waiting for permission to lead the team she already led. This issue walks through what she did, plus a few links on keeping design in the loop as AI writes more of the product, and four open roles worth a look. In today's email:
Design gems of the week
Open design roles:
You don't need a promotion to be a leaderIn September I had a 1:1 with Georgia, a lead product designer at a startup. On paper she led the design and research team. In practice, her head of product was assigning work straight to her designers, and she'd find out after the fact. She knew she should step in, but stepping in felt like overstepping. About a month later I checked in. She'd decided to "stop tiptoeing around" and lead the team, and had implemented seven changes in four weeks. None of it came with a promotion or a new title. She started acting on the parts of the job that were already hers. The changes fell into three groups. She got upstream of the work.The hardest part came first: asking her head of product to route all new work through her. What impressed me most was how she framed it as a solution to his problem of too much back-and-forth with individual designers and slow answers on scope and capacity. He agreed. Then she started reshaping what came through. One brief that arrived was 15 pages long, packed with every data point available. She cut it to four, moved the evidence into separate tabs so her designer could dip in when needed, and reframed his proposed solutions as hypotheses to test, which gave her designer far more room to do the actual design work. She also built an estimation matrix anyone in the company can check before submitting a request, so conversations about the roadmap start with a realistic sense of the team's time. She made capacity visible.A team-only capacity tracker shows her the workload at a glance. Her designers can update it when a project grows and use it to push back on trade-offs themselves. Company processes were still being worked out, so she set up a team board as a single source of truth in the meantime, with ad-hoc requests flowing into it from Slack. She got in the room.She asked to be invited to roadmap calls, so she hears about changes before they land on her team and can set capacity expectations with leadership early. She also started design drop-ins every two weeks, where anyone in the company can see rough work and weigh in, and added project critiques to the go-to-market process. Still to come.The piece she's still working on is sign-off, specifically when a decision actually needs to go to the CEO. My suggestion was to sort decisions by how reversible they are and how far their impact reaches, rather than by project size. A copy tweak in onboarding and a brand change can take the same amount of work and still need very different approval. If the CEO agrees to those criteria once, she can stop negotiating sign-off project by project. Georgia managed to do all of this in four weeks. On my coaching calls, the harder conversations come next.
Most of what Georgia did needed no one's approval. Where she did need buy-in, like routing work through her or joining roadmap calls, she asked for it directly. If you picked one of these to start next week, which would it be? Hit reply and tell me.
Have a topic you'd like me to write about? Reply to this email and let me know! I read every reply. |
Biweekly strategies for product designers ready to move from execution to influence. Learn frameworks for stakeholder management, getting ideas approved, and advancing to senior roles.