The most exhausting part of relationships may not be what people actually say. It may be the work of inventing what they have not said and then treating the invention as our responsibility.
Someone goes quiet.
“Are they angry?” “Are they bored?” “Did I do something?” “Did they actually hate it?” “Are they storing resentment without saying anything?”
A help desk opens in your head. A meeting starts without the other person present. You write the minutes, argue both sides, and somehow end up preparing an apology. It is a one-person play with two characters.
The rule I jokingly call the “Hachiware method” is simpler:
Read the speech bubble that actually appears. Do not generate the bubble that never appeared.
“They are crying” is an observation. “They are crying because of me” is a hypothesis. “They secretly want to end the relationship” is an even larger hypothesis.
If the answer matters, ask. Experiments have found that directly getting another person's perspective through conversation can improve interpersonal accuracy more than merely imagining their perspective in your own head.[1]
Do not train harder at mind-reading.
Go get another speech bubble.
1. “Mm-hm,” smiling, and politeness are not a certified display of inner enjoyment
Real people are harder to read than Chiikawa characters because feelings are not drawn in giant symbols across the face.
“Mm-hm.” “Oh, really?” “I see.” Smile.
It is tempting to translate all of this into “They are having fun.”
But we all perform politeness ourselves.
We can say “That makes sense!” while internally meaning only, “I have no particular opinion, but I am keeping the conversation smooth.”
That is not necessarily deception. It is ordinary social coordination.
So:
Looks like they are enjoying it ≠ confirmed that they are enjoying it.
A quiet former partner may have been comfortable, bored, tired, thoughtful, or simply listening. A person can enthusiastically nod during someone else's story and later say that the conversation was boring.
Observation can include:
“They nodded.” “They smiled.” “They asked questions.” “They brought the subject up again later.”
Beyond that, we are estimating probability, not directly reading subjective experience.
Humans have excellent graphics and terrible user-interface telemetry.
2. My responsibility is to make honesty easier—not to force hidden feelings out
Stopping mind-reading does not mean becoming indifferent.
I can:
- make it safe to say no;
- avoid punishing disagreement;
- listen when dissatisfaction is actually expressed;
- let rejection happen without creating relational penalties;
- ask directly when information is needed.
That is enough.
Research on psychological safety consistently connects safer interpersonal climates with speaking up and voice behavior.[2] But psychological safety is not a magical API that guarantees 100 percent access to another person's inner state.
What they feel, when they realize it, whether they choose to say it, and how they phrase it remain partly theirs.
Keep the entrance open. Handle what comes out. Do not start mining underground for secret feelings.
3. Hachiware-style self-disclosure: “I feel a little awkward going alone. Want to come?”
Instead of demanding that someone infer our motive, we can reveal a little of it.
“I want to go there, but I feel a little awkward going alone. Want to come?”
That sentence removes a surprising amount of ambiguity. The other person no longer has to wonder why the invitation exists.
If they answer:
“Not this time.”
The response can simply be:
“Okay! I’ll go then.”
Self-disclosure and obligation are separate.
Reveal your feeling without handing the other person responsibility for fixing it.
Research on intimacy has emphasized not only disclosure but also perceived partner responsiveness—feeling understood, validated, and cared for.[3]
4. When you hear “no,” do not excavate the secret meaning underneath it
“Want to come?” “No.” “Okay!”
That lightness is powerful.
Do not immediately launch:
“Do they dislike me?” “Was my invitation wrong?” “Do they secretly want to come but feel shy?” “Was this a ritual first refusal?”
Research on autonomy in romantic relationships links greater autonomy with less defensive and more understanding responses during conflict, while autonomy-supportive partner behavior has also been associated with better outcomes.[4][5]
Treat a no as an actual no.
That makes your own no easier to use too.
“You are allowed to decline. I am also allowed to decline.”
That is a decent operating system for equals.
5. For mild absurdity, deploy Usagi: “Huh?”
In an equal relationship, not every unreasonable request deserves a constitutional convention.
“I can refuse, but you have to do it.” “You should have known even though I never said it.” “You do not know this game, so you are behind.”
A long rebuttal often means fully entering the other person's scoring system.
Sometimes the better answer is simply:
“Huh?” — Usagi sticker
A flat “What?” can sound aggressive. The Usagi imitation turns the refusal into a joke. The semantic content is still “I am not accepting that premise,” but the delivery is now a wild creature.
It is a compressed boundary.
Serious conflicts still require real words. But minor nonsense does not always deserve a dissertation.
6. Momonga-style requests: “Can I have this?” is the core; “GIVE IT!” is theater
For requests, I have apparently stolen parts from Momonga.
The real operating line is surprisingly normal:
“Can I have this?” “Is it okay if I use this shared material?”
Ask first.
If the answer is yes, use it. If the answer is no, do not take it.
Sometimes the sequence becomes:
“I want this.” The other person laughs. Then: “GIVE IT!”
On paper, civilization has collapsed. In context, however, the system is:
State the desire. Ask permission. Preserve the right to refuse. Add Momonga only as special effects.
This is easier to deal with than silently wanting something, receiving nothing, and later becoming resentful because the other person failed to detect the hidden request.
Desire: 100. Coercion: 0.
A polite request wearing a Momonga costume.
7. The gift problem: what if “I like it” later becomes “Actually, I hated it”?
A difficult pattern in relationships is when an agreement changes after rumination.
For example:
“Is this gift okay?” “Yeah, I like it.”
Later:
“Actually, I wanted you to do something different.” “I thought it was fine then, but after thinking about it, I disliked it.”
People are allowed to change their interpretation later. That is normal.
But one distinction matters:
A later feeling is new information. It does not retroactively make previously unavailable information available.
So the response can be:
“I see.” “So that ended up feeling bad.” “Okay, next time I can do it differently.”
And, when necessary:
“At the time you told me it was okay, so next time it would help if you tell me when you notice it.”
Do not turn yesterday's agreement into a conviction using tomorrow's evidence.
8. The other person's rumination is their task
This may be the most useful boundary of all.
The other person goes home and thinks:
“Maybe I actually hated that.” “I wish they had done something else.” “This makes me anxious about the future.”
That internal process belongs to their mind.
My responsibility begins again when they output something:
“Actually…”
Then I can listen, empathize, and change future behavior when appropriate.
What I cannot reasonably manage is:
“Predict today what the other person will decide after three days of private rumination.”
Respect the feeling. Do not outsource their rumination process into your brain. Participate in future repair, not retroactive telepathy.
The family-systems concept of differentiation of self similarly concerns maintaining connection while preserving a distinct self rather than fusing emotional positions.[6]
9. A breakup and a resignation turned out to have the same structure
In a past breakup, the other person eventually concluded that they wanted to end the relationship.
I listened. I had responded to requests that were actually expressed.
But when their final answer was, “I want to break up,” the response was essentially:
“Okay. I respect that decision.”
Later, in a workplace resignation, the roles reversed.
I said I had decided to leave for another opportunity. People around me had their own sadness and inconvenience, yet some responded:
“Given those conditions, you should go.” “If you have decided, I support it.”
The same structure, reversed.
A 2026 retrospective cross-sectional study found that greater autonomy support during romantic relationship dissolution was associated with more positive post-breakup psychological outcomes, though its design does not establish causality.[7]
Caring about someone does not automatically mean overruling their final choice.
I can be sad and still leave your decision in your hands.
The surprising part was realizing that the respectful way people handled my resignation resembled the way I had handled someone else's decision to leave a relationship.
10. At work, read structure instead of writing psychological fiction
This rule becomes even more useful in organizations.
“Does that manager hate me?” “Was this self-protection?” “Jealousy?” “Did they secretly expect more?”
Unknown.
Instead, observe:
- Who had decision authority?
- Who received responsibility afterward?
- Was staffing sufficient?
- Did authority and accountability match?
- Where did work concentrate?
- What happened after someone spoke up?
- What changed in evaluation, role, pay, or assignment?
Replace:
“Person A avoids responsibility.”
with:
“In this case, A had decision authority while post-failure responsibility shifted to B.”
The second statement creates possible actions:
Document approval. Clarify ownership. Identify the decision maker.
Workplace analysis becomes much cleaner when it is based on structure, behavior, and outcomes rather than invisible motives.
Mind: unknown. Structure: observable. Behavior: recordable. Outcome: remains.
11. The “Game Refund Monkey” seems to have an extremely high-resolution comparison system only for games
Then the discussion suddenly moves into games.
One friend remembers character names, maps, systems, and obscure game details at an absurd level and plays alone for long periods.
Interestingly, this does not look like competition across all of life.
I can say:
“My career move went well.” “My income went up.” “I somehow got an absurdly long break.”
Response:
“Huh. Anyway, about this game…”
Major life update loses to patch notes.
But inside games, another pattern appears:
I am behind → “Get stronger faster.”
We are close → keeps playing.
I move ahead or outperform him → somehow boredom with that game arrives.
We do not know the internal reason, so “he quit because he was jealous” would violate the entire method of this article.
The defensible observation is:
In a domain that appears highly important to him, relative position against a close comparison target seems to matter.
Classic self-evaluation maintenance research suggests that being outperformed by a close other can threaten self-evaluation when the domain is personally relevant.[8]
Salary difference: “Whatever.” Boss-clear order: emergency national broadcast.
The allocation of cognitive budget is beautiful.
12. “My no is final, your no starts negotiation” still gets an Usagi “Huh?”
This same friend can decline games suggested by other people.
But when I decline his suggestion, he may push:
“Come on.” “Progress faster.” “Do this.”
Behaviorally, the rule starts to look like:
My NO = final answer
Your NO = opening bid
That asymmetry does not need a psychological diagnosis. It just needs a boundary.
“Do it.” → Huh?
If the game looks fun, I may join later. If not, I do not.
“Not knowing a game means you are behind” is his scoreboard. I never signed up for the tournament.
Download the useful game information. Decline the optional hierarchy plug-in.
13. The pioneer and the Momonga: a bizarre but functioning game ecosystem
The funniest part is that if left alone, he progresses by himself.
He clears content. Collects materials. Makes equipment. Brings information.
I do whatever I feel like doing, then sometimes ask:
“Can I have this?” “Can I use these shared materials?”
And receive the profitable parts.
There are even exchanges like:
“Why did you use that item?” → “Hmph!” → he starts gathering replacement materials → I respond, “Hm!”
Human language has been abandoned, but the game continues.
Shared materials are asked about in advance, so this is not silent theft.
The real division of labor is:
Him: enjoys early progression, knowledge, and gathering
Me: joins the fun parts, asks before taking useful things
Random status pressure: returned with “Huh?”
When I seriously overtake him, “boredom” sometimes arrives, so paradoxically the ecosystem seems most stable when I simply play at my own pace.
This is not competitive accommodation.
It is wildlife conservation.
14. Why can someone remember game character names and maps so absurdly well?
He claims that if it is game knowledge, he remembers almost everything.
That does not necessarily mean universally extraordinary memory. A better explanation is that games have become a huge, richly connected knowledge domain.
Inside a game:
- names attach to faces;
- places attach to navigation;
- items attach to functions;
- bosses attach to failure and success;
- the same facts are repeatedly retrieved during play.
This is not isolated memorization. Names, images, places, actions, emotions, and consequences form a network.
Memory research shows that retrieval practice strengthens long-term retention more than mere restudy.[9] High curiosity can enhance memory for desired information and even incidental information encountered in that state.[10] Virtual navigation research implicates hippocampal and entorhinal systems in spatial orientation.[11]
So the cycle becomes:
play → remember → prior knowledge makes new games easier to understand → competence makes gaming more rewarding → play even more.
That still does not guarantee far transfer to every real-world occupation.
“Game quiz tournament!” is technically an application.
Unfortunately, the tournament contains people who have somehow played even more games.
The competitive edge disappears again.
15. “I like a partner who walks one step behind me” and the urge to stay ahead in games share a structural resemblance
This discussion reminded me of an old-fashioned relationship preference: liking a woman who “walks one step behind.”
This cannot be generalized to all older generations or all men.
But structurally, some people may attach security or identity to the relationship:
I lead; the other follows.
The game pattern looked oddly similar:
“Play with me.” “Catch up.” Yet when the other person moves ahead, interest drops.
We cannot claim the same internal psychology. The Hachiware method forbids that leap.
Still, the structure resembles a situation where relative position itself carries meaning, not merely absolute performance.
The practical conclusion remains simple:
I am not responsible for preserving someone else's preferred ranking.
If they want to stay ahead, that is their task. I play at the speed I want.
If they lose interest:
“Oh, okay!”
16. Do not install whole people. Salvage the useful parts
Another major lesson was realizing that learning from someone does not require adopting the entire person.
Friend who knows games:
Finds interesting games → keep that.
Has deep game knowledge → ask about it.
Treats unfamiliar games as proof that you are “behind” → reject.
Status jab → Usagi.
Same with Chiikawa characters.
From Hachiware: receive information, self-disclose, respect choices.
From Usagi: a low-drama “Huh?”
From Momonga: state desire openly.
Installing all of Momonga would obviously be a production incident.
Adopt ideas, not entire personalities.
Human beings mix too easily. We absorb other people's emotions, values, and scoreboards until they start feeling like our own.
Selective import is stronger.
Understand feelings. Return responsibility. Keep good ideas. Do not carry the whole person inside your head.
17. It would be awful if Hachiware were canonically “an expert in psychology who builds sophisticated interpersonal relationships”
After all this psychology, one point must be protected:
Hachiware probably is not thinking any of this.
Imagine the character profile:
Hachiware
Expert in interpersonal cognition, differentiation of self, autonomy support, and empathic accuracy; applies advanced psychological theory to maintain high-quality relationships.
Terrible.
If “Whoa, you started crying!” secretly meant:
“I will temporarily suspend causal attribution pending acquisition of additional data,”
the character would be ruined.
Hachiware is probably operating closer to:
“You cried!” “What happened?” “Oh, I see!” “Want to do this together?”
Humans can spend years constructing theories and eventually arrive at a place where a small cat-like creature was already standing without theory.
That is the charm.
18. Conclusion: psychology is complicated; the interface becomes “Oh, I see,” “Huh?” and “Is this okay?”
The final operating system is surprisingly small.
The other person speaks → “Oh, I see!”
I do not know → ask.
I have a feeling or constraint → “Going alone feels a little awkward.”
I invite → “Want to come?”
They refuse → “Okay!”
Unreasonable demand → “Huh?”
I want something → “I want this—would that be okay?”
Later: “Actually…” → listen, empathize, adjust the future. → do not accept retroactive responsibility for mind-reading.
Work → analyze structure, behavior, and outcomes instead of invented motives.
Good idea from another person → keep it.
Unwanted value system → return to sender.
Academic labels may include differentiation of self, autonomy support, psychological safety, social comparison, and interpersonal accuracy.
None of those labels appears on the actual control screen.
The control screen says:
“Oh, I see!”
“Huh?”
“Can I have this?”
After enough psychology papers, the final interface somehow becomes Chiikawa.
And Hachiware probably knows none of it.
Good.
