Organisational Dysfunction of the Day

Team leads

Context: Most teams in modern agile organisations may not formally have a manager in the same sense as before. Many still have someone they report to as an employee, dealing with yearly reviews, career development, and any job issues, but they are not formally involved in the daily work. It should therefore be possible to have leaderless teams, where all members are peers and have the same say in everything. No ranking. Still, many teams end up being appointed a team lead, often because the organisation wants one contact point and one person in charge of the work done. Many in this position try to deal with this dissonance by taking on a coaching type role, seeing themselves as a "servant leader," giving space to the team and protecting them from the outside. Some even try to switch, being directive sometimes, supportive at other times (aka situational leadership). Not only is this a tricky job to have, but it also creates so much confusion in the team about who really decides and is in charge.

OST explains: DP1-type organisations require personal leadership positions, as that is how control, coordination and alignment are managed. Agile tries to counter that for efficiency, having teams take more control of the work, in an attempt to shorten the feedback loop and the learning. This is similar to DP2, with self-organising teams, while adding team leaders is not and is an attempt to adapt them to the existing bureaucratic DP1 model. The problem with this is that DP1 and DP2 fit together like oil and water; they are fundamentally so different that no matter how good the adapters are, they will lead to confusion and operational problems. You can remove the need for this adapter by ditching DP1, having teams everywhere and letting them take responsibility for their own goals and the integration needed to work with other teams. Teams may decide to appoint a leader, though, for their own needs, either permanently or when needed, but it is not a formal position of power. It is a participative democracy through and through.

#OpenSystemsTheory #SocioTechnical #OrgDesign #agile

Organisational Dysfunction of the Day

Quiet quitting

Context: During the COVID-19 pandemic, many things were exacerbated in the population, including how people feel about work. A major trend in America was referred to as the Great Resignation, in which many cited the quality of work as a reason for leaving. Another trend that surfaced about the same time was Quiet Quitting, where employees who are fulfilling their job requirements, but not taking initiative, working overtime or volunteering for extra projects or responsibilities. In short, people are not engaged at work, something the Gallup's State of the Global Workplace report confirms, saying that only 20% of are engaged and 16% are actively disengaged. So not only are sick leaves and absenteeism a problem; when people are at work, just a small minority are actually enjoying it.

OST explains: The reason for these dreadful numbers drops right out of OST and all the research it builds on since the 1950s. Given that the extrinsic motivators for work are satisfactory, such as security, work hours, and pay, the defining reasons for people enjoying work are how well their intrinsic motivators are being fulfilled. A minimal set of six psychological job requirements is the basis and they measure how well a job design works, be it the processes, the technology, the organisation, or the colleagues. If people score well on things like ownership, learning on the job, variety, support and respect, meaningfulness, and career path, they will not only enjoy work, be engaged and produce better results; they will also get a better quality of life.

#OpenSystemsTheory #SocioTechnical #OrgDesign #agile

Organisational Dysfunction of the Day

Individualism

Context: Often, there is a large disproportion in how much people are celebrated for their achievements and when blame is placed for accountability when something goes wrong. This feels natural in most parts of the world, as we want to take care of the people and make them feel as good as possible so that they'll feel well and stick around. Being human, as we say. Even toward the people who clearly take on the accountability, and are even paid good money to do so, often leading to few or no consequences. We value the individual when celebrations are due, when heroes are praised, but hide them when there is not. Typically, hero cultures are also a power play, as the ones praised become stretch goals for the rest, showing what lengths they have to go to feel respected and truly valued.

OST explains: This focus on the individual is almost anathema in OST, not because the individual is not valued, but it realises that the group is the basic unit of life, be it your family, your friends or your colleagues. It's founded on the belief that people have both the need for autonomy and homonomy; be able to self-govern and fit in with the group. Actually, valuing individuality as an acontextual thing hides a vital paradox, as it inevitably isolates people as the problem because there is nothing else to blame. It even goes beyond blaming the victim; it creates them. By instead focusing on the group, and having it take responsibility and accountability, it can take both the praise AND the blame. The individual is protected in the group, and it can jointly grow and learn from successes and failures. As it takes them to their shared goals.

 #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

Organisational Dysfunction of the Day

Analysis paralysis

