Complexity. It’s not complicated …
I’m part of the digital first project, the team that’s looking into new ways of working that will help Scottish Enterprise improve its projects’ performance.
One of the things the team is doing is a 12-week training course on Value, Flow, Quality. That probably doesn’t mean much to most people, but basically it’s a methodology we can use to organise ourselves and our work to deliver value to our customers, quickly and flexibly.
One of the things we looked at in our first session was why IT and software projects regularly fail (by some measures, only one project in three is successful).
This alarming statistic tells us something is very wrong with the way businesses approach these projects. But what?
Riding a bike is a complex business
Well, it seems the ‘rules of thumb’ we use to make decisions emerged from a manufacturing background. The problem is that, while manufacturing is a _complicated_ business, software development takes place in a _complex_ environment.
We use the words complicated and complex almost interchangably, so what do I mean by drawing this distinction? Well, here’s an analogy.
## Making a bike is complicated …
To manufacture a bike, you need hundreds of different parts, each engineered to very fine tolerances, which you then assemble in a particular order.
So it’s tricky, and you have to get it exactly right every time. But if you stick to the design specification exactly, and follow the correct process you will eventually have built a bike.
What’s more, if you repeat the process you will have an absolutely identical bike, every time.
## … but riding a bike is complex
As soon as you get on the bike and start pedalling though, things change. Sure, some things are straightforward; you push down on the pedals, the force turns the back wheel and you’re propelled forward.
If that were all you were doing it’d be simple. But it’s not. As you ride along you are constantly taking in information about your environment. Is that car going to pull out? Does that energetic-looking dog have a thing about cyclists? I need to turn right ahead. Is there anything behind me? Does that puddle up ahead conceal a wheel-wrecking pothole?
As a result of all this information you are constantly adjusting – adjusting your riding position, pulling your brakes, changing direction, anticipating.
And the adjustments you make in turn affect other road users – if you swerve to avoid an opening car door, the driver of the bus behind you will also have to take evasive action.
The Cynefin model
It is from this feedback loop that complexity arises, and which makes complex systems inherently unpredictable. There is no ‘right answer’ you can pin down in advance. Instead, you have to set out on your journey, be vigilant and react quickly to events around you. And accept that things will change.
Software development takes place in a similarly complex, almost chaotic environment. New technologies emerge daily, and these technologies can be hugely disruptive, even to established industries. You only have to think about what has happened to booksellers in the last 10 years to see that if companies don’t adapt quickly enough they very quickly get left behind.
To compound this, our software projects take place in the context of economic development. Few systems are more complex than an economy. And as events of 2008 showed, complexity in economic systems can very quickly turn chaotic.
So we have complexity squared. How can Scottish Enterprise adapt to this and deliver projects that add value for our customers, quickly and responsively, and still achieve value for money?
That’s what we’re here to find out.
* * *
Images from Wikipedia, reused under a Creative Commons licence.
* Bicycle courier
* Cynefin framework
David O'Brien
Website | + postsBio
I'm a service designer in Scottish Enterprise's unsurprisingly-named service design team. I've been a content designer, editor, UX designer and giant haystacks developer on the web for (gulp) over 25 years.
* David O'Brien
__Standard accessibility acceptance criteria
* David O'Brien
__The point of the doing is the doing, not what gets done
* David O'Brien
__No more cookies for you
* David O'Brien
__I cycled to work
* David O'Brien
__The disability myth
* David O'Brien
__Who are we willing to exclude?
* David O'Brien
__What do service designers do?
* David O'Brien
__Good Services Scale: an interactive assessment
* David O'Brien
__Making our account managers appy
* David O'Brien
__Show your stripes
* David O'Brien
__Telling a story
* David O'Brien
__How to create inclusive personas, without creating inclusive personas
* David O'Brien
__Go with the flow
* David O'Brien
__On colours
* David O'Brien
__Joining the dots from intent to outcome
* David O'Brien
__On calculating carbon
* David O'Brien
__Operating in the open
* David O'Brien
__WCAG 2.2
* David O'Brien
__On twitter
* David O'Brien
__Joining the Federation
* David O'Brien
__Providing text alternatives for non-text content
* David O'Brien
__Running an asynchronous retrospective
* David O'Brien
__Service landscape maps: seeing the bigger picture
* David O'Brien
__Measuring our carbon output
* David O'Brien
__On alternatives
* David O'Brien
__The exporting experience: one year on
* David O'Brien
__How to create accessible Word documents
* David O'Brien
__Make the service standard work for you
* David O'Brien
__How to deliver agile projects to a deadline
* David O'Brien
__Measuring performance
* David O'Brien
__What I learned at Service Design in Government 2019
* David O'Brien
__A story is the promise of a conversation
* David O'Brien
__Preparing for Brexit
* David O'Brien
__You can do things, or you can get things done
* David O'Brien
__Talk first. Ask for detail later
* David O'Brien
__Fidelity increases as uncertainty decreases
* David O'Brien
__A form of conversation
* David O'Brien
__We need feedback
* David O'Brien
__What digital transformation really means
* David O'Brien
__Why users do what they do, when, where, how, and what they do it with
* David O'Brien
__Towards agile UX
* David O'Brien
__Designing for mobile first
* David O'Brien
__Embrace uncertainty
* David O'Brien
__It’s your first date. Behave …
* David O'Brien
__Open up
* David O'Brien
__Making it up
* David O'Brien
__Love’s the needle, not the North*
* David O'Brien
__Stop starting. Start finishing
* David O'Brien
__It’s unexpected. But it’s also unexpectable
* David O'Brien
__Go on then. Motivate me
* David O'Brien
__When is a team not a team?
* David O'Brien
__Faking it
* David O'Brien
__Why Big Design fails
* David O'Brien
__Our first live event: the facts and figures
* David O'Brien
__Personas: fact or fiction? Answer: neither, and both
* David O'Brien
__Design content first … who would have thought of that?
* David O'Brien
__Digital first is … what?
* David O'Brien
__Why accessibility matters
* David O'Brien
__The problem with pixels …
## Possibly related
* Accessibility - Sharing knowledge between organisations
* A new life in the unknown
* Volunteering
* How many people does it take to design and build a service?
* How we provided evidence for the Digital First Assessment
* Invisible Disabilities