October 2026

Designing for Personal AI Assistants

Seven rules for AI assistants that say less, show more and leave people in control.

The seven rules

  1. 01BrevityAnswer with the smallest thing that works
  2. 02InputLet the moment choose the input
  3. 03FocusKeep one task in front
  4. 04OutcomeRecommend one, keep the rest close
  5. 05Generated UIShow an interface, not a transcript
  6. 06ControlAsk before acting, then report what really happened
  7. 07ContinuityCarry the task, not the chat
  8. Across devices One task on six kinds of device

Every example follows one task: planning dinner with Alex on Thursday at 6:30, at a restaurant called Juniper. The examples are simulations; nothing is recorded, sent or booked.

Background

Why this guide exists

Chatbots and chat boxes have almost ruined everything over the past few years.

Reading endless chat full of filler is exhausting. Even a simple yes-or-no question gets a long explanation, unless you constrain it with a prompt. You read that right: now you get to write the essay.

As models grow more capable, I suspect this isn’t an intelligence problem. It’s a deliberate choice in how agent makers design their products and internal harnesses, and choices can be made differently.

Long conversations and visible reasoning traces may help researchers and trainers find problems. For everyday users, they are a disaster.

Interfaces should take responsibility for presenting information and enabling action, instead of asking people to keep adding prompts and finish the product’s interaction design themselves.

Use the interaction that fits the moment: voice, real-time voice, generated UI, a briefing. Whatever the moment, the answer should rarely be several long paragraphs.

Rule 01 · Brevity

Answer with the smallest thing that works

Match the size of the answer to the size of the question. A yes-or-no question gets a yes or no, plus the one action that follows.

Padding is the most common failure of AI assistants: a friendly preamble, the question restated, a paragraph of caveats, an offer to help further. The answer ends up somewhere in the middle, and the person has to dig for it.

Start with the answer. Add only what changes the person’s decision or next step, and keep everything else a tap or a question away. Nobody should have to write a prompt just to get a shorter reply.

Don’t
Did the invite to Alex go out?
Great question! I’d be happy to give you an update on your invitation. As you requested earlier, I prepared an invitation for dinner with Alex at Juniper on Thursday at 6:30 PM. After you approved it, I sent the invitation to Alex’s email address. Please note that delivery times can vary between email providers, so Alex may not have seen it yet. Is there anything else I can help with, such as setting a reminder?

76 words to say yes.

Do
Did the invite to Alex go out?
InviteYes, sent at 4:12 PM.
View invite

The answer is the first line.

Best practices

Answer first. Put the answer, decision or result in the first line. Skip the preamble and don’t restate the question.

Budget length by context. A glance on a watch, one sentence from a speaker, a short card on a phone. Go longer only when the person asks or the task truly needs it.

Keep detail on demand. Put reasoning, sources and alternatives behind a clearly labeled control instead of inline.

Try it Simulation

What to notice
  1. Both views answer the same question. Compare the word counts.
  2. The card leads with the answer and the action that follows it.
  3. The detail is still there, one tap away rather than in the way.
Rule 02 · Input

Let the moment choose the input

Voice when hands and eyes are busy, typing when it’s quiet or the words must be exact, a tap when the decision is simple. Switching never starts the task over.

No single input is right everywhere. Speaking is fastest while walking or cooking and awkward on a train. Typing is precise but slow on a watch. Confirming a time is quickest as one tap. Offer the input that suits the situation and keep the others within reach.

Voice needs visible state. When the assistant listens alongside another app, keep that app in front, show whether it is listening, working or done, and make stop a single action.

Don’t
AssistantI’m listening…

Your draft is hidden until I finish.

Voice takes over the screen, with no visible way to stop.

Do
Mail · Draft to AlexListening

“…and say I’ll book Juniper for 6:30.”

StopType instead

The draft stays in view. Stop and typing are one tap away.

Best practices

