Every new tool has a first enemy: the blank screen. Now make the screen spatial. The user is not filling a document, they are placing thoughts in space. Now make it radial, where everything orbits a center and position itself carries meaning. Each layer multiplies the problem, and there is no established playbook for onboarding someone into a spatial, radial thinking system the way there is for a signup form, a settings page, or a notes app. You do not look it up. You build the intuition by iterating, getting it wrong, watching where people freeze, and slowly learning what the interface is actually asking from them.
What I have found along the way is that the issues are the asset. A hard onboarding problem rarely resolves into a patch. It usually resolves into a better architecture, a sharper experience, a new feature, or, best of all, a feature that sidesteps the original problem entirely. This is the story of being wrong twice, and what each wrong turn handed me.
Being wrong twice
The first version I believed in was the AI version. The idea made sense to me: you tell the system what you are working on, and the AI generates the foundational structure of the project. It creates the twelve radial categories around the center, giving the user twelve general places to think from. Not a finished answer, not a completed plan, just the starting structure of the map.
In my head, that solved the template problem before anyone even asked for templates. Why would I hand someone a canned “marketing plan” or “startup plan” when the AI could listen to their actual situation and generate a structure specific to them? But people did not really want to test it. They could understand the idea when I explained it. They could understand that the AI created the twelve categories. They could understand that the goal was to give them a foundation to think from. But understanding the premise is not the same as wanting to step into the product. The ask was still too high: sign in, trust the AI, tell it what you are thinking, wait for the structure, then understand what to do next. It was powerful, but it was not a clean front door.
So I went the other direction. I made a blank map version. No heavy AI premise up front. No demand that you trust the system before touching it. Just open the map and start creating. That was more promising. People could at least see the environment. They could click around. It was closer to the actual object. But it still had the same deeper problem: the map did not explain how to begin thinking inside it.
A blank map does not feel like freedom at first. It feels like exposure. It asks the user to invent the subject, invent the structure, invent the first node, invent the relationship between nodes, and understand the spatial logic of the interface all at once. That is too many first moves stacked on top of each other. People pattern-match it to a mind map, do not see what makes it different, and leave.
Then I posted it to Reddit, and about ten comments came back saying the same thing: we want templates. My first reaction was defensive. The AI already solves the template problem. Tell it what you are working on and it builds the structure for you. What is a template next to that? But the comments kept nagging at me, and eventually I flipped the whole thing around. Maybe they were not asking for templates. Maybe they were asking for a way in. Not a finished project, not a canned workflow, not “pick marketing plan and receive marketing plan.” They were asking for a starting shape. Something that makes the blank stop being blank. They were asking for a path to think.
A path in order to think
That is where thinkpaths came from: literally, a path in order to think.
There are two pieces. The first is the starting structure. For the system to work, a project gets laid out as twelve radial categories around a center. Twelve places to think from. You can build those categories yourself if you already have the idea and its shape in your head, or you can say whatever is on your mind, and the AI figures out the foundational structure for you.
But the important part is what the AI does not do. It does not give you a finished project. It does not answer the whole thing. It does not pretend your thinking is complete before you have even started. It gives you twelve doors, all of them empty, each one a place you can begin thinking from.
The second piece is the thinkpath itself. Off any one of those nodes, you can fan out a way of thinking: a Socratic chain, a 5-Whys path, a steelman path, a claim-assumptions-evidence-opposing-view path. It gives your mind a sequence to move through. And the bubbles arrive empty. That detail is the whole philosophy.
// A thinkpath bubble arrives with a prompt — never an answer.
const bubble = {
method: "5-whys",
prompt: "Why does this actually matter?",
content: "", // ← the hole. only you fill it.
}
Not capture. Not an AI that thinks for you.
There are two obvious categories a tool like this could fall into, and both are wrong. The first is capture: notes apps, transcription tools, mind maps. You have a thought, and the tool records it. The artifact is a history of thinking that already happened.
The second is the current AI default: a machine that thinks for you. Prompt it, and it produces the thinking. Clean demo. Easy screenshot. But it asks a stranger to trust an AI with their reasoning before they have seen a single payoff. Worse, it quietly removes the one thing they came to do, which is think.
What I am building is a third thing, and the empty bubble is how you can tell. The system gives you a structure to push against, but it cannot put a word in your mouth, because what it gives you is a hole you fill. It does not record your thinking after the fact, and it does not do the thinking for you. It scaffolds the thinking while you do it.
Why scaffolding is the right word
I had been reaching for verbs like “shapes your thinking,” but they all felt wrong. They smuggle in coercion, like the software is driving and you are just along for the ride. That is the opposite of the feeling I want.
Scaffolding fixes it. Not loosely either. It is a real idea from learning theory, associated with Vygotsky, about temporary support that lets someone do something they could not yet do alone, and then fades as they gain the ability themselves. The freedom is built into the meaning. Scaffolding is not the building. Your thinking is the building. You can climb it or walk around it. It exists to be outgrown.
And that freedom is not just a marketing claim. It has to be structural. It has to be enforced in the architecture. The recommended starting point is not a wizard or a forced first step. It is a soft suggestion, a good place to begin, not a command. Clicking a node does not cascade edits across the map. One click, one focused action. Freedom of choice is preserved at the interaction level.
// One click, one focused action — never a cascade.
function onNodeClick(node) {
focusOn(node) // soft: frame it, offer a next move
// no auto-fill, no forced wizard, no edits rippling outward
}
The AI’s job is to build scaffolding, never the building. It can generate the twelve categories so you have somewhere to think from. It can suggest a thinkpath tuned to the node you are on. But every category and every prompt it makes still lands as an invitation. You fill it. You decide if it lives. You can ignore all of it and start somewhere else. The AI gets you to the edge of the thought and hands you the pen. The system holds the structure. You hold the thought.
Never blank, never bossy
Concretely, this is what the environment is trying to do. It should never leave you staring at a blank page, and it should never boss you around either.
A blank page asks you to generate from nothing, which is one of the most expensive cognitive states there is. A thinkpath gives you something to react to, and reacting is cheaper and sharper than generating. But because the prompt is empty, the thought is still yours.
Your past thinking stays in view while you work on the next idea. You are not trapped inside a text box pretending the rest of your mind disappeared. The map keeps your accumulated reasoning beside you. The neighborhood appears at a glance too. Hover an idea and its connections light up. Lateral recall, associative recall, context, and relationship are surfaced instantly without pulling you away from the thought you are inside.
And the hardest moment, the first move, gets softened. Not solved by force. Not replaced by a tutorial. Just softened. Here is a good place to begin. That one small gesture matters because in an open environment every direction can feel equally arbitrary. A soft start removes the paralysis without removing the choice.
Think more, not less
This is what all of it is actually for.
There is a whole genre of tool right now built around the idea of a second brain. You copy information from somewhere, paste it in, store it, and let the AI fetch it back later. And every time I look at one, I think: that is a great memory for your AI. But what about you? What about your thinking process? You did not think anything. You moved a thing from one box into another box, and now it is stored so the machine can retrieve it.
I do not want to build a place where you store thoughts you already had somewhere else. I want to build a place where you actually think them. And because you thought them, you remember them differently. It is not a copy-paste tool. It is not paste-a-URL-and-call-it-knowledge. The map is there to amplify your thinking, not to replace it. Every decision in the system is biased toward getting you to think more, not toward letting you think less and go brainless because “the second brain has it now.”
That is the whole bet in one line: never blank, so you always have somewhere to start. Never bossy, so the thinking stays yours.
Where this is going
My guess is that, taken far enough, onboarding stops being a separate thing at all. A mature environment does not have an onboarding mode. It is always quietly offering you a next move, whether it is your first hour or your thousandth. The generated categories, the recommended start, the thinkpaths, the empty prompts: those are not tutorials you graduate from. They are early versions of an environment that always has scaffolding ready and never forces you onto it.
I have not proven the conversion side yet. I have moved the front door. I have not won the argument. But the reframe is the part I am sure of now: the job was never to capture people’s thinking, and it was never to do the thinking for them. It is to build a place that is never blank and never bossy, and then trust people to think, because they were always going to be better at it than the machine.
Building this at thinkspatial.ai. If you have onboarded people into a genuinely new interface — not a new feature, a new shape of interaction — I would love to hear where they froze and what fixed it.
Top comments (0)