David O'Brien

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.
Posted on

Fidelity increases as uncertainty decreases

Graph showing how the fidelity of your product increases as uncertainty decreases, but asymmetrically

No, this is not a couples counselling site.

I and others on my team have had a lot of discussion recently about what we are doing, why we're doing it, what we can test and why we are testing it.

In an agile team, this is healthy. As long as the discussion remains respectful, talking is great, because we need to reach a consensus, agree a course of action, and commit to it. As a team.

We may not all be 100% convinced that what we're doing is the right thing to do. But we all agree to do our best to achieve it, even if (sometimes) our motivation is to demonstrate that it was the wrong thing.

But you can only demonstrate that by doing the wrong thing right (if you see what I mean).

I saw this on Twitter this evening.

Then I did this recalulation.

Continue reading “Fidelity increases as uncertainty decreases”

Posted on

We need feedback

Yes, we do.

But what do you mean?

We need to understand why those users don't engage further with our content. We need to get in front of them and ask why they think the way they do. Why aren't they engaging with our content?

A feedback loop
A feedback loop

If those users are 6,000 miles away, that's going to be pretty expensive feedback. Sure, it will be valuable, qualitative feedback. 

But it won't be the most valuable feedback we can get.

Because what people say and what they actually do are two completely different things.

Continue reading “We need feedback”

Posted on

What digital transformation really means

Taking a digital photograph

First, the bad news: it doesn't mean everyone gets an iPad.

Digital transformation isn't about technology, it's about the change the technology enables.

Think about the railways in the 19th century. You didn't have to be Robert Louis Stevenson to understand that being able to get from Edinburgh to London in day, rather than a week, was a game changer. 

You don't have to be able to design the train, or even ride it, to benefit from it.

Let me give you a picture.

Continue reading “What digital transformation really means”

Posted on

Why users do what they do, when, where, how, and what they do it with

Storyboard showing people using mobile devices while commuting, or in social situations

OK, so that's a long title.

It's why we use a bit of jargon in user experience (UX).

We call "why users do what they do, when, where, how, and what they do it with" context of use.

It's a crucial piece, or, rather, set, of information.

If you know who your users are, what they're trying to get done, why the want to do it, and how they will interact with it – including the environment and circumstances they're in – you will have a really clear picture of what your product or service needs to do to make that happen.

It's critical to know, because – well, basically, if you don't know this stuff, failure is an absolute certainty.

Continue reading “Why users do what they do, when, where, how, and what they do it with”

Posted on

Towards agile UX

So I recently studied for, and sat, the exam for, the CPUX-F qualification*.

