I argued in their vocabulary (statute, precedent and exposure) rather than in design vocabulary, and I wrote it all down so it could outlive me.
The system came with an enterprise reference guide. For each of the eight patterns it gives:
- The requirement and its legal basis
- Documented in-product examples from other Fortune 500 companies
- The risk of leaving it out
The guide is why a designer with no authority over Legal got a first-pass approval from outside counsel: it did not ask them to trust a design; it showed them the law the design came from. It shipped with the spec pages engineering needed: the 2×4 grid as a one-pager, the consent-modal and card anatomies, and the first-run flow (sign-in, terms, AI consent) for desktop and mobile.
Adoption followed the same logic:
- Engineering got one component and a set of settings.
- Product got a decision rule instead of a meeting.
- Designers across the department got a guide they could apply without me.
I was told afterward that counsel was shocked at the level of detail, comprehensiveness and thoroughness in the system, and that it was clear to her that I cared. That meant a great deal, because the care was for the user.
The same principle (AI proposes, the user decides) runs through the Insights & Recommendations cards that shipped in Ecolab3D. Each card carries what the agent observed, its source, the problem, the impact level (low, medium, high or safety), the justification and a recommended action. The user reviews, approves, defers, edits, comments or tags someone, and the decision is recorded as the card moves through new, reviewed, approved and deferred states. Deferral carries no penalty, because a user on a site cannot always act right now. That card anatomy is the subject of Case Study 4.