audience & revenue growth tips for B2B startups and creators

My mission is to build predictable pipelines for B2B startups. I share what I learn along the way. 

Read more if you are ready to build your pipeline 👇

💡 I am super relevant if you are:

→ Indie Hacker
→ Freelancer
→ Early Startup Founder
→ B2B Sales Person
→ Creator (any profession)

✍️ I write about:

→ B2B sales
→ Go to market strategies
→ Signal-based prospecting

Little more about me:

Cryptocurrency Investor. SaaS Enthusiast. Agriculture Business Owner. 

Lived in 3 countries.

I'm a T-shaped growth person who has experience in sales, content marketing, and growth.

Drop me a LinkedIn message if you need any help.

We will keep it simple.

Twitter: @sehaokudan

https://calendly.com/sehaokudan/30min

Seha Okudan

Is your sales team struggling? 
(The whole company is sinking.) 

No revenue. 
No growth. 
No jobs. 

If sales isn’t working, nothing else matters. 

You’re in the same boat. 

Even if you’re not in sales, you are still losing. 

When sales miss quota; 
(potentially) 

- Ops lose headcount 
- Marketing loses budget 
- Leadership loses investor trust 

Everyone loses momentum 

When sales struggle, it’s not their problem. 
It’s everyone’s problem. 

Because no revenue = no company to run. 

It’s everyone’s job. 

Agree or disagree?

5 ways to lose prospects:
(10 leads lost guaranteed)

5 ways to lose prospects

Salespeople lose deals they should’ve won.
Here’s how they kill it - without realizing:

How salespeople kill their deals

Powering Gemba Walks with Artificial Intelligence | Follow for posts on Continuous Improvement and Innovation

Hi - I'm Ivan, an industrial engineer with 7+ years of experience in Operations Management and Kaizen.

I serve two main groups of people:

1. Executives tired of broken processes burning money - I show them how to fix it and recapture 15-30% in Muda

2. Founders in Continuous Improvement who know their stuff but can't crack LinkedIn - I show them how to turn it into a legit revenue channel

(send me a direct message for more info)

I started writing on LinkedIn in October 2023. Since then, I have been sharing actionable, educational, and entertaining content to support LinkedIn community members in their Kaizen journey. It helped me grow my audience from 9,000 to 100,000 followers in 2024.

I have been posting around:

	• Continuous Improvement
	• Lean Manufacturing
	• Growth Mindset
	• Innovation

Including insights on 5S, Value Stream Mapping, Leadership, Industry 4.0, and Problem Solving. 

Now I'm building Gemba Walk AI to make every Gemba Walk part of a learning system, where collective insights drive faster, better decisions than any single expert could achieve.

For free weekly tips, subscribe to The Kaizen Geek newsletter.

Ivan Carillo

Toyota's competitors thought Taiichi Ohno was insane. He was letting line workers stop production over a scratched fender. They stopped laughing when Toyota dominated the industry for the next 50 years. Here's what happened:

After World War II, Ohno visited auto factories in Detroit. He expected to learn from the best. Instead, he found rework areas filled with broken pieces and leftover parts. Waste everywhere, hiding in plain sight.

He went back to Toyota City and did something nobody had tried before. At every station on the assembly line, he hung a rope called the Andon cord.

The instruction was simple: 

If you see a defect pull the cord. The line slows or stops. Engineers, workers, and suppliers huddle up and fix it on the spot. Detroit thought he was crazy. "How can you build thousands of cars a day if you stop the line for every little scratch?"

Ohno's answer was simple: 

A scratched fender is an early warning that a piece of equipment is failing. Fix the scratch today, and you prevent 500 defective fenders next week. Ignore it, and you're building rework areas just like Detroit.

That's the difference between firefighting and fire prevention.

Most operations leaders I talk to are stuck in firefighting mode. They walk past small defects every day because the line has to keep moving.

But those small defects are talking to you. They're telling you exactly where your next big quality failure will come from.

