You can describe a job the way you’d describe it to somebody covering your desk for the afternoon. Find the last thing Marcus sent about the lease. Clear the three newsletters at the top. Move Thursday’s call with Dana to Friday morning. Point works out what you meant and does the work. How far that work goes before it comes back to you is a setting you hold.
- The saving is in the gap. Finding a thing and doing something to it become one errand instead of two.
- A request lands when it names the thing, names the action, and says the limit. Almost every one that comes back wrong was missing the third.
- The shortcuts you’re already fast with are real speed. That speed is work you did, credited to the software.
- Asking for something and authorizing it are separate questions. A setting decides what arrives finished and what arrives waiting, rather than your sentence.
What counts as a request
A request is a sentence with a verb in it that names an outcome. That’s the whole test, and it’s the line between this and searching.
Put the two side by side on the same errand.
Marcus lease is a query. It hands you back a list of things that matched, and the list is where your work starts.
Draft a reply to Marcus about the lease saying we can sign Friday, and don’t send it is a request. It hands you back a draft.
Both begin with the same act of half-remembering. Both depend on the same ability to find a thing when the subject line and the month are gone. Only one of them ends with the job done. How that finding works, when your memory of the message is approximate, is searching your inbox by meaning. Where the box lives and what else it reaches is universal search with one shortcut. This guide is about the other half: the verb. One near neighbor is worth knowing early, before you meet it by accident. Some sentences have their answer inside a file rather than inside a message, the sort you’d otherwise open a forty-page statement to settle. That one is asking questions of your attachments and PDFs.
Requests run from trivial to compound. Seeing the range helps you decide what to trust one with.
One object, one action. Archive this. Snooze this until Monday. The kind of thing your hand does already, and the kind where a sentence is usually the slower route.
An object you haven’t opened yet. Pull up the last thing the county sent about the permit. Here the sentence does something a click can’t, because you’d have to find the thing before you could point at it.
A set. Clear everything from the payroll service since the first of the month. One sentence, an unknown number of messages, and no counting.
A chain. Find Priya’s last message about the audit schedule and put a reminder on Thursday to answer it. Two jobs in different parts of the product, joined by a pronoun. That’s the shape most of an ordinary morning actually has.
A chain that leaves the mailbox. Move tomorrow’s 9:00 with Dana to Friday and tell her why. That one crosses into the calendar and back out to a message, and what happens on the far side of it is moving a meeting that is already booked.
You can say the same sentence instead of typing it, on the mornings your hands are on something else. That’s talking to your inbox, hands-free, and everything below holds either way.
Why one sentence beats the sequence of clicks
The saving is in a step nobody counts. Typing is often slower than clicking, so the keyboard is the wrong place to look for it. The clearest account of that step was written forty years ago, by the people who were arguing for clicking.
In 1985, Edwin Hutchins, James Hollan and Donald Norman published Direct Manipulation Interfaces in the journal Human-Computer Interaction. They worked at the Institute for Cognitive Science at the University of California, San Diego. It’s one of the founding defenses of the point-and-click interface every mail program on your machine still uses. It names the cost too.
They split the work of using any software into two crossings. “The gulf of execution is bridged by making the commands and mechanisms of the system match the thoughts and goals of the user. The gulf of evaluation is bridged by making the output displays present a good conceptual model of the system that is readily perceived, interpreted, and evaluated.”
The first gulf is the one you cross on the way in. You have an intention, in your own terms, about your own business: I’m done with the county stuff. The software takes a search string, a set of checkboxes and a button. So before anything happens, you convert what you meant into what the program understands. That conversion is unpaid, invisible and constant. It’s the reason a five-second job takes forty seconds.
The authors are precise about who does that conversion, and this is the sentence worth carrying out of the paper: “It is always the case that the user must generate some information-processing structure to span the gulf. Semantic distance in the gulf of execution reflects how much of the required structure is provided by the system and how much by the user. The more that the user must provide, the greater the distance to be bridged.”
A plain-language request moves that structure across the line. You supply the intention, in the words you already had it in. The translation becomes somebody else’s problem.
There’s a second reason, and the same paper puts it more bluntly than any AI company would dare. Pointing at things is excellent for one visible thing at a time, and poor at everything else. “Direct manipulation interfaces have difficulty handling variables, or distinguishing the depiction of an individual element from a representation of a set or class of elements.” And the recommendation that follows: “But not all things should be done directly. For example, a repetitive operation is probably best done via a script, that is, through a symbolic description of the tasks that are to be accomplished.”
A description of a set is exactly what a sentence is good at. Everything from the payroll service since the first of the month has no number in it, no scrolling, and no risk that you missed one at the bottom. Say it once and it’s done.
The objection from people who are already fast
The strongest pushback on all of this comes from owners who are genuinely quick in their mail. They know the shortcuts. They can clear a screen without looking, and a box you type sentences into looks like a step backward.
The speed is real. The paper anticipated the argument and answered it in 1985: “Automatization does not reduce the semantic distance that must be spanned; the gulfs between a user’s intentions and the interface must still be bridged by the user. Although practice and the resulting expertise can make the crossing less difficult, it does not reduce the magnitude of the gulfs.”
Then the line that settles it. The fluency you feel “depends only on how much practice a particular user has with the system and thus gives the system credit for the work the user has done.”
You’re still doing the translation. You’ve simply done it so many times that you stopped noticing yourself doing it, the way a driver stops noticing the gear change. That fluency is worth having, and it costs something. It also has three specific holes in it that show up in a small firm every week. It covers the work you do daily, so the thing you do twice a year sits outside it, because you never practiced that one. It’s fluency per program, so the job that spans two programs sits outside it as well. And it goes missing on the afternoon you’re tired, distracted or on somebody else’s laptop, which is reliably the afternoon something matters.
The three parts of a request that lands
Nearly every request that comes back as something you didn’t want is missing one of three parts. They’re worth having as a habit. The habit takes about a week, and then you stop thinking about it.
Name the thing the way you would to a person who was in the room. Names, rather than keywords. The last thing Marcus sent about the lease beats lease, for a reason that has nothing to do with cleverness: only one message can be it. The date, the subject line and the exact wording can all stay fuzzy. You need enough that a second candidate never exists. Where more than one genuinely fits, Point asks instead of guessing. One tap settles it, and that tap is cheaper than discovering three weeks later that the work went against the wrong file.
Use a verb with an outcome in it. Archive, draft, schedule, move, remind, snooze, add. Deal with the Hollis thread is a mood, and a mood leaves the next step open. The test is the one you’d apply to a temp: could somebody carry out this sentence and get straight on with it? Where they’d come back with a question first, the sentence has one more part to add.
Say the limit. This is the part everyone drops. You’d say it out loud to a person without thinking, and somehow it never reaches the keyboard. But don’t send it. Only the ones from this month. Put it on Tuesday, not Monday, she’s out. A limit costs you four words in advance and saves you a correction afterward, and the correction is always the expensive one.
Two smaller habits go with those.
Write it as a sentence. Most people arrive with a decade of keyword reflex, and keywords produce lists. Verbs produce outcomes.
And when the sentence starts growing conditions, exceptions and an unless, stop. You’ve moved from describing a job to describing a policy, and a policy wants a different instrument. Which brings up the thing worth sorting out before you start.
Four things people say into the same box
Four different requests get typed into the same place, and they get muddled constantly. The words that separate them are small: now, when, always, by.
Now. Archive the three newsletters at the top. A one-off ask, carried out against what’s there at this moment, finished when it’s finished. That’s this guide, and it’s the one of the four that leaves nothing behind.
When. Tell me the moment the signed engagement letter comes back. That’s a standing instruction to watch, and it lives on until you end it. The whole of how those work, and which of your open loops actually deserve one, is asking to be told when something happens.
Always. Sign anything going to a client with my cell number. That’s a preference about how work gets done. Point keeps it as a plain sentence you can read back and change later. How Point learns your habits from one sentence covers what gets remembered and how to correct it.
By. Remind me Thursday to call the auditor. That’s a task with a date on it, which is a different object again, and adding one in five seconds is the shortest route to it.
The one that catches people is saying now when you meant always. Clearing today’s newsletters clears today’s newsletters. Tomorrow’s arrive as usual, and so do April’s. If you find yourself typing the same sentence on Monday mornings, that’s the signal you asked for the wrong shape.
Where the doing stops
Your sentence decides what Point does. A setting decides how far that goes before it reaches you. Keeping those two apart is the difference between using this comfortably and being nervous about it.
How far Point goes is held separately for each kind of work. Each of them has three positions: suggest only at the bottom, handled outright at the top, and review in the middle. A new account starts every kind of work in the middle. So the ordinary experience of asking for something is that the work comes back done and waiting on your yes. The reply is written. The time is found. Nothing has left the building. Where each kind of work belongs on that setting, and the two questions to ask about your own firm before you move one, is setting how much your inbox does on its own.
Two consequences follow, and both are worth knowing before your first request rather than after.
Asking leaves the setting where it is. The same request comes back as a draft that waits or as a message that goes, depending on where that kind of work sits today. The setting decides that, so look there when you want to know in advance.
And an action of a sort Point hasn’t done for you before gets its own moment of approval, the first time round. That’s approving anything new before it acts.
The half of the interface that gets quieter
Here’s the thing nobody mentions about making the way in easy. It comes straight out of the second half of that 1985 sentence.
A sequence of clicks is its own receipt. You saw the search results, you saw the checkboxes fill, you saw the count on the button. By the time the job was done you’d watched it happen, and the watching was free, because it was made of the same clicks as the doing.
A sentence works differently. You said a thing, and a moment later it was handled. The execution gulf got narrow. The evaluation gulf, the crossing back out where you work out whether what you wanted is what occurred, stayed exactly as wide. Cross one cheaply and the other one is suddenly the expensive one.
Which is why the record of what Point did is the other half of the same interface, rather than an audit feature for nervous people. It does the job the vanished clicks used to do. Every action taken for you is written down with what it was and when, and Point’s own moves can be turned down or put back from there. The activity log behind every action is what that surface holds, and undoing what Point did is where its reach ends. That matters most for the one action it can’t cover at all. A message that has reached its recipient sits on a machine you don’t own, and nothing in any product brings it back.
The practical version is small. In your first week or two, read the log at the end of the day. You’re calibrating, and that habit is much cheaper to build on an afternoon when nothing surprising happened.
When pointing at the thing is still the right move
A plain-language request has a range, and outside it people end up describing to a computer something they could have touched.
The rule is simple enough to hold in your head. If the object is on your screen and the action is one gesture, use the gesture. Archiving the message you’re reading by describing it is the long way around, and the paper’s own authors would say so.
If the thing is a set, a condition, or a chain of steps, describe it. That’s where clicking runs out, and it’s the case their own carve-out was written for. As they put it at the end: “When we give up the conversation metaphor, we also give up dealing in descriptions, and in some contexts, there is great power in descriptions.”
Two more boundaries worth naming, so you don’t spend a week finding them yourself.
Sometimes what you want is a hard, mechanical rule that fires identically forever, of the kind an insurer or a professional body might one day ask you to evidence. Your mail provider’s own filters are exact and dull, and exact and dull is the correct specification for that particular job.
And saying what you want is the part that stays yours. The 1985 paper is direct about this: “It is important not to equate directness with ease of use. Indeed, if the interface is really invisible, then the difficulties within the task domain get transferred directly into difficulties for the user.” Point drafts the message to the client about the extension. Whether to give them one is your call. When the sentence is hard to write, check which of the two you’re actually stuck on, because one of them is a software problem.
Common questions
Do I have to phrase it a particular way?
No, and there’s no syntax to memorize. The three parts do the work: a thing that only one item could be, a verb with an outcome in it, and the limit you’d say out loud to a person. When a request comes back as something you didn’t want, the missing part is nearly always the limit, because it’s the one that feels too obvious to type.
What happens if Point misunderstands me?
Two different things, and they have different remedies. Where the sentence is genuinely ambiguous, Point asks which one you meant instead of choosing, and one tap settles it. Where the sentence was clear and the reading of it was wrong, you get finished work that’s wrong, and what that costs you depends entirely on the setting for that kind of work. On review it’s a preview to correct. Above review it’s an entry in the log to reverse. Your configuration decides which of the two you meet, rather than your wording.
Is this the same thing as search?
No, and the difference is where the sentence leaves you. A search hands you a list and keeps the work. You still have to open, decide and act. A request hands you the finished thing. Most of what people call searching their inbox is really the first half of an errand, and the second half is where the morning actually goes. Finding by meaning rather than by exact words is its own subject, and it’s next door.
Can one sentence do more than one thing?
Yes, and the chains are where this stops being a novelty. Find the thing, then act on it, then leave something behind: that’s one sentence covering three surfaces that would otherwise be three separate visits. The limit is the conditions rather than the number of steps. Once the sentence starts sprouting them, you want a standing instruction rather than an ask.
Does asking for something count as permission for it?
No. The request and the permission are two separate controls, and mixing them up is the most common way people are surprised by this. Your sentence says what should happen. The setting for that kind of work, which is on review out of the box, says how much of it happens before you see it. You can ask for something confidently and still have it come back waiting, because the setting stayed where it was.
How do I know what I am allowed to ask for?
Describe the outcome in the terms of your own business rather than in the software’s terms, and find out in one sentence. That’s the cheap part: an ask that Point can’t do costs you six seconds, and hunting for a menu that may not exist costs more. If you’d rather see the whole territory first, everything Point does is the full inventory, and most of it turns out to be reachable from the same box.
The short version
A plain-language request is a sentence with a verb in it, and what it buys you is the translation step. That’s the one where you convert what you meant into what the program accepts, and you’ve been paying it so long you stopped seeing the bill. Name the thing precisely enough that only one item fits, use a verb with an outcome, and say the limit. Keep now apart from when, always and by, because those three want a watch, a remembered habit and a task. Then remember that making the way in easy makes the way out matter more, so read the log while nothing is going wrong. Everything the sentence can reach is on the benefits page, and the rest of what Point does with your mail runs on the same principle: you say it the way you’d say it, once.