Eight Japanese Principles — Read in Northern German, Lived in Indie Mode

TL;DR

Eight Japanese principles have accompanied me since IBM sent me to Tokyo for a project in the early 2000s. They are neither esoteric nor folklore — they are working models. Applied to indie building: Kaizen (Conductor v1→v8.1.0 in small increments), Ikigai (why I made the final switch from architect to builder in 2024), Wabi-Sabi (one idea, one repo, no polish), Hara Hachi Bu (restraint with 8 parallel projects), Shinrin Yoku (Sundays offline), Kintsugi (Conductor failures as visible gold seams), Gaman (the indie pre-revenue stretch), Omotenashi (anticipating customers). This hub post is the overview — three deep dives are linked, five will follow.

Featured: the stylized Ikigai venn — passion, mission, profession, vocation. The pivot of all eight.

Table of Contents

• Why Japan, why now
• The eight principles in one table
• Kaizen — small improvements beat big announcements
• Ikigai — why does this work actually exist
• Hara Hachi Bu — grow healthy, don’t overfeed
• Shinrin Yoku — a clear head is a competitive advantage
• Wabi-Sabi — not perfect, but real
• Kintsugi — breaks become experience capital
• Gaman — show character when it gets uncomfortable
• Omotenashi — service starts before the customer asks
• What about this is northern German
• FAQ

Why Japan, why now

In the early 2000s, IBM sent me to Tokyo for a project. Before that I had known two Japanese words, zero background in Zen, and had never read a book about Ikigai. What I brought: northern German directness, a Lufthansa Senator card, 27 years of age, and no humility.

What I brought back from Japan was a set of working principles that were not loud — but that helped over the next 20 years whenever louder management fashions bounced off. They are not Japanese in the sense of “must be imported.” They are Japanese in the sense of “Japan named them precisely.” Northern Germany has the same substance, just labeled differently.

Since my switch to indie builder in 2024, these principles are explicitly part of my working model — not as spirituality, but as operational discipline. This hub post summarizes; three deep dives are already live, five more follow.

The eight principles in one table

Three of these principles have dedicated deep-dive posts on this site:

• Ikigai for indie builders — how the intersection test decided that 2024 was the year of the switch
• Kaizen in Conductor — 8 versions, 8 breaks, 1%-per-day logic as iteration principle
• Wabi-Sabi and indie building — why polish is poison in indie mode

The remaining five follow in the coming weeks.

Kaizen — small improvements beat big announcements

What can we do 1% better today?

Kaizen is the Japanese principle of continuous incremental improvement. Not radical transformation. Not 80-slide strategy. But: what fits one small step better tomorrow than today.

I practice this daily on Conductor, my agentic coding stack. v1.0 ran in May 2024. v8.1.0 runs in May 2026. Eight major versions in 24 months — and not a single one a “big bang.” Each corrected exactly one old design flaw. That is Kaizen in code form.

More mechanics: deep dive on Kaizen.

Ikigai — why does this work actually exist

What is the reason to get up in the morning?

Ikigai is the intersection of four questions: what you love, what you are good at, what the world needs, and what you can be paid for. I did not learn this as a spiritual concept but experienced it in Tokyo as an operational question.

In 2023 I sat with exactly this question after 8 years of freelance as an architect. Money was no longer an argument. What was left: what I actually love (building, not consulting), what the world gets from it (AI for humans, not for models), what I am good at (system architecture), what I can be paid for (indie products, Moinsen consulting). The four-intersection answer triggered the switch to indie builder.

More mechanics: deep dive on Ikigai.

Hara Hachi Bu — grow healthy, don’t overfeed

Eat until you are 80% full.

Applied to work: do not plan every unit of capacity, do not take every commission, do not chase every growth offer. Preserve reserves.

I practice this in my eight-projects-parallel workflow as the 90-minute slot rule. Even when the flow state is pleasant: after 90 minutes, hard cut. The rest of the day belongs to other projects. Not maximum load, but stopping at 80% of theoretical capacity. The system works because I do not fill every slot.

Northern German equivalent: do not sew on the edge.

Shinrin Yoku — a clear head is a competitive advantage

Forest bathing.

Literally: walk into the forest, open the senses, do not train — just be. Applied to work: create breathing room for clear thinking. Good decisions rarely happen between two meetings.

For me concretely: Sundays are offline. A walk along the Alster or between the houses. No screen. No notifications. Not “I will just think briefly” — do not think at all. Only then do the ideas come back clearly.

Northern German equivalent: wind, water, vastness. Hamburg provides it for free.

