There's a lot of noise about AI replacing designers. In practice, that's not what happens on real product work. What Claude changes is the speed at which I can think through a problem — not whether the thinking has to happen.
Where it fits
I use Claude at the messy parts of the process, where the value is in exploring options quickly and pressure-testing my own assumptions:
- Exploring product structure and edge cases before I commit to a direction
- Drafting user flows, states and logic so I can react to something concrete
- Writing first-pass product specs and acceptance criteria
- Interrogating a design: ‘what breaks here?’, ‘what did I miss?’
Where it doesn't
AI doesn't talk to your customers, own the trade-offs, or carry the responsibility for shipping something that works. The judgement — what matters, what to cut, what's actually true for these users — is still the job.
Claude accelerates the work. It doesn't replace the thinking.
Used well, it means I get to a buildable, well-considered product direction faster — which is exactly what a fast-moving SaaS team needs.
← Back to all posts.webp)
