Monday, March 19, 2018

Continuous Deployment - more than a toolchain

A while ago, a prospective client approached me, "We've purchased a Continuous Deployment Toolchain, now we need someone to do the training." I was invited to meet the Head of Administration and an Admin team lead. 

Story Time.

Paying for vaporware

"Here is the toolchain we bought. We paid a six-figure amount for the strategy and a five-digit sum for the implementation. Now we need someone to train our Admins so that we can roll out the new process for all of our 500+ projects in the next Quarter."

I glanced at the Powerpoint slide.
If you think this is worth $100k, well ... I have a bridge to sell.

It's about culture!

I started asking: "Why the Admins? Wouldn't you much rather want to train the developers?"
I learned that this project was spearheaded by the Head of Administration and they didn't want the Head of Development to take credit for their idea. Plus, the introduction of Continuous Deployment (CD) was mainly supposed to relieve the efforts of the Admins.
Taking note, I asked: "So how did you come about this project in the first place?" In painstaking detail, the Admin team lead explained that the process of getting a release through the door often took months - and CD, automating the entire ordeal, would cut it down to minutes and free their time for much more important things.
Nodding, I probed: "So, the developers will check the code into git?" - "At the moment, they either send us the code via email or put it onto a Shared Folder." Remember - this was a good decade into the 21st century! "And then?" - "We manually compile the sources. In some cases, we've created some scripts to ease the job, but those scripts are brittle and fail with every new release." - "Have you considered giving the job of creating maven builds to the developers?" - "That's not their responsibility. We can't guarantee for the correct installation of the software any more if we let them do it."

Next icon. "What's Sonar supposed to do in this construct?" - "Check the code quality." - "Do you have code conventions or unit tests?" - "Neither." - "And who is going to do that job?" - "That would be the Offshore Testing Department."

This was getting more intriguing by the minute. "Are the Developers trained in the use of Ansible and Docker?" Shaking heads, "We will provide standard scripts and containers for others to use." Probing deeper, "How do you know which Ansible Configurations and Docker Images will be needed?" - "We will just create those which replicate our current environments." - "Are your Admins trained with either tool?". A smile, they figured that finally, I was coming to understand them: "That's why we need you."

"Just one last question, how are the tests going to execute?" - "If you look closely, after a Docker Container is created, it will automatically be deployed to the Test Stage for Manual Testing."

This was going to be an interesting ordeal.

Get ready for Continuous Deployment!

I devised a strategy and proposed the following approach:
  1. Basic Leadership training for beginning agile transformations
  2. Process Redesign Workshop to reconsider the current build process and responsibilities
  3. Start a Cross-Functional Team from across all departments to integrate the CD pipeline on one project in the next quarter.
  4. Coach this team in fundamental Software Craftsmanship - including Pairing, Test Automation and CI.
  5. Use the pilot team to set up meaningful quality metrics and create a working build pipeline.
  6. Involve others in the learning and gradually move towards cross-functional teams with e2e responsibility.

I was informed that my offer was probably a misunderstanding. I replied, politely, "If you ever choose to look deeper into this offer, feel free to reach out." They never did.

The toolchain is irrelevant until you have the culture and structure in place. CD isn't something that a single department in a silo organization can do all by themselves. Instead of architecting the entire pipeline upfront, experiment, discover what works - what helps - and what is actually being used!

If you seriously intend to move towards CD, the long journey and steep learning curve really pay off once the peak is climbed.
One disclaimer, though: There's no guarantee that you can keep any of your current processes, structures and mindset.

Sunday, March 11, 2018

Five signs you've got the wrong agile coach

You've set out to begin your organization's "Agile Transformation" and, lacking the expertise, you've brought in external consultants and/or coaches to make the endeavour successful. But since you're not agile yet, how do you know whether you have the right people on board?
Here are a few pointers that will help you identify rotten eggs - i.e. you can be almost certain that after the consultants leave, the show will be over, and best case you've only wasted money for nothing.

#1 - Lack of Battle Scars

Having the seniority to assist another organization in their agile transformation, the coach should have a lot of war stories to tell. Stories of experiments, pitfalls, troubles, joyful moments and cheerful victories. Stories of what they have experienced firsthand (not hearsay!).
What people tried, what they set out and where they landed - the differences between intent and destination, the obstacles and dangers on the journey - the small nudges that made the difference and so on.

If you see that the coach either has little to say from personal experience or is only quoting others ("double-hearsay"), beware!

#2 - A shelf full of solutions

It doesn't matter what your problem is, they already have the bottled solution ready! Just follow their advice, and you will become Agile. NOT!

Especially when they promote solutions as a silver bullet, i.e. universally applicable without concerns for context - you're in for trouble.

#3 - Change without change

Following pre-concocted agendas, outlining the change on fancy slide decks without ever talking to the people doing the actual work or knowing the real struggles they have isn't going to work.
The first three questions I would expect to ask: "Why would you want to become Agile?", "What will be different in a year?" and "What have you tried so far?".
If there are no comprehensible answers to these three questions: what exactly do you expect as a result?

#4 - Not rocking the boat

Many experienced consultants have learned to avoid challenging status quo and messing with people in positions of power. This is a great approach to maximize the amount of billable hours and to please those who decide whether their contract will be renewed.
As attributed to Einstein, "Problems can not be solved with the same mindset that created them.", it's essential to rock the boat - to identify and tell people about the root cause assumptions which lead to the problems that an agile transformation is supposed to solve. And if key decision makers aren't aware how they are contributing to the problem - how would they know what they must change to solve it?

Consultants who only compliments senior management aren't going to make an impact.

#5 - We've got this!

Probably the killer criterion for spotting fake coaches: They can do it by themselves! They have so much experience and expertise that whatever is brought to them, they have the right answer. Senior management doesn't need to involve at all, because the coach knows how to handle everything. Teams don't need to worry, because the coach will teach them everything they need to know.

The coach who offers the solution without teaching you how to find your own solution - doesn't help you learn, and if you don't become a learning organization, you're not going to be agile.


I would like to conclude with my favorite TheraminTrees quote, "People who don't want you to think are never your friends!"

A "coach" who doesn't make you think and challenge how you think - is the wrong coach.

Sour aftertaste? 
Let's fix this: Here are ten signs you might just have found the right coach!

Sunday, March 4, 2018

Eight character traits of good leaders

Many people like to be in a position of leadership - without ever considering what makes the character of a leader. In this article, I propose a list of eight character traits portraying good leaders, regardless of position, rank or role.

"Leadership" - image courtesy of @danielmassoud4 taken from


We acknowledge and respect people who walk the talk, who do what they say, who have and convey a clear purpose and work towards that purpose themselves.
Nobody would waste time with a hypocrite or someone who themselves doesn't know what they want or where they are headed. Good leaders spend a great deal of time considering what they want to accomplish and why - and their very being encourages others to join in.