Context: An agile team is working on a rewrite of an existing legacy solution and feels that its success depends on the function parity it must have with the old one. They therefore end up doing a detailed and extensive analysis to account for as much as possible, even tracking down former developers to get details on some of the more obscure parts. And, even more problematic, they have to figure out which business people own which parts and who all their users are. This drags out in time, and although they have started the work, the extensible analysis prevents them from releasing anything. They are stuck.

OST explains: Agile as a concept is pretty much designed to handle these kinds of situations; at least that is what many may think. It focuses on small increments and puts things in front of the users as soon as possible to tighten the feedback loop, so it makes sense. The thing, though, is that this is not product discovery, as it is an existing product with external product owners and users, both internal and external, and the team has no real product ownership of the app apart from the technical bits. They are not a self-managing product team as a DP2 style should be. Only when they have end-to-end ownership of the whole product, not just a part, can they take full responsibility and accountability so that they can manage it as they please.

#OpenSystemsTheory #SocioTechnical #OrgDesign #agile

Organisational Dysfunction of the Day

Forming–storming–norming–performing

Context: When putting together a new team or making big changes to an existing one, many recommend using Tuckman's "forming–storming–norming–performing" model to turn the team into a coherent and well-oiled unit. It begins with Forming (orientation), moves to Storming (conflict), progresses to Norming (cohesion), and ends with Performing (high productivity). Leaders are advised to manage this process closely as progress is not linear; teams may slip back to previous stages if new members join or goals shift. And conflict is regarded as necessary, as the "Storming" phase is essential to growth.

OST explains: Tuckman's model only makes sense in an autocratic bureaucracy, especially those of the Theory X type, and aligns with Taylor's view that people must be managed to perform properly. This is classic DP1 thinking, whereas in the DP2 style, McGregor's Theory Y is the model, which assumes employees are self-motivated, enjoy work, and thrive under trust, empowerment, and autonomy. Grouped into self-managing groups that have designed themselves using Participative Design. No need for either storming or norming; the teams jump right to performing after forming.

#OpenSystemsTheory #SocioTechnical #OrgDesign #agile

Organisational Dysfunction of the Day

Passivity in team workshops

Context: Workshops are for many a unique opportunity for people to get together and collaboratively work on a problem or a design of something they care about, be it EventStorming, Retrospectives, Design Sprints and such sessions. In larger groups, involving the whole team or even people from different teams, you frequently see people with more formal power join in, be it a team leader, department head, or even a intervening and controlling facilitator, and that often creates an unfortunate dynamic where the participants feel limited and restricted, so much so that many become inactive and passive, and not contributing in a way a way that they could have. Even though they probably really wanted to.

OST explains: This dynamic is very common in autocratic hierarchies, where power over something, be it people directly or even a certain subject like architecture, creates a dynamic where people often submit themselves to that person simply because of their position in the hierarchy. And not because of their expertise or good arguments. These emotional anxieties, often unconscious, can take different forms, in this case a dependency on the leader, but can also be a fight/flight reaction or subgroups forming. These are referred to as Bion's basic assumptions, "bas", and the only way to get rid of them and replace it with real productive work is not having an appointed leader present. Always go for DP2 in workshops, regardless of how you are organised otherwise.

#OpenSystemsTheory #SocioTechnical #OrgDesign

Organisational Dysfunction of the Day

Retrospectives

Context: You and your team have decided it's time to do a retrospective prescribed by the Agile methodology you are using. You all see the use of it and contribute with a lot of ideas and concerns about your work. You record them all and have a vote on the most important ones, but soon realise almost all of them are outside of your mandate to change. You note them down and hope the department lead can do something about it, but know that probably nothing will change, and the whole exercise feels like a complete waste.

OST explains: The members of the team come into this believing they are self-managing, at least to a level where they are able to adjust the work to make it better. Even the Agile methodology says so by incorporating the retospective as a recommended element. An essential element in learning is both looking back and improving going forward. The issue here is that the team is not self-managing, in a DP2 structure, as they are not able to change what really matters to them. Most likely, they are in an agile setup where the teams have been given some control, but most still reside in management outside, in the existing bureaucratic DP1 organisation. The retrospective and the learning it ought to provide are mostly ineffective.

#OpenSystemsTheory #SocioTechnical #agile