RY

Case study

ASAP

(AI Scaffolding Action Planner)

Turn big goals into small, doable steps.

ASAP is an AI-powered planning experience that helps people break down a goal, figure out what matters first, and start taking action.

  • AI Product Design
  • UX Research
  • Conversation Design
Role
UX Research & Conversation Design
Team
4-person team
Timeline
10 weeks
Platform
Mobile prototype
Technology
Claude API
ASAP home screen with a task entered
ASAP focus mode with a timer for the current step
ASAP’s five-step plan, with the first step marked high confidence

The problem

People have goals. The hard part is knowing where to start.

Whether it’s changing careers, learning a new skill, or starting a personal project, turning a broad goal into a plan can feel overwhelming.

Existing productivity tools assume the plan already exists. Generic AI can generate a lot of advice without helping you figure out what actually matters first.

That was the problem we set out to solve.

What we heard in six interviews

  • People froze at the blank page, not at the to-do list.

  • Participants already used Notion and Google Calendar. Storing and tracking tasks was never the gap.

  • Generic AI suggestions read as advice from something that hadn’t listened.

See ASAP in action

From “I don’t know where to start” to a clear next step.

ASAP starts with a broad goal, asks a few questions to understand the context, and turns the answers into a practical next step.

Watch the full flow below.

Try the prototype

Explore the planning flow yourself.

Product direction

We moved from “make me a plan” to “help me figure out the plan.”

The original concept was closer to a task-management tool.

Research showed that users already had places to store tasks and manage their time. What they struggled with was deciding how to break an unfamiliar goal down.

So we changed the role of ASAP.

Instead of generating a finished plan, the product would help users work through the decisions behind it.

  • Ask before recommending

    The AI gathers context before suggesting next steps.

  • One step at a time

    The experience avoids dropping a long plan on the user all at once.

  • Be clear about uncertainty

    Confidence cues and limitations help users understand how much to rely on an AI recommendation.

The experience

A simple flow from goal to action.

The experience is built around four moments.

  1. ASAP home screen with a task entered: “I need to prepare for a first client meeting”
    Goal

    Set the goal

    The user describes what they want to accomplish in their own words.

  2. ASAP asking “What best describes you right now?” with options such as early career professional and career changer
    Clarify

    Add context

    ASAP asks targeted questions before making recommendations.

  3. A five-step plan tailored for an early-career professional, with the first step highlighted and marked high confidence
    Plan

    Get next steps

    The system turns that context into practical actions.

  4. Focus mode for “Clarify the goal of the meeting” with a 15-minute timer and the week’s steps above it
    Focus

    Focus

    The user works through one step at a time.

Designing the AI

The interface was only part of the design.

Because ASAP relies on AI, I also had to design what happens behind the interface — how the system asks questions, uses context, responds to users, and communicates uncertainty.

  • Prompt structure

    Built the prompt logic around the information the AI needed to make useful recommendations.

  • Conversation design

    Defined how ASAP asks questions, responds to users, and moves the conversation forward.

  • AI behavior

    Defined when the system should ask, recommend, clarify, or stop.

  • Confidence and boundaries

    Made uncertainty and limitations visible instead of presenting every response with the same level of confidence.

How ASAP behaves

  1. 1

    Take the goal

    In the user’s own words, however broad.

  2. 2

    Ask

    Collect role and context before recommending anything.

  3. 3

    Recommend

    Break the goal into steps. Every step carries a confidence level.

  4. 4

    Clarify or stop

    Coach when someone is stuck. Stop once there’s a clear next step, and say plainly when a request is out of scope.

Steps labelled high, medium and low confidence, followed by the note “My time estimates are based on averages and may not match your pace. You know your speed better than I do.”
Confidence levels and a plain limitation note, as built.

Building with real AI

Testing the real AI exposed problems we couldn’t see in static screens.

Once the prototype was connected to the Claude API, we could see how the experience behaved with different inputs.

That surfaced a few issues we needed to address.

  1. Issue

    Recommendations were too similar.

    Different scenarios could produce similar recommendations.

    What changed

    Added role- and context-specific inputs to the prompt structure so recommendations could better reflect different scenarios.

    How we did it

    We expanded the prompt inputs to include the user’s role, goal, and relevant task context, helping the AI distinguish between scenarios instead of relying on generic task steps.

    In the prototype

    Onboarding screen asking “What best describes you right now?” with options including College student and Early career professional, and the note “This helps me tailor the language to your situation.”
    The plan for “I need to prepare for a first client meeting”: 5 steps, about 95 minutes, tagged “Tailored for early-career pro.”
    The role chosen on the first screen, and the plan it shapes — tagged “Tailored for early-career pro.”
  2. Issue

    Some responses were unreliable.

    Some interactions stalled or failed to return a useful response.

    What changed

    Refined prompt constraints and response handling to make outputs more predictable when responses were delayed or incomplete.

    How we did it

    We refined the instructions that bounded the AI’s response and clarified how the prototype handled incomplete, delayed, or unhelpful outputs. This made the interaction more predictable and helped surface failures during testing.

    In the prototype

    While the plan is generated, the screen reads “Breaking this down for you…” with an “Analyzing your task…” card and a typing indicator.
    While the AI is working, the screen says so — “Analyzing your task…” — instead of sitting empty.
  3. Issue

    Users lost track of progress.

    It wasn’t always obvious where users were in the planning flow.

    What changed

    Added clearer step and next-action cues so users could see where they were in the plan at a glance.

    How we did it

    We made the plan’s current step and upcoming actions easier to identify, using clearer progression cues and presenting next steps in a more structured sequence.

    After testing

    The active step marked “Start Here, 1 of 5, Next up”, followed by step 2 of 5 and step 3 of 5, each locked with “Unlocks after you finish step 1” and “step 2.”
    Each step shows its place — “1 of 5” — and later steps stay locked until the one before is finished.

