Hans Sprecher

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

I was at Config San Francisco last week and got to witness firsthand how Figma and its passionate community have evolved. Check out this post on what I saw and what it signals—AI starting to find its place in real workflows, and designers increasingly playing a role as system architects while the gap between design and development continues to narrow.

23

The best UX teams don’t stop at launch. They ask questions. Test assumptions. Look again. In this clip from the Bold Moves podcast with Angela Merzib 🥊 , we talk about why constant learning isn’t a nice-to-have, it’s the work. What’s one thing your team learned after shipping? #UXDesign #ProductLeadership #HumanCenteredDesign #UserResearch #BetterByDesign

6

2 Comments

She's right that the old design process is dead, but I think she's underselling how fast it happened. Jenny says her September talk already feels outdated. That tracks. The gap between idea and shipped code is measured in minutes now, not sprints, and the tooling is only accelerating. The part about "seven agents constantly running" hits close to home. That's the workflow and when you're moving that fast, the bottleneck isn't design or engineering anymore. It's deciding what actually matters. Taste/signal is key. Jenny nails it: someone still has to be accountable for the decision. The three hiring archetypes are worth paying attention to. Especially the "craft new grad" one. People without baked-in process assumptions are adapting faster than senior folks who spent 10 years learning a workflow that just got obsoleted. Blank slate is an actual advantage right now. One thing I'd push back on: she says Claude isn't hireable as a designer yet. That's true if you're comparing to her deep specialist archetype. But for the execution layer she described, pairing with an engineer and polishing the last mile, it's closer than people think and if you're a designer/engineer its already here.

4

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

SDK documentation is not supplementary material... it is a vital component of the SDK itself. It lets developers harness the SDK's potential by serving as a highly sophisticated technical bridge. However, the tone must be instructional, and the approach must be simple. Here is a quick explainer video on the need for SDK documentation and its essential components.

19

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

31

3 Comments

I’ve been writing a series of posts on the design principles behind Looping, a product I’m building to help teams run and evolve software over time. These principles shape the architecture underneath and have helped me prioritize clarity, composability, and long-term maintainability from the start. The latest post in the series is about Composable Services. In Looping, every service follows the same interface: it takes a hash of input and returns either Success() or Failure(). That consistency makes services easy to test, reuse, and chain together without resorting to sprawling conditionals or unpredictable side effects. The post walks through the structure, shows real examples, and touches on how it tracks source chains for observability and event logging. https://lnkd.in/ePkn-pF6 #ruby #rails #softwarearchitecture #buildinpublic

7

2 Comments