How many "minor" defects is your team walking past today that are actually early warning signs?

Kaizen vs. Innovation
 
Who wins?
 
There are two types of improvement:
 
Kaizen → Continuous improvements through ongoing effort. Involves everyone. Requires little money but sustained work.
 
Innovation → Dramatic improvements from large investments in new technology. Involves select champions. Requires big money but less sustained effort.
 
You need both. But here's how to proceed if you are forced to choose between the two.
 
 Choose Innovation when:
 
-you need dramatic breakthroughs to compete
-technology has fundamentally changed
-current processes are broken beyond repair
-you're entering new markets
-you must leapfrog competitors
 
Choose Kaizen when:
 
-you need sustainable competitive advantage
-you want to build organizational capability
-current processes work but need improvement
-you want everyone engaged in improvement
-you need to protect gains from innovation
 
Innovation creates the breakthrough.
Kaizen sustains it.
 
Without continuous improvement, every innovation you invest in will slowly erode back to zero.

A split illustration comparing Kaizen and Innovation. On the left, a hand-drawn sketch of a SIM card tray with a notched SIM card — labeled "Poka Yoke" — representing Kaizen's approach of error-proofing and incremental improvement. On the right, four SIM card generations shown in descending size order: Full Size, Mini SIM, Nano SIM, and eSIM — representing Innovation's leaps to entirely new solutions. Below both panels, the caption reads: "Kaizen gets you better, Innovation gets you different. You need both to thrive."

Taiichi Ohno said: "Where there is no standard, there can be no Kaizen."
 
He could have kept going:
 
 
Where there is no Kaizen, there can be no Innovation.
 
Standards don't kill creativity.
They create the foundation that makes creativity possible.

A pencil-drawn diagram of a steep incline with a ball marked "P" (representing a Process) at four progressive positions moving uphill. Each upward leap is labeled "kaizen" with a curved arrow. Between each position, a wedge or chock block under the ball — labeled "Standardization!" — prevents it from sliding back down. At the bottom left, a ball with no wedge shows the process rolling backward, labeled "process," illustrating regression without standardization. Below the illustration, the caption reads: "Where there is no standard, there can be no Kaizen."

My two cents:
 
In the era of mass customisation, pull systems are non-negotiable.
 
All brilliant processes are designed to result in
 
+balanced flow
+safe workplace
+zero defects
 
When talking about flow, we refer to either a Pull or a Push system.
 
Here is a breakdown of each:
 
1/ Basic Concept
 
 ↳ Push: Based on demand forecasts 
 ↳ Pull: Based on actual int/ext customer demand
 
2/ Production Trigger
 
 ↳ Push: Anticipated future needs 
 ↳ Pull: Current customer orders
 
3/ Inventory Levels
 
 ↳ Push: Higher inventories, safety stocks 
 ↳ Pull: Lower inventories, just-in-time approach
 
4/ Flexibility
 
 ↳ Push: Less flexible to demand changes 
 ↳ Pull: More adaptable to fluctuations
 
5/ Risk
 
 ↳ Push: Overproduction, obsolescence 
 ↳ Pull: Potential stockouts, backorders
 
6/ Information Flow
 
 ↳ Push: Forecasts flow downstream 
 ↳ Pull: Demand information flows upstream
 
7/ Costs
 
 ↳ Push: Higher inventory holding costs 
 ↳ Pull: Lower inventory costs, but potential lost sales
 
8/ Planning Complexity
 
 ↳ Push: More complex long-term planning 
 ↳ Pull: Simpler planning, but requiring responsive systems
 
9/ Market Suitability
 
 ↳ Push: Stable, predictable markets 
 ↳ Pull: Dynamic, uncertain markets
 
P.S. 60% of manufacturing professionals use 
a combination of push and pull systems in their operations.