Validation

What we learned from using it with people.

We ran 6 user interviews and 4 usability scenarios across 3 design iterations using a live AI-powered prototype.

User interviews
6
Usability scenarios
4
Design iterations
3
Functional AI prototype
1

What we found

  • The step-by-step model made the product easier to approach.

    Users responded well to having a smaller action in front of them instead of a long list.

  • Confidence cues helped set expectations.

    Users had a better sense of how much weight to put on an AI recommendation when the system communicated confidence.

  • The experience felt lighter when users could focus.

    Showing one action at a time reduced the feeling of having to manage everything at once.

The team’s synthesis board: problem framing, interview themes and feature prioritisation
Synthesis board from the research phase — problem framing and feature prioritisation with the team.

Impact

We ended with a clearer model for AI-guided planning.

ASAP addresses the gap between having a goal and knowing how to achieve it. By clarifying goals and guiding tasks with AI, the app makes complex work easier to navigate.

User testing surfaced challenges with generic recommendations, unclear response timing, and limited visibility into task progress. Those findings informed improvements in personalization, response behavior, and task progression.

ASAP’s task screen with the goal “I need to prepare for a first client meeting” entered.

The goal, as typed

The five-step plan ASAP builds from that goal, with the first step highlighted and marked high confidence.

The plan ASAP builds

  • Personalization

    Role and task context feed the prompt, so a plan can reflect who it’s for and what they’re facing.

    From issue 01

  • Response behavior

    Tighter prompt constraints and clearer handling of slow or incomplete responses made the interaction more predictable.

    From issue 02

  • Task progression

    Step counters, a highlighted next step, and locked future steps show where you are in the plan.

    From issue 03

My role

I worked on the experience between the user’s goal and the AI’s response.

On a four-person team, I focused on the parts of the product that shaped how users interacted with the AI.

I owned

  • UX research and usability testing
  • Conversation design
  • Prompt architecture
  • AI behavior and response patterns
  • Information architecture
  • Confidence and limitation states
  • Onboarding and product copy
  • Iterative prototyping
  • Translating research findings into product decisions

HCI capstone, DePaul University.

Design system

Calm by default, so the task stays dominant.

A slate-teal core with warm neutrals, sage and amber accents, and a restrained semantic set — enough structure to keep AI states legible without letting the interface turn decorative.

Weight carries hierarchy rather than colour, and amber is reserved for selection and guidance so a recommendation never competes with the step in front of you.

ASAP colour board: the Slate Teal ramp from 900 to 50, warm neutrals from dark background to light, sage and amber accents, and the four semantic colours, each labelled with its token and hex.
Colour tokens — slate teal, warm neutrals, sage and amber, semantic.
ASAP typography board: Inter from Google Fonts, with weight, size and line height for Heading 1 through Caption, and a note that heading line height and paragraph spacing are 1.1x the font size.
Type scale — Inter, with hierarchy carried by weight.
ASAP component board in dark and light mode: primary and disabled CTAs, secondary button, text link, circular icon button, option cards unselected and selected, sidebar nav items, the AI guidance card, dark and light text inputs with focus states, and the selection indicator.
Components in both modes — CTAs, option cards, sidebar, the AI guidance card, inputs and selection.

Never

Neon AI gradients, unrelated brand colours, colour as the only indicator of state, or decoration that doesn’t support the task.

What’s next

The next step is making ASAP useful beyond the prototype.

The current experience works as a focused planning tool. The next version would need to handle more complex goals, connect to the tools people already use, and prove that the guidance actually helps people follow through.

  • Handle more complexity

    Adapt the planning experience to different types and sizes of goals.

  • Work with existing tools

    Connect planning to calendars, notes, and other everyday workflows.

  • Prove the value

    Measure whether users actually complete more of what they set out to do.

Final thoughts

Good AI design isn’t about doing everything for people.

For ASAP, the better experience was one that helped people make the next decision themselves.

Next project

PM Dashboard

View case study