Why we all need to experience the overview effect

the-overview-effect.png

What happens to us if we see our planet from space?

The overview effect is a mind shift experienced by some astronauts when seeing the Earth firsthand from space.

They immediately get that we all live on the same small, fragile planet protected from the void by nothing more than thin air.

And the things we do to mess things up here – from conflict to resource exploitation – are simply stupid and what is needed is the united will to do something about it.

But – less than 600 people have travelled space and that probably isn’t enough to create a movement.

As a starting point, perhaps we can look at some pictures.

Benjamin Grant started a project called Daily Overview that curates stunning images of the Earth from space and our impact on it.

These images capture how we have completely taken over the planet and the scale of activity and building we carry out – from deforestation in Bolivia to iron ore mining in Australia.

A related set of images called juxtapose shows images of before and after – how Dutch tulip fields bloom or how a patch of desert turns into a refugee city.

Contrast “England’s green and pleasant land” with the Zaatari Refugee Camp in Jordan that holds refugees fleeing from conflict in Syria.

Grant was inspired by a film from the planetary collective, available on vimeo and now viewed nearly 8 million times that explores the overview effect.

We often think that solutions to problems like climate change have to be technological – we focus on things like reducing carbon through more efficient technology or processes.

To really get people engaged we should help expand their perspective and see things from a different point of view.

And you don’t get much more different from the moon – imagine seeing an Earthrise the way the first astronauts did.

Unless you travel to the edge of the solar system.

From 6 billion kilometres away the Earth is simply a pale blue dot, the size of a pixel on a screen.

Although most of us won’t get a chance to travel into space, perhaps technologies such as virtual reality and augmented reality can help us have the same experience right here on Earth.

Maybe the technologies we have have created to escape reality can also help us protect it.

How to give people feedback on their eco-behaviour

eco-feedback.png

Many of us assume that if we just give people the information they need, they will act in the right way.

This assumes that households and businesses are run by micro-resource managers who make decisions about how to act after looking at the costs and benefits of all their options.

To change behaviour all we need to do then is provide things like smart meters and everything will be better, won’t it?

It turns out that isn’t the case because there are a number of problems we face.

For starters, not everyone understands the language of energy or water as shown on a display or report.

It’s hard to visualise 140 litres of water, for example.

It may be easier to grasp when it is translated into something that people can relate to – for example a one litre bottle for every child in a small primary school or the amount of water that goes into making one unit of product.

Even when people understand it, they may not feel they have any choice about using energy.

No one wants cold tea – and we would rather wear clean clothes. That means using the kettle and washing machine.

We can’t turn off energy if we have to do things – we have no control really.

A related problem is focusing on visible things and forgetting the stuff running all the time in the background.

For example, using the kettle will turn displays red with a power spike – but it only lasts a small time.

Or many organisations focus on replacing lights, because that is a very visible way of showing that they are reducing energy – but miss out on larger savings.

Then there are traffic light systems – which have been shown to improve behaviour by getting people to try and stay in the green.

At the same time, they make it ok to do things as long as the display is green – consuming more power overall over time.

A major stumbling block is simply what we want. We’d like a bigger telly, even though the old one works.

Christmas is about shopping – and we’re not going to deprive the kids of stuff even if it’s mostly plastic.

All these problems and more mean that getting people to change behaviour is a bit of a challenge.

So, how should we look at solutions? We can take some lessons from the designers of better eco-feedback solutions.

First, we need to provide better information.

For information to work, it needs to be easy to understand, attract attention, have a social component and be provided at the right time – the EAST framework.

An example is making sure there are labels that say when and who something must happen – like a sticker on light switches saying the last person out should turn off the lights.

Then there are goals.

Companies that commit to targets like Science Based Targets will give people the responsibility and permission to take action.

Government targets can ripple through economies and cause changes in behaviour in order to comply.

There is some evidence that comparisons work – people like being on top of league tables, for example.

After a certain point, however, it may not be possible to eke out further savings, and so comparisons become less important as people feel they are impossible to achieve.

Incentives and rewards, even small ones, can affect behaviour.

Simply having a star after the names of people can change how the group views and engage with the activities required – either to get their own star or keep one they already have.

