We Need To Forget How We Worked

Description A reflection on how AI, tools, and connected context are changing the interface of work from manual operation to clear direction.

Post Draft

We need to forget how we worked.

That sounds dramatic, but I think it might be true.

The interface for getting things done is changing massively. For most of our lives, work has meant operating software. Open the app. Click the thing. Move the file. Find the tab. Copy the text. Paste it somewhere else. Build a little bridge between one system and another using your own attention.

That has been the interface.

But now the interface is starting to become language.

Text first. Voice probably soon after.

And the weird thing is that we are not habitually used to it yet. It still feels strange. It feels clunky. Some part of us still believes we are meant to click things around. We feel like real work happens when our hands are moving across interfaces.

But maybe that is already old.

Maybe the work is becoming: can you clearly say what you want?

If the system is connected to the tools, the context, the files, the data, the workflows, then the input changes. You do not need to manually operate every surface. You need clarity of intent. You need to describe the deliverable. You need to give the system enough context to act.

That is fascinating.

Because once tools can actually do things, not just answer questions, the productivity curve gets weird. MCP-style connections, agents, workflows, tool access, context windows, memory, files, publishing systems, design systems, codebases. All of these things start to become reachable through language.

And if productivity is output divided by input, the ratio can become completely mad.

Crazy fucking levels of productivity.

Not because the human disappears. That is too simple. More because the human’s job moves up a level.

The human becomes clearer.

Or has to.

The work becomes less “operate this app” and more “define the right outcome, connect the right context, create the right workflow, review the result, debug the system, and run it again.”

So what matters?

Clear thinking. Crystal clear thinking. Systematic thinking. Building. Debugging. Taste. Review. Knowing what good looks like. Knowing what is worth doing in the first place.

Work needs to be redefined from the ground up.

Maybe the old unit of work was the task. Maybe the new unit of work is the deliverable.

A goal creates a strategy. A strategy creates projects, milestones, or value engines. Those create workflows. The workflows connect to tools and context. The tools produce outputs. The outputs get reviewed, improved, and folded back into the system.

That feels closer to the first principles of work now.

Not “what do I need to click?”

But:

What is the goal? What is the deliverable? What context does the system need? What tools should it use? What process should it follow? How will I know if the output is good? How do I make the loop better next time?

This is a very different way of working.

And it is going to feel uncomfortable, because we are carrying old muscle memory into a new environment. We are used to proving work through friction. Through visible effort. Through the exhaustion of moving things around manually.

But the future of work may feel lighter than that.

Not easier exactly. Maybe sharper.

Less friction, more clarity.

Less operating, more directing.

Less clicking, more thinking.

And there is something quite fun in that. Still confusing. Still messy. Still early. But fun.

Because if the interface changes, everything around work changes with it.

The processes change. The skills change. The way businesses compound changes. The way one person creates leverage changes.

We should probably stop trying to make the new world fit the old habits.

We need to forget how we worked.

And then learn how to work again.