Offer voice, never require it. Make voice the fast path where it helps, and keep a visible text field on devices with a keyboard.

Switch without starting over. Moving between voice, typing and tapping keeps the request and the progress.

Show the microphone state. Distinguish off, listening, working and speaking, and keep stop and mute one action away.

Try it Simulation

What to notice
  1. The email stays in front while the assistant listens.
  2. The control always shows its state: off, listening, working or done.
  3. “Type instead” keeps the words heard so far.
Rule 03 · Focus

Keep one task in front

Give the current task the screen and one next action. Background work reports quietly and waits its turn.

An assistant can run many tasks at once; a person attends to one. Give the task in hand the main view and a single primary action, and keep everything else in a compact activity area.

Background updates shouldn’t steal focus. A price drop or a finished task can wait for a natural pause unless the timing really matters, and nothing should move the button the person is about to press.

Don’t
Dinner: pick a timeConfirm
Price drop! Headphones $179Buy now
Alex replied to youOpen

Three primary buttons. Which one matters now?

Do
Dinner with AlexDoes 6:30 work?

Juniper has a table for two.

Keep 6:30Try 7:00

One decision in front. The price drop waits in the activity row.

Best practices

One primary action. Make the step that moves the task forward obvious, with no competing primary buttons.

Status, not interruption. Show background tasks as small indicators that the person can open when they choose.

Interrupt only when it can’t wait. Break in only for something that loses value if it waits, such as a table that will be released in five minutes, and say why it couldn’t wait.

Try it Simulation

What to notice
  1. The dinner decision owns the view and has one primary button.
  2. Simulate the price drop: it updates the activity row and leaves your focus alone.
  3. Switch tasks with the tabs; each keeps its own state.
Rule 04 · Outcome

Recommend one, keep the rest close

Lead with the best answer, give the reason in a line, and keep alternatives one step away. Compare side by side only when comparing is the task.

A long list of options hands the work back to the person. When the assistant knows the preferences, it should commit to a recommendation, explain it briefly and make the next action obvious.

Be specific about uncertainty. A wall of general caveats helps no one. One clear note about what the assistant doesn’t know, and the question that would settle it, does.

Don’t
Where should we have dinner on Thursday?
Here are some great options near you for Thursday evening! 1. Juniper, a modern bistro with a seasonal menu. 2. Olive Room, a lively Mediterranean spot. 3. Little Table, a casual neighborhood café. 4. Harbor Kitchen, seafood with a view. 5. Sakura House, Japanese food that’s good for groups. 6. The Corner Grill, classic comfort food. Each one has its own strengths, so it really depends on your preferences! Let me know which one you’d like.

Six options and no opinion.

Do
Where should we have dinner on Thursday?
Best fitJuniper

Quiet, a 12-minute walk, and a table for two at 6:30.

Not sure: whether Alex eats meat. Juniper has vegetarian dishes.

Book2 alternatives

One pick, one reason, one honest unknown.

Best practices

Commit to a recommendation. Give the best option a clear position and the action that follows from it.

Explain in one line. State the reason that matters (quiet, close, free at 6:30) and keep the evidence behind a “Why” control.

Name the unknown. Flag a specific gap next to the result instead of burying the answer in general caveats.

Try it Simulation

What to notice
  1. The recommendation and its action come first.
  2. “Why” and the alternatives open in place, without leaving the result.
  3. The one uncertainty is stated plainly, with a way to resolve it.
Rule 05 · Generated UI

Show an interface, not a transcript

When a task has structure, such as dates, places or a draft, generate the controls for it inside a familiar frame instead of describing it in another message.

Chat suits open questions. Once a task has a shape, prose becomes a poor interface: reading a paragraph of times to pick an evening, or asking for a rewrite to change one word. Generate a calendar, a comparison or an editor instead.

Keep the frame stable. Navigation, the task name and the assistant input stay where they were while the content changes, and whatever the person selected or typed survives when the view regenerates.