Wabi-Sabi — not perfect, but real

Value in the imperfect, grown, real.

Wabi-Sabi is the principle that does not hide imperfection. A cracked tea bowl is not less valuable than a perfect one — it tells a story.

For indie building this means: one idea, one repo, no polish. The 424 repos exist not despite the imperfection but because of the speed of that iteration. Whoever waits for polish ships 5 projects instead of 50.

More mechanics: deep dive on Wabi-Sabi.

Kintsugi — breaks become experience capital

Mend the broken with gold lacquer so the seam becomes part of the story.

Kintsugi ceramics does not hide repairs — it makes them visible. Applied: document failures, do not hop over them.

That was the explicit reason I wrote what does not work in agentic coding the way I did — seven concrete Conductor version breaks, each with cause and fix. Not as a best-practice list but as an anti-best-practice. The gold seams are the lessons.

Gaman — show character when it gets uncomfortable

Dignified endurance.

Gaman is not passive suffering. It is steadiness with character. In indie mode it is the discipline of the pre-revenue stretch.

From 2015 I had eight years of freelance-architecture transition until the real indie-builder mode in 2024. Of those, the first three were strong, the middle two were dry, the last three were a slow correction. Anyone who quits in the dry years never reaches the indie point. Gaman is the discipline of staying in, without complaining.

Northern German equivalent: clear edge. Do not get hectic.

Omotenashi — service starts before the customer asks

Anticipatory hospitality. Attentive, respectful, precise.

Omotenashi is service that anticipates the problem before the guest names it. Applied to SME consulting: catch problems before they escalate. Answer questions before uncertainty forms.

My SME offering at kmu.moinsen.dev follows this principle explicitly — free tools (website check, hourly-rate calculator, AI readiness check) deliver value before first contact. Whoever still gets in touch has already half-found what they need.

What about this is northern German

What sounds Japanese about these eight is, at the core, also Hanseatic:

• Substance beats show (Wabi-Sabi, Gaman)
• Restraint, no posturing (Hara Hachi Bu, Kaizen)
• Clarity under pressure (Gaman, Shinrin Yoku)
• Trust is capital (Omotenashi, Ikigai)
• Learn from failures, stand up (Kintsugi, Kaizen)

The language is different. The substance is the same. Anyone raised in Hamburg or Schleswig knows these values by different names — reliability, clarity, restraint, responsibility, quality, long-term thinking.

Perhaps neither SMEs nor indie builders need loud management fashions. Perhaps they need principles that hold.

Where this goes next

Three deep-dive posts are already live (Ikigai, Kaizen, Wabi-Sabi). The five more (Hara Hachi Bu, Shinrin Yoku, Kintsugi, Gaman, Omotenashi) will follow in the coming weeks. This series is part of my personal pillar — this is the material I know well and use gladly.

If you work with one of these principles yourself or think one is wrong: reach me on LinkedIn. I trade notes happily.

FAQ

Are these principles really Japanese?

Yes and no. The words are Japanese — Kaizen, Ikigai etc. are fixed Japanese concepts with documented meaning (see e.g. Ken Mogi: “Ikigai — The Japanese Secret to a Long and Happy Life”, Penguin 2017). The substance exists in many cultures — northern Germany knows almost all of them under different names.

Do I have to travel to Japan to get this?

No — but it helps. I was in Tokyo in the early 2000s for an IBM project. What you see in daily Japanese life (precision in the subway, cleanliness in parks, anticipatory courtesy in shops) brings these principles closer as lived practice than any book can. But books by Ken Mogi or Hector Garcia + Francesc Miralles, combined with daily application, get you to 80% of the understanding.

Which principle should I apply first?

Kaizen. It is the lowest-threshold one — one small improvement per day, no strategy workshop needed. The other seven require more reflection. Kaizen you can start tomorrow.

Are these only relevant for SMEs / solo founders?

No. Large corporations have used Kaizen since the 1980s as a lean-manufacturing method (Toyota Production System). But for SMEs + indie builders they are more directly applicable because there is no 6-stakeholder filter in the way.

Does it make sense to practice all eight in parallel?

Practically not. I use Kaizen + Ikigai + Wabi-Sabi daily. Hara Hachi Bu + Shinrin Yoku are weekly disciplines. Kintsugi + Gaman + Omotenashi are situational helpers — you pull them out when the situation calls for them.

Written on May 17, 2026 in Hamburg. This series is a translation between Tokyo (early 2000s, IBM) and Hamburg (today, Moinsen). If you find this post useful, link to it.