Lou Downe Lou Downe

Principle #6: Requires prior knowledge to use

At the Bad Services Corporation we have 15 principles of Bad Service Design.

Principle #6: Requires prior knowledge to use

If you want to implement this principle, make sure the person who is going to use your service has to learn about how it works, what to do, in a really long and antiquated way

Read More
Lou Downe Lou Downe

Understanding the ‘chain of users’

How do we work out who our users are and what they need?

When we think about who the users of our service are, it is tempting to only think about the ‘end’ user or customer. The patient in the hospital, the recipient of a passport, the buyer of a car.

Read More
Lou Downe Lou Downe

When services fail, we see what they are made of

Whenever a major service goes down, I always think it's a tipping point

It's the moment the general public really starts to understand the infrastructure behind how a service gets delivered to them.

When services fail through complete outage, we uncover the materials of how they are made.

Read More
Lou Downe Lou Downe

Principle #5: Works in a way that is extremely unfamiliar

At the Bad Services Corporation we have 15 principles of Bad Service Design.

Principle #5: Works in a way that is extremely unfamiliar

If you want to implement this principle, make sure the design of the service is totally unrecognisable to anything users have encountered before

Read More
Lou Downe Lou Downe

Short-term thinking does not fix long-term problems

Whether we call them ‘wicked’ or ‘sticky’ problems, they’re ones that take years to make an impact on and involve multiple organisations collaborating to overcome. As such, because they’re not urgent, we’re often extremely unmotivated to look at them.

Read More
Lou Downe Lou Downe

Principle #3: A bad service does not explain it’s purpose

At the Bad Services Corporation we have 15 principles of Bad Service Design.

Principle #3: Does not explain its purpose

If you want to implement this principle, make sure you’re extremely vague about what your service does, how it works and who it’s for

Read More
Lou Downe Lou Downe

Design your infrastructure or your infrastructure will design you

The groundwork and infrastructure we set for our services can define their future for years to come. Despite this, when trying to fix services, we’re often kept at arm’s length from infrastructure used to run those services.

‘Legacy’ technology is a permanent fixture of fixing services. We are always encountering a roman road or a long-lost database. So, what’s the solution?

Read More
Lou Downe Lou Downe

Why risk aversion is increasing your risk of delivering a bad service

‘Risk management’ isn't a topic that comes up a lot in conversations about how we design better services. 

It's usually something that we are vaguely aware of but is either someone else's job to deal with, or something that we feel we don't want to, need to - or sometimes - can't get involved in.

Read More
Lou Downe Lou Downe

Principle #1: A bad service is hard to find 

At the Bad Services Corporation we have 15 principles of Bad Service Design.

Principle #1: A bad service is hard to find 

If you want to implement this principle, name your service using your own organizational language. 

Read More
Lou Downe Lou Downe

Bad services create bad relationships with users

Ever noticed that it's the services that are the worst that find it the hardest to change? This isn’t a coincidence. It’s not just that the problems with the service are difficult to overcome, bad services actively create bad relationships with users that makes it much harder for our organisation to buy into change. 

Read More
Lou Downe Lou Downe

The materials we use define how our services work

Services are defined by the materials we use to build them: those materials govern how our services work. Take, for example, the various services we’ve used to wake up on time over the last three hundred years

Read More
Lou Downe Lou Downe

Every purpose has infinite service possibilities

We always say at the School, ‘your user defines what your service is’ for a very good reason. A service is something that helps someone to do something. It's that ‘someone’ who defines what that ‘something’ is. 

Read More
Lou Downe Lou Downe

15 billions hours are wasted each year dealing with broken services, but do we care enough to fix it?

A 2022 paper by the UCD Geary Institute for Public Policy in Dublin (Martin, Delaney and Doyle, 2022) found that we spend an estimated 15 billion hours in the UK each year ‘administering our personal lives’. That’s roughly an hour per day paying bills, requesting refunds, locating our pensions, making a complaint, losing our customer ID and a plethora of activities involved in ‘life admin’.

Read More
Lou Downe Lou Downe

You can't design a service if you don't know why you’re delivering it

Without a clear sense of why our services exist, it's easy for our services to 'go through the motions' while never achieving what we set out to do

Purpose is a vital ingredient of service design, but It's also the one ingredient we perpetually forget. Take a sneak peek at chapter 1 of Bad Services, Purpose

Read More