Omote Standard

“No standard, no improvement.”

This simple phrase sits at the heart of the Toyota Production System. Yet in many workplaces, we face a very real problem: what do we do when there is no standard to begin with?

No clear process. No visual guide. No shared understanding.

In that situation, trying to improve is like renovating a house that exists only in someone’s imagination. There is nothing concrete to inspect, question, or change.

So where do we start?

When There Is No Standard

In many teams and organizations, work happens based on experience, habit, and individual preference. People “just know” what to do. New members learn by watching others and copying what they see.

This might seem efficient at first. After all, things are getting done. But this way of working hides several problems:

• Only a few people truly understand the work.

• Quality and speed depend heavily on who is doing it.

• When something goes wrong, it is hard to see where or why.

• Improvement discussions turn into opinions and arguments instead of facts.

In other words, when there is no standard, the work is invisible. And if the work is invisible, improvement is almost impossible.

So we need a starting point.

Create a Temporary Standard: “Hyoujyun” and Omote

When we have no standard, we don’t wait for the perfect one to appear. We create a temporary standard.

We call this “Hyoujyun.” Normally, “standard” in Japanese is written as 【標準】. But here, we intentionally write it as 【表準】 and read it as Omote-Standard.

Why change the character?

Because Omote 【表】 has very important meanings: “front” and “public”.

When there is no standard, everything is hidden in the back—inside people’s heads, unspoken habits, and undocumented routines. By creating Omote-standard, we bring that hidden reality to the front. We make it public, visible, and shareable.

A temporary standard is not about being perfect. It is about being visible.

The Meaning of Omote and Arawasu

The character 表 (Omote) carries another reading: arawasu. This means “to express,” “to show,” or “to describe”.

There is another important word pronounced similarly: arawasu 【現】, which you can see in terms like:

• Genba 【現場】 – the actual workplace

• Genbutsu 【現物】 – the actual thing, the real object

This gen points to what is actual, what truly exists in reality.

So we can think of it this way:

• Gen is about the real thing.

• Arawasu (Omote) is about making that real thing visible in some form—through words, drawings, numbers, or standards.

When we create an Omote-standard, we are not inventing fantasy. We are describing the actual work as it is currently done, and making it visible so everyone can see it.

Only then can we start to ask: Is this the best way?That question is the beginning of Kaizen.

What Can an Omote-Standard Look Like?

One of Omote's strengths is that it doesn’t require a perfect or complex format. There is no strict rule about what an Omote-standard must look like.

It can be:

1. A simple takt time calculation. For example: “We need to produce one unit every 3 minutes to meet customer demand.” Just writing this down makes it clear what pace we should aim for.

2. A short list of basic steps. For example:

1. Receive the order.

2. Confirm requirements.

3. Prepare materials.

4. Execute the task.

5. Check and deliver.It may be rough, but it creates a common sequence everyone can refer to.

3. A simple layout or location rule.For example: “All tools are stored on this board, labeled by process,” or “All documents for Project A go in this folder.”Even such a basic rule creates consistency and reduces wasted searching.

4. A quick checklist.For example: “Before sending a report: (1) Check numbers, (2) Confirm date, (3) Confirm recipient, (4) Attach files.”A checklist is a very simple form of Omote-standard that can immediately improve quality.

None of these is perfect. That’s the point.Omote is not the final answer. It is the first shared version of reality.

Why a Temporary Standard Matters

When people hear the word “standard,” they often imagine something rigid, bureaucratic, and difficult to change. That fear can block improvement.

But Omote-standard is intentionally temporary.

We acknowledge from the beginning:

• It is incomplete.

• It may contain mistakes.

• It will need to change.

So why create it at all?

Because even an imperfect standard has powerful effects:

• It aligns everyone’s understanding of how the work is currently done.

• It gives us a baseline to measure against.

• It makes problems visible: when we see variation from the standard, we can ask why.

• It creates a common language for discussion: instead of “I do it this way,” we can say, “This is the current Omote—how can we improve it?”

Without this visible baseline, improvement conversations are vague and emotional. With it, they become concrete and objective.

Omote and Kaizen

The heart of this approach is Kaizen—continuous, step-by-step improvement.

Kaizen is not about waiting for the perfect solution. It is about:

1. Making the current state visible (Omote).

2. Trying a small change.

3. Observing the result.

4. Updating the standard.

5. Repeating.

We know that the Omote-standard is imperfect, but that is exactly what makes it useful. It invites questions:

• “Is this really the best sequence?”

• “Can we remove this step?”

• “Why does this task take so long?”

• “Can we reduce errors by changing this check?”

Every improvement we make is then reflected back into the standard. Over time, the temporary standard evolves into a stronger, more stable way of working—until the next improvement.

In this way, standardization and Kaizen are not opposites. Standardization is not the end of change; it is the platform that supports ongoing change.

What is critical here is that everyone is actively involved in improving the Omote-standard. Celebrate any small improvements or contributions from anyone. This is the beginning of Kaizen. Encourage and recognize even the smallest improvements or contributions from anyone, regardless of their role or experience. By valuing these incremental steps, we create a culture where people feel safe sharing ideas and taking initiative. This is the beginning of true Kaizen—a continuous, collective commitment to making things better, one small improvement at a time.

A Simple Way to Start

If your team or organization has no clear standards today, you don’t need a big project or a thick manual to begin. You can start small.

Here is a simple approach:

1. Choose one process.It could be how you handle customer inquiries, prepare a report, run a meeting, or process an order.

2. Observe the actual work (Genba).Watch how it is really done today—not how people say it is done.

3. Express what you see (Omote / arawasu).Write down the main steps, draw a simple flow, or capture the key timings. Don’t aim for perfection. Aim for visibility.

4. Share it publicly.Put it on a whiteboard, in a shared document, or in your team channel. Invite comments and questions.

5. Operate according to this temporary standard.For a period of time, ask everyone to follow it. Notice where it works and where it doesn’t.

6. Kaizen.When you find a better way, update the Omote-standard. Date the change. Repeat.

This small cycle is Kaizen in action.

No Standard, No Improvement

The phrase “No standard, no improvement” is not a criticism. It is a reminder.

If we want to improve, we must first see.If we want to see, we must first express.That is what Omote—表準—is about.

When there is no standard, create a temporary, visible one.Call it Omote. Accept that it is imperfect. Use it anyway.Then keep improving.

No standard, no improvement.A visible, temporary standard—Omote—is where real Kaizen begins.

P.S. At some point, we should develop standardized work, including a standardized work chart and combination tables.