top of page

Nomos Ingeniare

Empower Your Business Growth

Your Path to Operational Excellence

Insights

Services

Consultation
Book Now

Collins describes leadership as a progression through five levels:

1. Highly Capable Individual – Contributes through talent, knowledge, and work ethic.
2. Contributing Team Member – Works effectively with others toward shared objectives.
3. Competent Manager – Organizes people and resources to achieve goals.
4. Effective Leader – Inspires commitment and drives the organization toward a compelling vision.
5. Level 5 Executive – Combines fierce professional resolve with genuine personal humility to build lasting greatness.

One of the paradoxes of Level 5 leaders is that their greatest strengths can make them less visible.

Collins describes leadership as a progression through five levels:

1. Highly Capable Individual – Contributes through talent, knowledge, and work ethic.
2. Contributing Team Member – Works effectively with others toward shared objectives.
3. Competent Manager – Organizes people and resources to achieve goals.
4. Effective Leader – Inspires commitment and drives the organization toward a compelling vision.
5. Level 5 Executive – Combines fierce professional resolve with genuine personal humility to build lasting greatness.

One of the paradoxes of Level 5 leaders is that their greatest strengths can make them less visible.

Do you go to the Gemba… or do you go to a line-side show?

One of the most common pieces of Lean advice is:

"Go to the Gemba."

Go where the work is done.
Observe the process.
Talk to the people doing the work.

I couldn't agree more.

But in many large organizations, that's not what actually happens.

Instead, top management announces a plant visit weeks in advance.

Suddenly everyone is:

- Cleaning and painting.
- Updating visual boards.
- Making sure every machine is running.
- Rehearsing presentations.
- Preparing the "perfect" route through the plant.

By the time leadership arrives, they aren't seeing the operation.

They're watching a performance.

That's not the Gemba.

That's theater.

I've seen this firsthand more times than I can count.

The intention is understandable. Every team wants to make a good impression.

But there's an unintended consequence:

The very people who have the authority to remove barriers, allocate resources, and drive change never get to see the real problems.

Meanwhile, operators—the people who live with those problems every day—rarely get an opportunity to have an honest conversation.

If your quality, OEE, uptime, delivery, or safety metrics aren't where they need to be...

What is the value of pretending everything is fine for one afternoon?

In fact, it often makes things worse.

Problems stay hidden.

Resources are allocated based on perception instead of reality.

Opportunities for improvement are missed.

Real Gemba walks require more than comfortable shoes.

They require curiosity, humility, and psychological safety.

Go to the line.

Talk to operators, technicians, maintenance, and supervisors.

Ask questions instead of giving answers.

Observe more than you speak.

And if possible, visit without the fanfare.

One of the best signs of a healthy culture is when people feel comfortable telling leadership:

"Here's what's really happening."

Because you can't improve what you never truly see.

So here's my question for manufacturing leaders:

When you visit the floor, are you seeing the operation... or are you watching a well-rehearsed show?

#Lean #Gemba #Manufacturing #OperationalExcellence #ContinuousImprovem

Do you go to the Gemba… or do you go to a line-side show?

One of the most common pieces of Lean advice is:

"Go to the Gemba."

Go where the work is done.
Observe the process.
Talk to the people doing the work.

I couldn't agree more.

But in many large organizations, that's not what actually happens.

Instead, top management announces a plant visit weeks in advance.

Suddenly everyone is:

- Cleaning and painting.
- Updating visual boards.
- Making sure every machine is running.
- Rehearsing presentations.
- Preparing the "perfect" route through the plant.

By the time leadership arrives, they aren't seeing the operation.

They're watching a performance.

That's not the Gemba.

That's theater.

I've seen this firsthand more times than I can count.

The intention is understandable. Every team wants to make a good impression.

But there's an unintended consequence:

The very people who have the authority to remove barriers, allocate resources, and drive change never get to see the real problems.

Meanwhile, operators—the people who live with those problems every day—rarely get an opportunity to have an honest conversation.

If your quality, OEE, uptime, delivery, or safety metrics aren't where they need to be...

What is the value of pretending everything is fine for one afternoon?

In fact, it often makes things worse.

Problems stay hidden.

Resources are allocated based on perception instead of reality.

Opportunities for improvement are missed.

Real Gemba walks require more than comfortable shoes.

They require curiosity, humility, and psychological safety.

Go to the line.

Talk to operators, technicians, maintenance, and supervisors.

Ask questions instead of giving answers.

Observe more than you speak.

And if possible, visit without the fanfare.

One of the best signs of a healthy culture is when people feel comfortable telling leadership:

"Here's what's really happening."

Because you can't improve what you never truly see.

So here's my question for manufacturing leaders:

When you visit the floor, are you seeing the operation... or are you watching a well-rehearsed show?

#Lean #Gemba #Manufacturing #OperationalExcellence #ContinuousImprovem

It's race week!!!