We natually have a tendency to commend diligent people. Those who are pay the necessary attention to detail while still having a clear direction tend to be successful and a pattern for those around them.
It's often the small things that become the downfall of people in position in power - so great leaders take care not to get stumbled over small rocks.


People who are willing to go the extra mile for what they believe in serve as positive examples. Few can shrug off a setback and march forward with unwavering zeal - so those who do will eventually rake in successes that are the result of harsh failure learning. Like this, they become exemplary even to those who never knew about the troubles along the road.


When you firmly believe in what you do, you're unashamed and unafraid to act and speak. Even when we disagree, we still notice and acknowledge those who are bold to take a step, expose themselves and their ideas to a broader audience and are willing to take the heat and fire of criticism and resistance.


People look for those that do something for everyone, maybe even for others. On the other hand, we disdain those who selfishly try to fill their own coffers and get out of the line of fire. Because of this, we admire those all the more who put themselves out of the center of attention and put the social benefit of their ideas and goals first.


Everyone has different needs and different perspectives. We like to be accepted where we are and how we are. While bad leaders express ruthlessness and recklessness, good leaders spend time to accomodate those around them, making them feel welcome and cherished. Being social creatures, we tend to flock around those who make us feel comfortable.


"Measure twice, cut once" - when dealing with people, we often don't get a second chance, so it's best to spend time pondering how we and our actions affect those around us. We need to be watchful what we say and do - a single careless word can burn bridges. On the other hand, a nice word creates a positive atmosphere, a little support in times of need builds bridges and by moving from basic courtesy to full acknowledgement of others' circumstances, we become people who others enjoy being around.


"We all are where we are" - yet, that's no reason to stay put. Nobody is perfect, but we need to move on. Commendable leaders aren't only good at being who they are, they're continuously improving upon themselves. That character quirk we noticed yesterday is a great opportunity to reflect on how we want to be - and what we can do to be even better people today. By not being stuck either with themselves, their ideas or the world around them, the best leaders continuously adapt themselves, their ideas and their environment to move forward.


Leadership isn't about position. It's about who you are - and no classroom training can make you a leader. Only you yourself can do that, and you must work on your character in order to be one. This is not a one-time act, it's a lifelong process: The day you stop working on your character is the day you have stopped leading.

Saturday, March 3, 2018

What is a Scrum Master?

The question, "What is a Scrum Master?" may sound easy to answer - RTFM, the Scrum Guide has a very concise section. But when looking at what a Scrum Master really does, it becomes a profound topic in and of itself.

The narrow definition

The most narrow definition is that it's the one person on a single Scrum team making sure the Scrum Guide is being followed and the team successfully delivers on their Sprint Plan. Most people work in organizations that think of this narrow definition and also behave likewise.

For people looking to move into such a role, the best starting point is reading the Scrum Guide, getting a few books (such as Geoff Watts: Scrum Mastery) and a certificate or two (PSM-I from or CSM from Scrum Alliance come to mind) then start job hunting and learning on the job.
Sticking with the narrow definition is not a very fulfilling job, as systemic impediments never get addressed.

The broad definition

The most broad definition is that it's a person coaching an organization on becoming more agile, challenging existing paradigms and opening the way to more flexibility, and this means individuals, teams and managers on every level - from intern all the way to senior executive.


When it comes to being a Scrum Master in a broader sense, then Scrum is maybe 5% of the picture. In fact, Scrum itself will become less and less important and - just like the Agile Manifesto states - people and their interactions will become prevalent.

Agile Frameworks

The first thing you will need to explore is the other agile frameworks, starting with the team-level ones such as Extreme Programming and Kanban - and getting yourself familiar with the organization-level ones such as SAFe (Scaled Agile Framework), Nexus, LeSS (Large-Scale Scrum), DAD (Disciplined Agile) and S@S (Scrum at Scale). Of course, that doesn't mean you will be using all of these - but you should have a sufficient understanding to comprehend where they are useful and what their limitations are.


Having a bag of agile theory under your belt, you need to move into organizational design and management by reading publications from authors like Drucker, Deming, Crosby, Taguchi, Taylor etc - and learning to compare and recognize their models.


You will also want to explore the field of psychology to understand how and why people tick the way they do. That's a vast field, where you might want to reach into behaviouristics (Pavlov, Skinner), basic needs (Maslov), negotiation models (Ury), transaction models (Berns), habits (Duhigg) and many others.


To round this off, you may want to gain a deeper understanding of philosophy, which also has a lot to offer, with the most notable things you may want to get being logic (assumptions, fallacies, mental models), axiology and epistymology.

It's not very useful to do all of this upfront, but continuing to learn while you're on the job and working to continuously increase your sphere of influence within the organization.


The Scrum Master is a very deep role which, when taken with a deep, serious learning attitude, has a lot to offer and provides a tremendous field for growth. If you put your heart into it, you will reach tremendous awareness of and influence on your surroundings.
Don't let people tell you that a Scrum Master is "just a team role". Great Scrum Masters can make a massive impact on their organizations.

Sunday, February 25, 2018

The effect of new ideas on learning

"It's always good to learn something new" - or so the proverb goes. Let's examine whether this is true, and how to maximize the impact of our learning.

In this article, I will classify new ideas into two categories: growth beliefs and limiting beliefs.

How our beliefs affect our learning.

To keep this article short, I will make a claim that I'm not going to back up further: Whatever we learn is merely a new belief, a new concept we hold about reality.

Growth beliefs

A growth belief is an idea which accelerates our future learning. Adopting a growth belief has a sustained beneficial effect on our ability to understand the world. Growth beliefs tick off slowly by slightly broadening our horizon, allowing us to integrate new ideas faster. Thinking in networks, a growth belief is a belief where further beliefs can easily be attached to. The following illustration visualizes the idea:

Upon the growth belief, further ideas are built and can be adopted easier.
The growth belief acts as a sustainable basis for growth of ideas

Limiting beliefs

A limiting belief is an idea which inhibits our future learning. Adopting a limiting belief has a long-term negative effect on our ability to understand the world. Unfortunately, the danger of limiting beliefs is that in the short term, they might give a massive boost to our ability to understand certain things. Again, thinking in networks, a limiting belief has a strong connection to related ideas which are oftentimes adopted immediately - while at the same time, the limiting belief is inconsistent with other ideas which become harder to adopt:

The limited belief is closely related to similar ideas
 - and inconsistent with other ideas, which we then struggle with or reject. 

When conflicts between ideas arise, we usually reject the new idea based on the ideas we already hold. Subconsciously, we find reasons why the new idea is wrong - either by trying to prove how it is deficient, or by trying to prove how our current belief is "superior". We are no longer open to listen to the merit of the new idea, as long as the cost of adopting it feels higher than the cost of rejecting it.


