attenzione please


should product managers prototype with ai in a design tool or on the real codebase?

note 004 · published · tags: , , ,

on the codebase, with the actual components. ai design tools make up a lot of stuff. on the repo the prototype is way more accurate, and for a first pass they don't need it perfect.

the real question is the team, not the tool

ai design tools exist so product people can design things, and maybe push things, without even needing design. so the question for a team is simple. do they want pms designing things? do they want pms pushing things? if yes, the tool follows.

what the workflow looks like

the pm does the first pass. it's more of a wireframe, but made directly with the actual components, pulled from the component library. they share it and the designer iterates from there.

it works best for small changes. a client already had our designs and wanted to test new little things and move forward without needing us so much. normal ui changes are doable. a full screen works too, but it will make up small things and it won't be perfect. they wouldn't need it perfect, right?

if they won't touch the codebase

not every team is comfortable working on the repo. the alternative is a plugin that lets the ai use the codebase from inside a chat app. it won't always be 100% right, because it doesn't have the entire codebase, but it will be like 80% there. still way better than a design tool guessing.

markdown: https://attenzioneplease.com/notes/should-pms-prototype-with-ai-in-a-design-tool-or-on-the-codebase.md
short link: https://attenzioneplease.com/4
cite as: attenzione please, note 004, "should product managers prototype with ai in a design tool or on the real codebase?", 2026-11-18, https://attenzioneplease.com/notes/should-pms-prototype-with-ai-in-a-design-tool-or-on-the-codebase