Work

Every Rhyze engagement runs on the same spine: organisational and cultural change, led through technology. What differs is the arena it plays in — IT that has to deliver business outcomes, or IT in service of the living world. The method does not change. The people problem does not change. Only the stakes do.

Arena 1 — IT as an A-Team

IT that delivers business outcomes

Most enterprise IT organisations were built to keep the lights on and are now being asked to win the game. The technology is rarely the hard part. The hard part is turning a cost centre with a service-desk reflex into a team the business actually calls first.

The pattern is always the same. The board wants growth, the CFO wants cost out, and the CIO is sitting on a modernisation programme that is many months behind and quietly losing the room. The programme plan says the mountain is the architecture, the migration, the target operating model. It is not. The mountain is the people — the middle managers whose authority is eroding, the functional leads whose careers were built on the old way of working, the finance partner who cannot reconcile the new cost shape against a budget designed for the old one.

The numbers are not encouraging. BCG’s study of 825 executives and seventy transformation programmes found that 70% fall short of their objectives, with only 30% meeting their targets and sustaining the change. Meanwhile Gartner’s workforce research tracked employee willingness to support enterprise change collapsing from 74% in 2016 to 38% in 2022, as the average employee absorbed ten planned changes a year instead of two. Change fatigue is not a risk to be managed any more. It is the starting condition.

My own reading of why these programmes stall is simpler, and it is a judgement rather than a finding: the binding constraint is almost never technical. It is that nobody is staffed to own the organisational half of the work, so it defaults to whoever has the least time to do it.

Transformation does not fail at the keyboard. It fails in the meeting where a director nods along and then changes nothing.

What I do about it

I work inside the leadership team — not above it, not adjacent to it — to convert resistance into ownership. That means mapping the real influence network, including the people whose authority never appears on an org chart. It means giving the frozen middle a new identity before the old one is taken away, so they become architects of the change rather than casualties of it. And it means landing early wins that are visible and attributable, because hearts and minds shift through evidence, not messaging.

The goal is an IT organisation that operates as an A-Team: trusted by the business, fluent in outcomes rather than tickets, and able to sustain continuous change without an external advisor in the room. When that is true, my work is done.

Where I am brought in

• Transformation rescue — stalled programmes diagnosed, re-sequenced, and unblocked, usually by fixing the people plan rather than the technology plan.
• Operating-model redesign — from cost centre to product-oriented delivery: structure, funding, governance, and the culture that holds them up.
• Leadership coaching — one-on-one work with CIOs and their directs through the shift from command-and-control to leading by influence.
• Board and ExCo alignment — briefings and working sessions that get the top table honestly behind the change before it reaches the organisation.

Who this is for

CIOs, CTOs, and transformation leads in mid-market and enterprise organisations — typically €50M–€2B revenue — whose technology programmes are technically sound and organisationally stuck.

What you get

• The real blocker behind each stalled workstream, named — and a 90-day review where I tell you what has moved and what has not
• A named champion network that outlasts the engagement
• Passive resistance surfaced and named — the quiet “wait and see” that kills programmes, made discussable instead of deniable
• A leadership team that runs the playbook without me

Proof

Nine years as Principal Strategic Advisor and Enterprise Strategist at AWS, running this playbook inside banks, insurers, automotive OEMs, and public-sector agencies across Europe. Co-author of Reaching Cloud Velocity (2020, second edition 2024), where my chapters include those on culture, teams, and the operating model.

Arena 2 — IT for sustainability

Technology in service of the living world

The bottleneck you are already paying for is usually a sustainability outcome in disguise. Energy costs, supply-chain fragility, regulatory load, waste streams — solve the operational problem properly and the nature and carbon outcomes arrive as a byproduct, not a surcharge.

The commercial logic comes first. German and European mid-market companies have operational bottlenecks they know about but cannot solve strategically, and many of those bottlenecks overlap directly with sustainability pressure: energy spend, fragile supply chains, compliance burden, waste. Fix an energy bottleneck with efficiency and renewables and you have also resolved a Scope 1 and 2 reporting problem. De-risk a supply chain with local sourcing and Scope 3 improves on its own. You are not paying for sustainability. You are paying to fix the bottleneck, and the sustainability outcome comes with it.

Where I go deeper is nature data. Biodiversity is the next frontier of commercial risk, TNFD adoption is accelerating, and the data infrastructure underneath it is years behind the demand being placed on it. Most organisations cannot yet answer basic questions about the ecosystems their own sites depend on — not because the science is missing, but because the monitoring data is patchy, the standards are still settling, and the skills are scarce. That gap, between what an organisation needs to know about its nature dependencies and what its data can actually tell it, is where I work.

Nature risk is becoming a board-level number before the plumbing exists to measure it. Someone has to build the plumbing — and make the organisation want to use it.

What this looks like in practice

Geospatial and AI pipelines that turn satellite, sensor, and field data into decision-grade nature intelligence. Diagnostics that tell a leadership team where they actually stand on their nature dependencies and impacts, and what it would take to close the gap. And the same cultural-change spine as Arena 1 — because a biodiversity dashboard nobody acts on is just expensive wallpaper. Data infrastructure, standards, and scientific authority all matter; so does the organisational will to use them. I bring both halves.

Where I am brought in

• Nature-dependency diagnostics — where you actually stand on nature-related dependencies and impacts, and a sequenced path to close the gap.
• GeoAI and nature-data platforms — architecture and delivery leadership for geospatial, remote-sensing, and biodiversity-data capability: build, buy, or broker.
• Bottleneck-to-sustainability programmes — operational fixes in energy, supply chain, and waste, structured so the nature and carbon outcomes are captured and measurable.
• Ecosystem orchestration — assembling and leading the specialist partners a delivery needs, from sensor firms and energy engineers to data scientists and ecologists, under one method.

Who this is for

Leadership teams in Mittelstand and enterprise organisations feeling nature and sustainability pressure as an operational problem — and sustainability leaders who need their agenda to survive contact with the CFO.

What you get

• A nature-risk position you can defend at board level
• Decision-grade data capability, not another pilot that dies in a lab
• Bottleneck fixes whose sustainability outcomes are measured, not asserted
• Internal capability that persists after the engagement ends

Proof

Quoted in IDC’s perspective on geospatial data and AI for climate adaptation. Profiled by Sustainability Magazine. Working relationships across the biodiversity-data spine — data infrastructure, standards bodies, and scientific institutions.

The shared spine

Different arenas. Same five moves

Whether the brief is a stalled cloud programme or a nature-data platform, the engagement runs through the same sequence. The arena changes the content. It never changes the method.

• Map — stakeholder cartography and bottleneck diagnosis. The org chart is never the real influence map.
• Frame — turn the operational problem into a transformation narrative the business can fund and the team can own.
• Move — early, visible wins, attributed to the people who need the credibility. Evidence moves people; announcements do not.
• Build — champions activated, capability transferred, the delivery machine assembled, whether internal or orchestrated.
• Leave — handoff by design. The playbook runs without me in the room. That is the deliverable.

The measure of the work is how quickly you no longer need me.

Rhyze engagements are built to make themselves redundant. Fixed scope, visible capability transfer, and a defined exit. If the organisation cannot sustain the change alone once the engagement ends, the engagement failed — no matter how good the slides looked.

Which arena is yours?

A stalled transformation, a nature-risk question you cannot yet answer, or a bottleneck that might be both. The first conversation costs nothing and commits you to less.