Brilliant framing on the structural disconnect between delivery workflow and model maintenace. The comparison to software architecture's evolution (C4, living docs near codebase) is spot on, we're stuck treating models as separate artfacts when they should be first-class citizens in the pipeline. I've seen similar pain in teams where the 'update diagrams' ticket sits forever becuase there's no clear home for it in sprint commitments.
Thanks! Happy to see it resonated. And yes, looking at SW/EA's evolution shows a pragmatism and acknowledgement that previously held assumptions (everything flows down from their models) to our current reality holds the key imho for how we must evolve as well. I will try address how I see this in part 2.
Excellent analysis. Really resonated
Thanks. Much appreciated, really. Hope you like the 2nd and (upcoming) 3rd pieces as well
Brilliant framing on the structural disconnect between delivery workflow and model maintenace. The comparison to software architecture's evolution (C4, living docs near codebase) is spot on, we're stuck treating models as separate artfacts when they should be first-class citizens in the pipeline. I've seen similar pain in teams where the 'update diagrams' ticket sits forever becuase there's no clear home for it in sprint commitments.
Thanks! Happy to see it resonated. And yes, looking at SW/EA's evolution shows a pragmatism and acknowledgement that previously held assumptions (everything flows down from their models) to our current reality holds the key imho for how we must evolve as well. I will try address how I see this in part 2.
Awesome post!! Very well written