I Built Apps Because I Was Tired of Broken Processes — LLeanStore Journal

I never planned to become a software developer.

If you had asked me years ago what I wanted to do, my answer would have had nothing to do with writing code or building web applications.

I spent more than ten years in Lean Manufacturing, working with teams to improve processes, reduce waste, and solve problems on the shopfloor. My days were filled with gemba walks, PDCA coaching, standardization, and discussions about how to make work easier and better.

Technology wasn't my focus.

Improvement was.

The same frustrations kept appearing.

No matter which team I worked with, I noticed familiar patterns.

Someone would come up with a brilliant improvement idea.

Everyone would be excited.

An action plan would be created.

Then life happened.

The PDCA report would end up in a folder that nobody opened again.

Improvement actions would continue without a clear owner.

Excel trackers would slowly become outdated because nobody remembered to update them.

Follow-up discussions would disappear into long email chains or chat groups.

Months later, people would ask, "Didn't we already solve this problem?"

Sometimes we had.

We just couldn't find the record anymore.

I kept thinking: there has to be a better way.

I don't dislike spreadsheets.

They are incredibly useful.

But after years of working with them, I realized they often become another task to maintain instead of a tool that supports improvement.

Every time I created another tracking file, I wondered if I was solving the problem or simply adding another layer of administration.

I wanted something different.

Not another spreadsheet.

A system that could make improvement visible.

A place where actions had owners, deadlines stayed visible, documentation was easy to find, and teams could focus on solving problems instead of searching for files.

That's why LLeanStore exists.

LLeanStore isn't just a software shop.

For me, it's a collection of practical solutions inspired by real challenges I encountered in manufacturing.

Every product starts with the same question:

"What problem was I trying to solve on the shopfloor?"

Sometimes the answer becomes an application.

Sometimes it's a template.

Sometimes it's an ebook or a guide.

But the goal is always the same—to make continuous improvement a little easier to sustain.

I'm still a Lean practitioner first.

People sometimes ask whether I'm now a software developer.

The truth is, I still see myself differently.

I don't see myself as a programmer who learned Lean.

I see myself as a Lean practitioner who learned enough technology to solve the problems I faced.

Learning to build software wasn't part of my original career plan.

It became another form of problem solving.

And in many ways, that's exactly what Lean has always taught me to do.

Where I'm going next

LLeanStore is still growing, and so is my list of ideas.

Some projects I'm currently building or exploring include:

Digital PDCA management tools Yamazumi Creator applications TPM-related resources and applications Visual management solutions Leadership and supervisor ebooks Practical templates for continuous improvement

Most of them come from notebooks filled with observations I made while working in factories.

Some of them started with a simple sentence I wrote to myself:

"If only there were an easier way to do this."

Final reflection

I've learned that better systems don't replace people.

They help good people do their best work.

The best operators, engineers, supervisors, and managers I've met were already capable.

What they often needed wasn't another meeting or another spreadsheet.

They needed a system that made it easier to stay organized, follow through, and keep improvement moving forward.

If you've ever been frustrated by lost follow-ups, forgotten improvements, or disconnected spreadsheets, I hope you'll find something useful in the growing collection at LLeanStore.