# Principles, Designing for AI

**URL:** <https://forum.zurb.com/t/principles-designing-for-ai/484>\
**Category:** Using AI\
**Tags:** ai-design, ai\
**Created:** [January 6, 2026, 12:36am UTC](https://forum.zurb.com/t/principles-designing-for-ai/484 "2026-01-06T00:36:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![EricZ](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/ericz/32/692_2.png) [@EricZ](https://forum.zurb.com/u/EricZ)\
**Post date:** [January 6, 2026, 12:36am UTC](https://forum.zurb.com/t/principles-designing-for-ai/484/1 "2026-01-06T00:36:47Z")

</div>

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

> **[AI Product Adoption: Clarity is Key to Traction | Veruska Oropeza posted on...](https://www.linkedin.com/posts/veruskaoropeza_ai-product-lessons-part-1-clarity-drives-activity-7406421164027396097-eZJR?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAZ798sBhOE5LowzM94jsZPEykWeuja_aK0)**
>
> After years as the sole designer at an AI startup, I learned that building a powerful AI product is only half the battle.
> 
> Getting people to actually use it is a different challenge altogether.
> 
> I’m sharing some lessons from taking an AI product from...

Some great reasoning in here.

---

<div class="post-metadata">

**Author:** ![EricZ](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/ericz/32/692_2.png) [@EricZ](https://forum.zurb.com/u/EricZ)\
**Post date:** [January 6, 2026, 12:37am UTC](https://forum.zurb.com/t/principles-designing-for-ai/484/2 "2026-01-06T00:37:27Z")

</div>

Round 2 is good as well, especially Principle 4:

> The UI should not  
> reflect backend  
> constraints

> **[Lessons from designing AI product UX, Part 2 | Veruska Oropeza posted on the...](https://www.linkedin.com/posts/veruskaoropeza_designing-ai-products-part-2-ugcPost-7412211830707851265-h0Fa?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAZ798sBhOE5LowzM94jsZPEykWeuja_aK0)**
>
> Lessons from being the sole designer at an AI startup -\> Part two ✌🏽 
> 
> Good UX hides system complexity and meets users where they are.
> One of the biggest lessons I learned designing an AI product from 0 to 1 is how easily backend logic can leak...

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?

---

<div class="post-metadata">

**Author:** ![ben](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/ben/32/442_2.png) [@ben](https://forum.zurb.com/u/ben)\
**Post date:** [January 6, 2026, 1:58am UTC](https://forum.zurb.com/t/principles-designing-for-ai/484/3 "2026-01-06T01:58:50Z")

</div>

Very awesome share @EricZ. Clarity and making decisions hits home for me when trying to build out great experiences.

---

<div class="post-metadata">

**Author:** ![Bryan](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/bryan/32/448_2.png) [@Bryan](https://forum.zurb.com/u/Bryan)\
**Post date:** [January 6, 2026, 3:45pm UTC](https://forum.zurb.com/t/principles-designing-for-ai/484/4 "2026-01-06T15:45:38Z")

</div>

> [@EricZ](#):
>
> The UI should not  
> reflect backend  
> constraints

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.