For @f1 fans, that always means something special. And when the calendar reaches the streets of Monaco, it feels even more significant.

#Monaco is often called the crown jewel of F1. While some fans are not very keen on Monaco due to the difficult to overtake, Monaco is still a place where precision matters, mistakes are punished immediately, and there are very few second chances. And that's what make it more interesting.

As I think of everything that goes on around a race weekend, I can't but wonder of how much manufacturing can learn from Formula 1.

The most obvious lesson is that success is never the result of a single person. It is a team effort. Everyone has a task to do, and doing it right reflects on the results of the team.

Behind every driver is a highly coordinated team of engineers, strategists, mechanics, analysts, and support staff—all working toward a common objective.

Sound familiar? In manufacturing, we often face the same reality.

Quality, delivery, safety, maintenance, engineering, supply chain, and operations must all work together. If one piece fails, the entire system feels the impact.

What I admire most about F1 teams is their mindset. They approach problems with a "can-do" mentality. Not why it wouldn't work, or how much work for so little gain. They say, if there's a way, we'll find it!

There is no:

- "That's not my job."
- "We've always done it this way."
- "Good enough."

Instead, there is a relentless focus on:

- Problem solving
- Continuous improvement
- Data-driven decisions
- Flawless execution

When something isn't working, the question isn't whether it can be fixed. The question is: How quickly can we understand the problem and improve it?

Another lesson is the value of marginal gains. An improvement of a few hundredths of a second may seem insignificant on its own, but in a sport where the difference between the winner and the rest is measured sometimes in thousands of a second, that's when dozens of those improvements are combined, they can be the difference between standing on the podium and watching from the garage.

Manufacturing works the same way.

It's race week!!!

For @f1 fans, that always means something special. And when the calendar reaches the streets of Monaco, it feels even more significant.

#Monaco is often called the crown jewel of F1. While some fans are not very keen on Monaco due to the difficult to overtake, Monaco is still a place where precision matters, mistakes are punished immediately, and there are very few second chances. And that's what make it more interesting.

As I think of everything that goes on around a race weekend, I can't but wonder of how much manufacturing can learn from Formula 1.

The most obvious lesson is that success is never the result of a single person. It is a team effort. Everyone has a task to do, and doing it right reflects on the results of the team.

Behind every driver is a highly coordinated team of engineers, strategists, mechanics, analysts, and support staff—all working toward a common objective.

Sound familiar? In manufacturing, we often face the same reality.

Quality, delivery, safety, maintenance, engineering, supply chain, and operations must all work together. If one piece fails, the entire system feels the impact.

What I admire most about F1 teams is their mindset. They approach problems with a "can-do" mentality. Not why it wouldn't work, or how much work for so little gain. They say, if there's a way, we'll find it!

There is no:

- "That's not my job."
- "We've always done it this way."
- "Good enough."

Instead, there is a relentless focus on:

- Problem solving
- Continuous improvement
- Data-driven decisions
- Flawless execution

When something isn't working, the question isn't whether it can be fixed. The question is: How quickly can we understand the problem and improve it?

Another lesson is the value of marginal gains. An improvement of a few hundredths of a second may seem insignificant on its own, but in a sport where the difference between the winner and the rest is measured sometimes in thousands of a second, that's when dozens of those improvements are combined, they can be the difference between standing on the podium and watching from the garage.

Manufacturing works the same way.

One of the most surprising inequalities I see in organizations has nothing to do with gender, race, or background.

It’s the inequality in workload, expectations, and accountability among people in similar roles.
You’ve probably seen it.

The most responsible employee consistently gets:
- The most complex assignments
- The tightest deadlines
- The highest expectations

Meanwhile, the underperformer is considered “successful” for simply not creating problems.
It’s similar to parenting: the responsible child gets pushed harder because they can handle it, while the troublemaker gets praised for basic compliance.

This dynamic isn’t inherently wrong—high performers should be challenged.

The problem arises when:
- The added responsibility isn’t reflected in compensation
- Promotions don’t follow contribution
- One mistake from the top performer outweighs a pattern of mediocrity from others

Performance evaluations fail to capture true impact. Over time, this creates burnout at the top and complacency at the bottom.

As leaders, it’s our responsibility to:
- Develop all team members—not overuse the strongest ones
- Distribute responsibility intentionally
- Recognize and reward sustained high performance
- Communicate appreciation clearly and consistently

Too often this imbalance isn’t driven by necessity—it’s driven by lack of management involvement.

It’s easier to rely on your strongest people than to develop the rest of the team.

But that approach is expensive. Sometimes fewer people with higher capability outperform larger teams operating at uneven standards—but building that caliber of team requires investment, clarity, and courage.

When headcount limits, rigid salary bands, and ineffective performance evaluations enter the picture, the cycle perpetuates.

The question for leaders is simple:
Are we developing capability across the team—or are we overloading our best people because it’s convenient?

Operational excellence depends on people.
And fairness in expectations is part of leadership discipline.

