Making software organizations future-ready — from technology to strategy.
AI brings the disruption, and your experience won't protect you from it. But rethought and organized well, it can become your greatest advantage.
Get in touchLicenses are bought quickly, pilot projects are set up, a few impressive demos follow. And then — surprisingly little happens.
It's rarely about the technology. It's usually because almost everyone treats AI as something it isn't: just another tool.
Two years ago I wrote an article about why software organizations so often fail even though nobody is short on knowledge or skill. The answer: they optimize individual parts in isolation. Three dimensions decide the success of a software ecosystem — technology & architecture, product & business, organization & team dynamics — and value only emerges when they're thought through holistically.
And AI? It's not an ordinary tool swap in the technology corner. It attacks exactly where the boundary between machine and human used to run: it shifts what technology can do — and with it, what product and organization even need to do anymore. That one corner shakes so hard that the other two are forced to move with it, whether the organization wants that or not.
Anyone who just buys tools right now is optimizing one corner and wondering why the value doesn't show up. Only those who rethink the triangle as a whole — technology, product, and organization together — pull the real lever.
Technology is only the beginning here. Product and organization have to change along with it.
I'm drawn to the whole picture. Not because I don't go deep — but because what interests me is how the parts work together, not just each on its own. Over the years that's become a conviction that carries everything I do: the greatest value of an organization doesn't lie in one strong area, but in how closely its areas come together as a whole. And that's exactly where most organizations are weakest.
That's why I'm at home in every corner of a software organization — in technology and architecture, in product, in the organization, in the boardroom. Deep enough to be taken seriously everywhere, and broad enough to see what gets lost between the areas. That's usually what decides everything.
I meet people in each of these worlds as an equal — the developer as much as the board member — and speak their language. That's how I translate where others talk past each other, and make sure the best argument wins in the end, not the loudest one.
Ideally, fully embedded. Not as a consultant who hands over a concept and leaves, but as someone who becomes part of the team and shares responsibility for making it work. That's how I worked most recently — as Domain Product Owner at MOIA, where I led not a backlog, but an entire team of product owners. Before that, in very different kinds of companies, from corporates to startups. Not alongside — inside.
When an organization shifts how it works to embrace AI, that decision isn't made in a workshop — it's made in the daily work: how product decisions get made, how teams are cut, where AI takes on real responsibility and where people do. I step into a concrete role — product, organization, the interface to the board — and shift things from the inside. That's the work I'm best at and enjoy most: right in the middle of it, sharing responsibility, until it holds.
That ranges from „we know something has to change but not how“ to „we have a direction and need someone to help us get there.“ I saw how deep this can go at Zeiss: restructuring the Data & Analytics organization around Data Mesh and Team Topologies — structure, technology, and ownership thought through together. That's exactly what I bring: product ownership, agile ways of working, organizational development — all aimed at one question: where does sustainable value emerge, and what's standing in its way.
Sometimes what's needed isn't another pair of hands on the team, but a sounding board for the person carrying the decisions. Someone who knows the perspectives — technology, product, the board — and helps sort through them without taking over the role itself. I do this when it's the right path. But my strength remains rolling up my sleeves and getting involved.
I've experienced software from almost every angle: as a developer and CTO, through agile coaching and product, all the way to organizational and boardroom work. This wasn't wandering from role to role, but a directed path — every step let me understand the domain more holistically, from code to strategy. Software is the anchor. That's exactly where the comprehensive view I bring to this field today comes from.
Transforming a MaaS (Mobility-as-a-Service) platform organization, planned for Hamburg, Berlin, and Munich. Realigning how Sales and IT work together into a joint product-and-tech organization, building a domain-driven design structure for the roughly 150-person delivery organization, and strategic sparring with the CEO — up to the question of how the company evolves into an AI-driven organization.
Designing and building a fully self-hosted AI solution to support medical work: analyzing workflows, selecting suitable models, and a privacy-compliant architecture (Whisper and Llama 3.3 on ISO-27001-certified infrastructure, end-to-end encrypted, GDPR-compliant). A small project, but an instructive one: not advising on AI, but building it myself — from prompt design to compliance for sensitive health data.
Building a hybrid multi-project and product organization. Aligning teams around long-term product strategies instead of short-term project delivery, introducing Team Topologies for better collaboration, and agile coaching across several teams and projects.
Building the „eVA“ data & analytics organization as a decentralized data mesh architecture, in direct partnership with Microsoft. Designing a Team-Topologies-based organizational model that brings people, value, and responsibility together as a whole — structure, technology, and ownership thought through jointly. Agile coaching across several international locations.
Responsible for the strategic development of the ridepooling user journey. Led a team of five product owners and evolved a product and organizational structure built on domain-driven design and Team Topologies, within a SAFe-inspired environment. Not responsible for one backlog, but leading an entire PO team.
My first real startup environment: introducing agile ways of working at a US-Polish IoT company. Building and coaching seven Scrum teams (around 65 people) across the full span from hardware design and low-level firmware to object-oriented mobile app development.
Scaled agile transition for an engineering software company: building and coaching 15 Scrum teams (around 150 people) across four international locations, including a custom-built agile ALM environment. One of the largest transformations of my career.
The full path that got me here — the roots in the craft:
Whether you're at the very start and looking for direction, or already know where you want to go — the best way to find out if I'm the right fit is a conversation. Most of what I bring shows up in the exchange itself anyway.
Drop me a line about what's on your mind. I'll get back to you.
robin.adam@nordwind.work