Management has 2 functions: maintenance and improvement. The higher you go in management, the more time you spend on improvement. (here's what most managers miss about ↓)
 
There are two types of improvement:
 
Kaizen → Continuous improvements through ongoing effort. Involves everyone. Requires little money but sustained work.
 
Innovation → Dramatic improvements from large investments in new technology. Involves select champions. Requires big money but less sustained effort.
 
You need both.
 
But there's one thing most managers misunderstand:
 
Kaizen focuses on process, not just results.
 
Result criteria:
 
-sales targets
-cost reduction
-production quotas
-quality metrics
-profit margins
 
Process criteria:
 
+discipline
+time management
+skill development
+participation & morale
+communication
 
Traditional management rewards results only.
 
Kaizen management rewards both.

A sketch comparing two approaches to reaching a mountain peak: on the left, labeled "KAIZEN," a person hikes up a long, winding switchback path; on the right, labeled "INNOVATION," a helicopter flies directly to the summit via a straight dotted line. The illustration contrasts continuous incremental improvement (Kaizen's gradual climb) with disruptive innovation (the helicopter's rapid leap to the top).

Most companies are stuck on one speed. That's why they never reach Operational Excellence. The Japanese solved this decades ago with 3 concepts most leaders still confuse:
 
Kaizen - Kaikaku - Kakushin
 
Most leaders treat them as buzzwords. A few use one of them well. Very few uses all three in the right way, at the right time.
 
Here's what they mean (and why you need all three):
 
1/ Kaizen → Change for the better
 
Small, continuous improvements. Every day. Everyone involved.
 
→ Low cost, low risk
→ Driven by frontline workers and managers alike
→ Builds lasting habits, not one-time fixes
 
Example: Adjusting a workstation layout to cut motion by 10%.
 
Kaizen doesn't create breakthroughs.
It sustains them, and compounds gains over time.
 
2/ Kaikaku → Radical change
 
A deliberate, large-scale transformation of a process or system.
 
→ Top-down decision driven by urgency or opportunity
→ Higher investment and risk
→ Rewires how an entire system operates
 
Example: Redesigning your entire production flow to implement pull-based manufacturing.
 
Kaikaku creates a new baseline.
Kaizen then locks it in.
 
3/ Kakushin → Innovation
 
Reinvention. Creating something that didn't exist before.
 
→ Highest risk, highest potential reward
→ Disrupts markets or creates entirely new ones
→ Requires courage to abandon what's working
 
Example: Building an AI-powered process that makes the old one obsolete.
 
Kakushin opens new territory.
The other two make sure you can hold it.

Hand-drawn graph on aged paper showing three levels of process improvement over time: Kaizen as small incremental steps, Kaikaku as a steeper staircase of radical change, and Kakushin as an exponential curve representing innovation and reinvention.

Visual Management changes how people think, not just what they see. (here's what most leaders miss about ↓)
 
Kaizen is 90% Mindset, 10% Tools.
 
But what is the most powerful tool in your toolbox?
 
Well, your eyes.

We humans are visual creatures - our eyes take in information very quickly.

Visual Management is used to 

+share information 
+set new work standards 
+provide workflow transparency 

Key Steps: 

1/ Make information visible and accessible 
2/ Create visual cues that can be understood quickly 
3/ Highlight abnormal conditions that need attention 
4/ Enable teams to see project status and progress 

Some Examples: 

+Dashboards that display KPIs 
+Kanban Cards to limit work-in-progress 
+Gantt Charts to illustrate project timelines 
+Andon Systems that signal problems 
+Color-Coding systems for quick identification 

Another example is in this photo!

Remember: 

Humans process visual information much faster than text.

A clean indoor parking garage with three yellow-lined parking spaces on a polished concrete floor. A red Tesla Model 3 occupies the left space, a silver Ford F-150 truck occupies the right space, and the middle space is empty — visually demonstrating visual management through floor marking that makes normal (occupied) and abnormal (empty) conditions immediately obvious at a glance.

People want better processes as long as they don't affect their daily work. When you interfere with their way of working, you hear about this:
 
 
-unique challenges
-special circumstances
-knights, fairies, and golden dragons
 
Change means uncertainty and temporary incompetence.
 
I know, that's uncomfortable.
 
Change is often given a negative connotation.
As if it took something away from us, instead of enriching us.
 
As a change agent, you can't ignore all this.
 
→ Be honest about disruption upfront 
→ Make the personal cost visible 
→ Tell people exactly how this affects them 
→ Provide real support
 
The most change-ready organizations are filled with people who trust their leaders enough to feel uncertain together.

Side-by-side illustration showing two rooms labeled 'People who want change.' Left: A speaker presents to a packed auditorium of hundreds. Right: A single person works alone at a laptop with one empty chair beside them. Both rooms display the same network diagram on screens above.

21 sentences every kaizen leader must hear at least once (read my fav ones below ↓)


When I read books, especially about Kaizen, I always look for something that will stay with me. I end up writing down the things that strike me most in my journal. Here are the 4 sentences in the list that I believe are most powerful (and why):

1/ Gemba never lies

I've seen leaders make terrible decisions because they trusted Excel sheets over their own eyes. The problems that cost us millions are often visible on the shopfloor, but nobody bother to look. Reports tell you what people want you to know. Gemba tells you what's actually happening. I think the moment you stop walking the floor is the moment you lose touch with reality. Your operators won't lie to you if you show up regularly, ask good questions, and actually listen to their answers.

2/ Without psychological safety, Kaizen dies.

I've watched brilliant Kaizen programs collapse because people were terrified to speak up. Companies that blame individuals for systemic problems get exactly what they deserve. Silence. Workers hide defects, skip reporting near-misses, and watch waste happen rather than risk looking stupid or getting punished. I think this is why most Kaizen initiatives fail within a year. You can't improve what people won't talk about, and people won't talk about problems in a culture of fear.

3/ People who do the work are the experts

I learned this the hard way early in my career when I implemented a Kaizen idea. The operators supported it, then immediately went back to their old method the moment I left. Every time I've ignored frontline expertise, I've wasted time and money solving the wrong problem. I think we underestimate how much knowledge lives in the hands and muscle memory of people who do the same task hundreds of times daily.

4/ Kaizen culture doesn't support strategy. Kaizen culture is strategy.

I spent years thinking CI was something that helped execute our "real" strategy. I was wrong. Companies with a strong Kaizen culture adapt faster, survive disruptions better, and outperform competitors with superior strategic plans. I think this is the principle most executives miss. Your competitors can copy your products in months, but they can't copy a culture where thousands of people solve problems every single day.

P.S. What's your fav one in the list? Anything else to add here?

21 Sentences Every Kaizen Leader Must Hear At Least Once — A numbered list of Kaizen leadership principles on a textured beige background, including: Gemba never lies; Challenge the status quo, always; Everyone must own improvement; Problems are treasures, not threats; Plan, Do, Check, Act—repeat forever; Data tells you what, people tell you why; Simplicity is the ultimate sophistication; People who do the work ARE the experts; Speed and quality are not opposing forces; Without psychological safety, Kaizen dies; Expertise isn't about having all the answers; Standardization comes BEFORE improvement; Leaders must resist the urge to jump to solutions; Kaizen doesn't support strategy, Kaizen IS strategy; If the student hasn't learned, the teacher hasn't taught; The master knows when to step aside and let others grow; KPIs can improve even as the culture declines, watch both; Creating a Kaizen culture cannot be separated from sustaining it; and others.

Mistakes. We all make them.
 
But what if there was a fail-safe way to minimize them?
 
Poka-Yoke is a Japanese term that means "mistake-proofing".
 
It refers to any mechanism helping an operator avoid mistakes by preventing, correcting, or drawing attention to human errors as they occur.
 
Here's a 4-level Poka-Yoke hierarchy:
 
(from strongest to weakest)
 
1/ Prevention → Impossible to Fail
Design makes errors physically impossible:
 
→ USB-C connectors that only fit one way
→ Different connectors for oxygen vs. medical air 
→ Luggage carts won't roll without handle pressure
→ Car keys can't be removed until the transmission is in Park
→ Credit cards with chips that only insert one direction
→ Microwaves that won't start with the door open
 
2/ Detection → Instant Feedback
System catches errors immediately and alerts you:
 
→ Spell-check underlining misspelled words as you type
→ Weight scales flagging wrong shipments
→ Temperature alarms for too high/low
→ Seat belt warning chimes
 
3/ Mitigation → Reduce Mistake Impact
Error can happen, but damage is limited:
 
→ Circuit breakers preventing electrical fires 
→ Dual engines on aircraft
→ Airbags deploying in crashes
→ Safety goggles protecting eyes during mistakes
→ Backup generators kicking in during power loss
→ RAID storage systems surviving hard drive failures
 
4/ Warning → Cross Fingers
Relies on human attention and compliance:
 
→ "Caution" signs 
→ Speed limit beepers
→ "Check your mirrors" stickers
→ Password expiration reminders
→ "High voltage" warnings
→ Recommended tire pressure labels
 
P.S. Smart people make mistakes.
 
Brilliant systems prevent them.
 
Which are you building?

Hand-drawn diagram showing the four-level Poka Yoke (error-proofing) hierarchy in lean manufacturing. Level 1 - Prevention (Impossible to Fail): sketch of mismatched connectors with X marks showing parts that cannot be incorrectly assembled. Level 2 - Detection (Instant Feedback): alarm sensor icon with 'BEEP BEEP' sound waves indicating immediate error alerts. Level 3 - Mitigation (Reduce Impact): steering wheel with deploying airbag showing damage reduction when errors occur. Level 4 - Warning (Cross Fingers): wet floor warning sign representing the least effective method that relies on human attention and compliance

Wrong is wrong, even if everyone is doing it. Right is right, even if no one is doing it. I'm seeing a pattern I can't ignore:
 
 
People claiming credit for someone else's work. Making choices they know are wrong for quick wins. Sharing information without checking if it's true. The internet didn't create these behaviors. But it amplified them.
 
Now everyone feels pressure to weigh in on every topic, present a polished image regardless of reality, and look productive even when nothing meaningful is happening.
 
Real leadership looks different.
 
Give credit. It comes back. Stay quiet when you don't know. People notice that too. Do the uncomfortable right thing. It's uncomfortable for a reason…most people won't.
 
You won't need to prove anything to anyone anymore. Your actions will speak for you.

Minimalist image with four lines of Japanese wisdom in black text on a light background: 'If it's not yours, don't take it. If it's not right, don't do it. If it's not true, don't say it. If you don't know, be quiet.' Below the text is a simple sketch of a traditional Japanese torii gate reflected in water.

Fast, Cheap, Good - Pick two.
 
(trade-offs are inevitable)
 
"We need it fast, under budget, and perfect."
 
Everyone knows it's impossible. Nobody says it.
 
Three months later:
 
The project is late, over budget, or broken.
 
 You can't have everything.
 
The worst project managers?
 
They promise all three.
Then they blame the team when it doesn't work.
 
PS. Do you think the project management triangle is still relevant?

Before you launch your next improvement initiative, ask yourself one question:
 
Have I stabilized the current process first?
 
Improvement efforts layered on top of unstable processes produce unstable results.
 
The gains look real for a few time, then quietly disappear.
 
Standardize. Document. Train. Hold the standard.
 
Then improve.

Hand-drawn diagram showing three targets representing process states. Top-left: an 'Unstable Process' target with dots scattered across all rings. A solid arrow labeled 'What most teams try' points directly to the top-right 'Stabilized Process' target, where dots are clustered near the center but still spread out. A dashed arrow with an X crosses out this direct path. Instead, a second path goes downward to a 'Stabilized + Improved' target at the bottom, where all dots are tightly grouped in the bullseye, then curves up to the Stabilized Process — labeled 'What actually works.' The message: don't try to improve an unstable process directly — first stabilize it, then improve.

The over-reliance on one generation is going to hold Gen Z back. Here's why:
 
 
For the entire arc of human progress, community and tradition moved vertically: elders passed down wisdom, younger generations brought new energy and fresh questions. Progress came from the tension between the two.
 
Now we pretend experience is optional and novelty is enough.
 
Society has stopped valuing inter-generational learning. We are isolating generations from one another. 
 
The caricatures are everywhere now. The "geriatric millennial." The myth that every 22-year-old should be a CMO. These are symptoms of a broken world where new professionals rely on peer-to-peer validation and algorithmic feed.
 
Where has deep mentorship gone?
 
When we remove the elders from the equation, we lose the most critical instinct in professional growth: the ability to ask, "You've been through this before. Teach me."
 
True growth requires respect for the past to build the future.

A black-and-white line drawing showing an older man on his hands and knees at the edge of a deep pit, reaching down with one hand toward a younger person sitting at the bottom. The young person, wearing a hoodie and sneakers, is absorbed in their smartphone and appears unaware of or indifferent to the outstretched hand above them.

Let's be honest. Your endless meetings are a waste of time. Here's how Kaizen organizations turn 10 minutes into millions of dollars in savings:
 
Traditional meetings:
 
→ 30-60 minutes of opinions
→ Problems hidden in PowerPoints
→ Action items that die in email
→ Same issues next week
 
Daily huddles:
 
→ 10 minutes standing up
→ Problems visible on boards
→ Ownership assigned immediately
→ Issues escalate or resolve in 24 hours
 
We implemented this at a 300-person manufacturing facility.
 
Week 1: "We don't have time for daily meetings"
Week 4: "How did we survive without this?"
 
Here's the structure that made a difference:
 
Tier 1 → Frontline - Daily
 
+What broke?
+Who needs help?
+What's blocking us?
 
Tier 2 → Supervisors - Daily
 
+What can't frontline solve?
+Where do we need support?
 
Tier 3 → Managers - 2x week
 
+What patterns are emerging?
+What resources needed?
 
Tier 4 → Leaders - Weekly
 
+What strategic issues surfaced?
+What investments required?
 
Results after 90 days:
 
Problems solved → 73% faster
Employee engagement → +34%
Productivity → +22%
 
P.S. Your teams don't need longer meetings.
 
They need better systems.

A pencil sketch illustration of five businessmen in suits sitting around a conference table, reacting in shock and alarm as a dark, tentacled monster emerges from a swirling vortex at the center of the table. Money bills float through the air. Financial charts and graphs — showing upward trends, bar charts, and pie charts — cover the whiteboards on the surrounding walls. The creature has multiple eyes and dripping tentacles, cracking through the table's surface, symbolizing a hidden threat consuming organizational resources or time during a business meeting.

Stop calling them solutions. They are countermeasures. Here's why it changes how you think: (not a wordplay at all)
 
 
"Solution" means the problem is solved.
 
Done.
Move on.
Forget about it.
 
"Countermeasure" means you countered today's conditions.
 
Tomorrow brings new ones.
Stay sharp.
 
Watch what happens when teams use each word:
 
SOLUTION MINDSET
 
→ Fix it once
→ Walk away
→ Blame someone when it breaks again
→ Resist going back to look
 
COUNTERMEASURE MINDSET
 
→ Counter what you see now
→ Watch how it holds
→ Expect things to shift
→ Plan your next adjustment
 
One word builds complacency. The other builds discipline.

A pencil sketch-style portrait of Taiichi Ohno, the father of the Toyota Production System, depicted as a middle-aged Japanese man in a collared shirt and tie, with a factory floor illustrated in the background. Beside his portrait is a quote that reads: "Something is wrong if workers do not look around each day, find things that are tedious or boring, and then rewrite the procedures. Even last month's manual should be out of date." — Taiichi Ohno.

The operator put all his setup tools on a cart instead of walking back and forth. 

Setup time down 15%. 

No engineers. No capital. No approval process.

That's Kaizen.

A pencil-sketch illustration of a maintenance worker in work clothes and a beanie hat standing in an industrial workshop. To his left, a rolling tool cart sits in front of a pegboard wall displaying organized hand tools including wrenches, screwdrivers, pliers, and gauges. A toolbox rests on the floor beside the cart. To his right, a large metal lathe machine occupies the background. The setting evokes a factory floor with exposed brick walls and overhead pipes.

Traditional management follows Plan-Do-Check-Finish. After checking results, they stop. Here is why their improvements don't last:
 
Companies preach the use of PDCA, but they are used to skip the Act phase.
 
No standardization. No next cycle. Improvement quietly dies.
 
Sound familiar?
 
1/ Team builds a detailed improvement plan
2/ Implementation starts with real enthusiasm 
3/ Results get measured once, maybe twice
4/ The new process gets abandoned when the next crisis hits
 
Real PDCA never stops spinning:
 
Plan → Set the target and action steps
Do → Run the pilot on a small scale first
Check → Measure results against expectations
Act → Standardize what works, kill what doesn't
 
In a Kaizen culture, every completed cycle starts the next one.
 
That's how small gains compound into advantages your competitors can't copy.

A site operations lead fixed a morale crisis in 45 days. His total investment: 3 minutes per day. Zero dollars. Here's the story:
 
 
A manufacturing plant had a turnover problem nobody could explain. The plant manager brought in an HR consultant to interview employees at every level.
 
The complaints weren't what he expected.
 
→ "When I walk past the site lead, he doesn't look me in the eye."
→ "I've never seen him smile."
→ "I sacrificed time with my children for that task. Not a single thank you."
→ "I was presenting to leadership. Every one of them was texting."
 
No one asked for more money.
 
They wanted to be seen. They wanted to know their work mattered.
 
The fix took no budget, no program rollout.
 
 The plant manager committed to 3 minutes a day:
 
→ Greeting people by name on the floor
→ Asking one person about their weekend
→ Saying "thank you" when someone delivered work
→ Putting his phone away in meetings
 
3 minutes of respect and consideration each day.
 
That's it.
 
45 days later, morale scores had jumped. Attrition slowed. The floor felt different.
 
People don't leave bad companies. They leave leaders who make them feel invisible.
 
PS. When was the last time you walked the floor and thanked someone by name?

Do you know what the clearest expression of leadership contradiction is? Executives who say they want a Continuous Improvement culture, but then punish people who report problems. (read this ↓) 
 
Some executives say they want to build a Kaizen culture.
Then they punish people for surfacing problems.
 
Let me be clear about this:
 
You can't build a Kaizen culture in the dark.
 
Kaizen organizations understand that
problems aren't threats. They're treasures.
 
You should strive for true transparency.
 
It means:
 
→ Making problems intentionally visible
→ Celebrating when problems are surfaced
→ Creating systems where hiding issues is harder than solving them
 
Remember:
 
Secrecy is the enemy of excellence.
 
P.S. How visible are problems in your organization?
 
Can people surface issues without fear?

Hand-drawn sketch of an iceberg. The visible tip above water is labeled "What executives see." The massive submerged portion is filled with operational problems: waste, delays, defects, conflict, rework, inefficiency, miscommunication, technical debt, bottlenecks, poor planning, manual work, overproduction, inventory, transportation, motion, waiting, non-value-add, quality issues, misalignment, burnout, bugs, broken processes, silos, lack of transparency, poor alignment, cultural friction, bureaucracy, duplication of effort, hidden costs, missed deadlines, and systemic flaws.

taplio

The Battle

Seha Okudan

Ivan Carillo

Followers

Posts

Engagements

Likes

Performance ScoreSeha Okudan's LinkedIn Performance

Performance ScoreIvan Carillo's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Seha Okudan

Ivan Carillo

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Seha Okudan's LinkedIn Performance

Performance ScoreIvan Carillo's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreSeha Okudan's LinkedIn Performance