Great set of principles from Veruska Oropeza on designing for AI. What struck me is how familiar these principles seem, especially Principle 3:
Time-to-Value beats Feature Depth
Some great reasoning in here.
1 Like
Round 2 is good as well, especially Principle 4:
The UI should not
reflect backend
constraints
Despite the different context, balancing how to provide more value by understanding user goals and desired outcomes with the complexity of the backend remains mostly same.
Or does it? Curious if there’s any pushback on this one?
Very awesome share @EricZ. Clarity and making decisions hits home for me when trying to build out great experiences.
This reminds me of early web work, where a lot of designers tripped up.
I get the point. The technology should not dictate the experience. But understanding the constraints, and how the system actually works, is what lets you design something clear and reliable. Working within real limits is often what makes an experience strong.
I think trust comes from cognitive honesty (still taking notes from @schuboxaz). Be clear about what the system does, what the user does, and where things can break.
1 Like