Product Design and UX

Turn validated evidence and chosen scope into observable behavior people can complete and recover from. Design the interaction, not the brand, pixels, CSS, component implementation, or a particular tool.

Entry Check

Confirm the approved scope, outcome, users or roles, evidence links, constraints, measurable experience goals, and open product decisions. Record missing inputs rather than inventing them.

• Need stakeholder evidence, validation, or raw research? Use product-discovery.
• Need prioritization, scope, or why a feature is being built? Use product-methodology.
• Need WCAG, ARIA, native semantics, or accessibility testing depth? Use web-accessibility.
• Need an approved interaction contract translated into a software specification and delivery gates? Use spec-driven-development.
• Need to design an AI-assisted, generated, predictive, recommendatory, or tool-using interaction? Read AI interaction and uncertainty and use the AI interaction contract alongside the general contract. Route model evaluation and observability design to agent-evals-and-observability, governance to ai-governance, runtime authority to agent-production-operations, product measurement to product-analytics-and-measurement, accessibility to web-accessibility, and cost/value decisions to ai-operating-economics.
• Need a person to delegate to an agent they use outside the product, then inspect or resume the work across apps? Read external agent interactions and fill the external agent handoff alongside the AI interaction and task-flow contracts. Do not assume the product hosts that agent or can see its private conversation.

Workflow