Context is scattered.
A recording preserves the discussion, while the next step often lives somewhere else—in a note, a message or memory.
01 / SIMPLIFAI · RECALL / AI MOBILE APPLICATION
Be present.
Keep the meaning.
Choose what’s next.
An AI conversation companion that transcribes discussions, summarises the meaning and suggests next steps—with the source and the final decision in your hands.
AI product concept · Human review · Mobile UX9:41▮▮▮ ▰
RECORDING IN PROGRESS
Listening, deliberately.
08:42
Audio stays in this session
LIVE TRANSCRIPT
“Let’s aim for Friday, but confirm after the supplier responds.”
Pause capture · Stop and review
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINK
Product catch-up
SummaryTranscriptInsights
AT A GLANCE
A delivery date is still open.
The team discussed Friday. Final timing depends on the supplier’s response.
Source · 18:42Suggested next steps
2NEEDS REVIEWConfirm delivery with the supplierFriday mentioned · not confirmedReview action
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINK
Make it your next step.
Suggested · not savedFriday was mentioned conditionally. Choose a date when it is agreed.
View source at 18:42
Confirm & save
Dismiss suggestion
TodayLibraryActionsAsk
- My role
- Product Designer
Mamta Mahato - Design scope
- AI interaction design, research framing, flows, wireframes and mobile UI
- Evidence
- Reference review + design rationale
Participant testing planned
Overview
A clear summary is only half the job.
After a conversation, people still need to decide what was agreed, what remains uncertain and what they will do next. Recall focuses on that handover: from spoken context to a commitment the person has checked.
A suggestion can sound final.
“Let’s aim for Friday” should not silently become a confirmed Friday deadline.
Keep evidence in the loop.
Connect each suggestion to its source, make uncertainty readable, and ask for confirmation before saving an action.
How might we make conversations actionable while keeping people in control of their meaning?
01
Frame
Define the risky moment
02
Explore
Review patterns and assumptions
03
Structure
Map the information and journey
04
Design
Move from wireframes to UI
05
Evaluate
Test comprehension and control
AI experience
AI finds the signal. You decide what it means.
Recall is designed around a reviewable AI workflow: turn a conversation into useful context without turning a model’s interpretation into an unchecked commitment.
Audio → transcript
Speech recognition produces a timestamped transcript after everyone agrees to recording.
Transcript → suggestions
A language model proposes a summary, decisions and possible actions. Conditional dates remain uncertain.
Question → source
Ask retrieves relevant saved excerpts before composing an answer, with a link back to the original words.
Suggestion → action
The person checks the source, corrects the owner or date, and confirms what enters their task list.
WHAT WAS SAID · 08:42
“Let’s aim for Friday, but confirm after the supplier responds.”
AI SUGGESTION · NEEDS REVIEW
Confirm the delivery date
Friday is tentative. Owner and due date need confirmation.
View source · 08:42YOUR DECISION
Review, edit or dismiss.
Nothing becomes a saved commitment automatically.
Confirmed by youDesigned product behaviour, illustrated with sample content. This portfolio walkthrough does not record audio or call a live AI model.
No evidence?
Show “I couldn’t find that in your conversations” instead of a confident invented answer.
Analysis fails?
Keep the recording saved, explain the failure and offer a separate retry.
Meaning is wrong?
Keep the original words nearby. Let the person correct or dismiss the suggestion.
Research
Start with the product. Be precise about the evidence.
I separated desk-research observations from questions that would require research with people. The design questions below guide the prototype; they are not findings from interviews conducted.
What this means for Recall
The opportunity is to make the transition between interpretation and action understandable on a small screen.
- A summary and a confirmed task need different states.
- Source evidence should be reachable from the point of doubt.
- Capture controls should be visible without a settings detour.
- Search answers should show where the information came from.
Review the design questions
| Observed pattern | Question to investigate | Recall response |
|---|---|---|
| Record-to-task journey | When does a suggestion feel like a commitment? | A review step before an action joins the task list. |
| Multiple specialist perspectives | How do people interpret competing outputs? | One chosen lens, with the source always available. |
| Questions across saved conversations | What makes an answer trustworthy? | A source excerpt and a clear no-evidence state. |
| Consent and human-review guidance | Can people find control at the right moment? | A pre-capture check and per-conversation privacy controls. |
View the proposed interview guide
Interview guide / proposed
Ask about the last real conversation.
Recruit people who regularly turn meetings or catch-ups into follow-up work. Include people who take notes and people who rely on recordings.
No participants have been recruited or interviewed for this case study.- Walk me through how you captured your last important discussion.
- What did you do immediately after it ended?
- Tell me about a time the notes and your understanding did not match.
- How did you check who owned the next step or when it was due?
- What would make you stop recording or delete a conversation?
Affinity map
Group the questions before choosing the features.
This hypothesis board organises the review into four themes. The notes describe design concerns to investigate; they are not participant quotations or measured findings.
Capture & consent
Knowing when recording begins
Pausing without losing the session
An alternative to audio capture
Design response: deliberate entry
Meaning & certainty
Tentative dates read as deadlines
Decisions mixed with suggestions
Interpretations need a source
Design response: visible evidence
Follow-through
Actions need a clear owner
Review can happen later
Too many suggestions add work
Design response: confirmation queue
Control & trust
Who can access a conversation?
What happens when it is deleted?
Answers need boundaries
Design response: explicit controls
The person carrying the follow-up.
A project contributor moving between discussions, responsible for remembering decisions and coordinating the next step. The working need is continuity—not simply a longer transcript.
Help me check what matters.
“When a discussion ends, help me recover the important context and confirm my next step, so I can follow through without turning every suggestion into a promise.”
Illustrative job statement, not a participant quote.User flow
One journey. Three deliberate decisions.
The core journey asks permission before capture, preserves uncertainty during review, and requires confirmation before a task is created. Secondary paths support recovery and later recall.
Agree to capture
Consent is explicit; a note is available as an alternative.
Keep control
Pause and stop remain separate, visible actions.
Check meaning
Review the summary and open the source when needed.
Confirm the action
Edit the owner or date, then save intentionally.
01Today→
02Consent check→
03Record→
04Stop & save→
05Summary→
06Review action→
07Confirm & save
No agreement → Write a note
Interrupted analysis → Keep recording, retry
Unclear suggestion → Read source, edit or dismiss
Today
Recent conversations
Reviews waiting
Start a capture
Library & Ask
Saved conversations
Transcript and insights
Questions with sources
Actions
Confirmed next steps
Owners and dates
Open and completed
Wireframes
Resolve the hierarchy before adding polish.
The first pass establishes six critical layouts. It gives capture one primary action, keeps the summary skimmable, and reserves a dedicated review screen for decisions that need attention.
9:41▮▮▮ ▰
STRUCTURE / home
A little more clarity.
ONE THING TO CLOSE
Confirm the delivery date.
Product catch-up · 2 suggestions need your review
Review suggestionsRecent conversations
View allProduct catch-upToday · 24 min · 3 people
Ideas for the next sprintYesterday · 12 min
New conversation
TodayLibraryActionsAsk
9:41▮▮▮ ▰
STRUCTURE / consentYou can pause, stop or delete the recording at any time.
Before we begin.
Make room for everyone’s choice.
Tell everyone that this conversation will be recorded and summarised.
Everyone has agreed to recording.
Start recording
Write a note instead
TodayLibraryActionsAsk
9:41▮▮▮ ▰
STRUCTURE / recording
Listening, deliberately.
08:42
Audio stays in this session
LIVE TRANSCRIPT
“Let’s aim for Friday, but confirm after the supplier responds.”
Pause capture · Stop and review
TodayLibraryActionsAsk
9:41▮▮▮ ▰
STRUCTURE / summary
Product catch-up
SummaryTranscriptInsights
AT A GLANCE
A delivery date is still open.
The team discussed Friday. Final timing depends on the supplier’s response.
Source · 18:42Suggested next steps
2NEEDS REVIEWConfirm delivery with the supplierFriday mentioned · not confirmedReview action
TodayLibraryActionsAsk
9:41▮▮▮ ▰
STRUCTURE / source
The words behind it.
Product catch-up · 18:42AYA · TRANSCRIPT EXCERPT
“Let’s aim for Friday, but confirm after the supplier responds.”
18:42
WHY THIS NEEDS REVIEW
The date is conditional. Recall leaves it unconfirmed until you decide.
Back to action
TodayLibraryActionsAsk
9:41▮▮▮ ▰
STRUCTURE / task
Make it your next step.
Suggested · not savedFriday was mentioned conditionally. Choose a date when it is agreed.
View source at 18:42
Confirm & save
Dismiss suggestion
TodayLibraryActionsAsk
Save actions directly from the summary?
Faster, but it hides the distinction between an extracted suggestion and an agreed commitment. A single tap would make ambiguous dates too easy to accept.
Use a short, focused review.
One additional screen exposes the wording, owner, date and source. It adds a deliberate pause at the point where an interpretation becomes an action.
Visual system
Warmth, with a clear point of focus.
Terracotta highlights the next action. Warm white surfaces and charcoal text keep the conversation readable.
TYPE / DM SANSAa
Keep the meaning.
Display 28 / body 16 / metadata 12–14
A consistent 4 / 8 / 16 / 24 spacing rhythm.
Action#ad3f25
Ink#30221e
Surface#fff0e7
Confirmed#15805b
STATUS / BEFORE REVIEWSuggested
STATUS / AFTER REVIEWConfirmed by you
PRIMARY ACTIONConfirm & save
Icons support labels. Status uses words as well as colour. Capture controls are sized for touch, with clear focus states in the prototype.
App screens
From a conversation to a clear next step.
Follow the app journey, or choose a step to explore.
HOW THE AI APP WORKS
9:41▮▮▮ ▰
WEDNESDAY, 23 SEPTEMBER
A little more clarity.
ONE THING TO CLOSE
Confirm the delivery date.
Product catch-up · 2 suggestions need your review
Review suggestionsRecent conversations
View allProduct catch-upToday · 24 min · 3 people
Ideas for the next sprintYesterday · 12 min
New conversation
TodayLibraryActionsAsk
Explore all 12 app screens
9:41▮▮▮ ▰
WEDNESDAY, 23 SEPTEMBER
A little more clarity.
ONE THING TO CLOSE
Confirm the delivery date.
Product catch-up · 2 suggestions need your review
Review suggestionsRecent conversations
View allProduct catch-upToday · 24 min · 3 people
Ideas for the next sprintYesterday · 12 min
New conversation
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINKYou can pause, stop or delete the recording at any time.
Before we begin.
Make room for everyone’s choice.
Tell everyone that this conversation will be recorded and summarised.
Everyone has agreed to recording.
Start recording
Write a note instead
TodayLibraryActionsAsk
9:41▮▮▮ ▰
RECORDING IN PROGRESS
Listening, deliberately.
08:42
Audio stays in this session
LIVE TRANSCRIPT
“Let’s aim for Friday, but confirm after the supplier responds.”
Pause capture · Stop and review
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINK
Connecting the details.
Your recording is saved.
Preparing a summary and possible next steps.
Transcript ready24 minutes captured
Finding key momentsYou can leave this screen
Back to Today
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINK
Product catch-up
SummaryTranscriptInsights
AT A GLANCE
A delivery date is still open.
The team discussed Friday. Final timing depends on the supplier’s response.
Source · 18:42Suggested next steps
2NEEDS REVIEWConfirm delivery with the supplierFriday mentioned · not confirmedReview action
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINK
The words behind it.
Product catch-up · 18:42AYA · TRANSCRIPT EXCERPT
“Let’s aim for Friday, but confirm after the supplier responds.”
18:42
WHY THIS NEEDS REVIEW
The date is conditional. Recall leaves it unconfirmed until you decide.
Back to action
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINK
Make it your next step.
Suggested · not savedFriday was mentioned conditionally. Choose a date when it is agreed.
View source at 18:42
Confirm & save
Dismiss suggestion
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINK
Room to follow through.
Open · 3Completed
Confirm delivery with the supplierMe · No date · Product catch-upConfirmed by you
Share the updated project briefToday · Sprint planning
Prepare review questionsTomorrow · Design sync
A CALMER INBOX
Only actions you confirm appear here. Suggestions stay with their conversation.
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINK
Find the moment.
Did we agree to deliver on Friday?
RECALL
Based on 1 conversation in your library.Friday was proposed, but the team had not confirmed it.
The supplier’s response was the dependency.
Product catch-up · 18:42
Ask a follow-up
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINK
A different perspective.
Choose what to look for. The original conversation stays the same.
Next steps
Possible actions, owners and open dates.
Decisions
What was agreed, and what remains open.
Open questions
Details to clarify before moving forward.
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINK
Your conversations. Your rules.
Private by default
Choose what to keep and what to share for each conversation.
Keep audioUntil I delete it
Export conversationReview before sharing
Delete conversationIncludes transcript and summary
Deleting a conversation also removes its linked source excerpts.
TodayLibraryActionsAsk
9:41▮▮▮ ▰
YOUR SPACE TO THINK
Start with one conversation.
A place for what matters.
Record with everyone’s agreement, or begin with a written note.
New conversation
Write a note
No recording starts until you choose it.TodayLibraryActionsAsk
Usability testing
Test understanding—not just task completion.
The next step is a moderated study with a small mix of people who coordinate follow-up work. Five to six participants would provide an initial qualitative round, followed by iteration and a second round. No participant sessions or measured results are claimed here.
Use a realistic, low-stakes scenario.
Ask participants to think aloud through a fictional team catch-up. Start without a feature tour. Observe the first attempt before offering prompts.
Capture wrong turns, assistance, interpretation of status, and the person’s explanation—not only whether they reached the last screen.
Look for different habits.
Include people who currently use manual notes, recordings, or AI summaries. Mix confidence levels with AI tools and include mobile accessibility needs.
Request permission for session recording and anonymise notes. Use sample conversations rather than personal or workplace recordings.
View the usability-testing protocol
| Task | What to observe | Decision informed |
|---|---|---|
| Start a conversation without recording yet | Can the person tell when the microphone becomes active? | Consent wording and primary-action placement |
| Explain whether Friday is an agreed deadline | Does the person notice the conditional date? | Suggestion labels and uncertainty language |
| Find the words behind a suggestion | Can they locate and interpret the relevant source? | Source-link visibility and excerpt context |
| Correct an action and save it | Are owner, date and confirmation understood? | Review-screen hierarchy and form labels |
| Find an earlier decision with Ask | Do they inspect the reference before relying on the answer? | Answer structure and source prominence |
| Delete a conversation | Can they explain what will be removed? | Deletion wording and dependent-content warning |
Design decisions
Make the trade-offs visible.
The design review centres on three decisions to validate. These are prototype decisions, not changes proven by participant testing.
EXPLORATION
Automatic due date
DESIGNED DIRECTION
No date until confirmed
A conditional statement stays conditional. The user supplies the commitment.
EXPLORATION
Summary as a dead end
DESIGNED DIRECTION
Summary connected to source
A person can inspect the relevant sentence without searching the entire transcript.
EXPLORATION
Every suggestion in Actions
DESIGNED DIRECTION
Only confirmed actions in Actions
The task list reflects deliberate choices, while unreviewed suggestions remain with the conversation.
The quieter screens matter too.
Say that no supporting conversation was found. Suggest a narrower question rather than inventing an answer.
Keep the saved recording available. Show retry separately from starting a new recording.
Offer a written note. Explain microphone access only when the person chooses audio capture.
Business impact
Connect the design decision to a measurable business result.
Turn conversations into useful next steps without removing human judgment, creating value through better follow through rather than more generated content.
Less time spent rewriting notes into actions
Fewer missed decisions and unclear responsibilities
Stronger trust through editable and traceable suggestions
Measuring after release
Signals I would track with product, data and engineering.
These are success measures for post launch evaluation, not claimed results.
- Action conversion
- Share of conversations that produce a confirmed next step
- Suggestion quality
- Share of proposed actions accepted, edited or dismissed
- Follow through
- Confirmed actions completed by their intended date
- Retention
- People returning to review conversations each week
ROI lens
Value the time saved in review and follow up, then compare it with product delivery and model operating costs.
Final reflection
A useful suggestion should stay open to correction.
The concept keeps the original conversation close, shows what the system inferred and gives the person the final say before a suggestion becomes an action.
More work
Making AI workflows easier to build and understand
Simplifai · Flow Builder
SPRINTO DESIGN LANGUAGE / V5
Design system
Variables ComponentsDocumentation
8 px rhythm
Variables ⋯
NameValue
◇ space.14
◇ space.28
◇ space.312
◇ space.416
◇ space.624
TYPOGRAPHYAa
Built to belong together.InterRegular · Semibold
Giving product teams a shared component foundation
Sprinto · Design System
Making vendor risk easier to review and act on
Sprinto · Vendor Management