Same right argument. One team accepts it; another silently doesn't. Why?
1. The Unease
The logic has no holes. The slides are immaculately crafted. And yet there are moments when those words simply don't land in a team.
There's nothing to argue against. You actually agree. But something stays clogged inside. "I mean, well, it's just that..." — and you can't finish the sentence, because you don't know what you wanted to hold back.
This unease repeats itself across many organizations. The long-tenured person resists, in ways they can't quite articulate, the correct proposal from the new arrival. Calling it "old-guard syndrome" closes the case quickly. But is that really all? Could there be something not being observed, sitting in that gap?
For me, this unease keeps landing in the same place.
History.
2. Right Arguments That Don't Read History
There are two kinds of right arguments, I'd suggest.
One is the right argument that has read the history. It has observed why the current structure took this shape, what constraints made it possible, what failures lie layered underneath — and then, after all that, says: maybe another shape would be better.
The other is the right argument that hasn't read the history. "This is just how it's done." "Best practice is X." "That's how they do it elsewhere." Correct as general statements. But placed without ever asking why the structure in front of us became what it is.
The unease I keep noticing is only the second kind.
The first kind I can listen to, even when its conclusion runs opposite to where we are now. We're looking at the same landscape; they're proposing a different summit. What sits underneath is observation, not the pasting of a template.
The second kind has no observation. In its place, there's an import of the correct answer. A solution that worked in someone else's organization, a solution written in someone's book, a solution presented at someone's conference — transcribed directly onto the context in front of us.
What's happening here may not be a problem of correctness, but a problem with the direction of intelligence.
Intelligence that doesn't observe history, however sharp, doesn't land in context. Intelligence that does observe history can hold strong meaning inside an organization, even when its conclusion seems "ordinary" from the outside.
I'm not rejecting right arguments. I want to place a small reservation against the posture of intelligence that doesn't observe history. When I rephrase it that way, the outline of my unease starts to come into view.
3. Organizations, Code, and Communities All Have History
Every structure has a reason.
Why does this module take this shape? Why is this team in this configuration? Why is the evaluation system designed this way?
The reason doesn't sit only in the original intent. The failures in between, the retreats, the recoveries, the compromises — all of them hold up the current shape. The design intent, the operational accidents, the political constraints, the moments when someone broke, the moments when someone gave up. They've stacked up like strata, and the current structure rests on all of them.
If you only assess the surface without looking at the strata, you usually misread.
When someone dismisses an architecture in one phrase — "this is old" — the layered exploration underneath often goes unobserved. Why did it settle into this form? How many other forms were tried and abandoned? What limits did it hit? Without observation, only the surface gets evaluated.
This isn't only about code. Organizational systems, team customs, community rules — they all hold the same structure, I think. What sits here right now is someone's final point of exploration. If you only see the endpoint, without reading the path that led there, you haven't really observed.
To read history might be the posture of looking at strata, not the surface.
4. Incorrect Answers Are Not Meaningless — Ethics Lives in Hesitation
Branching off from that, there's another thing I want to ask.
I keep getting caught on the idea that "you should just pick the correct answer from the start."
This catch was already inside me. But what gave the catch a shape I could speak from was Uoto's manga Chi. — About the Movement of the Earth (チ。―地球の運動について―). The story follows people in medieval Europe who believed in heliocentrism, died without ever proving it, and yet kept passing fragments to the next generation. By the standards of their time, their observation was "incorrect." They were killed before it could be proven. And yet that strata passed to the next person, and the next, until the way the world was seen had shifted entirely.
A line from the work has stayed with me ever since.
But an incorrect answer doesn't mean it's meaningless.
—— Uoto, Chi. — About the Movement of the Earth (Shogakukan)
Even the moments judged "incorrect" — the strata they produced kept meaning.
The thought of choosing only correct answers looks efficient. No detours, no failures, a straight line to the answer. But isn't that an efficiency that only stands by sacrificing exploration?
Exploration is movement that includes stepping on incorrect answers. Try, miss, return, try again. All of it becomes observation. "It's not here" also becomes a map for the community.
And another line from Chi. stayed strongly with me.
...But when you forget your conviction, you wander.
Wander.
And surely, ethics lives within that wandering.—— Uoto, Chi. — About the Movement of the Earth (Shogakukan)
Ethics lives within wandering — when this line landed, something that had long stayed unworded inside me finally found a place to sit.
For someone who has the correct answer from the start, ethics may not be very necessary. Decisions become answer-checking. Ethics rises in the moment the answer isn't yet known — the moment when observation is still incomplete, and you have to carry the risk of your judgment yourself.
A decision without hesitation is often just following someone else's template. A decision that has passed through hesitation carries the weight of the person who made it. Perhaps ethics only resides at the end of hesitation.
So an organization that refuses to let people step on incorrect answers is also, I'd suggest, one where ethics has a hard time growing. As long as everyone imports "the correct answer," no one carries the risk of their own judgment. No one hesitates, so no one's decision holds responsibility.
Incorrect answers are not meaningless.
Hesitation is not meaningless.
They are the indispensable strata of observation that hold up both future correctness and future ethics.
An organization that imports only correct answers loses its path of observation. When the same correct answer fails to apply in a different context, there's no place to return to — because the organization hasn't recorded, in its own body, how it arrived here.
I sometimes see organizations that take pride in "not spending time on trial and error." That pride is the reverse side of adopting best practices quickly. And yes, it does look efficient. But whether that organization has built the muscle to explore on its own, and the ethics to hesitate on its own, when it faces the next unknown problem — that's a different story.
An organization that has folded up exploration stops the moment a correct answer no longer descends from outside. And an organization that has folded up hesitation loses the source of its ethics.
A community that allows incorrect answers is also, I'd say, a community that holds observability. And one that holds ethics.
5. Replacement That Carries Succession
By here, the natural pushback is: "So we're not allowed to touch existing structures?" That's not what I mean.
I've stood on the side of replacing structures several times — renewing architectures, redesigning evaluation systems, rearranging team compositions. Reform is sometimes necessary.
The problem isn't reform itself. It's the craft of reform.
What I've practiced for a long time is a posture I'd call replacement that carries succession.
- First, read the rationality of the existing structure
- Trace the history of why it took this shape
- Re-perform, inside yourself, the constraints and the optimal solutions of the time
- Observe the heat that's been mixed into it
- Then, separate what should be replaced from what should be held
- Carry the risk of replacement yourself
This isn't a destroyer. A successor as reformer, you might call it.
A successor-as-reformer doesn't deny the past. They place the new structure on the extension of the past. The previous people's accumulation has to be properly integrated into the foundation of the new structure — that becomes the precondition for reform.
Reform without succession often denies history. "This is old." "This was wrong." "It's not best practice." Strong words. But the moment those words come out, the heat of the people who stood here in the past leaves the community. One stratum gets peeled off, from outside.
Heat keeps existing as strata even after the person who held it has left. Replacement that carries succession adds a new layer on top of those strata. Reform without succession is the work of returning the strata to bare ground.
Both look the same if you only look at the result — "they replaced it." But inside the community, the meaning is probably entirely different.
6. History as Love
From here, one step further up in abstraction.
I've held the question "what is love" inside me for a long time, and recently the outline has come into focus.
Love is taking history on yourself.
The object can be anything. A team, a product, code, an organization, a community, a person. Who built the heat into the thing as it stands here today? What failures did they step on? Through what hesitations did it arrive at this shape? Remembering all of that. Respecting it. Carrying it forward.
"Liking" and "love" often aren't separated. But for me, the two have quite different operating principles.
Liking affirms the object's present.
Love takes on the object's history.
Liking can hold in a single moment; love requires a time axis. Who built it up, why it became this way, what exploration sat behind it. In the moments those aren't observed, love thins.
So what is dishonesty?
Not observing history. Not reading context. Not remembering who stood where. Indifference to the strata of the community.
I'm writing this not as personal feeling but as a problem of observation. The question isn't whether someone got hurt — it's whether the community's history has been excluded from the observation apparatus.
I should also put my own danger on the page.
When love for history grows strong, side effects appear. If I don't stay aware of this, I become exactly what I most disliked.
- It tips easily into old-guard worship
- People who don't share the history get held lightly inside me
- "Of course they should understand this" becomes implicit
- When the assumed-shared history collapses, I want to give up explanation and close the circle to those who already understand
The last one is the pattern I find most frightening.
I think deeply on the premise that "we're looking at the same landscape." When that premise collapses, a sharp loneliness arrives. Not just a disagreement — a realization that the observation universe itself wasn't shared.
In those moments, I often start to give up explanation. "Fine, you don't have to understand" — a line gets drawn inside me.
But the moment that line is drawn, the community closes. A closed community's history can't be observed from outside. New arrivals can't see the strata. The result: the community itself starts reproducing the very "intelligence that doesn't read history" I most disliked.
Love for history tips easily into insiderdom. Which is exactly why design that keeps history observable from outside becomes necessary. The structural work of not locking love inside.
7. To OrbitLens
By here, I can finally place the motive behind OrbitLens.
OrbitLens isn't a list of features. At least, not to me.
When I say "tool," the conversation closes around features. What sits at OrbitLens's root is the thought of keeping history observable, in a form the community can hold.
EIS observing seven axes only from git log and git blame, and OrbitLens Ace — the SaaS observatory currently in development — tracing structural stories along the time axis: the root is the same place. Who built what heat onto what, and making that observable as strata, not as surface.
Why do I want this?
Because I've watched right arguments break organizations, many times. Watched intelligence that doesn't observe history peel away the strata of communities, one layer at a time. I've watched the opposite too. Communities that get observed are strong. Communities that don't get observed disappear, along with their history, the moment someone leaves.
To put it in more human terms: I don't want the heat of a certain kind of interesting person to die out.
People who read history. People who don't jump at easy "correct answers" and instead hesitate inside themselves. People who, while hesitating, still carry their own risk and face truth on their own feet. People who can offer respect to someone else's accumulation. Just a few of them on a team gives the community a different temperature.
But work like this is hard to see. The voices aren't loud. The slides aren't flashy. The contribution of people who till the strata, not the surface, slips through the net of most evaluation systems.
And these are exactly the people who tire out. When intelligence that doesn't observe history "optimizes" an organization, the heat that drains first is usually theirs. The moment "okay, I'm done" gets drawn inside them, the most important stratum quietly leaves the community.
But this "okay, I'm done" — I believe it's the kind of thing structure can prevent.
Heat is born inside an individual at first. The community has to observe it the moment it's born. The observed heat has to propagate to someone else. At the destination of propagation, new heat has to be born again. If this circulation is built into the structure, the community's heat is conserved.
To conserve the heat that's born, to propagate it, to not let the next generation of heat die out. The central work of organization design is, I think, here.
OrbitLens is, you could say, the first step of that circulation — an apparatus for making someone's heat observable as strata.
Heat conservation. Visibility of history. Restoration of the time axis. Holding the community's observability open.
The words aren't flashy. But the principles at the root of organization design might just be this simple, I find myself thinking lately.
Love is taking history on yourself.
Organization design might be the design that places that love in an observable form.
I'm not against right arguments. I want to place a question, once more, in front of intelligence that doesn't observe history:
"Whose accumulation is your right argument standing on, and what is it inheriting?"
This essay carries questions from Uoto's manga Chi. — About the Movement of the Earth (チ。―地球の運動について―, Shogakukan).
The Japanese original is on OrbitLens Library.
OrbitLens / machuz
P.S. I designed this logo myself. The three slightly-misaligned orbits are my favorite part of it.
Top comments (0)