Finding the task is the easy half

Here’s a work email, in full:

“Ridgeway declined our offer. Let’s pursue Alderton.”

Just seven words are needed to do two very different jobs. The second sentence is a task. Somebody has to go and pursue Alderton, and that belongs on a list where it can be assigned, chased and closed. Every AI inbox tool on the market will find it. We find it too, and it becomes a DoBox item.

The first sentence is a fact about the world that just changed, and it needs to reach the people who’ll act on it later.

Today that sentence has nowhere to go.

The task is the part everyone solved

Pulling commitments out of messages is now table stakes. A dozen assistants sit on top of Gmail and Outlook extracting action items. The competition on that ground is about accuracy and interface, not about whether it can be done.

So what happens to everything that isn’t a task? Your filters have a category for spam and one for newsletters. There’s no category for a statement of fact that arrived in a message and changed what the company knows.

Ridgeway declined. A customer moved their office. A supplier’s lead time went from four weeks to nine. Someone’s title changed. A contract clause got renegotiated in the eighth reply of a thread.

None of these is a task. They’re things to know, and usually there’s no document where this sort of information is kept. 42% of what a company knows has a single copy, in someone’s head.

Calling it a hidden task is the wrong fix

You could say the first sentence contains an implicit task: update the CRM to show Ridgeway declined. Then the problem disappears, because you already have machinery for tasks. Extract it, route it, done.

That works for one example and falls apart across the rest. Most facts have no home to go into, so a task made from one tells someone to file something where there’s no file. It has no natural owner and no deadline either, so it sits on a list being nobody’s job. Worse, a task that says “update the CRM” asks a person to type in something a machine has already read. Turn every fact into a task and you add manual filing on top of a system that was reading the message anyway.

Facts and tasks are different things and need different homes. A task goes to a list. A fact should go into a knowledge base.

The medium decides how much gets mixed together

A Slack message often has one purpose. Somebody asks for something, or reports something, and the discussion ends.

A long email thread mixes a decision, three facts and a request, and the request is in the fourth reply. Slack threads do this too, just less often. Even a message your filters called social can carry both. A newsletter announcing a breach tells you a fact about a service you use and asks you to change your password, in the same paragraph.

This is why sorting by category, the way mail clients have done for years, gets you a useful start and no further. Category is a property of the message. Task and fact are properties of the sentences inside it.

What a company forgets

Take one of these with nowhere obvious to go: the supplier whose lead time moved from four weeks to nine.

Nobody records it, because no task came attached and no system has a field for it. Six weeks later someone promises a customer a date based on four weeks, and the company misses it. Now it looks like people at the company don’t share information, which is the impression that costs the next deal too.

The information existed. It arrived in writing, in a system the company owns, and was read by at least one person. It just never got transcribed into anywhere another person would look.

That gap isn’t a knowledge management problem in the old sense, where somebody has to remember to write a page. Nobody forgot to document anything. The fact was already written down by the person who sent it. It simply stayed where it landed.

Where we think this goes

Two halves, then. The task goes to DoBox, where someone can assign it and close it. The fact goes into the brain, and workflows are the mechanism that puts it there and keeps it current.

We’re further along on the first than the second. DoBox reads your messages and turns commitments into tracked work today. The brain holds operational knowledge today, and the broader version, where the full picture of a business stays current from its communication without anyone maintaining it, is the direction we’re building rather than something finished.

The seven-word email is why. Half of it has been solved by everybody. The other half is sitting in an inbox right now, already written, in a system the company pays for. The only thing missing is somewhere for it to go without a person retyping it.