Joshua Rudd

Most designers say they want impact. What they really want is proof. At scale, I had to formalize proof. I once built a quarterly UX strategy using Jared Spool's Persuasive Metrics to connect design decisions to revenue. A 2% reduction in onboarding friction translated into six figures in retained revenue. That was the language the room spoke. Dashboards. Quarterly reviews. Attribution models. Impact had to be quantified before it was believed. Now I’m at a tiny startup. Last week, a customer Slacked: “Magemetrics saves me days on campaign reports.” Following the rebrand, a prospect opened the site and said: “Okay. This feels serious.” These calls felt different: less explaining, fewer objections, more trust. No attribution model. No presentation. Just behavior changing in real time. Here’s what’s different: In enterprise, proof arrives as numbers. In startups, proof shows up as decisions. Enterprise feedback arrives filtered and quarterly; startup impact is immediate. Doubt slows deals. Confidence speeds them up. Immediacy forces clarity. You take fewer performative bets. You stop optimizing for presentations. You design to remove doubt. Because you’re not defending slides — you’re shaping what happens next.

12

12 Comments

Forrester reports that companies investing in design-driven innovation see a 228% ROI. As someone who advocates for design to have a seat at the table, I love this stat! But companies evolve… and so should design. It’s no longer *just* about securing a seat; it’s about questioning if you want a seat at *that* table. Maybe it’s about building a new one. One that welcomes the voices too often left out. ❤️

18

1 Comment

Are IC enterprise designers unintentionally sabotaging their portfolios in this AI-obsessed market? If you’re a Product Designer updating your case studies… you’ll probably want to read this... I’m actively hiring two Sr-to-Lead Product Designers, and after reviewing a lot of portfolios recently, a pattern keeps repeating: 👉 Too many portfolios are leading with AI chatbot projects. Not sprinkled in… leading with them. Often multiple ones in the same portfolio as Case Study #1 and #2. Here’s the problem👇 AI chatbots are important, but they’re not the center of gravity for most enterprise / SaaS product teams. In the last six-nine months, many of these patterns are already shipped and commoditized. And now with agentic flows, the UI work becomes more about reviewing, validating, and confirming work AI has already completed behind the scenes. Which means… “Old school” multi-step, end-to-end product flows are still valid – with a twist. Because every IC job post right now is calling for “high craft” or “consumer-grade design” – it’s no longer acceptable for flows to simply “get the job done.” Hiring panels want to see refinement and polish in the final output.  Otherwise you’ll get the feedback we give far too often: “The design thinking is great… but the visual design is just… [sigh/meh]… not quite there.” Visual craft always matters. Everywhere. At every company. Whether D2C or B2B or Enterprise. So if you’re refreshing your portfolio, here’s my ask as someone hiring in this tough market: Don’t over-index on AI chatbots just because they’re hot right now. Show me your complex, nuanced, multi-stage flows—the kind that prove you can handle the real product work most teams need. Just make sure they’re polished (ie. That “high craft” buzzword again), intentional, and tight. Because that’s what will actually differentiate you in 2025 and into 2026. And now the proverbial 🔌: If you’re a high-performing Sr. or Lead looking to innovate in the HR and Comp tech space, holler at me in my DMs or Comments. Thanks! 🙏

36

3 Comments

Terminal Fluency: As AI becomes more central to Designer workflows, I’ve been seeing more questions about whether the terminal is still worth learning. I think it is, terminal is core skill that compounds and unlocks next-level control over agents. Make terminal your second brain with this tmux + vim cheatsheet (or just get started) and keep your hands on the keyboard. https://lnkd.in/eV5bAFhF

34

1 Comment

