Skip to main content

Are your Corporate Values Weaponized?

How would you know if your organizations values that you and other leaders have worked so hard to propagate have become weaponized exclusion and status quo control devices?

Certainly values are only positive - affirmations of our best selves. Could our values work against us?

Yes.  And you may know it only after it is too late... your culture will turn toxic.  The rising stars you spend energy to recruit will say a few months, maybe a year or two and leave (happy to get out).  Or you will force them out within months, because they are not a "good fit" to your culture.

This failure to "fit" is a sure sign.  Can the executives read the sign, does you HR department work to protect the status quo?  Hiring decisions use the "good fit" measure and then a few months after they made the mistake of hiring the employee they reverse the decision and fire for "bad fit."

As a "journeyman" agilist I've made conscious decision to go into companies that I was reluctant to align with their corporate mission; so that I could practice my craft of building teams of performant software developers.  Assuming that corporate mission / values etc. were orthogonal (enough) to the stated goals of learning Scrum/Agile/etc. and building competency in modern software development. Several times the culture and environment, that is easy to read (when you are atuned), is the tell-tell signal that little we may attempt will ultimately (6 months) fail to make a difference.

Using a model to understand these environments is helpful.  I try to fit the culture to a model.  Try Schneider's Collaboration, Control, Cultivation, Competence model or Competing Values Framework, etc.  When you poke and prode around these value systems, attempting to understand the culture you may need another model to make sense of the behaviors that your questions and actions will invoke - try the Cynefin model by Snowden.  Consider that you are trying to make sense of the system - it is not a simple domain - assume it is Complex.  And take my advice - a safe to fail experiment to discover the culture may be unsafe to perform if you wish to keep your job.  Yet, if you are like me and feel safe to be fired by a culture that you would not wish to be a part of... then it opens up a whole range of safe-to-fail probing actions, which may result in desired emergent behaviors and movement toward agility.

Yet, it is my experience that the system will have many antibodies that will attack.  And when the company values are used as weapons - you know you have a toxic environment.  To give a touch of perspective - the opposite of weaponized values is a culture that invites divergent ideas and includes people with new perspectives.  See the modern movement of cultural diversity and inclusion for a case study in weaponized value systems.  A good book is by Steve L Robbins; What if? Short Stories to Spark Diversity Dialogue.

What is culture - can it be created - designed - controlled?  Ask a few people these questions and I'm quite sure you can receive hundreds of answers.  Personally I like thinking one can design culture... yet I'm also holding out the cognitive dissonance that culture is an emergent aspect.  Can one design a puppet shadow play - yes.
"Culture is like a shadow of the group, it may appear different in various lighting and it’s shape depends upon the structure of the background as much as the foreground (the group)."

See Also:

The  Weaponized Narrative Initiative at ASU
Weaponized narrative is an attack that seeks to undermine an opponent’s civilization, identity, and will. By generating confusion, complexity, and political and social schisms, it confounds response on the part of the defender.

3 Ways Senior Leaders Create a Toxic Culture - HBR
Scattered Priorities, Unhealthy Rivalries, Unproductive Conflict
Toxic Workplaces advice found on Twitter

Going full circle on values by Mike Burrows of Agendashift
"The Agendashift Full Circle exercise is so named because you’ve effectively created your own values-based assessment, akin to ours. Explore far enough into ‘outcome space’ and you’ll begin to identify themes and values. Back to where you started perhaps, but you’ve made them your own!"
Culture Mapping and metaphor by Dave Gray

 "Design Culture like a Garden; not like a Car."

Culture Mapping - a tool set at XPlaner

Dave Gray's keynote: Culture and Change
Post a Comment

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.


Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.

In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.

Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    To Do
    Work In P…

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?

Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

What belongs on the Task Board?

I wonder about these questions a lot - what types of task belong on the task board?  Does every task have to belong to a Story?  Are some tasks just too small?  Are some tasks too obvious?  Obviously some task are too larger, but when should it be decomposed?  How will we know a task is too large?

I answer these questions with a question.  What about a task board motivates us to get work done?  The answer is: T.A.S.K.S. to DONE!

Inherent in the acronym TASKS is the point of all tasks, to get to done.  That is the measure of if the task is the right size.  Does it motivate us to get the work done?  (see notes on Dan Pink's book: Drive - The surprising Truth about what motivates us) If we are forgetting to do some class of task then putting it on the board will help us remember.  If we think some small task is being done by someone else, then putting it on the board will validate that someone else is actually doing it.  If a task is obvious, then putting it on the board will take vi…

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.