Unfortunately, there is no certain way to know upfront which beliefs are growth or limiting ideas. As a general rule of thumb, though: The easier an idea tries to explain a complex problem, the more likely it will turn out to be a limiting belief. Or, in more scientific terms: The level of explanatory power of an idea is directly related to our long-term understanding of reality. Beliefs which we hold despite low or no explanatory basis are most likely limiting and should be put under scrutiny.

When ideas with higher explanatory power conflict with ideas we already subscribe to, we should examine what really makes us believe the things we already do and potentially discard the ideas we already hold.


It's only good to learn new things if we can either understand where the things we learn inhibit us, or if we have a mindset of letting go of inhibitive ideas. The latter is extremely hard, as beliefs we have already adopted are often strongly related and make up what we see as "real" - so the best thing is to avoid the trap of adopting limited beliefs wherever we can spot them.

Another thing we need to understand: One person's growth belief might be another person's limiting belief, based on both where the person currently stands and what the person is looking for. When we discover ideas to be truly limiting, it may already be too late to discard them without rejecting a major portion of who we are.

So - be careful what "new things" you learn! It might cost you dearly, years in the future!

Sunday, February 18, 2018

Thought Reform and Mind Control in the Agile Community

How do we know we're making progress towards a meaningful goal? Are we following a carrot on a stick - or even worse: are we being led astray in our attempts to become more agile?
Has the agile community gone too far in their attempts of making agility a lifestyle?

I feel the need to write this post because I recognized some patterns in the agile community which I know all too well from the years of my life I spent studying and discerning the phenomena of psychological abuse. 

But let me start from the beginning.


This article isn't singling out anyone or pointing fingers.
It's not about calling, labelling or stigmatizing anyone.

 Instead, it is a reminder to those who already display tendencies described in the article that they might be on a dangerous track - and an invitation to think for those dealing with such individuals.

If you feel that this article is talking about you or anyone you know, ask yourself: "Why?"
Why are we seeing those behaviours in the agile community?

Dangerous Behaviour

In this section, I will examine a list of behaviours based on the four common domains of "Mind Control" - neither with a claim that some specific persons would do all of these nor with a claim that some of the can't also be found elsewhere, just with a note that these behaviours raise a red flag. For brevity's sake, I am going to limit this to central points that are most notable.

I. Mind Control

Behaviour Control

a) Major commitment

of time and/or money for indoctrination purposes.This is talking about stuff like requiring attendance at group events and the trainings required to climb up the pre-defined hierarchy.

b) Group Think

instead of individual expression of thought. Society grows by bringing completely new ideas to the marketplace of ideas, then examining these based on their merit, instead of their point of origin. Group think means that ideas contradicting the group's doctrine will be rejected even if they are true and useful.

c) Obedience and Punishment

to enforce compliance. Obedience to the group's rules is paramount to keep order, even if said order is detrimential to growth and learning. Punishment and the threat thereof is used to keep members obedient.

Information Control

a) Deception

taking many forms, from outright lying over hiding facts all the way to distorting unpleasantries in order to make them acceptable. It's pretty much the opposite of transparency.

b) Discourage dialogue

with people who are critical towards the organization and its goals, including outsiders, ex-members and dissenting current members.

c) Compartmentalization

of sources. Information provided by "members in good standing" is good, information provided by "others" is bad, especially when in conflict with the organization's goals.

Thought Control

a) Axiomatic Truth

of any statement proclaimed by the group. There must be no doubt that the official doctrine is true by definition.

a) Black vs. White

thinking. There is no ambiguity and no alternatives. If it isn't A, it is B. This provides the basis for simple explanations to life's complex problems.

c) Us vs. them

mentality: There is no sane reason not to be on "our" side: Everyone else isn't enlightened enough or has a problem.

d) Loaded Language

reducing complex topics to contrite buzzwords. This inhibits, rather than growing, a deeper understanding.

e) Forced positivism

where people may be branded or shunned for "negative thinking".

f) Thought stopping

techniques are applied to suppress the need for analysis, critical thinking or constructive criticism of the group's doctrine.

Emotional Control

a) Manipulating feelings

of people for or against people or ideas by using psychological or linguistic triggers.

b) Blame shifting

towards those expressing ideas inconsistent with the group. Nothing can ever be the group's fault, it must be those who see the problem. Also manifests as: "Shooting the messenger".

c) Use of fear

tactics to keep people silent and in line. This is also combines with:

d) Phobia induction

in current members. Something bad will happen if you follow other ideas, or, God forbid, decide to leave the group. And remember: there are no legitimate reasons to quit - ever!

II. Apologetics

Apologetics is a huge chapter in and of itself. Talented apologists have a massive arsenal at their disposal, with the main goal of silencing dissent. Apologists tactics range anywhere from "working the issue" towards character assassination. Again, for brevity's sake, I will reduce this to an examination to the three core tactics employed by apologists.

Logical fallacy

The largest category of weapons in the apologist's arsenal is the employment of logical fallacies. There are too many to discuss - it's really worth exploring this domain of philosophy to be less prone to manipulation, so we will limit this to the most notable ones.

a) "Misunderstood"

When caught on a contradiction, the first line of defense will be "Ah, you misunderstood". Can be well combined with Loaded Terminology ("join us to lean what we mean") and blame shifting ("YOU get it wrong!") Note that the apologist will do their best to avoid clarifying the real meaning, as this would put the burden of proof on them.

b) Moving the Goalpost

Another powerful bait is to move the topic away from items which can be scientifically examined and scrutinized by changing the meaning of things mid-discussion. Combines very well with Loaded Language ("It means something else") and axiomatic truth ("If it were wrong, we wouldn't say it").

c) Appeal to Authority

or to Popular Opinion. Instead of tangible evidence, names and titles ("Doctor X") or sweeping statements ("Everyone knows ...") are offered as "proof".

Making it personal

Instead of arguing or providing evidence about the matter, the person of the critic becomes the topic of discussion in an attempt to "shoot the messenger" to avoid that the message itself needs to be examined. This can range anywhere from:

a) Who are you?

It looks easy to discredit a person who doesn't have the combined experience of those one the other side of the argument by simply stating, "We have industry leaders, professors and scientists - and you are?" If this doesn't end the discussion, they will move on to:

b) Mud slinging

and shifting the dicussion towards personal shortcomings of the dissenter, either in tangible aspects ("You failed at ...") or even their presumed emotions ("Why do you have such anger/hate towards ...?")

c) Character assassination

Providing unsubstantiated reasons why listening to the person speaking the different idea is a bad idea, such as "The person is a fraud, a criminal, psychologically defective and you'll be damaged if you listen"

