Barbara (Basia) Perkowski, UXC

Such a well written and thoughtfully articulated perspective on why the product design industry is shifting. Supporting new generations is how we nurture exceptional designers for the future. If expectations are misplaced too highly on delivery without room for growing people, the growth pipeline slows. The same applies to emerging leaders when they have less opportunity to develop key skills gained through mentoring junior designers.

7

Wondering how to get your company to let designers start writing code? I have been talking to designers about how empowering it is to deliver designs as final code, and one theme I keep hearing is, “I love this idea, but I don't think my company would let me try it.” Here is a proven playbook to make it possible: 1. Start with low-risk UI fixes Think spacing issues, color swaps, and font tweaks. These are simple, non-functional changes that improve the experience, but are work engineers usually don’t want to spend their time on. It should feel like you’re taking something off their plate without adding risk. 2. Commit to no “vibe coding” Don’t let AI run free in the codebase. Every change should be deliberate, something you understand, and something you update yourself. Use AI to understand and suggest code, but make the updates manually. 3. Follow engineering’s process and standards Use the same workflows as engineers: create tickets, open branches, submit pull requests, go through code review, run tests, and follow QA. Show that you’re holding yourself to the same quality bar. If you go through code review, they have no reason to be worried about code quality. 4. Ask for the same permissions given to engineering interns If IT or Security is hesitant, explain you only need the same access given to engineering interns. If they trust 20-year-old interns with that access, they can trust designers with years of experience. 5. Build trust slowly Start with small fixes. If something looks too complex, leave it. Prove that design contributions are safe and valuable. Once engineers see your updates are reliable, they’ll invite you to do more. The payoff: Handoffs disappear. Design QA goes away. The gap between design and code closes. Designers polish the experience in the final medium. Engineers focus on deeper problems. Everyone wins. This shift is not hypothetical. I’ve trained my own team and others to do it with AI, and the results have been huge. 👉 Full write-up here if you want more detail: https://lnkd.in/evtuBZHR

15

“Bad UX in healthcare doesn’t just frustrate users — it can delay treatments, confuse patients, and increase risk for providers. Good design isn’t just about aesthetics. In MedTech, it’s about saving time, building trust, and in some cases saving lives." At Create Ape, we design digital solutions that empower patients and support clinicians. Because healthcare deserves better design. This is just the beginning. See the full story on our blog — live now. Perfect timing for your Friday scroll: https://lnkd.in/g8XhEP9Q

13

Enterprise tech has a design problem. Too often, design is treated as “look and feel” — a coat of paint added at the end. But this mindset is cumbersome -- and costly. Poorly designed systems overwhelm employees, slow adoption, and in high-stakes industries can carry huge consequences. Design isn’t optional. It’s a strategy. It’s systems thinking. It’s the force that makes technology actually work for people. Look at Slack, Salesforce, ServiceNow, and Figma. Each transformed not just tools, but the way people connect, collaborate, and create. That shift didn’t come from technology alone — it came from design. Where design takes the lead, transformation inevitably follows — that’s the future of enterprise. Read more here: https://lnkd.in/gdbN5v5T #enterprisedesign #UXstrategy #humancentereddesign #designleadership #AItransformation

27

3 Comments