26 October 2026

Just talk to it: the bicycle for the mind, finally

For forty years we've had to learn the computer's language. Now it has learned ours. I think that's when the bicycle for the mind really starts.

Main point: For my whole career, the way people used computers was the GUI: windows, icons, menus, buttons. I built that career on the UX of those interfaces. But now the computer understands our language. I think that is the real start of what Steve Jobs called a bicycle for the mind, and assistants like Grok Bot are where it begins.

We always had to translate

Steve Jobs said the computer was like a bicycle for the mind. He was right about the potential, but we still had to pedal hard. Every interface, from the command line to the touchscreen, was a translation layer between us and the machine. Good UX made that translation easier. It never made it go away.

The desktop borrowed the office

Early personal computers needed a story people could follow, so we got a desk, a bin, folders and documents. People knew how an office worked, so they could guess how the computer worked. It was one of the best design decisions ever made, and it was still a translation.

AI borrowed the chat window

When AI went mainstream, it arrived as a chat box. Most of us already lived in WhatsApp and text messages, so typing to software felt normal straight away. It also framed the AI as someone on the other end of a conversation.

Now it knows our language

With Grok Bot I can just talk. Not type, not tap through menus, just speak, the thing we are pretty much born able to do. On my iPhone it is one press of a button. There is nothing left to translate. That is the potential the early computer industry saw but couldn't quite reach.

It doesn't just talk, it does

Understanding is only half of it. My bots already read and draft my email, join my meetings, run jobs on a schedule while I'm away, and build me live pages like reports and dashboards. They keep my cards and logins in a vault so they can fill in forms without me pasting passwords into chat. And the ability for a bot to phone people for me is on its way. You say what you want, and the AI deals with the apps.

The twist: the office is back

Once you can talk to a bot, you start giving it a job. A PA. A Chief of Staff. A Coach. I do exactly this: I have bots for engineering, coaching, marketing and running my projects, each with its own role. We left the office analogy behind with the chat window, and it has walked straight back in. Only this time it isn't the furniture, it's the people.

The bicycle, finally

We all have more ideas in our heads than we ever get round to. Most of them die in the translation: the apps, the forms, the admin. When the computer understands us and can act for us, that gap starts to close. That's the bicycle for the mind I think we are only now starting to ride.

Read more

Why roles work

Giving a bot a role sets expectations. You know what a PA does and what a Coach doesn't. It's the same trick as the desktop: borrow a structure people already trust.

What still needs designing

Talking is easy. Trust is harder. If the AI is the interface, it needs to show its work, ask before doing anything that can't be undone, and check with you before anything goes out in your name. That's the UX problem I'm most interested in now.