Issue 005 · 5 min read
A role is rarely one task. It is visible output plus context, judgement, relationships, escalation and responsibility. If AI makes the output easy, the hidden work becomes easier to miss, not less important.
Rather listen?
Skip if you like
An AI assistant is a tool you talk to in plain language, like a fast, very literal colleague who has read a great deal but knows nothing about your job until you tell it. It can draft, summarise and suggest, but it does not decide, and it can be confidently wrong.
A prompt is simply what you type or say to the assistant: your request, plus any background and examples you give it. The clearer and more specific the prompt, the more useful the answer, so treat it like briefing a new starter, not typing a search.
A context window is how much the assistant can hold in mind at once: your instructions, the document you pasted, and the conversation so far. When a chat gets long it starts to forget the earliest parts, so for a big task give it the key facts again rather than assume it remembers.
Start here
Newly announced
Being able to produce the visible task is not the same as owning the judgement, context or responsibility around it.
See the detail and the sources →Newly announced
A finished-looking deck or document can hide weak context. The review has to happen before polish makes it feel settled.
See the detail and the sources →Newly announced
When the tool follows the work for longer, the human checkpoint needs to be designed into the workflow rather than remembered at the end.
See the detail and the sources →
The one that mattersWhat's genuinely new
The week's reviewed signals all point in the same direction: AI is moving closer to live work, longer workflows and tasks that used to sit inside another role.
What the makers claim
Providers describe capability and convenience. The Human Bit frame is different: capability changes what can be handed over, not what should be handed over without a checkpoint.
Where it helps
Tasks where the visible output is clear and the hidden context can be named, supplied and checked before the result changes anything real.
Where it doesn't
Tasks where trust, money, privacy, safety, reputation, access or a promise to another person depends on context that is not in the prompt.
What remains yours
OpenAI classified a substantial share of occupation-specific work messages as tasks historically associated with another occupation.
Before automating a task, write down the visible output, hidden context, judgement, relationship risk and human checkpoint.
Try this
One task feels ready to automate, but the work around that task may include context, judgement or responsibility that is not visible in the output.
Draft the visible output, list assumptions, organise context and surface the points that need a person to decide.
Name the hidden context, decide what matters, understand who is affected and approve the checkpoint before anything is sent or changed.
Pick one task that looks easy to automate
Write the visible output in one sentence
List the hidden context a good human would know before doing it
Name the judgement call and who is affected if it goes wrong
Place a human checkpoint before the output changes something real
If the task touches trust, money, privacy, safety, reputation, access or a promise to another person, keep the checkpoint close.
The Human Lens · what stays yours
The goal is not to protect every old job exactly as it was. Some work should change and some tasks should stop wasting people's time. But the useful question comes before the cut, before the workflow and before the new tool: what is the work behind the output?
One question
See you next Monday.
Bring it back to your work
Bit starts from this issue, then asks you enough about your own work to make it worth acting on. If the honest answer is that none of this touches your job yet, it will tell you that too.