For eco-feedback to work, it needs to follow the Goldilocks principle.

Not too much, not too little, but just right.

What is a smart contract?

smart-contracts.png

We hear a lot about smart contracts these days.

But what exactly is one, how do we create it and when can we use it?

The term was invented by Nick Szabo, who applied his interests in computer science, law and cryptography to create a cyberspace equivalent of gold – and came up with the idea of decentralized digital currency.

The point of a currency, however, is that it acts as a store of value and a medium of exchange – but when do we actually need it?

Nick, in his original article, says a contract is really a set of promises.

The things that go into a contract have evolved over time – from a contract of marriage to a contract of employment, from a contract of sale to a contract of lease.

All these structures say that the people involved promise to do certain things as set out in the contract.

While the concept of a contract can encompass a blood oath sworn at midnight under a lightning blasted oak tree, normal contracts have four characteristics:

  1. The participants can observe how each party is performing on the contract.
  2. An arbitrator can verify that the contract is performing as set out or is being breached.
  3. The only people involved are the people that need to be involved – their rights are secure and private.
  4. The contract can be enforced – for which we need acceptance of the contract by the powers that be.

A smart contract takes these concepts and recreates them in the digital world.

The difference is that parties enter into a digital agreement instead of signing a paper contract.

This has been done several times before – every payment with a Visa debit card, Ebay purchase with Paypal and software contract we sign without reading are all digital contracts.

The idea of smart contracts when linked with Blockchain technology adds a few ideas to standard paper contract.

The first is that contracts can be expressed in code using an algorithm.

Common algorithms may be if-then or when-do.

For example, if you pay me X, then I will give you an hour of work.

Or when a shipment of copper is delivered in two months time I will pay you the price then that we agree now.

So this means that we need to identify the real life elements that the contract talks about like money and stuff.

For example, payments might be done using a decentralized digital currency like Bitcoin or Ethereum while each hour of work or shipment of copper is tagged with a digital identifier.

So, a second part of a smart contract is the ability to give things a digital ID.

Then there is the question of where to store the smart contract – and that’s where the idea of a ledger comes in – especially a blockchain based distributed ledger.

This keeps the information related to the contract secure by design.

Smart contracts are the way things are going to go – paper agreements have little place in the future.

Many other part of a contract – the promises we make, the reliance on the state to enforce agreements, and the lawyers that create and interpret them – are all still likely be around.

The key, however, is going to be to get the contract algorithm right.

How to think about waste in knowledge work

7-wastes.png

A principle of lean thinking is to remove waste – anything that stops us from producing our product or service for a paying customer.

This is called muda in Japan and seven ways to create waste are especially important to manufacturing organisations.

They can also be used to think about knowledge work and if we are doing it effectively or not.

Take transport for example. Are we moving work between locations unnecessarily?

This can be as simple as splitting a process up between teams, so that one team focuses on just one part and the other team on another.

This is a good way of creating silos – where people focus on their bit and forget the overall system and waiting customer.

Having a small group of multi-skilled individuals close together that can handle the entire process from starting the project to delivering to the customer reduces this type of transport and waste.

What might inventory look like in knowledge work?

Could it be the collection of reports, analyses, studies, comments, meeting notes and so on that accompany the simplest of projects or decisions?

Is all that really necessary?

A lean organisation can design and test a product with a customer and iterate to a finished version in the time it takes for another to come up with specifications.

Motion simply adds heat to a process. The best knowledge work gets done when people sit down and work on a single task for a stretch of time.

Flapping between projects, having to check in all the time with managers and getting interrupted break the flow of work, raise stress levels and increase the total time needed to do the job.

Then there is the time we spend waiting. Meetings are places where we wait – where interminable discussions happen to decide what to do.

We spend so much time in meetings that there is little time left over to do any of the work or actions that come out of them.

Or, we often do too much – over-processing the work we need to do.

Modern computer systems are so powerful that we can do almost anything on them – which means we spend ages selecting fonts and sizes and colours and logos and header placement instead of creating content or analysis.

User interfaces that try and make things simple don’t help.

A quote from an old newsgroup says that graphical user interfaces (GUIs) make simple things simple and complex things impossible.

