Frank Chen

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

In roles like Product Design Director or VP of Design, there are moments when you get to shape the end-to-end process exactly as you believe it should be. Stressful at times, exciting at others, but often deeply fulfilling. Then there are moments where doing that feels like pushing inertia uphill. You can operate, but strictly within guardrails. The stress is still there, with the added layer of frustration. Recent conversations with peers reminded me of something I’ve seen many times before. These constrained moments are often the ones that force us to understand the bigger human and professional picture. Here’s what I mean. Very often, the solution to a problem feels obvious to us. A UX improvement, tech debt that needs addressing, less over-explaining to unlock execution. And yet, the proposal stalls. It gets pushed back, challenged, or quietly deprioritized. Our first assumption is usually that senior leadership understood the proposal and chose to ignore it. In my experience, that’s not always true. I’ve worked with brilliant leaders who knew how to maximize revenue, optimize adoption, and integrate complex technology. But many of them had simply never been exposed to Product Design and strategy the way we practice it. They never had to redesign a feature, remove a harmful pattern, rethink an end-to-end experience, or consider long-term brand perception as a daily responsibility. Dropping a bag of issues on their desk and expecting clarity rarely works. It adds cognitive load. Most are not dismissing the solution. They are experts in different problems. I’m still learning that translating, framing, and pacing our thinking for different professional minds is often the real lever. That’s a pattern I keep seeing. If this sounds familiar, I’d be curious to hear how others are navigating it. Happy to exchange experiences. (Note 02: Bridging the gap)

45

Claude’s new “Skills” could change how design teams use AI. Every designer knows the grind. You open AI. You paste the same wall of text. Brand tone. Design rules. File names. Review process. You do it every time. That’s the context tax. Claude just killed it with Skills. Think of them as mini brains. Each one remembers a part of your world. Your brand voice. Your UX principles. Your accessibility checks. Your Figma rules. You teach it once. It remembers forever. And the best part? Skills stack. One for tone. One for motion. One for layout. Claude pulls them together when needed. No more messy prompts. No more “oh, I forgot to mention” moments. Just consistent, on-brand output every time. This could change how design teams use AI. From creative briefs to brand QA. It’s not RAG. It’s not fine-tuning. It’s on-demand design memory.

24

2 Comments