Think back to the last time you joined a new organisation. What was your onboarding like? “Hi, here's your laptop. Here's where the toilets are. Here is the printer. Here is the cupboard with the pens. Here are a whole bunch of people whose names you won't remember for weeks. Here's a technical introduction to the work. Here are your logins to the tools you will need. Off you go.” There might be a welcome lunch to help you get to know the people you will be working with, or some sort of ritual embarrassment at the next all hands meeting so they can "get to know you" a bit better (what's one thing about you that no one knows...). There will probably be some mandatory, cover-our-legal-butts "training" in health and safety and various HR policies that will leave you feeling dumber than when you started.

I suspect most people around the world have similar onboarding experiences in just about every organisation. It's the way things are done. And it's wrong. Not so much for what it includes, but for what it leaves out. The traditional onboarding experience misses some crucial things that help new people get settled into a new role in a new organisation. While it might give you the basic mechanics of your job, it doesn't help you integrate into the new organisation. You are left to discover all the hidden little things all by yourself. The fact that we can't raise that topic in meetings because of last time. The fact that while the process says this, what we actually do is something else because of history. Or the fact that, given a choice between this and that, we always chose this because that's what is important to the organisation. In short, what traditional onboarding doesn't do is introduce you to the culture of the organisation you have just joined.

No one comes in to work and deliberately tries to make your day bad. Actually, let me amend that slightly - very, very few people come in to work and deliberately try to make your day bad. There is a very small percentage of people who are vindictive, hateful, small minded, petty people (or just plain old psychopaths) who will deliberately come in to work and delight in spreading misery and pain wherever they go. Whether it's to make everyone else feel as miserable as them, or whether it's because they get joy from other's misery, whatever the reason, these people are few and far between. We are not concerned with them.

What we are concerned with are the other 99.99% of the population who aren't raving psychopaths. Who are genuinely nice people, who care about others and would never dream of inflicting pain and suffering; but who proceed to come in to work and make your day rotten anyway. Why would they do that? What turns normal, caring, decent people into mobile misery factories? What makes them hinder, block and frustrate us at every turn?

Last time we looked at some of the problems organisations face around decision making using traditional top down or consensus based techniques. We also introduced the idea of collaborative non consensus as a decision making technique - where everyone can discuss the decision but not everyone has to agree to the decision for it to be ratified. These can range from fairly simple systems where people can say “yes”, “no” or "can live it it" which allows them to raise an objection but not veto the whole decision, right up to fairly involved systems based around the idea of principles and objections - objections based not on just not liking an idea but on violating some fundamental principle that the organisation lives by.

While principled systems work well for organisations that are deeply in touch with their principles, other organisations may need a more structured approach. One such approach is the Advice Process which was developed at an organisation called AES many years ago and was documented in Frederic Laloux's wonderful book Reinventing Organisations. The Advice process is a simple, structured decision making process that involves 4 steps -

• Deciding who decides

• The Proposal

• Seeking Advice

• The Decision

As an agile coach I am always pushing for cultural change. That's what agile is really - it's not a delivery mechanism, it's a fundamental change in the culture of an organisation. What do we mean by organisational culture? There are many definitions but the one that I like is that culture is a shared understanding of values. It's the understanding everyone has of what the organisation thinks is important. Culture drives behaviour - people will seek to maximise what is considered important in the culture and will behave in ways that do that.

The problem of course is that, as anyone will tell you, cultural change is hard. CEOs are tasked with changing culture and spend years failing to do it. People say that the only way to change culture is to change all the people. Or that cultural change only happens when a generation of employees retire. I don't agree. Cultural change is really easy. You just need to let people know what the organisation values. "Hang on", I hear you say, "Just wait a minute. Organisations have been putting out statements for years about what they want in their new culture. People can often quote chapter and verse from the CEO's latest values statement. Millions are spent on flashy communications. And nothing changes."