Closely related to over-processing is overproduction.

There is little point creating work-in-progress that has to go through a bottleneck.

It makes more sense to work to the capacity of the bottleneck and spend the rest of the time working on a different project or improving the performance of the bottleneck.

And finally, there are defects.

Defects in knowledge work often result from not understanding the end result well enough and rushing to create something too quickly.

Information degrades quickly it is passed along links in the chain of communication.

For example a customer speaks to a sales person who speaks to an operational manager who asks an analyst to do some work who then creates something.

It is almost a certainty that the something that is created is not what the customer had in mind.

The problem is that knowledge work is not as visible as manufacturing – we don’t see piles of inventory piling up.

We may only see a cluttered desk and be aware of late projects.

We’ll also see the effect of waste in rising stress levels among colleagues.

And all that’s just a waste.

What are people really looking for from us?

servitization-model.png

Theodore Levitt, a Harvard economist and professor, said People don’t want to buy a quarter-inch drill, they want a quarter-inch hole.

With larger purchases come greater expectations of performance, reliability and longevity.

An approach companies use to deliver these is servitization.

Servitization is a change in mindset from selling a product to selling a Product-Service System.

Professor Andy Neely from the University of Cambridge is a leading researcher in this area and says that the term has been around since the 1980s.

The classic example here is Rolls Royce.

It no longer sells jet engines. Instead, it sells flying hours.

Rolls Royce now delivers reliability – done through planned and predictive maintenance by analysing data from monitoring systems in the field.

Making a move from scheduled repairs to targeted repairs based on performance data enables fleet operators, from the military to councils, to improve things from combat readiness to bus times.

The way we get media has changed with this approach.

Netflix offers media as a service and Amazon offers ebooks.

Servitization has quietly transformed the software business.

It’s hard to buy a software product any more. It’s all software as a service (SAAS) now.

This is not always a good thing.

Netflix has lots of rubbish on it. The good stuff still needs to be paid for.

We get a million books with an Amazon Unlimited subscription – but the good authors still set their own prices and get committed readers.

Servitization in these cases gives the companies a revenue stream and a customer convenience – but the pressures of controlling costs means that the performance is not superior to just buying a really good collection of books and movies.

And software as a service really all-too-often means self-service software.

So, it’s still a product sell rather than a service when we think about it.

According to Professor Neely, servitization is something of a paradox.

Many firms offer product-service systems, but it makes less money and carries higher risks than we first think.

The key thing is a change in mindset – in how we connect a product, service and performance.

This shift starts with the customer going from wanting to own a product to being happy with a service.

How to think about mining data for value

data-mining-phases.png

Why should we try and use data better?

The short answer is because we can make money or save money using the insights we get from analysing data.

But a more useful answer might be because it helps us see more clearly.

That’s very Zen.

Zen teaches that we normally see the world through a haze – a fog made up of the assumptions, preconceptions and fixed ideas – that is created by our desires.

For example, many people are so involved in the way they do something that they fail to see that the something they do is no longer relevant. Innovation simply passes them by.

Or, if we really want something to happen or believe that an approach is right, we become blind to anything that contradicts that point of view.

The way to see clearly is to look at the world as it is.

This is pragmatic advice, but how do we go about doing it?

The Cross Industry Standard Process for Data Mining (CRISP-DM) is now over 20 years old – but still useful.

There is data everywhere these days, leaking out of sensors, meters, surveys, analysis and social media.

We could analyse everything, but we should probably start with an understanding of the business.

What is special about this particular industry, what is the competition doing, how do customers act and what would the business like to do?

We can then stick our heads in the fog and try to understand the data that’s available – going back to the business to ask questions or get some more.

Is it clean or patchy? Do we have lots of numbers or is it full of words? Is it in an open format or do we need to get it out of databases or proprietary formats?

For example, the way we treat energy metering data is different from twitter comment mining or newsfeed monitoring

A huge amount of work then often goes into data preparation.

The data needs to be bashed and cut and manipulated into a form that we can work with.

All too often, the data preparation takes so long and ends up in another messy form that there is little time left to do any modelling.

