eng-user-impact

# User Impact and Product Sense ## Intent - Translate technical work into clear user outcomes (fun, trust, productivity, revenue). - Ensure flows are accessible, consistent, and measurable across mobile, web, and decentralized surfaces. ## Workflow 1. **Clarify the user story** - Write the scenario in plain language (persona, goal, success metric). - Note must-haves vs delights; align with PM/design if ambiguous. 2. **Define acceptance signals** - Specify behavioral analytics, A/B guardrails, or smart-contract events to prove impact. - Include accessibility requirements (screen readers, haptics, color contrast, controller support). 3. **Prototype + validate early** - Use lightweight demos, storybooks, simulators, or testnets to gather feedback quickly. 4. **Instrument thoughtfully** - Add analytics hooks or telemetry to measure adoption without leaking sensitive data. 5. **Close the loop** - Plan post-launch follow-up: metrics to review, user feedback channels, rollback criteria. ## Verification - Acceptance criteria mapped to concrete tests or demo steps. - Accessibility checks (linting, WCAG tools, platform inspectors) run for affected surfaces. - Analytics/telemetry schemas reviewed with stakeholders; events verified in staging/testnet before release.