Your team is capable.
The project is still stuck.
Usually the problem is not skill or effort. Somewhere along the way, people stopped understanding each other, or lost sight of what they were actually trying to solve. The mismatch is real — it is just not where everyone is looking.
I find it.
Who this is for
You might recognize one of these.
- A capable team is delivering the wrong things with precision.
- You brought in smart people. The complexity only grew.
- Everyone understands their part. Nobody agrees on the whole.
- The project keeps slipping and the explanation keeps changing.
- Everyone is working hard. Nobody can explain why it still feels this difficult.
These are not execution problems. They are clarity problems. And they compound quietly until they become expensive.
What I do
I find the real problem inside the stated one.
I come in, spend time understanding how people in the room are actually thinking — what they assume, what they have stopped questioning, what they cannot see because they are too close to it — and I find the point where things went sideways.
Sometimes the problem you are solving is not the problem you have. Sometimes two sides of the same organization are describing the same situation in completely different terms and nobody has noticed. Sometimes there is one thing that, once named, makes everything else easier to move.
The gap is almost never purely technical. It lives between the people who build and the people who decide. I work in that space.
The engagements that work best are ones where the client genuinely wants to know what is actually happening — not just a more comfortable version of it. That means real access to the people involved, honest conversations, and willingness to act on what we find together. I will always tell you what I see. I need to know you are ready to hear it.
The work
One conversation. A year of wrong decisions avoided.
A software company was hiring for a role they could not quite define. In one conversation it became clear why. They had three distinct product types, each requiring different approaches and different levels of investment, but nobody had ever named that distinction. Every process, every hire, every priority had been made as if they had one homogenous product.
It also became clear they needed two different roles, not one. Hiring a single person would have left critical gaps or burned someone out trying to cover everything.
They came into the conversation not knowing what they did not know. They left with a clear picture of what they actually had, what they actually needed, and a roadmap for building it without overspending or hiring wrong.
That conversation cost them an afternoon.
The most useful thing I told them was to stop paying me.
A healthcare software startup engaged me to professionalize their QA process. What I found on arrival was a blank page dressed up as a process — no tooling, no standards, no deployment strategy with quality in mind. Fixable, given time and buy-in.
But as I mapped how work actually moved through the organization, something else became clear. The company had not yet found product-market fit. They were still in the phase of fast iteration, testing hypotheses, looking for what sticks. At that stage, a mature QA process does not help — it slows the very thing the business needs to do to survive.
What they needed was not me. They needed senior developers with enough QA instinct to keep quality reasonable while moving fast. Building the infrastructure I had been hired to build would have cost them time and money they could not afford to spend on the wrong problem.
I made the case carefully, with specific examples, over several months. By the time the head of engineering reached the same conclusion, we were already aligned. We agreed on a clean transition and I handed over everything I had found.
Sometimes the most valuable thing an outside eye can do is tell you what to stop spending money on. Including their own services.
What others say
Ondrej is self-directed, resourceful, and thoughtful in how he approaches both technical problems and team dynamics. I would not hesitate to work with him again.
Cody Thompson, VP Engineering, Thrive Health
Background
Ten years inside the problems I now help solve.
I spent a decade inside organizations like yours — not as a consultant observing from the outside, but embedded in the delivery, sitting in the meetings, watching how decisions actually get made versus how they are supposed to get made. Healthcare technology, enterprise fintech, telecom, automotive. Large companies with strong teams and persistent problems.
What I kept seeing was the same thing everywhere: the technical problems were rarely the real problems. The real problems were happening in the gap between what leadership believed was being built and what the team understood they were building.
That gap is expensive. And it is almost invisible from the inside.
That is where I work now.
Experience
10+ years in technical delivery and organizational consulting
Industries
Healthcare, fintech, telecom, automotive, enterprise software
Regions
Western Europe, Canada, United States
Based in
Czech Republic, working remotely