But – getting to the right kind of data structures can make the task of modelling much easier.

Models help us create and test theories.

Do we think there is a relationship between variables or a robust way to identify problems?

Then its time for evaluation.

We could do an infinite number of analyses, but we need to focus on the ones that are aligned with what the business needs to know.

Are we providing useful insights that can be used to make the business more effective?

If so, then we can head towards deployment.

There is no point doing analysis once and then forgetting about it.

The law of entropy – things decay over time – means that without management things will simply drift and become worse again.

Ideally, we’d automate the analysis and reports and let people know when things are going wrong so that they can get involved and fix things quickly.

The CRISP-DM is a process we can follow to create a data mining project.

The real value comes from the understanding we get when we see what is actually going on.

How can we solve messy real-world problems?

learning-cycle.png

What do we do when we have a situation – perhaps something has gone wrong?

We probably rely on experience – either fix things ourselves or get an expert in to solve the problem.

Most solvable problems like this tend to be hard problems, in the sense that they have clean edges.

For example, the tap is broken, a flood has disrupted shipments and we need an alternative or the printer is jammed and we have to get this proposal to the couriers in the next fifty minutes.

Many other problems are less well defined – how do we reduce our environmental impact while still growing the business, how can we develop people’s skills, what information systems do we need to invest in or what changes do we need to make now to stay relevant?

As a species, we have been phenomenally successful at solving hard problems.

For example, many of us live safer, longer and healthier lives as a result of the medical and technological breakthroughs of the last couple of centuries.

This success has been accompanied by an unexpected problem.

Many people are concerned about the growth in population as we head towards 8 billion people.

They point out that it’s unsustainable and we’ll run out of food to feed everyone and really it would be much better if everyone in all these developing countries stopped making so many babies.

But is the cause of population growth really more babies?

It’s not, reallyit’s not that we breed like rabbits – it’s just that we’ve stopped dying like flies.

The real solution to population growth might be somewhere else.

It turns out that richer people have fewer children.

So, if we want to manage population, a better way might be to help everyone get richer – so instead of aid should we focus on trade?

We normally think that charities or the UN handle big problems like that but maybe it’s business that will solve it in the end.

The thing is that we don’t know. And with many real-world problems we don’t know what solution is going to work – or for that matter what the real problem is.

That’s where a learning cycle comes in.

Hard problem solvers like to say give me your requirements, I’ll build a system and you’ll be happy.

That works sometimes – but all too often it doesn’t.

That’s because most real-world problems are context specific – they depend on the ideas and assumptions of the people involved as well as the situation and environment.

So, instead of solving a problem we may need to work our way to a solution.

In a learning cycle, we have a theory about what might work and that leads to ideas we can put into practice.

We can learn from the results and that leads to modifying our theory and ideas.

It’s not rocket science – but it’s easy to fall into the trap of thinking a new system or platform will solve our problems.

Real-world problems, however, are usually solved after going round the learning cycle loop several times.

Reference: Information, Systems and Information Systems – Peter Checkland and Sue Holwell

Where should we begin – again?

kicking-a-whale.png

Creating something new is usually interesting and fun.

There are no restrictions – we’re focused on the problem at hand – and we can choose from a variety of tools to carry out the work.

Over time we develop processes and workflows that streamline things and make us more effective, especially as we add people to the project.

Things ramp up – we improve quickly – until we start to plateau.

And then we start to move more slowly – as the steps and processes and interactions start to hinder, obstruct and finally block progress.

At this point things aren’t fun any more.

At this point the friction involved in doing anything – the effort that it takes appears overwhelming.

It’s like being asked to kick a whale down the beach.

This happens in all kinds of systems – whether it’s programming, process engineering, or business strategy.

What we already have stops us from moving ahead and getting better.

So… what can we do about it?

Perhaps it starts with a mindset.

Steve Jobs, for example, was famously minimalist.

His house had hardly any furniture in it – perhaps the barest essentials – a mattress, a chest of drawers and a few folding chairs.

His philosophy led to the creation of devices like the iPad, so intuitive in design that a child can instantly use it and without the buttons and controls that others slapped on.