Don’t
When are we both free next week?
You and Alex are both free on the following evenings next week: Monday the 12th after 7:00 PM, Tuesday the 13th between 6:00 and 8:00 PM, Thursday the 15th from 6:30 PM onwards, and Friday the 16th after 8:00 PM. Wednesday the 14th doesn’t work because you have a team dinner. Which of these would you prefer? Just reply with the day and time and I’ll take care of the rest.

A calendar, typed out as prose.

Do
When are we both free next week?
Both freeThursday 15 · 6:30 PM
Mon12Tue13Wed14Thu15Fri16
Use Thursday

Pick the evening by tapping it.

Best practices

Use the control the data calls for. A calendar for dates, a map for places, a table for comparisons, an editor for text.

Keep the frame familiar. Navigation, task identity and the assistant input stay put while the content adapts.

Never lose the person’s edits. Regenerating a view keeps selections and typed text, and flags anything that needs a second look.

Try it Simulation

What to notice
  1. Schedule, Compare and Edit swap the working view; the frame around them doesn’t move.
  2. Choose another day and an untouched draft updates itself.
  3. Edit the message first, then change the day: your words are kept and flagged for review.
Rule 06 · Control

Ask before acting, then report what really happened

Show exactly what will change before the assistant acts. While it runs, show real progress. When it stops, say what succeeded, what didn’t and what’s left.

Proposed, in progress, waiting for input, done, failed and partly done are different states, and each needs its own words and controls. Never say “Done” about something that is still running or quietly failed.

Agents increasingly work for minutes, not seconds. Long work needs a visible plan, steps that tick off as they finish, a stop button that keeps working, and a short summary at the end. Not a spinner followed by a wall of text.

Don’t
Book dinner with Alex for Thursday.
All done! 🎉 I’ve taken care of everything for your dinner with Alex on Thursday. Enjoy your evening!

“Done”, but the restaurant hasn’t confirmed.

Do
Book dinner with Alex for Thursday.
2 of 3 doneDinner with Alex
  • Done: Invite sent to Alex
  • Done: Added to your calendar
  • Waiting: Juniper hasn’t confirmed the table yet
Call Juniper

What’s done, what isn’t, and what to do next.

Best practices

Show the change before approval. Name who and what is affected, with the exact values, right next to the approve button.

Make long work visible. List the steps, update them as they finish, and keep stop available throughout.

Report the real result. Separate what succeeded, what failed and what still needs the person, with a next action for each.

Try it Simulation

What to notice
  1. Before you send, the card shows who, where and when, and nothing has happened yet.
  2. After you send, each step reports its own state, and Stop works until the last one finishes.
  3. The table stays “waiting” until Juniper confirms. Nothing claims success early.
Rule 07 · Continuity

Carry the task, not the chat

When someone moves from voice to screen or from phone to laptop, bring the task with them (choices, drafts and progress), not a transcript to scroll back through.

Switching devices shouldn’t mean starting over, or reading back through a conversation to find where things stand. Open the task at the same step, with the same selections and the unfinished draft exactly as it was left.

Be clear about what is kept. Show when a change is still syncing, never overwrite a newer edit with an older one, and keep private details off shared screens.

Don’t
Welcome back! Here’s everything we discussed about dinner with Alex: 47 messages. Scroll up to pick up where we left off.

The task is in there somewhere.

Do
Continued from your phoneDinner with Alex

Thursday 6:30 PM · Juniper

“Hi Alex, how about dinner…”

Finish the draft

Same step, same draft.

Best practices

Resume at the same step. Restore selections, unfinished input and progress, not the conversation history.

Adapt the layout, keep the meaning. Use the new device’s space and input while the task stays recognizably the same.

Be explicit about sync and privacy. Show pending sync, protect newer edits, and keep private content on personal devices.

Try it Simulation

