They wanted a blue button. We delivered an app that transformed the company

Managing app development sounds simple—until the first sprint begins, the scope changes, and someone asks for a feature that “obviously can’t be missing.” Sometimes it’s organized chaos, other times a joyful ride. And somewhere between those two extremes, real solutions start to take shape. What does developing Gemba or DRS look like from a project manager’s perspective? That’s what this article is about.

A year ago, I was still working in recruitment—finding the right people for the right teams. Today, I help those teams deliver working solutions that transform how companies operate. I didn’t plan it this way, but as life often does, it had a plan of its own—and it went full throttle. Over the past few months, I’ve been involved in developing several applications now running at corporate clients. I helped build solutions like Gemba, DRS, Safework, and Project Tracker. On top of that came workshops, training sessions, and customer meetings where we fine-tuned how to put everything together—and most importantly, how to make it all truly work.

When a customer says they just want “a simple app” and that “a blue button will do,” an experienced project manager knows—it’s only the beginning. Agile development isn’t about planning everything down to the last detail and ticking off tasks. It’s more about the daily balancing act between what’s needed, what’s possible, and what still fits the budget. And it’s exactly in that space—between expectations and reality—where solutions with real impact are born.

Sprints That Make Sense

In every sprint, we sit down with the customer to set clear priorities. Whether it’s Gemba or DRS, there’s always something that matters most right now. Sometimes it’s a safety training module, other times an audit report or a simple performance tweak. The key is that the customer doesn’t have to wait six months—they see results right away. And the team knows exactly what’s worth focusing on.

Translation Between Worlds

There’s often a long road between the initial request and the final solution. And that’s exactly where my role comes in—to translate the customer’s business language into developer-speak, and the other way around.

When a customer says they want it to be blue, the developer asks what exactly the blue is supposed to do. And I’m the one who has to make sure everyone ends up on the same page. Every day, I juggle expectations, technical possibilities, and budgets. I try to keep the customer, the team, and the accountant happy. In a perfect world, all three walk away satisfied. In the real one, it’s a win if none of them are unhappy for too long.

But when I see that Gemba is genuinely improving safety culture, or that DRS is saving time for receptionists who no longer have to run around with paperwork, I know it’s all worth it.

It wouldn’t work without a sense of humor

Development isn’t just about code. It’s about people too. Somewhere between bug fixing and deployment prep, you sometimes need to ease off the gas and lighten the mood. One time, someone on the team suggested that the “Show Chance” button in the Opportunity Tracker should display lottery odds instead. Sure, the idea got scrapped—but the name stuck, and we still laugh about it today.

Humor je v týmu stejně důležitý jako kód. Když spolu lidi mluví, vědí, proč co dělají, a mají prostor se ptát, zvládnou i náročnější sprint. A když to občas drhne, zachrání to kafe. Nebo dobře mířené meme, které vystihne situaci líp než status v Jirové tabulce.

It’s not about the board – it’s about the outcome.

In the end, it’s not about sticking to the Gantt chart. It’s about creating something with real value. Gemba makes it easier to report risks. Safework handles safety checklists. Project Tracker helps plan capacities. Every project is different, but the essentials stay the same: listen, plan, refine, and deliver. And deliver in a way that works—not just in a presentation, but in everyday operations.

Why do we actually do this?

If you’ve made it this far and still aren’t quite sure what a typical day for a project manager looks like—well, it’s a ride. Sometimes it’s emotional, sometimes it’s high-pressure or stressful. And other times, it’s pure flow, focus, and the joy of seeing everything fall into place.

But that moment—when we hand over the app and the customer says it’s exactly what they needed—is priceless. Suddenly, all the tension, the struggles, the fine-tuning, and the compromises fade away. What’s left is the feeling that it was all worth it.

And even when it hurts sometimes, most of those tough moments eventually turn into stories we laugh about over coffee. Because we’re not in it alone—we’re a team. Often, a bit like a family. And that’s exactly why I do this job.


Lukáš Pospíšil – Project Manager

Since 2022, he worked as a recruiter for renowned companies on the Czech market, focusing on talent acquisition and development across various industries. In 2024, he transitioned into the role of project manager and product owner, contributing to the development of corporate applications and digital solutions. He played a key role in the creation of projects like Gemba, DRS, and Project Tracker, combining a strong understanding of business needs with a focus on delivering functional and meaningful outcomes.

Další články

Delegated responsibility in Azure

Cloud technologies have become an integral part of modern business, enabling companies to be flexible, scalable and efficient. A key concept in this area is delegated responsibility, which defines...