Brett Owers
← All Projects

Yumutsu

Archived

April 1, 2023

A web shop built around a phrase from my boss: "Your Understanding, My Understanding, The Same Understanding." It became my license plate (YUMUTSU), a brand pulling in Japanese philosophy, and a shop that made fewer than 10 sales. A lesson in the difference between a concept you love and a concept the market loves.

Purpose

My boss said "Your Understanding, My Understanding, The Same Understanding" and I thought it was genius — the idea that alignment between two people is the foundation of everything meaningful. I compressed it into YUMUTSU, got it on my license plate, pulled in Japanese philosophical aesthetics, and built a shop around the concept. The brand was beautiful. The sales were not.

Stack

WebE-CommerceShopifyDesignBranding

What I Learned

  • YUMUTSU — Your Understanding, My Understanding, The Same Understanding — is a communication philosophy compressed into an acronym. The premise: every conflict, every miscommunication, every failed collaboration is a misalignment of understanding. If two people can achieve the same understanding of a problem, the solution becomes obvious. The phrase stuck because it named something real that most people feel but cannot articulate.
  • The Japanese philosophy connection was aesthetic and philosophical: wabi-sabi (beauty in imperfection), ichigo ichie (one time, one meeting — every encounter is unique and unrepeatable), and the concept of wa (harmony through alignment). These mapped naturally onto "the same understanding" — harmony is not agreement, it is shared comprehension. The branding was cohesive. The products were clean.
  • Fewer than 10 sales is a data point, not a failure. It tells you that the concept resonated with you (strongly enough to put it on your license plate) but did not resonate with enough strangers to sustain a business. This is the hardest lesson in branding: your personal attachment to a concept does not predict market demand for that concept.
  • The shop taught the mechanics of e-commerce that later powered the Potatuhs storefront: product photography, listing optimization, pricing strategy, print-on-demand integration, and the emotional arc of launching a store to silence. Every zero-sale day teaches patience. Every single sale teaches that the pipeline works. Fewer than 10 sales taught both.

Key Insights

  • The difference between a concept you love and a concept the market loves is distribution and demand. YUMUTSU was personally meaningful — it encoded a communication philosophy I genuinely believe in. But personal meaning does not create market demand. Potatuhs works as a brand not because potatoes are personally meaningful (they are, but that is not why it works) — it works because potatoes are universally recognizable, inherently funny, and visually distinctive. YUMUTSU required explanation. Potatoes do not.
  • Putting a brand on your license plate before it has product-market fit is the most optimistic thing a founder can do. It is also diagnostic: if you are willing to drive around with YUMUTSU on your car, your conviction is real. Conviction without validation is expensive, but conviction is the prerequisite for validation. You cannot test a brand you are not willing to commit to.
  • The phrase itself — "Your Understanding, My Understanding, The Same Understanding" — is still the best description I have heard for what makes collaboration work. It lives on as a personal principle even though the brand did not survive. Some ideas are better as philosophies than as products. YUMUTSU is one of them.
  • Every failed brand attempt is a design portfolio entry and an operational dry run. The YUMUTSU shop required: a brand concept, a visual identity, product design, supplier selection, storefront setup, listing copy, and launch marketing. Those are exactly the skills that built the Potatuhs storefront. The brand died. The skills transferred.
#e-commerce#branding#Shopify#Japanese-philosophy#wabi-sabi#YUMUTSU#product-market-fit#entrepreneurship#design#Potatuhs

This post was composed through a conversation between Brett Owers and Claude Code (Anthropic). The content reflects Brett's recollection of each project and the lessons drawn from it. Some details may be approximate or omitted — the purpose is to paint an honest picture of a software engineer's development over time, not to serve as a precise historical record.