Skip to main content
Design/ux-craft

UX Craft

You need to build design foundations from personas through prototyping to review.

This is a skillset -- it chains /persona-draft -> /journey-map -> /information-architecture -> /client-prototype -> /design-review in sequence. Each skill also works independently.

Use this when entering a new product area, starting a new engagement, or refreshing design foundations quarterly. Takes you from research-backed personas through journey mapping, information architecture, prototyping, and structured design review.


The chain

StepSkillWhat it produces
1/persona-draftUser persona definitions grounded in research data
2/journey-mapUser journey maps with emotional arcs and opportunity areas
3/information-architectureIA structure with navigation, content hierarchy, and labeling
4/client-prototypeBranded interactive prototype built from IA decisions
5/design-reviewStructured feedback on accessibility, consistency, edge states, and AC coverage

When to use: Project start or quarterly refresh. After /ux-research has produced insights.


How skills chain

  • /persona-draft crystallizes research into user archetypes -> personas ground all subsequent design decisions
  • /journey-map maps the end-to-end experience for each persona -> reveals pain points, gaps, and opportunities
  • /information-architecture structures navigation and content from journey insights -> IA becomes the blueprint for the prototype
  • /client-prototype builds a branded, interactive prototype from IA decisions -> the prototype is what gets reviewed and tested
  • /design-review critiques the prototype against accessibility, consistency, and acceptance criteria -> feedback drives iteration

What the designer does between stages

After...Designer decision
/persona-draftValidate personas with the team and stakeholders -- do they recognize these users?
/journey-mapIdentify the highest-value journey stages to prototype first
/information-architectureReview IA with engineering lead -- is the structure technically feasible?
/client-prototypeWalk through the prototype with users informally before formal review
/design-reviewFix critical issues, discuss trade-offs with PM, prioritize remaining feedback

Related skills: Part of the ux-orbit recipe. Takes input from /ux-research insights. Prototype output feeds into /ux-validate for testing.

Example Output

