# Eng User Impact

> Anchor every engineering decision in user value, measurable outcomes, accessibility, and cross-platform experience coherence.

- Skill: `tjboudreaux/eng-user-impact` (Agent Skill)
- Install (CLI): `npx skillmds@latest add tjboudreaux/eng-user-impact`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tjboudreaux/eng-user-impact/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: tjboudreaux (https://skillmd.com/u/tjboudreaux)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tjboudreaux/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.