Discipline makes Daring possible.

Process: complicated or complex?

Process: complicated or complex?

When we think of ‘process’ we tend to think of production lines.   Marvellous arrangements of machines, belts and equipment, where activities like baking a biscuit, or assembling a car, are broken down into the simplest possible steps, so that each step can be reliably repeated with the minimum of variation.   At speed, and at volume.

Production lines are fascinating to watch on ‘Inside the Factory’, but are probably less rewarding to work at.  Each step is in itself, meaningless, constant repetition makes it tedious.

A production line, whether it’s built in hardware or software, mechanises a complicated process.   And once you’ve applied that technology spectacularly well to biscuits, or cars, or mobile phones, it’s tempting to try and apply it everywhere.

But most processes are not complicated, but complex.   They involve multiple systems, which interact with each other in unpredictable ways to produce unforeseeable outcomes.

This happens even inside an automated factory.  Often the few people you see are not there to perform any of the steps in the process.   Their role is to respond to the emergent consequences of several interacting systems, which if left to the mechanicals, would bring the factory grinding to a halt.

All living things are complex systems.   Which means that any process involving them is necessarily complex.

It is possible to de-complexify, of course, but only at the expense of de-animating the living.   This is why we find factory farming, factory warehousing, factory customer support or even factory schooling disturbing.   The only way to incorporate a living system into a production line is to remove its potential for emergent properties – in other words, to kill it.

No wonder people in service industries are wary of ‘process’.  They are right to be.

There is a solution though.  Which is to recognise the difference between the processes in your business that are complicated and those that are complex and treat them accordingly.

The complicated is amenable to mechanisation and automation.   That means it makes sense to automate the complicated wherever you can.   Free up your human capacity to deal with the complex, such as interaction with other humans.

The complex can’t and shouldn’t be mechanised or automated.    But it is possible to inject some consistency, repeatability and therefore scalability into it, by adopting the analogy of a creative collaboration rather than a production line.

Music, construction, drama, dance, film-making are just some of the complex collaborative, creative endeavours that use a framework, expressed in a shared language, to be more productive, while still allowing scope for the emergent.

The shared language of this kind of process can be idiosyncratic, prompts and reminders rather than instruction, the score more or less sketchy, the film improvised around a premise rather than a script.   It can leave room not just for interpretation, but for exploration and experimentation.

That’s the kind of ‘process’ I’m interested in generating.  Process that helps us be more human, not less.

 

 

 

 

 

Process vs People

Process vs People

Why do I need process if I have good people?

Because making good people reinvent the wheel over and over again is a shocking waste of talent.

Talent that could be used to invent better wheels, or more interesting uses for them.

Self checkouts are great for social distancing

Self checkouts are great for social distancing

I now by preference use the self-checkout at my local Co-op, out of consideration to the person behind the counter.

But it also feels much better to use the self-checkout when I know the next person in the queue is two metres away –  I feel somehow less pressured, less rushed.

Will this change of feeling last beyond the crisis?   Who knows?  On my part I doubt it.

But I may not have the choice.

There may not even be a supermarket.

We really are living in interesting times.

How to quickly capture a business process/procedure/work instruction

How to quickly capture a business process/procedure/work instruction

With teams suddenly dispersed, all that tacit knowledge of ‘what it is we’re trying to do, and how to do it’, is much harder to access.  You can’t simply shout across the office “How do I do X again?”

It will be very tempting to start automating everything.   But you need to think about what you’re automating first, else you can get trapped in the software manufacturer’s model of how your business should work.

So here ‘s a quick guide to capturing ‘What we do round here’ that will work over Zoom, Skype etc.

Key Principles:

  • Assume competence.
  • The quicker you test it, the quicker you can improve it.
  • If it feels like you’re trying to fit too much in, you probably are.
  • It’s a prompt, not a novel.
  • Practice makes perfect.
  • It’s about the process not the people.

How to go about it:

  • Start with the most critical process.
  • Get someone else to help you.
  • Sketch the whole thing as a series of bubbles – 7  plus or minus one should cover it.
  • Start with the 80% case.
  • Start at the very beginning.
  • Carry on right to the end.
  • Think ‘Get Outcome’.