A lot of conversations I have with design teams start the same way: “We’re moving fast… but we keep circling back.” It’s rarely a skill issue. It’s a timing issue. Most misalignment doesn’t come from bad design. It comes from discovering truth too late—after engineering starts, after a sprint closes, or after launch. And the cost of that delay is enormous. A late fix can be 100× more expensive than catching the issue early. But the teams that validate upfront—concepts, prototypes, even simple assumptions—consistently move faster, not slower. I’ve seen: • 25% fewer iteration cycles • Clearer rationale behind decisions • Less friction between design, product, and engineering Early insight isn’t a tax on velocity. It’s the engine of velocity. When we test earlier, we spend less time reworking and more time progressing. And our teams feel it—not just in timelines, but in confidence and morale. These themes are showing up across the teams featured in our newest Leadership Signal. It’s a great pulse check on how leaders are tightening alignment earlier in the process. https://bit.ly/4ixuGp2

26

3 Comments

I used to talk about the design-to-engineering handoff like it was a necessary evil—something to smooth out, automate, or make more collaborative. But product development has never really worked that way. It isn’t linear. It’s not a handoff. It’s a conversation—messy, layered, and collaborative. As designers, our job is to move through ambiguity toward clarity. We shape questions, structure choices, and test the logic of an experience before anyone writes code. Our work anticipates behavior, scale, and feel. Engineers don’t just implement that thinking. They build on it, pressure-test it, and often propose better paths forward. The strongest teams work like a dialogue. That’s why tools like Lovable are interesting—not because they replace this process, but because they let us enter it differently. Lovable lets us describe a product idea in plain language and get back a working front-end built in React, Tailwind, and Supabase. It’s not perfect or production-ready, but it behaves like software. It’s real enough to test, critique, and build on. Instead of waiting on mocks or sprint availability, we can align quickly on an idea and generate something functional the same day—grounded in user needs, and built before momentum fades. At PrescriberPoint, we’re exploring whether this could help us get prototypes in front of users weeks earlier than usual—and because the output is built with components, it may also reduce friction when we bring engineering in. Tools like Lovable don’t remove design from the starting line. They let design start earlier—with less friction and more clarity. Momentum doesn’t have to wait for mocks or specs anymore. It can begin with a prompt and a pattern, grounded in insight and built for feedback. Speed is neutral. What makes it meaningful is context. When we stay close to the problem, and apply judgment rooted in evidence, tools like Lovable help us act while the insight is still fresh. What's tricky is that Lovable doesn’t enforce your design system out of the box. It won’t respect tokens or guardrails unless you give it structure—through prompts, through knowledge files, through clean Figma components. But it’s getting closer. And the pressure will only increase to bridge those gaps. Eventually, generative apps like Lovable won’t just produce prototypes—they’ll produce system-aligned starting points that teams can carry forward without backtracking. That’s going to change the role of the design system itself. It won’t be a source of documentation; it’ll be the logic layer behind how ideas take form. This isn’t automation. It’s a shift in leverage. We're giving shape to what used to stall in ambiguity—and building momentum where it used to fade. The designers who do this well aren’t just working faster. They’re helping everyone else understand more clearly. And that clarity—when it’s grounded in customer mental models—is what moves the whole product, and business forward.

2

The design-to-code handoff is one of the most expensive gaps in enterprise software development. Weeks of engineering time spent interpreting Figma files, reconciling spacing math, and rebuilding what designers already specified. On March 30, join Aditya Karra, Blitzy's Founding Designer, and Ben Bergerson, Senior AI Solutions Consultant, for a walk thru of Blitzy native Figma-to-production capability. No prototypes. No Refine PR. Production-ready code. - Every design token read before a single line of code is written - Responsive output across five viewports from one desktop frame - A new feature integrated into an existing codebase, brand-aligned, checked directly into the repo Designers and product teams can now move at the speed of design. Come see what that looks like in practice. Register with the link in the comments. March 30 | 12pm ET | Free with live Q&A #Blitzy #Webinar #Figma #Platform40 #FrontendDevelopment #EnterpriseAI #ProductVelocity

29

1 Comment