Hey Glarers(?) (Glarites? Glare Heads? What do we call ourselves?) –
I’ve been talking a bit with @Bryan on my thinking around AI and incorporating into Design Sprints. I have a draft of a proposal around that in a Notion doc that I want to shape into a published essay on my website.
For further context, I was pitching this idea in some form or another at Versapay prior to my departure there but was not able to get it fully up and running, though people were excited about it in theory. So that’s what it is at this point…theory.
Bryan suggested sharing it here. For those interested in this topic and shaping the conversation, I’d love any feedback/input you’d be willing to offer.
Not a designer, but as a builder and software developer (you might even say PM too) needing to lean into design skills and even have AI take some of the lift, this is actually super cool and helpful.
It feels like you could use LLMs to create feedback as well, especially in the early prototyping phases. Of course, with a grain of salt .
Just an FYI, I start to get a bit lost in the walls of text towards the end. Wondering if there are ways to break some of it up (starting at the “What this is” section).
I enjoyed this! When reading through AI related articles, there’s a sort of scan that I do for red flags, and I got all green flags along the way.
The artifacts of the design process are still important.
“This de‑skills design.” It doesn’t. It removes ceremony and puts pressure on judgment. The sprint still relies on taste, systems thinking, and craft to tell good ideas from plausible‑sounding junk.
It’s built for product, design, and go‑to‑market teams who already have a good sense of the problem space
The framing of the purpose and which teams can benefit is important here. Love that.
Some thoughts to develop:
Would like to see the AI stack articulated further, perhaps leading with a bullet-list of tools with brief descriptions, then discuss how they’re leveraged.
Figma / FigJam both have AI integrations, but unsure if that is assumed to be referenced here.
There’s an angle toward prototyping using UX Pilot, Magic Patterns, or similar “Prompt to code” tools that would potentially skip ‘design’ in Figma. Would you recommend for or against that?
.
The artifacts of the design process are still important.