#sociotechnical — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #sociotechnical, aggregated by home.social.
-
Organisational Dysfunction of the Day
The change they stopped believing in
Context: The organisation has been through four transformations in seven years. Agile. DevOps. Product thinking. Now a platform strategy. Each time, a consultant arrived, a framework was introduced, roles were renamed, and the deck said this time it was different. Each time, the same people learned new tools, attended new ceremonies, adapted to new reporting lines, and rebuilt working relationships that the reorg had broken. Real disruption. Real cost. And each time, the same people did the same work in the same structure, now with new vocabulary. The current initiative has better executive sponsorship than the previous three. The teams are quiet. Not hostile. Just quiet. They fill in the surveys, attend the workshops, and wait for it to pass.
OST explains: The people in the room are carrying two things. The first is the accumulated cost of repeated disruption: workflows relearned, tools replaced, relationships severed by reorganisations, expertise rendered obsolete by the next methodology. These costs are real, and they compound. Even a well-designed change can produce a net loss when it arrives as the fourth disruption in seven years, the cost of relearning outweighing whatever the change itself was meant to fix. The second is the mounting evidence that the disruption does not produce the promised improvement. Vocabulary, consultants, and frameworks have all changed across four initiatives; the design principle has not. What looks like resistance or exhaustion is pattern recognition operating at a high level of accuracy. In DP1, there is no mechanism by which the people doing the work can decide whether to incur the cost of a change that affects them, let alone shape what that change actually is. They receive it fully designed and handed down, and absorb it. The organisation reads the quiet as cynicism, a personal failing to be managed with better communication. People are not tired of change. They are tired of change that was never theirs to make.
#OpenSystemsTheory #SocioTechnical #OrgDesign #changeManagement
***
The series has become a book, available now on Leanpub.
https://www.organisationaldysfunctions.com -
Organisational Dysfunction of the Day
The change they stopped believing in
Context: The organisation has been through four transformations in seven years. Agile. DevOps. Product thinking. Now a platform strategy. Each time, a consultant arrived, a framework was introduced, roles were renamed, and the deck said this time it was different. Each time, the same people learned new tools, attended new ceremonies, adapted to new reporting lines, and rebuilt working relationships that the reorg had broken. Real disruption. Real cost. And each time, the same people did the same work in the same structure, now with new vocabulary. The current initiative has better executive sponsorship than the previous three. The teams are quiet. Not hostile. Just quiet. They fill in the surveys, attend the workshops, and wait for it to pass.
OST explains: The people in the room are carrying two things. The first is the accumulated cost of repeated disruption: workflows relearned, tools replaced, relationships severed by reorganisations, expertise rendered obsolete by the next methodology. These costs are real, and they compound. Even a well-designed change can produce a net loss when it arrives as the fourth disruption in seven years, the cost of relearning outweighing whatever the change itself was meant to fix. The second is the mounting evidence that the disruption does not produce the promised improvement. Vocabulary, consultants, and frameworks have all changed across four initiatives; the design principle has not. What looks like resistance or exhaustion is pattern recognition operating at a high level of accuracy. In DP1, there is no mechanism by which the people doing the work can decide whether to incur the cost of a change that affects them, let alone shape what that change actually is. They receive it fully designed and handed down, and absorb it. The organisation reads the quiet as cynicism, a personal failing to be managed with better communication. People are not tired of change. They are tired of change that was never theirs to make.
#OpenSystemsTheory #SocioTechnical #OrgDesign #changeManagement
***
The series has become a book, available now on Leanpub.
https://www.organisationaldysfunctions.com -
Organisational Dysfunction of the Day
The change they stopped believing in
Context: The organisation has been through four transformations in seven years. Agile. DevOps. Product thinking. Now a platform strategy. Each time, a consultant arrived, a framework was introduced, roles were renamed, and the deck said this time it was different. Each time, the same people learned new tools, attended new ceremonies, adapted to new reporting lines, and rebuilt working relationships that the reorg had broken. Real disruption. Real cost. And each time, the same people did the same work in the same structure, now with new vocabulary. The current initiative has better executive sponsorship than the previous three. The teams are quiet. Not hostile. Just quiet. They fill in the surveys, attend the workshops, and wait for it to pass.
OST explains: The people in the room are carrying two things. The first is the accumulated cost of repeated disruption: workflows relearned, tools replaced, relationships severed by reorganisations, expertise rendered obsolete by the next methodology. These costs are real, and they compound. Even a well-designed change can produce a net loss when it arrives as the fourth disruption in seven years, the cost of relearning outweighing whatever the change itself was meant to fix. The second is the mounting evidence that the disruption does not produce the promised improvement. Vocabulary, consultants, and frameworks have all changed across four initiatives; the design principle has not. What looks like resistance or exhaustion is pattern recognition operating at a high level of accuracy. In DP1, there is no mechanism by which the people doing the work can decide whether to incur the cost of a change that affects them, let alone shape what that change actually is. They receive it fully designed and handed down, and absorb it. The organisation reads the quiet as cynicism, a personal failing to be managed with better communication. People are not tired of change. They are tired of change that was never theirs to make.
#OpenSystemsTheory #SocioTechnical #OrgDesign #changeManagement
***
The series has become a book, available now on Leanpub.
https://www.organisationaldysfunctions.com -
Organisational Dysfunction of the Day
The change they stopped believing in
Context: The organisation has been through four transformations in seven years. Agile. DevOps. Product thinking. Now a platform strategy. Each time, a consultant arrived, a framework was introduced, roles were renamed, and the deck said this time it was different. Each time, the same people learned new tools, attended new ceremonies, adapted to new reporting lines, and rebuilt working relationships that the reorg had broken. Real disruption. Real cost. And each time, the same people did the same work in the same structure, now with new vocabulary. The current initiative has better executive sponsorship than the previous three. The teams are quiet. Not hostile. Just quiet. They fill in the surveys, attend the workshops, and wait for it to pass.
OST explains: The people in the room are carrying two things. The first is the accumulated cost of repeated disruption: workflows relearned, tools replaced, relationships severed by reorganisations, expertise rendered obsolete by the next methodology. These costs are real, and they compound. Even a well-designed change can produce a net loss when it arrives as the fourth disruption in seven years, the cost of relearning outweighing whatever the change itself was meant to fix. The second is the mounting evidence that the disruption does not produce the promised improvement. Vocabulary, consultants, and frameworks have all changed across four initiatives; the design principle has not. What looks like resistance or exhaustion is pattern recognition operating at a high level of accuracy. In DP1, there is no mechanism by which the people doing the work can decide whether to incur the cost of a change that affects them, let alone shape what that change actually is. They receive it fully designed and handed down, and absorb it. The organisation reads the quiet as cynicism, a personal failing to be managed with better communication. People are not tired of change. They are tired of change that was never theirs to make.
#OpenSystemsTheory #SocioTechnical #OrgDesign #changeManagement
***
The series has become a book, available now on Leanpub.
https://www.organisationaldysfunctions.com -
Organisational Dysfunction of the Day
The change they stopped believing in
Context: The organisation has been through four transformations in seven years. Agile. DevOps. Product thinking. Now a platform strategy. Each time, a consultant arrived, a framework was introduced, roles were renamed, and the deck said this time it was different. Each time, the same people learned new tools, attended new ceremonies, adapted to new reporting lines, and rebuilt working relationships that the reorg had broken. Real disruption. Real cost. And each time, the same people did the same work in the same structure, now with new vocabulary. The current initiative has better executive sponsorship than the previous three. The teams are quiet. Not hostile. Just quiet. They fill in the surveys, attend the workshops, and wait for it to pass.
OST explains: The people in the room are carrying two things. The first is the accumulated cost of repeated disruption: workflows relearned, tools replaced, relationships severed by reorganisations, expertise rendered obsolete by the next methodology. These costs are real, and they compound. Even a well-designed change can produce a net loss when it arrives as the fourth disruption in seven years, the cost of relearning outweighing whatever the change itself was meant to fix. The second is the mounting evidence that the disruption does not produce the promised improvement. Vocabulary, consultants, and frameworks have all changed across four initiatives; the design principle has not. What looks like resistance or exhaustion is pattern recognition operating at a high level of accuracy. In DP1, there is no mechanism by which the people doing the work can decide whether to incur the cost of a change that affects them, let alone shape what that change actually is. They receive it fully designed and handed down, and absorb it. The organisation reads the quiet as cynicism, a personal failing to be managed with better communication. People are not tired of change. They are tired of change that was never theirs to make.
#OpenSystemsTheory #SocioTechnical #OrgDesign #changeManagement
***
The series has become a book, available now on Leanpub.
https://www.organisationaldysfunctions.com -
From the Leanpub Blog: The Leanpub Podcast 🎙 Feat. Yevgen Nebesov, Author of The Architecture of Power: See what shapes outcomes. Find where you can act.
#books #leanpublishing #selfpublishing #systemsthinking #powerstructures #organizationalchange #sociotechnical #architectureofpower #changemanagement #softwarearchitecture #leanpub #techlead
-
From the Leanpub Blog: The Leanpub Podcast 🎙 Feat. Yevgen Nebesov, Author of The Architecture of Power: See what shapes outcomes. Find where you can act.
#books #leanpublishing #selfpublishing #systemsthinking #powerstructures #organizationalchange #sociotechnical #architectureofpower #changemanagement #softwarearchitecture #leanpub #techlead
-
From the Leanpub Blog: The Leanpub Podcast 🎙 Feat. Yevgen Nebesov, Author of The Architecture of Power: See what shapes outcomes. Find where you can act.
#books #leanpublishing #selfpublishing #systemsthinking #powerstructures #organizationalchange #sociotechnical #architectureofpower #changemanagement #softwarearchitecture #leanpub #techlead
-
From the Leanpub Blog: The Leanpub Podcast 🎙 Feat. Yevgen Nebesov, Author of The Architecture of Power: See what shapes outcomes. Find where you can act.
#books #leanpublishing #selfpublishing #systemsthinking #powerstructures #organizationalchange #sociotechnical #architectureofpower #changemanagement #softwarearchitecture #leanpub #techlead
-
NEW! The Leanpub Podcast 🎙 Feat. Yevgen Nebesov, Author of The Architecture of Power: See what shapes outcomes. Find where you can act.
#books #leanpublishing #selfpublishing #systemsthinking #powerstructures #organizationalchange #sociotechnical #architectureofpower #changemanagement #softwarearchitecture #leanpub #techlead
-
NEW! The Leanpub Podcast 🎙 Feat. Yevgen Nebesov, Author of The Architecture of Power: See what shapes outcomes. Find where you can act.
#books #leanpublishing #selfpublishing #systemsthinking #powerstructures #organizationalchange #sociotechnical #architectureofpower #changemanagement #softwarearchitecture #leanpub #techlead
-
NEW! The Leanpub Podcast 🎙 Feat. Yevgen Nebesov, Author of The Architecture of Power: See what shapes outcomes. Find where you can act.
#books #leanpublishing #selfpublishing #systemsthinking #powerstructures #organizationalchange #sociotechnical #architectureofpower #changemanagement #softwarearchitecture #leanpub #techlead
-
NEW! The Leanpub Podcast 🎙 Feat. Yevgen Nebesov, Author of The Architecture of Power: See what shapes outcomes. Find where you can act.
#books #leanpublishing #selfpublishing #systemsthinking #powerstructures #organizationalchange #sociotechnical #architectureofpower #changemanagement #softwarearchitecture #leanpub #techlead
-
Listen to this podcast if you want to know why security and security champion programmes may thrive in a good company culture. And also to learn a bit about good company culture. And a lot more.
For me it was yet another reminder how everything in software development is a people problem as well as a technical one.
#security #SoftwareEngineering #sociotechnical #companyculture
via @lisihocke