One of the most surprising inequalities I see in organizations has nothing to do with gender, race, or background.

It’s the inequality in workload, expectations, and accountability among people in similar roles.
You’ve probably seen it.

The most responsible employee consistently gets:
- The most complex assignments
- The tightest deadlines
- The highest expectations

Meanwhile, the underperformer is considered “successful” for simply not creating problems.
It’s similar to parenting: the responsible child gets pushed harder because they can handle it, while the troublemaker gets praised for basic compliance.

This dynamic isn’t inherently wrong—high performers should be challenged.

The problem arises when:
- The added responsibility isn’t reflected in compensation
- Promotions don’t follow contribution
- One mistake from the top performer outweighs a pattern of mediocrity from others

Performance evaluations fail to capture true impact. Over time, this creates burnout at the top and complacency at the bottom.

As leaders, it’s our responsibility to:
- Develop all team members—not overuse the strongest ones
- Distribute responsibility intentionally
- Recognize and reward sustained high performance
- Communicate appreciation clearly and consistently

Too often this imbalance isn’t driven by necessity—it’s driven by lack of management involvement.

It’s easier to rely on your strongest people than to develop the rest of the team.

But that approach is expensive. Sometimes fewer people with higher capability outperform larger teams operating at uneven standards—but building that caliber of team requires investment, clarity, and courage.

When headcount limits, rigid salary bands, and ineffective performance evaluations enter the picture, the cycle perpetuates.

The question for leaders is simple:
Are we developing capability across the team—or are we overloading our best people because it’s convenient?

Operational excellence depends on people.
And fairness in expectations is part of leadership discipline.

Today, I want to talk about people.

They are the most valuable resource any organization has—yet they are often the most taken for granted.

If you want sustainable operational success, you need more than capital investment, systems, and dashboards. You need a strong, aligned team. A team that understands not only what they are doing, but why it matters.

Alignment to company goals—including those BHAGs (Big Hairy Audacious Goals, as defined by Jim Collins)—is not optional. It is foundational.

When people understand the mission, the objectives, and how their work contributes to them, performance changes. Communication and alignment are not soft skills. They are operational requirements.

Link in Bio

Today, I want to talk about people.

They are the most valuable resource any organization has—yet they are often the most taken for granted.

If you want sustainable operational success, you need more than capital investment, systems, and dashboards. You need a strong, aligned team. A team that understands not only what they are doing, but why it matters.

Alignment to company goals—including those BHAGs (Big Hairy Audacious Goals, as defined by Jim Collins)—is not optional. It is foundational.

When people understand the mission, the objectives, and how their work contributes to them, performance changes. Communication and alignment are not soft skills. They are operational requirements.

Link in Bio

Starting a new automation project always comes with a learning curve.
Whether it’s a new engineer, contractor, integrator, or consultant, there is an unavoidable ramp-up period:

- Understanding the current process and constraints
- Learning how the line actually runs versus how it’s documented
- Identifying true bottlenecks versus symptoms
- Understanding ownership, decision paths, and escalation

Too often, automation teams are expected to deliver results quickly without being given the context needed to succeed.

The fastest way to shorten ramp-up time in automation projects isn’t more meetings—it’s structure:

- A clearly defined problem statement and success criteria
- Stable, documented processes before automation begins
- Access to reliable data and historical performance
- Clear technical and operational ownership

When companies invest upfront in alignment and clarity, automation projects move faster, cost less, and deliver real value.

Automation success isn’t just about technology.
It’s about enabling people to execute effectively.

Question:
What has made the biggest difference in getting automation projects up to speed quickly in your organization?

Starting a new automation project always comes with a learning curve.
Whether it’s a new engineer, contractor, integrator, or consultant, there is an unavoidable ramp-up period:

- Understanding the current process and constraints
- Learning how the line actually runs versus how it’s documented
- Identifying true bottlenecks versus symptoms
- Understanding ownership, decision paths, and escalation

Too often, automation teams are expected to deliver results quickly without being given the context needed to succeed.

The fastest way to shorten ramp-up time in automation projects isn’t more meetings—it’s structure:

- A clearly defined problem statement and success criteria
- Stable, documented processes before automation begins
- Access to reliable data and historical performance
- Clear technical and operational ownership

When companies invest upfront in alignment and clarity, automation projects move faster, cost less, and deliver real value.

Automation success isn’t just about technology.
It’s about enabling people to execute effectively.

Question:
What has made the biggest difference in getting automation projects up to speed quickly in your organization?

.pro-gallery-wix-wrapper {display: block !important;} .pro-gallery-wix-wrapper .gallery-item-container {opacity: 1 !important; display: block !important;}

Follow us on Instagram

@nomosingeniare

Who We Are and What We Do

Our Vision

Nomos Ingeniare specializes in operations improvements, industrial automation, lean manufacturing, and six sigma. Our goal is to optimize manufacturing processes and align the management strategy with operational effectiveness.

bottom of page