enterprise-ux-process
Operationalize Synechron's enterprise UX process for premium-priced enterprise engagements (financial services, insurance, regulated industries, large internal apps, B2B SaaS). Produces maturity-level declaration + activity evidence pack + heuristic evaluation + 5-outcomes pre-launch declaration. Cite when scoping, executing, or auditing premium enterprise UX work.
Best use case
enterprise-ux-process is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Operationalize Synechron's enterprise UX process for premium-priced enterprise engagements (financial services, insurance, regulated industries, large internal apps, B2B SaaS). Produces maturity-level declaration + activity evidence pack + heuristic evaluation + 5-outcomes pre-launch declaration. Cite when scoping, executing, or auditing premium enterprise UX work.
Teams using enterprise-ux-process should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/enterprise-ux-process/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How enterprise-ux-process Compares
| Feature / Agent | enterprise-ux-process | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Operationalize Synechron's enterprise UX process for premium-priced enterprise engagements (financial services, insurance, regulated industries, large internal apps, B2B SaaS). Produces maturity-level declaration + activity evidence pack + heuristic evaluation + 5-outcomes pre-launch declaration. Cite when scoping, executing, or auditing premium enterprise UX work.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Enterprise UX Process Skill **Source:** Operationalizes `book-extractions/enterprise-ux-financial-insurance-extraction.md` (Synechron, 2018; derived from The Design Ladder + Natalie Hanson's UX Maturity Model). --- ## Use when - Scoping or executing a premium-priced enterprise UX engagement (financial services, insurance, healthcare, regulated industries, large internal apps, B2B SaaS) - Auditing whether an enterprise project is positioned correctly on the maturity scale - Defending a premium-pricing claim against an internal or external review - Bridging strategy (Levy) and tactical UX work (Branson, Deacon, Fekeshazi) into a single enterprise-grade process ## Do not use when - The work is consumer-grade (single-interaction, low-stakes) — use simpler skills - The artifact is a prototype or experiment, not a production deliverable - The project is explicitly priced as standard tier and the team has agreed not to pursue premium positioning ## Required inputs Before invoking this skill, the following must be available or generated: - Problem definition statement (what is the need; why now; for whom) - Stakeholder list with roles (funder, owner, executor) - Business objective (what success means in measurable terms) - Success criteria (signed off by stakeholders) - Target maturity level: **3 (UX Design)** for standard premium, **4 (Experience Design)** for top-tier ## Workflow — 9 phases The process maps directly to Synechron's Activity-by-Level matrix. All 9 phases must produce documented evidence at Level 3+; the additional Level 4 activities are noted inline. ### Phase 1 — Problem Definition + Business Objective - UX team meets with business stakeholders and product owners - Answer: What is the need? Why now? For whom? How does this make life easier for the end user? - Document vision, hopes, aspirations, and fears from the business perspective - Output: signed problem-definition document ### Phase 2 — Stakeholder Discussions / Interviews - Identify funders, owners, executors - Conduct focused-group discussions OR individual interviews - Capture: roles, expectations from UX, problem perception, end-user identification, collective goals, organizational/competitive/scope context - Output: stakeholder-interview transcripts + summary brief ### Phase 3 — Success Criteria sign-off - Checklist of measures the deliverable must hit to be successful - Documented and agreed by all stakeholders - Treat as non-negotiable acceptance criteria - Output: signed success-criteria document ### Phase 4 — User Research (qualitative + quantitative) - Methodologies: interviews, contextual inquiries, eye tracking, surveys, A/B testing, web analytics, field studies - Quantitative: how many, what % - Qualitative: why behaviors occur, what users notice - Output: user-research report with both data types ### Phase 5 — Competitor Analysis - Use Levy's 19-column competitive matrix (cite `book-extractions/levy-ux-strategy-extraction.md` Part VII or, in `website-skills`, `skills/design-reference/references/levy-competitive-matrix.md`) - Minimum: 5 direct + 3 indirect competitors - Output: filled matrix + 1-page distilled brief ### Phase 6 — Personas + User Journeys + Information Architecture - Personas: apply Branson's discipline (Essential Persona declared, Mechanics floor — name, demographics, goals, environment, pain points, stress points) - User Journeys: chronological touch-point sequence per primary persona - Information Architecture: organization, structure, labelling of all content; navigation strategy/flow; site map; content buckets; intuitive labels - **Level 4 also requires:** Experience Maps - Output: persona deck + journey deck + IA deck ### Phase 7 — Wireframes + Clickable Prototype + Visual Design Mockups - Wireframes: low-fidelity (paper) + high-fidelity (no color, focus on flow) - Clickable prototype: stitched screens behaving like the real product per crucial user scenarios - Visual design mockups: full-scale static representation with colors, branding, graphics - **Level 4 also requires:** Mood Boards - Output: wireframe pack + interactive prototype + mockup set ### Phase 8 — Heuristic Evaluation - UX expert reviews against Nielsen-style heuristics: 1. Visibility of System Status 2. Match Between System and the Real World 3. User Control and Freedom 4. Consistency and Standards 5. Error Prevention & Error Handling 6. Recognizing Rather than Recall 7. Flexibility and Efficiency of Use 8. Aesthetic and Minimal Design 9. Help and Documentation - Plus Branson's 4-stage cognitive affordance audit per primary CTA (Presence → Visibility → Recognizability → Intelligibility) - Output: heuristic evaluation report listing flaws + improvements ### Phase 9 — Usability Testing + ADA / Section 508 verification (Level 4 + all-levels accessibility) - Usability testing: moderated in-person, moderated remote, OR unmoderated remote - Test scenarios derived from actual use cases and task flows - ADA / Section 508 / WCAG 2.1 AA verification — required at ALL maturity levels - Output: usability test report + accessibility audit ## Outputs A complete enterprise-ux-process engagement produces: 1. **Maturity-level declaration** — single sentence at the top of the engagement summary: "This engagement operates at UX Maturity Level [3 / 4], per Synechron's 5-level model." 2. **Activity-by-level evidence pack** — see `references/maturity-checklist.md` for the matrix and required evidence per activity 3. **Heuristic evaluation report** — Phase 8 output 4. **Five-outcomes pre-launch declaration** — Yes/No with evidence per outcome: - Useful (persona-validated) - Easy to use (first-task success without coaching) - Efficient (task time benchmarked) - Pleasing (≥ 4/5 first-impression rating) - Accessible (ADA/Section 508/WCAG 2.1 AA) - **Rule:** 4-of-5 disqualifies premium pricing. One No = no launch. ## Cross-references ### Canonical extraction (source-of-truth) - `book-extractions/enterprise-ux-financial-insurance-extraction.md` ### Related skills in this engine - `book-extractions/levy-ux-strategy-extraction.md` — strategy framing (Four Tenets) that should sit upstream of this process - `book-extractions/branson-ux-ui-design-extraction.md` — persona discipline + working memory + 4-stage affordance applied within phases 6 and 8 - `book-extractions/deacon-ux-ui-strategy-extraction.md` — 3 levels of UX scope; declare in Phase 1 - `book-extractions/fekeshazi-pm-ux-guide-extraction.md` — PM collaboration rules and the "design is ongoing" stance ### Operational skills in other engines - `website-skills/skills/design-quality-score/` — Category 8 (UX Maturity) scores the same artifacts independently - `website-skills/skills/premium-ui-ux-design/references/enterprise-five-outcomes.md` — same 5-outcomes gate applied to website templates - `srs-skills/01-strategic-vision/07-premium-software-product-execution/` — premium-positioning gate using the same 5+5 model - `srs-skills/03-design-documentation/05-ux-specification/` — UX spec produced under this process ### Quick-use checklist - `references/maturity-checklist.md` — standalone activity-by-level checklist for use in project workspaces
Related Skills
saas-sso-scim-enterprise-auth
Use when implementing enterprise auth on a multi-tenant SaaS — SAML 2.0 and OIDC SSO with per-tenant IdP configuration, SCIM 2.0 user provisioning/deprovisioning, custom-domain support with automated TLS, IP allowlists per tenant, audit-log API, and the migration from email-password tenants to IdP-enforced tenants. The price of entry for enterprise SaaS.
gis-enterprise-domain
Use when administering ArcGIS Enterprise or building real-estate-specific GIS features — ArcGIS components, publishing services, security/roles, backup/DR, plus property search, neighbourhood analysis, catchment/isochrones, market heatmaps, and real-estate-SaaS integration.
web-app-security-audit
Use when auditing a PHP/JavaScript/HTML web application for security vulnerabilities. Covers configuration, authentication, authorization, input validation, XSS, API security, HTTP headers, and dependency scanning. Produces a severity-rated audit...
vibe-security-skill
Use when designing or reviewing security for a web application, API, or multi-tenant SaaS — produces threat model, abuse case list, auth/authz matrix, and secret handling plan; covers OWASP Top 10 2025 and the AI-code-generation blind spots. Neighbours — api-design-first owns auth model fields, deployment-release-engineering owns secret rotation choreography, ai-security and llm-security own model-specific threats.
network-security
Use when designing, hardening, or auditing network-layer security for self-managed Debian/Ubuntu SaaS infrastructure — firewalls (nftables/UFW), WAF (ModSecurity + OWASP CRS), VPN (WireGuard, OpenVPN, IPsec), TLS/PKI ops, IDS/IPS (Suricata, Fail2ban), zero-trust, SSH hardening, DDoS mitigation, DNS security. Complements web-app-security-audit (app layer) and cicd-devsecops (secrets/CI).
linux-security-hardening
Use when hardening a Debian/Ubuntu server — user/group/sudo hardening, file permission audits, PAM password policy + MFA, AppArmor mandatory access control, auditd system call logging, kernel sysctl hardening, file integrity monitoring (AIDE), rootkit detection (rkhunter/chkrootkit), unattended security patching, GRUB + UEFI + LUKS boot security, and CIS benchmark compliance.
dpia-generator
Generate a Data Protection Impact Assessment (DPIA), Uganda DPPA 2019-compliant. Use when producing or reviewing a data protection impact assessment, a privacy impact assessment, when uganda-dppa-compliance flags [DPIA-REQUIRED], or when processing large-scale or sensitive personal data for a new feature.
code-safety-scanner
Scan any codebase for 14 critical safety issues across security vulnerabilities, server stability (500 errors), and payment misconfigurations. Use when auditing code before deployment, reviewing AI-generated code for production readiness, or...
world-class-engineering
Use when designing, building, reviewing, or upgrading production software systems that must be secure, performant, maintainable, scalable, and user-centered. Apply before writing specs, code, architecture, APIs, databases, mobile apps, SaaS platforms, or ERP systems.
update-Codex-documentation
Update project documentation files (README.md, PROJECT_BRIEF.md, TECH_STACK.md, ARCHITECTURE.md, docs/API.md, docs/DATABASE.md, AGENTS.md, docs/plans/NEXT_FEATURES.md) when significant changes occur. MANDATORY at end of each work session to...
skill-writing
Use when creating or upgrading skills in this repository. Covers repository-specific frontmatter rules, progressive disclosure, reference-file strategy, validation, and the quality bar required for production-grade engineering skills.
skill-safety-audit
Scan new or updated skills for unsafe or malicious instructions (unknown tools, external installers, credential harvesting) before accepting them into the repository.