Follow the rapid improvement cycle:

  • You tell a colleague how it works, they write it down
  • They do it, following what you told them.
  • You observe, and where it goes wrong, between you, you modify the instructions to get the outcomes you want.
  • You clarify how it really works (not how you think it works).
  • They suggest ways to make it easy for them to do.
  • They write up the improved version.
  • Save the latest version where everyone can get at it.

Repeat until you have a work instruction/procedure/process that can be run reliably by anyone who needs to.

Automate the bits humans shouldn’t be doing.   Then let the humans get on with the rest.

The irony of automation

The irony of automation

“[t]he more we depend on technology and push it to its limits, the more we need highly-skilled, well-trained, well-practised people to make systems resilient, acting as the last line of defence against the failures that will inevitably occur”  

Most businesses, even giant auto-assembly plants where robots outnumber humans, are more like orchestras than music boxes.

And it’s the highly trained, skilled and experienced people that keep them running smoothly, as this fascinating read shows.

Good Design makes a product understandable

Good Design makes a product understandable

It clarifies the product’s structure.  Better still, it can make the product clearly express its function by making use of the user’s intuition.  At best, it is self-explanatory.   Dieter Rams, Design Principle number 4.

How many times have you pulled at a door that was meant to be pushed?  Or pushed a door that was meant to be pulled?

There are 4 simple design solutions that would prevent that tiny but all too frequent source of wasted energy and frustration:

  1. Put a flat plate on the ‘push’ side and a handle on the ‘pull’ side.
  2. Allow the door to swing both ways, and have a flat plate on both sides (because both are now ‘push’).
  3. Allow the door to swing both ways, and have a handle on both sides (because both are now ‘pull’).
  4. Have the door open automatically as someone approaches it.

1, 2 and 3 make the door understandable, 4 makes it self-explanatory.

 

We live and work among millions of designed products every day, from doors to roundabouts and office blocks to business processes, organisational structures and governments, many of which provide all too frequent sources of wasted energy and frustration.

How would you re-design them?

Brave New Worlds

Brave New Worlds

The term ‘robot’ was coined in in 1920 by Josef Čapek for his brother Karel.   The word meant “forced labour”.

For all the impressive advances in robotics since then, some of which we saw on the BBC series ‘Revolutions‘ last night, the idea of “forced labour” – including, for Jim Al-Kalili, child-rearing – remains almost unquestioned.

It reminded me that we humans often dive into technology, when we should be re-thinking how we relate to each other.

Sawubona

Sawubona

You can’t be seen until you learn to see.

Sawubona.

Questions

Questions

People are asking big questions about accountancy.

Both from a technology perspective, as in this paper from Deloitte, and from a more existential perspective, exemplified by Professor Richard Murphy and the Corporate Accountability Network.

Big changes create great opportunities to re-think our models of the world as consumers and as producers.

Where do you think accountancy should go?   What should accountants do?  For whom?  What do we want from accountants?   Most importantly, what could we want?  What should we want?

Big questions, now is a good time to ask them.

Learned carelessness

Learned carelessness

Here’s a scary thought.   When their satnav says there is a road, but all they can see is water, drivers will believe the satnav, rather than their own eyes, and end up having to be rescued.

Luckily, most of the time the results of such satnav errors are not drastic – they simply start the conversation after a late arrival – “You won’t believe where the satnav took us!”

But the phenomenon behind these stories – automation bias or “learned carelessness” – is a serious problem.   Confronted with a ‘black box’, whose workings we don’t understand, and which seems on the whole to be reliable, we humans switch off, stop monitoring, and stop thinking.  “Computer says no.”

There are ways to prevent this.

You can de-mystify the ‘black box’, so people understand that it is part of a system designed and built by humans to achieve certain ends; you can frame the information provided by the system as support or advice rather than instruction, and you can engage the human brain by making the human do some of the work – especially where there are other humans involved.

Automation is great, but I want the best of both worlds.

Thanks to James Bridle for sparking this one.