XPollination
XPollination Earth — ecosystems interconnected

Your organization has potential it can't see yet.

I step into your system, carry the load alongside you, analyse the bottleneck, optimize for value — and transfer capability before stepping back.

Sound familiar?

"Our system doesn't scale anymore."

What worked for 20 years doesn't work at this size. One person held everything together — now they're the bottleneck. You've tried consultants. They wrote reports and left. Nothing changed.

Read more →

Or maybe this

"We just need help right now."

There's a gap. Someone left. A role is unfilled. You need someone who can step in today and keep things running — but also make visible what's actually happening underneath.

Outgrowing your system?

"The investment closed. Now we need to scale — fast."

The team is growing after investment, but the system that worked for three people doesn't hold at fifteen. Or you see it coming and want to get ahead of it — before the cracks show.

Read more →

The problem no one talks about

Every organization has two systems running. The formal one — processes, org charts, KPIs — and the informal one: what people actually feel, fear, avoid, and desire.

The informal system is always running. People learned not to say what they feel. But they still act on it. The actions are invisible. The outcomes are not:

  • Missed deadlines with unclear causes
  • Conflict that keeps recurring
  • Turnover in key positions
  • Projects that technically succeed but culturally fail
  • "Resistance to change" that nobody can explain

Management sees outcomes. They don't see causes. You can't steer what you can't see.

"Most often it's a broken communication flow. People learned not to say what they feel. And then they do what they feel but it's not seen. But the outcome of it IS seen." — Thomas Pichler

What I actually do

Bees don't create flowers. They carry something vital between ecosystems that could not connect on their own. I work the same way.

1

Enter and take charge

I take an interim role with real responsibility. Not observing from outside — carrying load, finding the bottleneck, being in the loop. From inside the system, what blocks value becomes clear.

2

Transform what exists

I don't impose frameworks. I identify bottlenecks from inside the system and transform what already exists into working systemic loops — aligned with all connected parts. Documented incrementally, so the system remembers.

3

Transfer and let go

I train the people around me. Bring awareness to the gaps. Define how it's done without me. Train the successor who takes over. Then I step back. The system continues — and improves — without me.

"It drives me to enable others to achieve things they wouldn't have thought themselves capable of." — Thomas Pichler

This is not consulting

Consultants recommend
I do the job, then transfer it
Coaches observe
I carry the load alongside you
Trainers teach
I build the system, then train people to run it
Interim managers keep seats warm
I hand over something better than I found

What changes

  • Bottlenecks identified, value unlocked Patterns, constraints, unspoken dynamics — analysed and addressable
  • Working systems, not imposed frameworks Transformed from what existed, not prescribed from outside
  • Documentation that outlasts individuals The system remembers what was learned
  • Trained people, not dependency Capability transferred. Successor ready. Your team stands on its own.
  • A living learning loop Teams that surface challenges, talk about them, decide, act, and learn from the outcome — on their own, again and again

This cycle — surface, talk, decide, act, learn — is what I install. Not as a framework on paper, but as a reflex in the team. That's why the system doesn't just maintain after I leave. It improves.

The ultimate test: three months after I leave, the system is still running. Six months later, it has improved without me.

How we work together

Start 30 min

Discovery call

A conversation to see if we're a fit. You explain the challenge, I explain the process. No commitment — just clarity.

Phase 1 3 months

Commitment

I enter your system. Interim role or transformation partner — whatever the situation needs. In the loop: carrying responsibility, making visible, documenting incrementally, beginning to transform.

At the end: written documentation of what was found. A projection of what's needed. Decision point: continue or conclude.

Phase 2 up to 12 mo

Integration

The gap is filled by your people. But the culture of continuous change isn't self-sustaining yet. This phase builds that muscle: enabling managers to be the change and teaching them to train their teams.

The cycle — surface, talk, decide, implement, learn — must be repeated many times before it becomes natural.

Phase 3 ongoing

Independence

The system continues without me. Managers know how to surface what's challenging, create space for it, bring in change, and train their teams. I exit. The capability remains.

The paradox of constraints

It sounds counterintuitive: more constraints create more freedom. But when boundaries are clear, ambiguity disappears. People know what they must do. Freedom emerges within structure.

Define what you cannot do Clarity on what you must do
Set boundaries for roles Freedom within those roles
Document the process Autonomy in execution
Define when to escalate Confidence to act without escalating
Record what was learned Memory that outlasts individuals
"Paradoxically, constraints created freedom from ambiguity. I do not decide policy. I do not approve designs. The constraint is in the system, not in my behavior. I don't have to remember — I have to read." — a team member, after working with Thomas

Thomas Pichler

20 years in IT realization. Software engineer, process manager, project manager, program manager, COO. Every seat at the table — each one a system designed: from architectures that scale to organizational structures that optimize for value through design. TU Graz: Software Development and Knowledge Management.

I build systems that make teams self-sustaining. I analyse bottlenecks — not to escalate, but to optimize for value through structure. I create transparency where interests diverge, hold the line with patience, and design outcomes where everyone wins.

"I step into systems, analyse the bottleneck, and optimize for value." — Thomas Pichler

When transformation surfaces challenges too deep for team process work, I collaborate with specialists: Quiring Beratung (trauma pedagogy, resource coaching) and Das Nest (meaning-centered counseling after Viktor Frankl, psychosocial support, faith-compatible depth work).

Remote-first. Worldwide. In-person when the situation shows it's needed.

Let's see if we're a fit

30 minutes. No pitch, no pressure. You explain your situation, I explain how I work. If there's a fit, we discuss next steps. If not — clarity is valuable too.