I always felt uneasy about tools that split your thinking apart

What "juggling five tools well" really meant

As a QA engineer working on-site through SES (contract staffing in Japan), I've worked at more than 100 companies. Different industries, different sizes, different tools — but wherever I went, I saw the same scene.

An idea sketched out on a whiteboard would get copied by hand onto a kanban board once the meeting was over. A structure organized in a mind map sat there, never reflected in task management. People spent time just moving between three tools, trying to remember "where did I even write that idea down."

Brainstorming, task management, structuring, documentation — each a good tool on its own. The problem was that people were carrying information between them by hand. And that manual work never showed up in any estimate.

Before anyone noticed, managing the tools themselves had become part of the job, and the people who could juggle five of them skillfully were called "capable." But was that really proof of competence, or were the tools simply offloading their own work onto people? That discomfort never went away.

The gap between thinking and doing

Time isn't the only thing lost when you copy something by hand.

The reasoning behind a mind map — "I extended this branch because..." — never makes it into a task's text field. The sense of priority, the nuance a spatial layout used to convey, all of it disappears the moment it's transferred. What's left is just a list of "things to do."

So weeks later, someone looking at nothing but that list asks, "wait, what was this even for?" And each time, someone has to dig back through memory and explain it all over again.

Thinking and doing were meant to be one continuous flow, but the tools cut them apart at the seam. A lot of what got written off as "that person just isn't good at managing things" was really a problem with the structure of the tools.

So we put them in the same place

In WeProcess, the tools for expanding your thinking and the mechanisms that drive execution live in the same place. Whiteboard, kanban, and mind map aren't treated as separate tools — they're treated as one continuous thinking space. That's been the design principle from the very start.

Where you start is up to you. The moment you create a project, both a whiteboard and a task board already exist. Some people start by spreading ideas across a blank canvas; others line up tasks first and stop to redraw the structure partway through. We don't think either order should be forced on anyone.

On top of that, a structure you've built in the mind map can sync straight into tasks, with no copying involved. The goal is to eliminate transcription itself.

90% of what we learn never gets used

This next part is a different story.

People feel satisfied the moment they think they "get it" — even though there's a huge gap between understanding something and actually being able to use it on the job. And putting what you've learned into practice always takes a bit of effort. Those small delays pile up, and most of what we learn ends up sitting unused, quietly going to waste.

There's another catch: the moment we learn something, we unconsciously start treating it as "ours." And once we're holding onto it, we stop reusing it and stop sharing it. But knowledge doesn't create value while it's being clutched. I think of it less as a "stock" to hoard, and more as a "flow" — something that only means anything once it's circulating.

Without someone willing to lend a shoulder, no one can stand on it

There's a saying: "standing on the shoulders of giants." Knowledge, by nature, is something that lets us see farther by passing from person to person.

But without someone willing to lend a shoulder, no one can stand on it. And in reality, lending that shoulder rarely comes with any reward. Whether you contribute code to an open-source project, present at an internal study session, or write an article, very little comes back to the person who put it out there. So the logic becomes, "if putting it out there doesn't pay off, why bother?" That's not laziness — it's a perfectly rational conclusion.

Knowledge doesn't go unshared because people lack the right mindset. It goes unshared because the structure doesn't reward sharing.

That's why, in WeProcess, you can package your own way of working as a template and publish it. When a good template gets a "like," the person who made it earns points. Those points can be cashed out. And the person who gave the "like" earns points too, because finding and recognizing something good is its own kind of contribution.

We want to build a foundation where knowledge doesn't sit dormant in someone's head, but keeps flowing from person to person. That should be part of the same connected space too.