What to notice
  1. Change the time or the draft on the phone, then switch to the laptop.
  2. The laptop opens at the same step with the same values. There’s no history to scroll.
  3. The layout changes; the task doesn’t.
In practice

Across devices

The same task on six kinds of device. Screen size is only one factor: viewing distance, input, shared or personal use and available attention all change how each rule applies.

Phone

Input
Touch · voice · keyboard
Context
Personal and in hand, often on the move. Attention comes in short bursts.

The seven rules on this device

  1. 01Brevity

    A short card: the answer in one line and one button.

  2. 02Input

    Voice and typing are both one tap away; the result stays visible when the keyboard opens.

  3. 03Focus

    The current task sits above the assistant input; background tasks fold into a compact activity row.

  4. 04Outcome

    One recommendation with its action within thumb reach; alternatives a tap away.

  5. 05Generated UI

    Full-width calendars, maps and editors. Let them scroll rather than cramming one screen.

  6. 06Control

    Review the exact change before approving. Dismissing a notification never counts as approval.

  7. 07Continuity

    Hand off to a laptop at the same step with the same draft; voice-started tasks arrive as editable views.

Computer & tablet

Input
Keyboard · pointer · touch · voice
Context
Personal and usually seated, with sustained attention and precise input.

The seven rules on this device

  1. 01Brevity

    More room is not a reason to say more. Keep the answer short and the detail collapsible.

  2. 02Input

    A text field is always visible; voice gets a shortcut and a visible stop.

  3. 03Focus

    One active workspace. Other tasks live in a side activity panel, never in competing windows.

  4. 04Outcome

    Use the space for evidence on demand or a real side-by-side comparison, not a longer list.

  5. 05Generated UI

    Generate richer tools, such as tables, maps and editors, inside the same assistant frame.

  6. 06Control

    Show recipients and values in full before approval. Pressing Enter in a field must never approve.

  7. 07Continuity

    Open exactly where the phone left off, and flag any edit that is still syncing.

Watch

Input
Glance · tap · short voice
Context
Personal, on the wrist, read in a two-second glance.

The seven rules on this device

  1. 01Brevity

    A few words and one tap. Anything longer goes to the phone.

  2. 02Input

    Short voice in; a haptic or a single line confirms.

  3. 03Focus

    Only the current step. Background results arrive as separate notifications that can wait.

  4. 04Outcome

    One takeaway. Images, video and comparisons open on the phone.

  5. 05Generated UI

    A compact step, such as picking a time. Never a phone-sized grid.

  6. 06Control

    Approve on the watch only when the full scope fits on the face. Send the rest to the phone.

  7. 07Continuity

    Show progress and the retained choice. Drafts stay on the phone.

Smart glasses

Input
Short voice · simple gesture
Context
Personal and in the field of view, while the world stays in front.

The seven rules on this device

  1. 01Brevity

    One line at the edge of view, or one spoken sentence.

  2. 02Input

    Short spoken turns. Switch to the phone to type when speaking is awkward.

  3. 03Focus

    One prompt at a time; everything else queues.

  4. 04Outcome

    Say or show the main takeaway. Visuals open on the phone.

  5. 05Generated UI

    Small task cards only. Maps and editors continue on the phone.

  6. 06Control

    A glance or a casual “okay” is never approval. Ask for a distinct confirmation.

  7. 07Continuity

    Resume with a short cue that names the task and the retained choice.

TV

Input
Remote · push-to-talk · phone handoff
Context
Shared and across the room. Everyone on the sofa can read it.

The seven rules on this device

  1. 01Brevity

    Readable from the sofa: one headline and two actions.

  2. 02Input

    Push-to-talk on the remote; type on a paired phone.

  3. 03Focus

    One large panel with a clear focus target. Background tasks sit behind an activity entry.

  4. 04Outcome

    One recommendation. Don’t autoplay generated media while someone is deciding.

  5. 05Generated UI

    Simple panels like a date picker. Dense tables and forms move to a personal device.

  6. 06Control

    It’s a shared screen: keep message text and recipients private, and approve on the phone.

  7. 07Continuity

    Show a summary that’s safe to share. Private edits continue on the phone.

