What is The UX Strategist?

The UX Strategist is a 3-step design flow that prevents two common design failures: building ideas disconnected from constraints, and anchoring on the first plausible concept. It chains GROW to map the design space within real constraints, SCAMPER to systematically break first-instinct thinking and generate unexpected alternatives, and SEED to convert the strongest concept into a deliverable-focused specification.

The critical sequence insight: constraints must precede creativity. SCAMPER without GROW produces clever ideas that can't be built. SCAMPER after GROW generates creative alternatives within achievable bounds. SEED then converts ideas into commissions — artifacts engineering can actually work from.

When to Use The UX Strategist

✨

Feature Redesigns

Existing features that aren't meeting user needs where first-instinct solutions are too incremental to make a difference.

🆕

New Feature Design

Brand-new features where the design space needs systematic exploration before committing to an approach.

🔀

User Flow Optimization

Multi-step flows with friction where incremental improvements have failed and a structural rethink is needed.

📱

Mobile-First Design

Mobile experiences where constraints are tightest and first-instinct desktop-adapted designs consistently underperform.

♿

Accessibility Redesign

Adding accessibility where it was retrofitted, requiring creative solutions that serve all users without degrading the primary experience.

🚀

Onboarding Design

First-run experiences where the gap between "user arrives" and "user succeeds" must be systematically reduced.

The Flow Algorithm

1

GROW — Map the Problem Space

Apply GROW to the design problem: Goal (the user experience you're trying to achieve — framed as what the user can do/feel, not what you'll build), Reality (the current friction — what is actually happening today, with data if available), Options (2-3 design directions that are conceptually distinct — don't evaluate yet, just identify), Will (constraint audit — what can actually be built given team size, tech stack, timeline, and technical debt). The Will step is non-negotiable — remove any option that fails the constraint audit.

Produces:

A problem-solution space map with constraint-qualified design directions. Ideation begins from here — within achievable bounds.

2

SCAMPER — Break First-Instinct Thinking

Apply all seven SCAMPER lenses to the current design or primary Option from Step 1. For each lens, produce one concrete design alternative (not a vague idea — a specific change to a specific UI element or interaction). Rate each alternative: viable within constraints (yes/no) and potential impact (low/medium/high). Select the 1-2 most promising alternatives for development in Step 3. Some lenses will produce weak ideas — prune them explicitly rather than keeping everything.

Produces:

A rated set of design alternatives, including at least one unexpected concept that wouldn't have emerged from linear design thinking. The best concept is selected for specification.

3

SEED — Specify the Deliverable

Apply SEED to the winning concept from Step 2: Situation (the user context and current state), End Goal (the specific measurable outcome — not "better UX" but "reduce time-to-first-action from 4 steps to 2"), Examples (reference designs or interaction patterns from other products), Deliverables (the exact artifacts needed: screen flows, component list, interaction states, edge case handling). The Deliverables section is the handoff artifact — specific enough that a designer can execute it without a follow-up meeting.

Produces:

An implementation-ready design specification with measurable success criteria, reference examples, and explicitly scoped deliverables. Ready for design tool execution or engineering handoff.

Example Prompt Sequence

Step 1 — GROW Problem Mapping

Apply GROW to this UX design problem:

Product: A B2B SaaS project management tool
Problem: New users abandon the product within the first 3 days because they can't create their first project successfully.

Goal: What does successful onboarding feel like for the user? Frame as user experience, not features.
Reality: Describe the current friction — what specifically causes abandonment at which step? (Infer from the problem if data isn't provided.)
Options: Identify 3 conceptually distinct design directions for reducing abandonment.
Will: For a 2-person design team with a 3-week timeline, which options are buildable? Remove any that fail this constraint.

Step 2 — SCAMPER Creative Exploration

Apply SCAMPER to the primary onboarding flow for the project management tool described below. For each lens, produce one specific design alternative:

Substitute: Replace one element of the current flow with something from a different interaction paradigm
Combine: Merge two currently separate steps into one
Adapt: Borrow a pattern from a consumer app (games, social media, e-commerce)
Modify: Change the scale, speed, or sequence of something
Put to another use: Repurpose an existing feature in a new onboarding context
Eliminate: Remove a step that isn't essential for first-time success
Rearrange: Reorder the sequence for better cognitive flow

For each: rate it (viable within 3-week constraint: yes/no) and (impact potential: low/medium/high).
Select the 2 most promising alternatives.

Current flow context from Step 1: [PASTE GROW OUTPUT HERE]

Step 3 — SEED Specification

Create a design specification using SEED for the winning concept below:

Situation: New B2B user, first login, no prior context on the product. Has agreed to try it but is skeptical. On desktop browser.
End Goal: User completes their first project creation with at least one task added within 5 minutes of first login. Measured by event tracking.
Examples: Reference Notion's first-run template picker, Linear's empty state guidance, and Figma's template gallery as positive patterns to draw from.
Deliverables: (1) Screen flow diagram (screens + transitions), (2) Component list with interaction states, (3) Empty state and error state specs, (4) Success measurement event list.

Winning concept from Step 2: [PASTE SELECTED SCAMPER CONCEPT HERE]

Pros and Cons

Strengths

  • GROW prevents ideating outside buildable constraints
  • SCAMPER systematically breaks first-instinct anchoring
  • SEED produces engineering-ready handoff artifacts
  • Measurable success criteria built into SEED output
  • Works for any product type or platform

Trade-offs

  • Some SCAMPER lenses produce weak ideas — requires judgment to prune
  • SEED spec quality depends on how well constraints are defined
  • Does not produce visual mockups — requires design tool follow-up
  • 3 separate prompt interactions add time versus direct ideation

Frequently Asked Questions

What is The UX Strategist prompt flow?

The UX Strategist chains GROW, SCAMPER, and SEED to produce design specifications grounded in real constraints. GROW maps the design problem within its constraints, SCAMPER generates creative alternatives that break first-instinct thinking, and SEED converts the best concept into an implementable deliverable.

Why use a coaching framework (GROW) for UX design?

GROW's four components — Goal (desired experience), Reality (current friction), Options (design paths), Will (what can actually be built) — are directly applicable to UX problem-framing. The Will component specifically forces constraint acknowledgment before ideation, preventing SCAMPER from generating designs that look great but can't be built.

How should I apply SCAMPER to UX design?

Apply each of SCAMPER's seven lenses to the current design or user flow: Substitute (replace a UI element or interaction pattern with something else), Combine (merge two separate features), Adapt (borrow a pattern from another domain), Modify (change scale, speed, or frequency), Put to another use (repurpose existing UI), Eliminate (remove an element entirely), Rearrange (change the order or layout). Some lenses will produce weak ideas — that's expected. The goal is one surprising, viable concept.

What does SEED add that a design brief doesn't?

SEED's four components force the design brief to be deliverable-focused rather than vision-focused. Situation (the context), End Goal (the outcome measurement), Examples (reference designs or interaction patterns), Deliverables (the specific artifacts required) — the Deliverables component is critical. It turns an idea into a commission: something engineering can actually build.

Can this flow be used for mobile design?

Yes. The flow is medium-agnostic. In the GROW step, specify mobile constraints (screen size, thumb zones, network variability). In SCAMPER, apply the lenses to mobile-specific interaction patterns. In SEED, specify mobile deliverables (screen flows, touch targets, component specs).

How far does this flow go — does it produce actual mockups?

The flow produces a design specification document — the brief that informs mockup creation, not the mockups themselves. For UI implementation, hand the SEED output to a designer or use it as input for a design tool. The flow's value is in producing a well-reasoned, constraint-grounded brief rather than in generating visual artifacts.