Shifting the burden of proof

What's more convenient than turning the entire discussion around - instead of "Why should I do X?", let the dissenter explain "Why do you not want to to it?", which allows the apologist to lean back while the critic has to waste time and energy, exposing their thinking and providing additional places of attack for the apologist.

Instead of digging deeper here, let me refer back to Hitchen's Razor: "That which is assumed without evidence may be dismissed without evidence." What this means: If someone claims that a certain thing works, you don't need to disprove that. They must prove that it does.

I also want to combine this with Sagan's Standard, "extraordinary claims require extraordinary evidence" - so the next time someone says that "this always works" or "it can be used in any context", remember: that's an extraordinary claim which still needs to be proven!

III. Change of character

Thought reform modifies people's character in ways that are detrimental to society as a whole. In order to avoid getting too personal to anyone, I will keep this section at short, commented headlines.

Situational ethics

Things which a normal person wouldn't do in normal circumstances are okay when it's required to protect the group's special interests or to further the group's declared mission. For example, being deceptive, outright lying or saying bad things about outsiders.

Need for conversion

Once you believe your group has "The Truth", you want to do everyone a favour by converting them to your group. Rejection isn't taken lightly, as this attacks the very thing you believe in. "They" must be evil if "they" don't take your gracious offer.

Following leaders

The group's charismatic leader(s) offer "The Truth", so what comes out of their mouth must be good. Critical thinking is shut down when words are spoken by a leader. Members of thought reform movements just can't understand why other people wouldn't have the same level of veneration for their leader as they do.


You don't have time to waste on things such as thinking or interacting with outsiders, as you need to do things which further the agenda of your group. After all, you have an important mission - and it can only be achieved if you're fully dedicated.

Mental shutters

You are no longer open to ideas that conflict with the group's ideology. Instead, you invest time into ideas that are "in party line".

Limited social interaction

You reject people who propose ideas that don't fit with the group - and break "dangerous" relationships, warning others about such "poisonous/toxic" people as well.


You don't understand a joke at the expense of your "truth". NOBODY is allowed to joke about the truth, and you will make sure that those who dare do so get put into place.

Concluding words

Thank you for continuing to this point. It is sad to see that even in the agile community, we see many people who are affected by such symptoms without even realizing. It's even sadder to see when people entrench themselves further in such limiting beliefs and behaviours day by day. Such behaviour is often the consequence of having too much vested interest in this entire Agile/Scrum thing a bit too far or too seriously.

I would leave you with a few open questions, that you may reflect for both you and those around you:

  • Do you see positive growth in character caused by following an Agile career?
  • Is there a willingness to discuss the option that there might be the slightest chance that all of it could be wrong?
  • Are sound, factual reasons brought forth when contradicting ideas are raised?
  • Is there respect and positive openness even towards those who hold conflicting beliefs?
  • Are any detrimental behaviours developing, and what is being done about them? 

Wednesday, February 14, 2018

Five Things to avoid as Scrum Master

What makes a good Scrum Master, what makes a bad Scrum Master? Here is my short list of things a Scrum Master will not do in my team. This post is written from a Product Owner perspective, so YMMV.

#1 - Dogma

This has got to be the absolute #1 on my list as it is my personal pet peeve.
I don't care what this or that guru said about Scrum, and I don't even care what you think Scrum means. I'm not using Scrum for Scrum's sake. I care for stuff that works - and for fixing stuff that doesn't work. I've had too many conversations with certified ScrumMasters who claimed "According to Scrum ...", and my only response was: "Show me the passage in the Scrum Guide!" (knowing full well they were proliferating a myth). If you can't explain to me (or my team) why the things you think should be different would work better than what we're currently doing, you're wasting everyone's time.

#2 - Factions

Your job as a Scrum Master is to create one high-performing team, and that just won't work if the team is wasting energy fighting against others (or even worse, against each other). If factions exist, you should try to mend them - and if none exist, I would expect you to be the last person to create some. Factions often come with actions such as placing blame (aka. finger-pointing) or perceived feelings of superiority. I expect you to not tolerate, much less support any such behaviour.

#3 - Menial labour

Also known as the "Jira Admin". If your entire responsibility in the team boils down to doing the things nobody else wants to do, such as updating tickets, writing reports or organizing meetings, you have clearly not understood your role. As Scrum Master, your value is exclusively limited to the additional performance you bring out in the team. If you can get 5 people to work 50% more effective, you're pulling your weight. If, however, you're just doing work that a minimum wage worker could do after a week of training, don't expect a higher pay than minimum wage.

#4 - Breach of trust

As Scrum Master, I expect you to be the person in the team who has the highest level of trust from anyone within the entire organization. I would expect that people should feel ready to confine their innermost secrets to you, even stuff that's totally NSFW, because they might need someone to talk about it in order to have a clear head for work. If you do stuff like reporting to management or tell team internal information to outsiders, you will never again be able to regain the trust you need in order to do a proper job.

#5 - Project Management

I do agree that not every team is ready for self-organization and sometimes, an intermediary path needs to be taken. As Product Owner, the person who would be doing inevitable PM activity would be me. As Scrum Master, frankly, you don't even need to know more about the team's progress than I and the team feel necessary. There is no reason why you should feel the need to coordinate, organize or report anything for anyone. Well, unless you're being asked to - and even then, you should ask "Why?"


If I see you, my Scrum Master, doing any of the above things, you're up for a long conversation with me regarding your role and responsibility. You will walk out with a clear list of things that you will change about your own behaviour as soon as possible.
If I see you continuing these things against better knowledge, I will make sure that I get a Scrum Master on my team who knows their ropes.

Sunday, February 11, 2018

The Agile / DevOps ecosystem

The question, "How does an organization, especially one that is already using an agile framework, benefit from DevOps?" is very common. In this article, I provide a succinct answer to this question by examining the benefits provided by some standard frameworks.

The development lifecycle

Irrespective of which approach a company is using, it all starts with a customer need:
This need must be understood, so we need to invest some effort into understanding.
In Scrum, we call this "Refinement". It could also be called an Ideation or Prototyping process. Regardless of how you call it - it's essential to build the right product!

Once understood, our next job is to build something. Any kind of iterative approach encourages us to build just a little, then learn from that. We want to minimize our upfront planning efforts and jump right into doing delivery work. In Scrum, that's our timeboxed "Sprint".

The objective of delivery is to get something shipped right to the customer, we want to make the product available. This is often called "Minimum Viable Product", in Scrum we call it the "Product Increment".

When we got the product out of the door, we want to learn how customers respond to it. This is where most agile implementations disconnect: Scrum has a "Review" - although the Review still happens disjoint of both the problems and opportunities arising when our product hits the shelves!
What happens in the "Real World" becomes the job of Support, Customer Service or Marketing.

