Activity vs Action.

In our modern world we are constantly expected to rush and frantically finish our tasks in the name of efficiency. Yet often we find that activity does not translate into the desired action or outcome. It is this “Rush to Action” which is the actual issue, often leading to poor outcomes and undesirable states of mind.

So why do we do it?

The basic fact is that we generally can not distinguish between activity and action. The realm of busywork is populated with people filled with a sense of accomplishment. The simple fact is we are driven by the evolutionary reflex of Fight or Flight. This predisposes us to rapidly respond by reaction, it is this proclivity to activity which makes us feel a sense of control when we are in activity. The difference between activity and action, is often only observed in the final outcome therefore it is very difficult for us and any onlooker to distinguish the two.

Doing things make us feel empowered and better; we feel in control and have a sense of fulfilment because we are doing something about it. Yet this activity is a hollow victory, if the end goals are not reached. The true reward is when we attain our objectives and goals.

If we take the real world example of Cave Diving, a highly technical and inherently dangerous activity, which happens to be fun and scary. Imagine you are diving in a sinkhole cave system and before you know it, you realise you’ve reached the bottom and have lost your bearings and the rest of your group. Initial instinct would be to begin searching for the others and this naturally becomes more frantic as time passes. Although this is a natural and understandable reaction, it usually is not the best course of action. This initial behaviour which manifests itself as activity, will often cause greater problems. The reason frantic activity in such a situation is not a good idea is that you will stir up any silt and mud off the bottom, this will muddy the water and reduce your visibility to the extent you can loose your orientation to the stage where you don’t even know which way is up.

Activity is not always the best action.

So in the above example reactionary activity is highly problematic but even in this example calmer heads and cool action will prevail. Surrounded by zero visibility, not knowing which way is up many would feel lost yet the fact that the bubbles you expire using SCUBA gear will always rise actually will help you identify which way is up. This simple fact and calm action can and will safe your life.

This predisposition to activity can and often does muddy the water when we are trying to determine the actions necessary to attain our goals. Running around like a headless chicken, is an apt description because we loose our senses in the frantic rush. We don’t see, don’t hear and can not clearly understand which are the best options, opportunities and course of actions.

Culture can be a Vexing Word

This post has been inspired by a conversation about culture with Tobbe and Steve.

I was pondering why I have trouble with the word ‘Culture’ and it’s related to the ways we misinterpret words and misuse them to influence people.
So I tweeted a thread earlier this week which captures some of the problems

Culture can be a vexing word

In this context ‘vexing’ means causing annoyance, frustration or worry (from the google dictionary)

The word ‘Culture’ is annoying when used as a convenient excuse For example ‘the culture is not right here’ or ‘we need to change the culture’

The word ‘Culture’ is frustrating when we try to define it
‘We need to change the culture’
…..’What do you mean by culture?’
‘You know – how we do things around here’
…..’What things?’
‘How we communicate, interact, collaborate…’
……..

…..’What is collaboration?’

And the word ‘Culture’ is worrying because it can lead to rabbit holes, wild goose chases and cans of worms It’s far too easy to focus on activities attempting to change the culture directly (and these are very hard to measure – see previous tweet about definition)

It’s very easy to vent about an issue and a lot trickier to propose ways to address these issues.
The simplest first idea is to stop spending large amounts of time trying to define culture – sometimes it’s like…discussion about culture eats everything else…(with apologies to Drucker – although according to Quote Investigator the quote might not be directly from Drucker).

The next simple idea is to catch ourselves when we think ‘the culture needs to change….’ or similar and apply something like the 5 Whys to it.

  • Why do we think the culture needs to change? – Because people keep doing the same things and won’t try new ideas
  • Which same thing are we concerned about and why? – The funding process
  • Why is the funding process a problem? – Because we have to fill out timesheets
  • Why do we fill out timesheets? – So that we can be paid
  • Are there any other reasons why we need to fill in timesheets? – I don’t know
  • Who might know? – HR, Finance, Managers
  • Why is filling in timesheets a problem? – Because the codes are confusing and it takes around 15 mins a week when I could be doing more valuable work

We can see that the list of whys and who might know is getting very long and there are a lot of interesting and branching threads to explore. The timesheet one can be fairly simple to follow and it often ultimately relates to how an organisation does its accounts as well as allowing us to get paid properly. Accounting standards are fairly universal and are not going to change very quickly – so we are much better off educating ourselves about the need of the organisation to meet taxation, corporate governance, audit etc. requirements and finding more effective ways to achieve these as well as communicating this need with our colleagues.

We might find that a very measurable thing (that an organisation is a going concern in accounting speak) can have a dramatic impact on culture when we focus on flowing our work around that need.

Agile is like using a Chef’s Knife…

Agile has been described as a change in mindset, which is a tricky concept to explain and even trickier to do.

What if agile is additive instead?

Here’s an analogy.

If we only had a butter knife in our kitchen, there would be some tasks that we can do very well, such as spread butter and jam on bread. Imagine if we wanted to chop up tomatoes. The tomatoes would be in very big chunks and it would be very messy with a lot of waste.

Then we discover the chef’s knife and learn how to use it. Now we can chop tomatoes (and other things) with a lot more precision and much less waste.

We do not get rid of our butter knife though (I imagine that trying to spread butter on soft bread with a chef’s knife will result in a very torn and unpalatable result).

Now we can do many more tasks in the kitchen, using the tool that is best suited for the job and the main changes we have made is to purchase the chef’s knife and learn how to use it properly – which is a case of ‘both/and’ not ‘instead of’.

The 12th State of Agile report from VersionOne has just been released, below is some data from the 11th (2017) report about the challenges experienced adopting and scaling agile.

Source: VersionOne 11th annual State of Agile report

www.StateOfAgile.com

Back to our chef’s knife analogy – it would be unwise of us to purchase one and start waving it around – they can be quite hefty and very sharp things. If used inappropriately, they can be very dangerous. We need to start slowly and learn how to use it until our muscle memory kicks in and then we can go a bit faster.

It’s the same with learning new ways of working – we need to know when it’s appropriate to use them and be careful that we don’t cause unintended damage as we build our ‘muscle memory’ and get used to the new practices, principles and techniques.

It’s interesting in the state of agile report data above that 2 factors appear that we can address in fairly obvious ways with training, coaching and deliberate practice.

  • Lack of experience with agile methods (47%)
  • Insufficient training (34%)

The remaining 10 factors have a lot more complexity and uncertainty to them and will be much trickier to influence.

If we stop thinking of agile as a change in mindset and see it instead as learning a new set of tools, perhaps that would help us to focus on the 2 factors above and reduce the impact of the other 10 at the same time.

It’s nice to get new things – and even nicer when we can still find uses for those items we have grown to love (like a favourite butter knife).