← Feed
@trondhjort@hachyderm.io
Post #3528716
2026-05-12 07:43 UTC
Organisational Dysfunction of the Day
Burned by design
Context: People are burning out. Not one or two, but a pattern across the organisation. The response is usually more support: capacity planning, better prioritisation, blocking time for work, reduced meeting loads, encouragement to take time off, and reminders that it is okay to set boundaries. Some people recover. Others leave. New people arrive and, after a while, show the same signs. The organisation is aware that this is not sustainable but frames it as a consequence of a demanding industry or a difficult period. It will get better soon; we just need to pass this hurdle.
OST explains: Burnout is not primarily a capacity or resilience problem; it is a job design problem. The conditions most strongly associated with burnout, like lack of control, unclear demands, and absence of meaningful feedback, are structural features of the bureaucratic DP1; not unfortunate side effects. Many do not burn out immediately; they switch off first. Presenteeism, being physically present but mentally absent, is the earlier stage of the same structural problem, and burnout is what happens when even the switching off stops working. The numbers are striking. The WHO projected that by 2020 depression would be the second leading cause of disability globally. Gallup reports that 20% of employees experience daily loneliness, in a setting where people actively come together to produce something. One documented DP1 to DP2 transition showed a 28% decrease in absenteeism and an 81% increase in engagement in the first year, with no major technical changes. Adding support resources helps individuals cope with a system that is harming them, but does not change the system. The tree was planted in the wrong soil; repotting is not optional.
#OpenSystemsTheory #SocioTechnical #OrgDesign #health
Replies (1)
-
Organisational Dysfunction of the Day
Professional leadership
Context: The organisation has invested heavily in leadership development. There are programmes, frameworks, coaching, 360-degree feedback, and a clear leadership model on the intranet. The managers are well-intentioned, many of them genuinely skilled, and they take their responsibility seriously. However, the teams below them are still not performing as hoped. Engagement is middling, decisions are slow, and the best people keep leaving. Some even because of their manager. Leadership quality is clearly not the bottleneck, so what is? In many industries, supervisors are expected to know the craft they oversee. Not so in most IT organisations, where the manager's job is people and process, not technology. That gap has been growing.
OST explains: The problem is not the leaders; it is the existence of the role itself. DP1 as bureaucracy requires leaders because control and coordination are handled by a layer above the real productive work, be it managers in the line, project managers, product managers, or even architects. You therefore need good ones, and training them makes sense within that logic. But no amount of leadership quality fixes the structural problem that the people doing the work are not in control of it. In DP2, the need for professional leadership largely disappears because coordination and control are handled by the group itself. The resources currently spent on developing leaders should instead be invested in developing the team's self-managing capacity. That is not a small shift; it is a fundamentally different theory of how organisations work. A DNA swap.
#OpenSystemsTheory #SocioTechnical #OrgDesign #leadership
Open ##3528715