Media hub

The Software Transformation Playbook

The series of video about Software Transformation & Modernization based on Systemic Event Discovery Approach

Part 1 – The Invisible Constraints of Sociotechnical Systems

Part 2 – Introducing Systemic Event Discovery Approach

Transformation looks simple only in hindsight. Once the dust settles, the story becomes neat: there was an old system, a vision for the future, and a sequence of steps connecting the two. Reality is rarely that generous. Most transformations feel like confusion, fatigue, and constant patching. Progress is uneven, priorities shift, and the future state remains uncertain for much longer than anyone expects.

The Problem is that change is designed and executed as a linear journey. The reality is different. A sociotechnical system changes only at the rate its structure allows. Architecture matters, but so do relationships. Teams, incentives, ownership, habits, and long-standing dependencies quietly determine what is possible and what is not. Systems remember. They carry the consequences of past decisions, even when the people who made them are no longer around.

This is not a criticism of ambition or effort. It is a criticism of treating transformation as a project with a predefined end state. Transformation is an ongoing negotiation with constraints, incentives, and learning loops.

To learn more about sociotechnical systems, software transformation, and an introduction to SEDA, take a look at the following article: ARTICLE


Part 3 – System Discovery & Diagnosis

Part 4 – Redesign Around Domains

Part 5 – Managing Emergent Behaviours and Feedback

Part 6 – Sustaining Evolution after Transformation


Podcasts

From Legacy to Leading-Edge – Principles of Software Transformation