It stands for Certified Professional for Usability and User Experience (that's the UX bit), if you really want to know.

It was interesting, though not novel; most of it was just formalising knowlege I and my colleagues have already acquired, willy-nilly, over the years.

Here's what the process look like.

The human-centred design process
The human-centred design process

Continue reading “Towards agile UX”

Posted on

Designing for mobile first

We recently released a Beta version of our export health check diagnostic.

It’s a simple thing that asks you 7 questions with yes or no answers. You can run through it in 2 minutes.

We know this, because we tested it through a rapid series of iterations. We made a prototype, put it out for testing and changed it the next day based on what we had learned the night before.

In the space of a week we had something we knew worked well, that people could use comfortably and delivered something of real value.

Export health check
Export health check (desktop version)

Continue reading “Designing for mobile first”

Posted on

Embrace uncertainty

Rhinoceros

OK, here's a quiz

I was going to write some whizzy code for this, but then I thought: be agile. What's the quickest, cheapest thing you could do to test this idea?

So I'm going to trust you.

All I'm asking is that you read the question and answer it without thinking too hard about it … your gut instinct is what I'm after.

Take no more than 10 seconds to reach a conclusion.

Otherwise, I may have to write some whizzy code to stop you from cheating …

Question

You have £100 to invest. You decide to invest it in a bank account that pays 1% interest per day.

After 1 year, how much money will you have? Scribble it down. Right now. Doesn't have to be on a post-it.

(And it would be great if you could tell us your estimate in the comments at the end of the article.)
Continue reading “Embrace uncertainty”

Posted on

It’s your first date. Behave …

We’ve been experimenting with mood maps to record customers’ emotions while they use the prototypes we test with them. The results are revealing …

Mood maps are pretty simple graphs of emotion over time. You just observe someone interacting with the app or content you are developing and plot how positive or negative their emotions are for the duration of the test.

But they allow you to tell a story.

Here’s what a mood map looks like.

Mood map
So, how was it for you?

Continue reading “It’s your first date. Behave …”

Posted on

Open up

Those of you with a 4 (or even a 3) ominously close to the start of your age will recognise the title of of a song by Leftfield with John Lydon on vocals.

For us, it's about being open, honest and transparent about what we're doing.

We don't want to hide the successes – and failures – of the things we try. It's just as important that we learn from our mistakes as our triumphs.

So if we try something and it doesn't work … well, here's the data.

Up to now, we've been open(ish) about our results. They're on a wall, visible to everyone who comes to see us, and updated every day.

But they're invisible to people who don't come to visit. And updates are manual. So we thought it would be a good idea to automate them, and to publish them publicly. And update them more frequently.

Every hour? Every minute? every second?

Very short update frequency seemed overkill for our needs. The truth is, though, that we didn't, and still don't, know.

So we thought we'd try to find out what the best thing is to do. And you, dear reader, are part of our experiment.
Continue reading “Open up”

Posted on

Making it up

I remember childhood games where my friends and I would say:

Make it that you’re a baddie and I’m the goodie.

Then 5 minutes later someone would declare:

Make it that we’re hiding and you cannae see us.

Or:

Make it that we can fly so when you find us we just fly away.

I’ve been on holiday for a few days, and I’ve been thinking about that phrase. “Make it that …”

Children playing
Make it that …

It’s like my 6-year-old self and my playmates really believed we could bend reality to our imaginations. If we decided we should make things this way, they would just be that way.

Of course they would.

Then I grew up and discovered that, unfortunately, the world doesn’t work like that.

But what if – in our work, at least – it did?

Continue reading “Making it up”

Posted on

Love’s the needle, not the North*

In a previous post, I said that big design up-front was a recipe for disaster.

And it is. So what’s the alternative?

The answer is not to plan less, but to plan more.

IMG_0392

Just don’t do it all at once. Plan the next week or two, do what you planned, and learn something.

We plan a lot. But we do it in small chunks. Lego-sized. Frequently. And regularly.

Because we recognise that the future is uncertain. We can’t predict it.

It’s pretty simple really. Don’t pretend that you know what will be happening in six months’ time. Accept that you won’t.

And move your planning cycle into a place where you can have some degree of certainty,

It’s like the weather forecast. We know what will happen in the next few hours with pretty-much 100% certainty.

After that, things get fuzzy. The weather next week looks cold, but that could change tomorrow.

And after that … well, the weather forecast two weeks from now is pretty much wishful thinking, even with the best brains and massive computation that the met office can throw at it.

This is what we’re about; what can we get done in the next week or two?

What can we get out there in front of actual people?

What will they do with it? And, in two weeks’ time, what will we do with that?

* If anyone got this far, the headline is a line from an Andrew Greig poem. My interpretation of it is that the thing pointing the direction we’re travelling in is not so important; where we’re heading for is.

Posted on

Stop starting. Start finishing

Can you run this report and get it to me by Thursday morning?

How do we stop starting and start finishing?
How do we stop starting and start finishing?

Eh … OK. But it’s now 4pm on Tuesday. And I’ve got to do …

… I need it by 10am on Thursday for a management meeting. Can you do that?

Yes … but …

… Is that OK?

Sure, yes. 10 o’clock on Thursday …

I’m sure I’m not the only person who has ever had a conversation like this. In fact, I’m pretty certain most of us have.

After all, the only way to escape these conversations is to be the big boss – the high heidjin, as we say in Scotland – and, necessarily, very few of us are that.

So what’s the solution?

 

Honestly, I don’t have an answer to that. But I do know this: if managers keep trying to stuff ever-fatter elephants down the pipe, it won’t end well.

Continue reading “Stop starting. Start finishing”

Posted on

Go on then. Motivate me

So, here I am.

I turn up for work, regularly on time, frequently early. Occasionally late.

Trains…

I sometimes leave the office early, but, if I do, I will always check emails later, when I get home.

Well, mostly. (We’re being honest here. And we are talking about email. As motivations go, it’s not up there.)

I do a good job, I think. No-one’s ever told me otherwise, Though, frankly, I don’t think anyone could write my job description any more.

I include myself in that, though a hashtag might cover it: #whateverItTakes

So, how could you motivate me to do a better job?

You could give me more money. Money’s always good. Isn’t it?

Continue reading “Go on then. Motivate me”

Posted on

Faking it

This week, I did something I thought I’d never do: I deceived our users. Our visitors.

Our customers.

That’s pretty much a sacking offence, so maybe I should explain.

As part of the digital first team, we’re looking for ways to get user feedback. After all, how will we know if customers think our products and services are valuable unless we ask them?

We can’t always do that face to face. Is there another way?

Continue reading “Faking it”

Posted on

Why Big Design fails

When businesses take on big IT projects (or any kind of big projects, I suppose), they puff their cheeks out and say, metaphorical hands on not-at-all-literal hips:

Gonna cost you guv.

They’re thinking: we’re going to have to plan this. We’ll need a risk register. We’ll have to fix the scope, gather all the deliverables, consult all the stakeholders.

Then we’ll create a PID, and a project plan. And if we get approval, and funding, we’ll start on an 18 month delivery plan that we’ve already been talking about for 6 months.

Then they’ll spend 2 months going round everyone who may have even the smallest stake in the project. They’ll seek their opinions, solicit their preferences.

Everything will be documented, in documents that will never be read by anyone.

Once all the stakeholders have been consulted, they’ll start planning. The risk register will be completed. A project plan will be drawn up. It is submitted for approval, and approval is granted.

Hey, we’ve been working on this thing for 6 months already and have delivered nothing but documentation. But we’ve already spent so much money on it that we can’t stop.

Sound familiar?

The Product Owner explains his priorities

Continue reading “Why Big Design fails”

Posted on

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? Continue reading “Complexity. It’s not complicated …”

Posted on

Our first live event: the facts and figures

On 22 and 23 July, we set up a live stream from the Commonwealth Games Business Conference.

As well as the YouTube video stream, we used every channel at our disposal – twitter, LikedIn, Google+, our websites – to stimulate the debate.

Scottish Enterprise CEO Lena Wilson talking at the Commonwealth Games Business Conference
Scottish Enterprise CEO Lena Wilson talking at the Commonwealth Games Business Conference

It was a huge effort for a small team. Three of us – including Erica Goodey, who led on this project -were at the event. I was backup and tech support, though thankfully I was not needed for that. Everything went smoothly. Others back at the office pitched in too, publishing updates live on our sites.

So, roughly half our entire available resource tied up for two days.

And there have been months of planning, preparation and practice leading up to these two days.

In all, we estimate our total effort involved in these two days is 124 hours: equivalent to one person working on nothing else for nearly a month. And we’re not even half-way done yet. Much of our planning is around what we do with the material we’ve gathered now the event itself is past.

You can see how the two days were received on our storify.

This was a first for my team, and for Scottish Enterprise/SDI too. We have been a publisher for years, but this was the first time we have been a live broadcaster.

So, how did it go?

Continue reading “Our first live event: the facts and figures”