The problem many of us have is we have added too many buttons and features to our lives and working environments – we have too many meetings, follow too many processes and try too hard to please everyone.

What would happen if we spent that time working on interesting and useful things instead?

Perhaps we should begin by looking at everything we do and cutting back on everything that simply doesn’t help us innovate or keep customers happy.

Perfection is achieved not when there is no more to add.

It’s reached when there is no more to take away.

Why we should first do as little as possible

prototype-then-polish.png

There are two traps we often fall into when developing something new:

  1. We try too hard to plan ahead and come up with everything we will possibly need before starting any work.
  2. We spend a lot of time making one part better and faster when it doesn’t help to make the overall performance better.

In software development the classic problem is one of requirements and specifications.

We usually don’t know what we need to do the first time we approach a problem.

It’s the process of engaging with and solving the problem usually helps clarify thinking – and when we have finished with our first solution we now know what we really need to do to solve the problem.

The idea of right first time simply doesn’t work when we don’t know what the right way is yet.

A better approach is to prototype our way to the right solution.

We ought to start small and simple – designing something we and others can understand.

Whether it’s a business process or a software program, once we can show others a working prototype we will be able to see reactions, get feedback and other useful information which can help us refine our ideas.

It’s also important we don’t get too fancy or try to locally optimise things.

Something very clever right now may be hard to understand in three year’s time by someone else, who might decide to throw out all our work and start again instead.

Local optimisation is the idea that we work very hard on speeding up one part of the process but miss the real bottlenecks in the system.

The overall time any system takes to work will be controlled by its slowest component. Making any other part work faster will not reduce the overall time.

For example, it doesn’t matter how fast we get ready in the mornings if the real bottleneck is how long it takes the bus to get to our stop.

We could be 20 minutes early – but it’s the bus time that will decide whether we are late or on time to work.

Our natural tendency, very often, is to try and do more – plan more, think more and have more.

In reality that leads to bloat – creating large unwieldy systems no one loves.

We would be better off following a few simple rules:

  1. Prototype then polish. Get it working first, then try and make it better.
  2. Doing nothing can be very constructive. Words that aren’t there can’t be read wrong. Code that isn’t written can’t fail.

If we must do something – then we should concentrate our time on the things that deliver exponential results, not incremental improvements.

Why we focus on our concerns instead of on users’ needs

conways-principle.png

Why is it that many systems – software applications, company policies, operational processes – are hard to use?

Take websites for example. How many company websites are structured in an easy to use, logical manner?

If we ask any company’s marketing team, they will probably say that their website is structured, laid out and easy to follow.

For them, that is.

This is an example of a principle called Conways’s law, which says that Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.

In other words, the way in which we structure ourselves influences the systems we create.

For example, if we have two factories, one making bread and the other making jam, we are likely to advertise ourselves as having two product lines, the bread line and the jam line.

We’re unlikely to combine them and pitch ourselves to customers as the jam sandwich line – even though they might actually be looking for a sandwich rather than a collection of components.

This is a natural way for an organisation to behave – after all the way they look at themselves seems natural and normal – so why not show themselves to the world in that way?

Except to a user with little experience, it’s hard to work out what companies do, so they will pick the one that makes it easiest for them to understand.

The problem gets worse as we try and create bigger and bigger systems.

For example, a large software application that tries to do everything will find itself bogged down as it grows, constrained by previous decisions and choices about architecture and design.

One solution to this problem is to limit the size of teams – use multi-skilled individuals in small teams that have end-to-end responsibility for a product.

This is the principle behind work cells in lean manufacturing.

These teams tend to produce work that has clean edges and plays nicely with other teams.

Small teams are also fast – they can get together, come up with a plan, develop a product, test it and get feedback, and iterate and improve in the time it takes for a large organisation to do the paperwork needed to get permission to start.

Although, the size of teams is not a solution by itself – it simply produces systems that may be smaller, simpler and work more independently, and so be easier to scale.

The point is that our default approach when trying to design anything is to focus on what we think a user needs.

But, that thinking focuses on us – not on the user – who might actually approach the situation from a completely different point of view.

Perhaps that’s why some of the most useful tools have been developed by people who made them for their own use – they knew exactly what they wanted from the start.