Screenless device

Input
Voice · sound and light cues · physical mute
Context
Shared or personal, with no screen. Everything is heard.

The seven rules on this device

  1. 01Brevity

    One sentence, then stop. Offer “more” instead of reading on.

  2. 02Input

    Clear start and stop sounds, and a physical mute that always works.

  3. 03Focus

    One spoken thread. Unrelated updates wait for a pause.

  4. 04Outcome

    Speak one recommendation and name the replies: “Book it, another place, or stop?”

  5. 05Generated UI

    Turn structure into short spoken steps with repeat, back and stop. Send maps and editors to a phone.

  6. 06Control

    Read back the action and values, then require an explicit approval phrase. Silence is not consent.

  7. 07Continuity

    Recap where things stand in one sentence and offer to continue on a named device.

Compare all devices
RulePhoneComputer & tabletWatchSmart glassesTVScreenless device
01BrevityA short card: the answer in one line and one button.More room is not a reason to say more. Keep the answer short and the detail collapsible.A few words and one tap. Anything longer goes to the phone.One line at the edge of view, or one spoken sentence.Readable from the sofa: one headline and two actions.One sentence, then stop. Offer “more” instead of reading on.
02InputVoice and typing are both one tap away; the result stays visible when the keyboard opens.A text field is always visible; voice gets a shortcut and a visible stop.Short voice in; a haptic or a single line confirms.Short spoken turns. Switch to the phone to type when speaking is awkward.Push-to-talk on the remote; type on a paired phone.Clear start and stop sounds, and a physical mute that always works.
03FocusThe current task sits above the assistant input; background tasks fold into a compact activity row.One active workspace. Other tasks live in a side activity panel, never in competing windows.Only the current step. Background results arrive as separate notifications that can wait.One prompt at a time; everything else queues.One large panel with a clear focus target. Background tasks sit behind an activity entry.One spoken thread. Unrelated updates wait for a pause.
04OutcomeOne recommendation with its action within thumb reach; alternatives a tap away.Use the space for evidence on demand or a real side-by-side comparison, not a longer list.One takeaway. Images, video and comparisons open on the phone.Say or show the main takeaway. Visuals open on the phone.One recommendation. Don’t autoplay generated media while someone is deciding.Speak one recommendation and name the replies: “Book it, another place, or stop?”
05Generated UIFull-width calendars, maps and editors. Let them scroll rather than cramming one screen.Generate richer tools, such as tables, maps and editors, inside the same assistant frame.A compact step, such as picking a time. Never a phone-sized grid.Small task cards only. Maps and editors continue on the phone.Simple panels like a date picker. Dense tables and forms move to a personal device.Turn structure into short spoken steps with repeat, back and stop. Send maps and editors to a phone.
06ControlReview the exact change before approving. Dismissing a notification never counts as approval.Show recipients and values in full before approval. Pressing Enter in a field must never approve.Approve on the watch only when the full scope fits on the face. Send the rest to the phone.A glance or a casual “okay” is never approval. Ask for a distinct confirmation.It’s a shared screen: keep message text and recipients private, and approve on the phone.Read back the action and values, then require an explicit approval phrase. Silence is not consent.
07ContinuityHand off to a laptop at the same step with the same draft; voice-started tasks arrive as editable views.Open exactly where the phone left off, and flag any edit that is still syncing.Show progress and the retained choice. Drafts stay on the phone.Resume with a short cue that names the task and the retained choice.Show a summary that’s safe to share. Private edits continue on the phone.Recap where things stand in one sentence and offer to continue on a named device.

About this guide

A working draft by Richard Q, last updated October 2026. These rules are opinions rather than standards, and they will change as assistants do.

Disagree with a rule, or have a better example? Open an issue on GitHub.