Input

  • Company: Northtide Health — a regional urgent care network (14 clinics, Pacific Northwest)
  • Product area: Patient self-scheduling and intake mobile app, replacing a phone-only booking system
  • Research input: 6 contextual interviews, 3 diary studies, NPS of 31 from post-visit surveys; top complaints are wait time uncertainty and redundant paperwork at check-in
  • Design constraint: Must meet WCAG 2.1 AA; brand colors are deep teal (#0B5E6B) and warm sand (#F2EAD8)
  • Stakeholders: VP of Patient Experience, Engineering Lead (React Native), and a compliance officer reviewing HIPAA data flows

Output

/ux-craft — Northtide Health Patient Scheduling & Intake App


Step 1 — /persona-draft

Primary Personas


Persona 1: "Pressed-for-Time Parent" — Maya

AttributeDetail
Age / Role38, operations manager, mother of two
Access patternMobile-first, books appointments during school drop-off or lunch
Core goalConfirm a same-day slot and know exactly when to show up
Top frustrationCalling during work hours, being put on hold, repeating insurance info every visit
Tech fluencyHigh — uses banking apps, food delivery, telehealth
Emotional state at entryMildly anxious, in a hurry

Design implications: Surface real-time wait estimates immediately. Pre-fill returning patient data. Minimize tap count to confirmation.


Persona 2: "Managing a Chronic Condition" — Dennis

AttributeDetail
Age / Role64, retired teacher, manages Type 2 diabetes + hypertension
Access patternTablet or desktop; brings a family member when navigating complex forms
Core goalCommunicate current medications and reason for visit accurately before arrival
Top frustrationSmall touch targets, unclear form labels, fear of entering wrong insurance info
Tech fluencyModerate — comfortable with email and video calls, cautious with new apps
Emotional state at entryMethodical, slightly overwhelmed by unfamiliar UI

Design implications: Large tap targets (min 48×48px), plain-language labels, progress indicators on multi-step forms, ability to save and resume.


Persona 3: "Walk-In Decision Maker" — Priya

AttributeDetail
Age / Role26, graduate student, uninsured / on student plan
Core goalUnderstand cost upfront and avoid surprise billing
Top frustrationNo price transparency before booking; unclear whether her plan is accepted
Emotional state at entryCost-anxious, comparison-shopping between Northtide and competitors

Design implications: Insurance + self-pay cost estimator visible before account creation. Trust signals (accepted plans badge) on the home screen.


Step 2 — /journey-map

Maya — Same-Day Booking Journey

TRIGGER → SEARCH → BOOK → PRE-ARRIVAL → CHECK-IN → VISIT → POST-VISIT
StageMaya's ActionEmotional ArcPain PointOpportunity
TriggerChild wakes with ear pain at 7am😟 WorriedNo quick way to gauge urgencySymptom triage nudge → "Book now or visit ER?"
SearchGoogles "urgent care near me open now"😐 FocusedNorthtide site not mobile-optimizedDeep-link from Google to live slot picker
BookSelects clinic, picks 9:15am slot🙂 RelievedHas to re-enter insurance she gave last visitReturning patient auto-fill from account
Pre-arrivalReceives SMS reminder 30 min before🙂 ConfidentNo real-time wait updateLive queue position in SMS + app
Check-inFills out intake form in waiting room😤 FrustratedRepeats same paperwork as last visitPre-completed digital intake, just confirm
VisitSeen by provider😊 Cared for
Post-visitGets paper discharge summary😐 NeutralNo digital record, hard to share with PCPIn-app visit summary + share-to-provider

Highest-value stages to prototype first (designer decision checkpoint): Book → Pre-arrival → Check-in. These three stages contain all four top-complaint moments.


Opportunity Areas Surfaced Across All Personas

  1. Real-time wait transparency — appears in all three persona journeys
  2. Persistent patient profile — eliminates redundant data entry for Dennis and Maya
  3. Cost clarity before commitment — critical for Priya, table-stakes for credibility
  4. Digital intake pre-completion — reduces check-in friction for all personas

Step 3 — /information-architecture

Navigation Model: Bottom Tab Bar (4 items)

[ Home ] [ Find Care ] [ My Health ] [ Account ]

Content Hierarchy

Home
├── Live Wait Times (by clinic, surfaced immediately)
├── Book Appointment (primary CTA)
├── Continue Where You Left Off (returning users)
└── Cost Estimator entry point

Find Care
├── Clinic Locator (map + list toggle)
│   ├── Filter: Open Now / Distance / Wait Time
│   └── Clinic Detail → Book slot
├── Symptom Checker (triage nudge)
└── Services Offered (per clinic)

My Health
├── Upcoming Appointments
│   ├── Pre-Visit Intake Form (pre-filled, confirm)
│   ├── Live Queue Position (day-of)
│   └── Cancel / Reschedule
├── Visit History
│   └── Discharge Summary (PDF + share)
└── Medications & Conditions (Dennis use case)

Account
├── Personal Info
├── Insurance & Payment
│   └── Saved Plans (auto-fill on booking)
├── Notification Preferences
└── Accessibility Settings (text size, high contrast)

Labeling Decisions

IA TermRationale
"Find Care" not "Locations"Action-oriented; matches mental model of users starting with a need
"My Health" not "Records"Less clinical; inclusive of upcoming + past + intake
"Live Wait Times" on HomeAddresses #1 stated frustration before any interaction
"Cost Estimator" not "Pricing"Softer framing reduces anxiety for uninsured users (Priya)

Step 4 — /client-prototype

Branded Prototype Spec — Northtide Health

Brand tokens applied:

  • Primary: #0B5E6B (deep teal) — CTAs, active nav, progress bars
  • Surface: #F2EAD8 (warm sand) — card backgrounds, form fields
  • Text primary: #1A1A1A — AA contrast on sand (7.3:1 ✓)
  • Destructive / alert: #C0392B
  • Font: Inter (system fallback: -apple-system) — 16px body minimum

Screen Flow: Core Prototype (Booking + Intake)

Screen 1 — Home

┌─────────────────────────────────┐
│  Good morning, Maya             │
│  ─────────────────────────────  │
│  🟢 Northtide Eastside — 12 min │
│  🟡 Northtide Bellevue — 28 min │
│  ─────────────────────────────  │
│  [ Book an Appointment →  ]     │  ← teal CTA, full-width
│  [ Estimate My Cost       ]     │  ← sand outline button
└─────────────────────────────────┘

Screen 2 — Slot Picker

┌─────────────────────────────────┐
│  < Northtide Eastside           │
│  Today · Est. wait 12 min       │
│                                 │
│  ○ 9:00 AM