The thesis
The technological illusion
Why million-franc budgets drain away in IT, and why AI makes the problem worse.
Technology gets bought. The friction stays.
Boards and CEOs are investing record sums in cloud architectures, SAFe frameworks and AI integration. Even so, a large share of these initiatives fails to deliver the value they were funded for.
The illusion is to take the problem for a technical one. A new platform, another framework or an AI pilot changes nothing about how people work together. AI makes it worse: it speeds up the writing of code and so exposes that the bottleneck was never there.
The reason is rarely the code or the language model. It is the friction between people and technology:
- Senior engineers stuck at a standstill because psychological safety or architectural leadership is missing.
- Legacy organisations that quietly block new systems out of fear of losing relevance.
- A language barrier between the board (business case) and the engine room (Jira, architecture).
Real transformation does not need another process framework. It needs someone who builds the bridge: who steers a development portfolio of over CHF 4 million a year as confidently as the dynamics of a deadlocked engineering team.
Three failure modes
I have lived each of these patterns from the inside, and resolved it.
- 01
The senior deadlock
Seen at: Federal Office of Information Technology (FOITT)
Experienced engineers, technically strong, but in constant conflict with each other, with their superiors and with the stakeholders. Nothing moves when frustration and turf wars drive the architecture.
Earn respect in the code first, then resolve the conflicts one to one, match tasks to the people and shield the team from the outside.
- 02
The commercial disconnect
Seen at: N47 AG
A development team sitting on the bench or building features in a vacuum. Nobody connects the work of the team to a client, a contract or a result.
Give the team a commercial mission: acquire and negotiate projects yourself, set clear architecture guardrails and lead all the way to production.
- 03
The legacy paralysis
Seen at: Swiss Federal Customs Administration
Long-serving specialists fear that they will not be able to operate the new system, or that it will make them redundant. That fear turns into quiet resistance, and the modernisation does not move.
Show prototypes early, take the domain knowledge of the staff seriously, get sign-off application by application and train the users yourself.
The method: architecture, psychology, governance
Code, people and budget cannot be aligned one after the other. They have to align in a single movement.
Architecture
I read the code, the backlog and the system landscape myself. Someone who cannot judge the technology is not taken seriously by the team and cannot defend an estimate in front of the board.
Psychology
I hear what is not said in the meeting: who blocks whom, who is afraid, who feels unheard. I resolve conflicts one to one, not with a new process.
Governance
Scope, roles, budget and milestones in one plan that management and the team both stand behind. Decision papers a board can understand.
My work as a technical advisor in mediation proceedings sharpened this view. Estimating and evaluating the open Jira tasks of a failed project shows exactly where communication tips over into an expensive standstill.
See the track recordNeed someone to step in?
A 10-day alignment audit, a fractional CTO or interim lead, IT mediation: I carry out mandates through my practice, Attic Solutions.