This final piece of the puzzle is vital to build an even better product in the future. We want to iterate a full cycle in increments as small as possible:

The business opportunities when integrating this cycle are immense: Anything that is of value can be turned into revenue, anything that wastes effort can be turned into saving. To harness this potential, it's essential that a single team has the ability to recognize and create these benefits.

Now, it's time to take a closer look at some agile frameworks:

Standard frameworks


Scrum is the most common framework. It excels as a delivery framework. Based on the Scrum Guide, it neither cares for what happens in order to get the right items into the Product Backlog nor what happens after the product increment has been delivered.
A small fly in the ointment is that Scrum scopes the timebox: it doesn't bode well for a Scrum team to deal with unplanned work. Yet, everything that happens with customers in real time is hardly planned, much less does it make sense to plan it upfront.


Like it's cousin Scrum, Kanban focuses strongly on optimizing the delivery process. Kanban provides less emphasis on getting a planned shipment through the door, offering higher flexibility in dealing with unplanned work. Teams that have productive maintenance responsibility often fly well with Kanban.

Side note: Scaling Frameworks

Scrum scaling solutions, such as Nexus, Scrum At Scale (S@S), LeSS focus on doing the same thing with more people - getting better at delivery. Combining these frameworks with Enterprise Kanban practices, like suggested in SAFe, is still limited to the delivery portion.
While SAFe strongly encourages integrating DevOps, the suggested use of DevOps is still restricted to getting the product through the door in the most reliable fashion.

Design Thinking

It's often adertised that Design Thinking combines well with Scrum, and indeed it does. Design Thinking addresses understanding the customer need through systematic exploration before delving into a more costly delivery process.

Lean / Six Sigma 

Regardless of whether you're thinking Lean, Six Sigma, or the standard combination "Lean Six Sigma" - these frameworks address optimizing our existing product through better insight:

Extreme Programming

Returning to the agile hemisphere, Extreme Programming and some of its derivates, such as Programmer Anarchy, add more emphasis on understanding the customer and providing the right solution for the customer's needs.


DevOps is concerned with two things: Getting the product to the customer with minimal overhead and delay - and understanding how the product is being used.
The first, and well-known, portion of DevOps is providing an automated delivery Infrastructure - Continuous Delivery, Infrastructure as Code, Containerization, Logging, Authentication and many other things come to mind.

In addition, DevOps, done well, provide a myriad of analytical insights into the product: which features are being used, how new features are being received, where unexpected things occur, how to solve customer issues etc. This requires more than technical insight - it requires harnessing business insight as well!

The big picture

DevOps is an essential piece of the puzzle towards hyperperformant teams. The full power of an agile team requires a smart combination of discovery and delivery methods. It's your choice whether your team sails under the Scrum, Kanban, XP, none or any other banner - just make sure you cover all of the blocks:

Design Thinking shines for the "Understanding customer needs". Scrum is great to cover the "Doing work on customer needs" section. Combine these two with DevOps to optimize your "Working on the available product - both before and after delivery" approach.
For best results, you might want to add a touch of Lean, an ounce of XP and a pinch of Kanban,

Closing the loop

Let's forget frameworks for a minute. What's important is that you got everything covered. Use Design Thinking where it helps you build a better product. Apply XP where it helps you build the product better. Try Scrum elements that improve your delivery process. Utilize DevOps tools and practices to ensure you're doing the right thing when the rubber hits the road. And never forget - Lean/Six Sigma has really powerful tools that help you do the right thing better!

If you look closely, you will discover that this cycle is an implied "Build-Measure-Learn" cycle, which is the core premise of Lean Startup, yet another framework from the agile bucket.

Closing remarks

No single framework, approach or method is sufficient to deal with the complexity of creating and maintaining a successful product. All frameworks have useful and important elements to offer. Combining them for best results is a core practice of agnostic agile practitioners.

Sunday, January 14, 2018

Rules in a structureless organization

A critical aspect for Structureless organizations is how they deal with rules. One might think, "As soon as humans need to deal with each other, we need rules". Yes and no. Let's explore how rules change as an organization becomes Structureless.

We will explore the topic by starting with an unstructured organization, then progress from there.

Unstructured rules

Martial law - Unstructured rules
Unstructured organizations have rudimentary rules, which are often simply made up on the spot, either ad hoc or post hoc. Rules mostly serve as a means to protect existing power structures, i.e. to beat others into submission and to exhibit superiority.
Rules are made exclusively by those who have power, and the rules serve them and their interests.

There is little mention of rules unless one is quoted or created to deal with a specific situation - and even then, the rule is hardly ever communicated to anyone beyond those involved. There is no examination whether these rules are consistent, conflicting or even make sense.

Most rules are arbitrary and wouldn't stand up to scrutiny, yet they never get challenged, as challenging them would equal challenging those who hold the power. The only people who will challenge rules are those higher up in the food chain, and only when it serves their purpose. This is usually not necessary, as further rules can be added at any point in time, as the lack of transparency around rules will already ensure that nobody realizes the conflict.

The following characteristics are symptomatic of "rules" in an unstructured organization:
  1. Double Standards: Rules apply only to some groups. Others are exempt from the same rules for no transparent reason. For example, favorable rules apply only to those with power and unfavorable rules only to others.
  2. Rules that don't solve problems: Rules serve more to shame those who have infringed upon them than to solve a real problem.
  3. Post-hoc rulemaking: When a situation occurs that is unpleasant to someone in power, rules are set up post-fact as a smoke screen to deflect the blame.
