About¶

One thread runs through everything I've done: take a complex system, make it legible, and build a community around it.

The magazine¶

My first senior role was editor-in-chief of a technology monthly. I got the position by proposing the best plan and then delivering it. Running a magazine is a systems problem disguised as a creative one — editorial calendar, contributors, fact-checking, print deadlines, distribution. I was twenty-something and loved every part of it.

What I was actually doing was documentation: taking a chaotic inflow of technical knowledge and turning it into something a reader could trust.

The IT years¶

I moved into IT project management because that's where the work was. More than twenty years of it — enterprise systems, integrations, transformations, migrations, most recently as a Programme Manager at Tesco CE People IT. Without planning to, I became the documentation person there: the one who built the Confluence space that actually worked, and gave talks on documentation practice and AI tooling. None of it was in my job description. All of it was the same instinct from the magazine.

Telč¶

Five years ago my family moved from Prague to Telč — a Renaissance town of five thousand in the Czech highlands, UNESCO heritage site, no skatepark.

I bought ramps, protective gear and skates for kids to borrow, and started training sessions twice a week. The municipality listened and trusted the project. In September 2026, a 59×19 metre skatepark opens. The full story is at Skate Club Telč.

It was the same thing again: a community that didn't exist yet, infrastructure built for it, values written down, people arriving.

libdrone¶

In 2025 I started building my first drone — not because I needed a drone, but because I needed to understand the system. What came out the other end was a complete documentation stack, written before the drone flew.

That's not backwards. That's how I work: understand the system completely, document it so a stranger can reproduce it without asking a single question, then build. The result is libdrone.eu — the full story is at libdrone as proof.

How I work¶

A mantra I built on the job:

Take position first. Propose the model. Align people to it. Define rules clearly. Focus on the critical 20%. Who–what–when locked. People informed. No surprises. Deliver consistently.

Let me define the model so people can align.

Two things at once: full responsibility for the outcome, and a plan built together with the people doing the work, not handed down to them. I hold the result. The people I work with hold the plan.

The daughter¶

My daughter is six. She comes to skate sessions, asks questions about the drone, and is growing up around a parent who builds things, documents things, and believes falling down is part of learning.

I'm not raising a skater or an engineer. I'm trying to raise a person who isn't afraid of hard things, knows how to learn, and understands that communities are built, not found.

What now¶

Two depths of the same fix.

I design documentation systems — information architecture, content schema, single source of truth — for organisations whose knowledge lives in one person's head.

For companies in Vysočina, I offer the broader version: a part-time head of IT. Your team or vendor keeps running the systems; budget, vendors and priorities get steady attention; and what's in people's heads gets written down — so nothing depends on one tired person's memory.

If that sounds useful, the door is open.