Such rules will never be written down, as the mere prospect of doing so might end up in a lawsuit. Those in power will make sure that it stays like this.

    Indirectly structured rules

    Indirectly structured organizations do have rules - and lots of them!
    There seems to be a rule for everything - and most of these rules are highly formalized. They are intended to prevent any potential misunderstanding.

    Most rules serve as a means of avoiding the need to address the root cause of the problems which have surfaced in the past, and every action of people is encompassed by some form of rule. Similarly to unstructured organizations, there is little discussion around whether rules make sense or are even applicable.

    When people are unsure what to do, they will either try to discover which rule needs to be applied, or will look to someone in charge to provide a rule. In fact, people will try to avoid situations where no existing rule can be applied, as this poses an undetermined challenge. People tend to be more concerned with keeping the rules they have than whether these rules make sense.

    Rules in indirectly structured organizations serve a more noble purpose than those in an unstructured organization. There are actually two different purposes:

    • Providing safety to those acting upon the rules that their actions are meeting prescribed standards.
    • Providing a sense of reliability to those creating the rules that people will act predictably.
    The most denominating characteristic of indirect structures is the separation of decision and execution: Those making a decision are not the same people as those acting upon that decision. The indirection is in full effect when people state, "If you want to know why - please ask that person!"

    The following three items are symptomatic for rule-making in indirectly structured organizations:
    1. Decision proposals: Instead of just doing the right thing, people need to prepare formal proporals with slide decks for managers to get approval for doing what they feel should be done.
    2. Central Process Decisions: It's not the people doing the work deciding what the best way to do the work is, but some people who - for some reason - are believed to have some form of superior knowledge about this work. This often comes with a Process Management division defining SOP's.
    3. Finger-Pointing: People would rather apply an inappropriate process than admit they are not aware of what needs to be done. They can point to someone who prescribed the process and will claim inaccountability for the consequences.

    The rules in indirectly structured organizations are often religiously followed by people at lower levels of the organization, while people on the higher levels are hardly aware of their existence. 
    Managers in indirectly structured organizations are often even aware of this problem, yet are unable to trace this back to the system they have created.

    Directly structured rules

    Directly structured organizations oddly have fewer rules than indirectly structured orgs!

    Rules are less constraining and prohibitive than in an indirectly structured organization, as they are aimed more at clarifying structure, helping people organize themselves and getting things done than at stopping undue actions.

    Rules serve everyone and no longer treat everyone equally unfair. Rules acknowledge context and provide guidance. Rather than abolishing the application of common sense as an indirectly structured organization would, they guide common sense decision making at every level. Unlike indirectly structured organization, inapplicable rules are scrutinized and reworked as needed.

    Rules help people discover the most sensible course of action without being prescriptive on the course of action, permitting leeway for sensible choices. As the social and procedural context of the work might be dynamic, people need to be comfortable with discovering the best way to move forward. Rules would only be created when those doing the work are unable to produce a desirable result.

    Rules in directly structured organizations serve an even more noble purpose than those in an indirectly structured organization. Rules are directed at:

    • Providing a basis for mutually beneficial, positive collaboration.
    • Providing consistency on a larger scale.
    • Avoiding preventable fault, thereby providing psychological safety for those doing the work.

    Direct structures align need and provision: Those who have the need are able to either resolve it by themselves or directly access those who can. Rule decisions are made by those who can see and affect the outcome of their choices. The most sensible form of rule making in a directly structured organization is by asking those at the receiving end of a rule which kind of rule makes most sense for them.

    Characteristics of rules in a directly structured organization include:

    • Alignement with business goals: Rules support the work, rather than impede it. Rules that contradict business goals will be revised.
    • Scrutiny: Everyone may discuss rules, and this doesn't happen out of frustration, but to drive improvement. Rules that no longer serve their intended purpose might be abolished or changed.
    • Consistency: Conflicting rules which would result in a stalemate get revised.

    Rules in a directly structured organization clearly correlate purpose and outcome. It's not essential for people in areas unaffected by the rule to know about the rule - and when effects occur that are not intended by the rule, it will be subject to scrutiny.

    Structureless rules

    The weird part about rules in a structureless organization is that they don't seem to exist. This, however, would be a misunderstanding as rules actually do exist - except that they are usually implied rather than defined and people don't even feel the need to formalize them, as this formalization does not add any value.

    In general, the need for rules decreases as mutual understanding and alignment increase - and the high levels of collaboration in a structureless settings foster these things. While the creation of collaborative bonds usually requires a clarification of mutual expectations, rules are often not very helpful, because they are created with a lot of ambiguity and therefore, often misdirected. Much more important than setting a rule is aligning on the intended outcome of collaboration and creating an environment where impediments are quickly addressed and resolved.

    Formal rules in structureless organizations are usually externally imposed, such as laws. It goes without saying that structureless isn't anarchy - so such imposed rules need to be maintained. As they are not an intrinsic part of the organization, people will discuss these rules not in a setting on what to do with them, but on the easiest way to get along with them.

    Because structureless organizations no longer care about the rules themselves, discussions aim at:

    • Finding positive, effective ways of collaborating
    • Aligning mutual perspectives, understanding and outcomes
    • Resolving issues which might otherwise require rules.
    Nonetheless, these are already implicit rules - the rules of getting along and communicating. Probably the most important implicit rule of a structureless organization is the "No Asshole Rule". It will never be mentioned, as the mere need to mention it already means that a problem occurred that should not exist.

    Characteristics of the rules in a structureless organization include:
    • Implicit: Probably the most important characteristic is their implicitness: Rules do not need to be formalized, because they are implied by interactions.
    • Minimal: Since rules cause or hide problems, they are a "last resort", when all else failed.
    • Ephemeral: Structureless organizations rely on being able to constantly change and adapt, so rules might simply disappear when their context disappeared.
    • Local: Rules would only exist in a local setting, and there is no attempt trying to consider whether they could be generalized to a broader context, as if there was a need, it would pop up anyways.
    Structureless organizations aren't about rules. They are about aligning, collaborating and moving forward. When considering, structureless organizations have a lot of implicit rules - potentially more than the explicit rules found in an indirectly structured setting. The big difference is that rather than being in a manual nobody has ever read, these rules live and are part of people's lives.


    An unkeen observer might confuse structureless rules with unstructured rules - although the difference is immense! Whereas unstructured rules are makeshift constructs to preserve power, a structureless organization understands the advantages and disadvantages of formalization and has moved from the level of top-down exercise of power to mutual understanding.

    Structures are created to minimize communication over rules, assuming that rules can be formalized in an unambiguous way. Structureless organizations acknowledge that communication is essential to move beyond a limited and superficial mutual understanding. Once the necessary communication over collaboration has happened, the need for formalization disappears. Hence, the rules become implicit rather than explicit.

    Sunday, December 24, 2017

    Communication in a structureless organization

    How do structureless organizations communicate - and why is that an advantage?

    In a recent post, I addressed the topic of "structureless organization" from a maturity perspective. Let us explore structureless communications by comparison.

    Unstructured communication

    An unstructured organization doesn't have direct, congruent or consistent links between people. Somehow, everyone fits into the picture - but this "somehow" may neither be meaningful nor helpful to the organization or its customers.

    Broken links, ineffectivity everywhere: Unstructured!
    In the above illustration, there are inconsistencies between formal and lived structure (center), people who are somehow isolated from the structure (on the left) and broken links (manager to CEO). This means that necessary communication either doesn't happen - or only by chance.
    An unstructured organization amasses communication debt at the missing links!

    Now, let's look at what the communication looks like:
    Rabbit Trails, Loose Ends - good hunting!

    There are two communication chains. Assume you are a customer and need something that only the person (!) can help with.
    Should you happen to address person (1) in the picture, they will refer to their manager, who will refer to another employee, who will refer to a coworker, who will ... blah yada yada -- until another manager gets involved, who will address an employee who happens to know the person who can help you. There's a good chance you've already stopped in frustration before you ever meet person (!).

    Should you be so unlucky to address person (A) in the picture, they will refer you to person (B) - and you are none the wiser.

    Of course, "unstructured" is merely a strawman as this is definitely an undesirable state for any organization to be in. Just be aware that even within your structure, there may be unstructured areas that simply "fall off the chart".

    Indirect Communication

    An indirectly structured organization has directed and usually consistent links between people. The only downside is the nearly inevitable incongruence between need and structure. 

    A typical org chart

    This is what a typical "org chart" looks like. Communication is centralized around managers, who then delegate the task back into their own unit, until an executable level is attained. The idea behind this is to maximize the efficiency of the workforce by minimizing the amount of disruption due to inadequate requests.
    And this is how the communication is intended to flow:

    Don't worry. You will get an answer. Eventually.

    When you have a request that needs to be served by Team Blue (Tech), but your contact point is Team Red (Customer Service), the request will be judged by their manager, who will then take it yet one level higher, who will then inform the division manager, who will then inform Team Blue. The only good news in this one is that even though you have a long wait, something is eventually going to happen. It just takes patience.

    Let us examine what happens when people are missing: Flu season is coming!

    In this example, the blue manager has delegated represenation (<) to (?), so when Manager Blue is missing, (?) will act in their stead. This works out quite well when only one person is missing at the same time. However, when (1) needs a specific kind of help from team Blue, and the person named by Manager Blue as contact (?) is also missing, the communication chain is broken. When (4) realizes that neither (<) nor (?) is available, they might approach one person that occasionally also represents (<) - (5). However, that person is equally unable to help and so, the matter might remain sticking around until (<) returns. Usually, by then, the issue will be rotting as mail #51194 in Blue Manager's mailbox - abandoned, forgotten.
    In the worst case scenario, person (1) would require something from their communication partner (2), but has been named representative of (2) and the superior of (2), namely (3) is also missing - so (1) might be stuck in a catch-22 - making indirect structures similarly susceptible to fault as unstructured organizations.

    Side note: I happened to work for an organization once where the CEO claimed in an official newsletter that "if everyone would follow the defined communication paths and stop addressing other departments directly, we would be much more efficient". Does he really believe that?

    In reality, most communication in org-charted, indirectly structured organizations happens outside the formal chart - because it's so terribly ineffective. They implicitly create - direct communication, just to be able to get things done.

    Direct Communication

    The issues so commonly often associated with indirected structured can abysmally hamper an organization. Silo structures with broken escalation chains lead to tremendous inefficiencies. Direct structures resolve this matter by installing direct points of contact between departments who reduce both the amount of managerial involvement as well as the amount of steps required to get something done.

    We know who can help you.
    The typical term commonly associated with direct organizations is SPOC - "Single Point Of Contact". A senior member of each unit who is familiar both with the work that can be done by the unit and the people doing the work within the unit is assigned "SPOC". This person can be approached by anyone regarding requests within their unit, so SPOC Red would receive all requests done by Team Red.
    SPOC's are transparent, so a customer would either approach SPOC Red directly, minimzing the amount of overhead - or, if they don't know who SPOC Red is, they would approach anyone who would immediately know that SPOC Red needs to be addressed.

    Optimized for efficient communication
    SPOC Red might either handle requests to Team Red immediately or involve any team member from Team Red who can help. If SPOC Red receives a request that would massively interfere with how Team Red operates, SPOC Red will involve Manager Red for a decision.

    The reason why many organizations do not move towards direct communication is fear - managers fearing the loss of control.
    In a directly structured organization, managers aren't even aware of what their staff do most of the time. They operate autonomously to do what they can do to help the organization. This requires trust

    So - are there any drawbacks? None that would warrant going back to indirect structures. Compared to indirect structures, there are no business relevant downsides to establishing direct structures.
    The only drawback is queuing - the SPOC is an implicit queue. In some cases, the queue becomes explicit by having a ticket system where the SPOC stores and distributes requests. The more SPOC's an organization has, the more queues they own.

    How do we solve the queuing problem?

    Structureless communication

    Queues are horribly ineffective to manage - request load is hardly ever balanced in the working world. While one SPOC idles, another might not know how to handle all those requests. Managers might be tempted to install multiple persons as SPOC - increasing the throughput of the queue without ever addressing the issue why the team receives so many requests.
    Structureless organizations are different:

    In a structureless organization, communication paths are replaced with communication networks. Each person has their own, individual network of persons they collaborate with to get their work done. Managers in a structureless organization work fundamentally different from indirectly structured organizations: instead of controlling the work and communication, each manager supports their own people in order to collaborate better.
    Structural boundaries start to lose importance, as the manager's focus moves from departmental efficiency towards organizational effectiveness.

    And this is how structureless communication happens:

    When someone (1) in team Blue needs something they aren't familiar with, they ask around in their network. Maybe this is another colleague or even the manager - no reason not to. Manager blue might refer them to another person who works closer to that area of expertise, but who might not have the answer either. This person will then check their network until they found someone who can help.

    This is where the Bacon Rule kicks in, which posits that the maximum separation path between any two people on Planet Earth would be six, so usually within an organization, there would usually be four or fewer leaps until someone (!) is found. Once help is avaiable, the person will connect directly with the requester - so the next time, no communication path would be traversed.

    In a structureless organization, neither Manager Blue nor Manager Red are concerned with what (1) or (!) are doing and how much time it costs: If it's the most important thing for (1) to work on, there's a good chance that (!) benefits the organization as a whole by chiming in.

    What happens in a structureless organization when people go missing? Not much. First, people get familiar with the work of people done in their network, so they might actually be able to do part of it by themselves - otherwise, they do have some insight who the contacts of the missing person are and will ask around there.

    I would like to conclude with a small illustration of what happens in a structureless organization when one person leaves: Fill a bucket with water and put your hand in. Look at the water, look at the hand. Take your hand out. Look at the hole it left ...

    In a structureless organization, you are treasured part able to contribute. No bad things happen when you leave. You are free to be where you are or go somewhere. The organization can cope with it. No bad feelings when you're on vacation.


    From an objective perspective of reason, there is no reason to not move towards a structureless organization. This does not mean that there are no arguments against structureless. Most of them fall into a fear category:

    1. Fear of the Unknown ("I don't know what Structureless is")
    2. Fear of Poor Results ("But we won't reach our quota")
    3. Fear of Losing Control ("I don't know what my team will be doing")
    4. Fear of Lack of Authority ("But people need to be told what to do"), or vice versa:
    5. Fear of Uncertainty ("I won't know what to do unless someone tells me")
    All of these fears can be handled, although this takes a lot of time. Once someone has seen the beauty and effectiveness of structureless organizations, most of them go away. 

    To conclude, I will provide you with some examples of structureless organizations:
    1. Your friends. Nobody manages the bunch of you, yet you still get along.
    2. Any well-functioning team. There might be managers, but it's about getting things done, not about following structure.
    3. The agile community. Not only do we have vastly differing opinions and goals, we also argue quite a bit. But we can well get things done.

    Sunday, December 10, 2017

    Moving towards a structureless organization

    In a recent post, I explained the concept of "Structureless". Let's dig a little deeper into how we can explore this concept to build high-performing teams and organizations.

    Structural Maturity

    Without explaining the above model too much further, let's see how we can use this model in team organization.

    Unstructured Organization

    It's very easy to set up an unstructured team - basically, all you need to do is: nothing. Even then, people dislike the chaos that ensues and will usually self-organize to create at least some kind of structure. What I see happen as a first step to move away from the total lack of structure is contact lists - people making lists who can be contacted for what.
    This is often the first thing people would do when confronted with a new working environment.

    Key characteristics:

    ComplexityNot clear
    People try to make ends meet.
    It's unknown how complex the system really is.
    Nothing is really known.
    There might be be problems hidden beneath the surface,
    which aren't even explored.
    When they surface, the way forward is unclear.
    Unstructured organizations are significantly less
    effective than even the added potential of each.
    Ad hoc
    Most problems never get addressed.
    Workarounds are commonplace.
    Ad hoc
    The best way to describe how roles are distributed is:
    "Might makes right".
    People either grab roles they can meet in ways that
    please people in charge or are assigned a role.
    There is constant dissonance between expectation and
    reality, bursting out in occasional conflict.
    The customer is the least problem people would care
    Next steps
    • Discover what structures already exist
    • Discover who is responsible for what
    • Make communication paths visible
    • Close communication path gaps
    • Create a "skill matrix" who contributes what

    Indirect Structured Organization

    Indirect structures solve the problem of not knowing who to address when or for what. The indirect structure tends to rely on bottlenecks, i.e. communication paths that are used more often than they are available. Most organizations never make the leap away from indirect structures, as those are already stable. Moving beyond this indirection means resolving the bottlenecks - and some people use their bottleneck status as safety zone.
    Typical bottlenecks are managers who insist on being part of communication chains and irreplacible specialists.

    Key characteristics:

    Indirections add complexity to even simple requests.
    When indirection chains break, processes or requests
    might be hanging "mid-air" without being resolved.
    Major effort is required to maintain consistency.
    The bottlenecks inherent to the communication chain
    reduce the effectiveness of all those who rely on
    anything provided by a bottleneck.
    Problems get addressed when a bottleneck is aware
    of a problem and has an interest in resolving it.
    Communication paths typically determine a person's
    role aligned with their communication network.
    A person's role is often defined by the bottlenecks
    which limit their progress.
    Bottleneck roles tend to have high satisfaction, both
    from the feeling of being needed and the power
    at their disposal.
    Those limited by bottlenecks tend to get frustrated
    when blocked.
    Indirection is a customer's worst nightmare.
    The complexity of the structure becomes the
    customer's problem one way or another.
    Not getting responses, delayed responses and
    unproportionally high transaction costs are just
    some symptoms.
    Next steps
    • Discover where the bottlenecks are
    • Address the indirection issues
    • Strengthen direct communication paths
    • Create a "delegation matrix" to relieve the
      overburden of bottlenecks

    Direct Structured Organization

    Direct structures emphasize the value of getting things done. They regard results higher than personal affinity and value outcome over process.
    Very few organizations make the leap from indirected towards directed structures, and this relies especially on "managers getting out of the way". Direction requires re-thinking the manager role in fundamental ways. The toughest nut an organization needs to crack when moving towards direct structure is Larman's Law #1, the implicit optimization around preservation of personal power.

    Key characteristics:

    Indirections add complexity to even simple requests.
    Processes do not rely on single points of failure.
    Managers/specialists move from being bottlenecks
    towards creating robust structures that reduce reliance
    on their involvement.
    Centralized structures remove redundancies and
    optimize for "The Greater Good".
    Problems get resolved where they occur, by those
    who have central control over the domain.
    Roles are typically created to meet a specific need.
    Communication paths are then updated to integrate
    the role properly.
    People know what they are doing and where they fit in.
    Customers get the impression that people know what
    they are doing and that their requests move forward.
    They do not like that the company's structure is their
    problem - at least to some extent.
    Next steps
    • Simplify request processing from a customer
    • Instill a "customer centric" mindset in those
      not directly working with customers
    • Identify the communication issues that exist

    Structureless Organization

    The structureless organization is not to be confused with an unstructured organization. Instead of optimizing for reaching some kind of internal goal, a structureless organization sacrifices internal efficiency for meaningful outcomes. Redundancies are the means by which a structureless organization generate robustness without falling victim to stasis. 
    Managers are no longer the joints by which organizational units move, instead they become the glue keeping the construct together.
    Specialists move from adding value by executing on their topic towards enabling others to excel in their field.

    Key characteristics:

    From an individual's perspective, complexity may
    appear to be higher, as each person requires to be in
    contact with more people. From an organizational
    perspective, complexity is reduced, because less
    formal communication is required.
    People are not concerned with structure as much as they
    are with collaborating to achieve results.
    Where communication links are missing, "self-repair"
    will create the most effective new links.
    Removing indirection and structural overhead results
    in maximal effectiveness from an organizational perspective.
    Decentralization removes the local inefficiency and the
    need for ineffective compromizes.
    On the fly.
    Problems get resolved where they occur, by those
    who are involved in their occurrence. There is no longer a
    concern for local optimization, as decentralization removes
    the problem of needing to globally optimize.
    Roles are simply no longer important, as the focus moves
    from "job descriptions" towards contribution potential.
    Even leadership becomes situational to meet specific needs.
    People are able to align their personal sense of worth with
    the company's goals. Motivation and morale become
    Customers feel that the company is out to please them, and
    everyone is pulling in the same direction. 
    Next steps
    • Be aware of the danger of falling back into old habits
    • Strengthen informal links
    • Continuously improve


    It's not inherently bad to be in any given stage, even if that stage is "unstructured" or "indirect structure". The important pieces of the puzzle are understanding:
    1. At which stage you are
    2. Why you are there
    3. What can you do to move forward
    4. Why it's worth moving forward

    While I think that it's possible in theory to move directly from unstructured or indirection to structureless, my personal observation has been that this is extremely difficult. I personally like to move towards direct structure in a matter of days or weeks, and enable structureless from there. 
    The most important piece of the puzzle is understanding that once we stop with an indirect or direct structure, we create a stable condition where change becomes increasingly difficult as time proceeds.