Joining the dots from intent to outcome

An intent to outcome diagram for the findbusinesssupport.gov.scot
Reading Time: 3 minutes

As a service designer, a large part of my job is making sure everyone on the project sees and understands the same picture.

We all need to have a shared understanding of:

  • why we’re here
  • what we’re trying to do
  • the outcomes (changes in the real world) we want to see

That sounds easy, but in reality it’s not. Everyone has their own perspective: designers, developers, content designers, architects, security people, product owners … everybody comes at the problem with their own priorities and experiences, their own preferences, language, biases and assumptions.

We can have hours of discussions and endless workshops to thrash these conflicting worldviews and languages out. Thousands of unmourned post-its may be lost in the process.

So one day, back in 2019, when I was working on the very early days of findbusinesssupport.gov.scot I decided we needed an authoritative way to describe and demonstrate our purpose.

In my experience at that time, it really helps to have a big reminder of “this is why you’re here” every time you enter the workplace. (It was ‘real’ then, it’s (mostly) virtual now.)

So I came up with this:

Continue reading “Joining the dots from intent to outcome”

Running an asynchronous retrospective

Reading Time: 4 minutes

The good, the bad, and the ugly

I seem to have been running a lot of retrospectives lately. And yes, I just used an Oxford comma. Get over it.

A simple, childlike image of a sailing boat on a choppy sea. The boat is held by an anchor hooked on rocks beneath the waves. There are wind puffs behind it and rocks in front of it. To the right of the images an island with a palm tree, with the sun overhead.
In the sailboat retrospective format, the boat represents the project or work we are doing; the wind is what is pushing us forward, the anchor what is holding us back. The rocks are dangers/risks we face, and the island is the goal or destination. I created this template in Miro.

In case you don’t know what that means, a retrospective (or a ‘retro’ for short) is a meeting-come-workshop where you look back on work you’ve done, as a team, and try to identify ways you could be better in future.

In agile methodologies, you can hold retros pretty regularly. With Scrum, you’d hold one at the end of every sprint – typically every 2 weeks – so you can get feedback quickly and adjust course immediately.

Think guiding a canoe through rapids; if you can’t change course quickly, you are going to hit a rock (a fairly common metaphor for retros uses a sailboat, as above) pretty soon, and pretty fatally.

Continue reading “Running an asynchronous retrospective”

Service landscape maps: seeing the bigger picture

Reading Time: 3 minutes

This is a service landscape map.

A service landscape map -click the link for full-size version.
Service landscape maps depict the different stages users go through when accessing a service as connected blobs, with the activities they do as circles within those blobs. It also captures who the external users are – the end users of the service and those who act in their support – the things users do to achieve their goals, the teams of people who deliver the service and are granted some power or authority within the system, and supporting organisations that also have a role to play in meeting user needs.

Services rarely, if ever, exist in a void. They exist within a context. A landscape.

Service landscape maps capture and illustrate that wider context and allow us to see the complexity at play, and to develop a better understanding of the user’s whole experience.

Continue reading “Service landscape maps: seeing the bigger picture”

How to create accessible Word documents

Reading Time: 7 minutes

First, some definitions

An accessible document is a document that people with a range of physical and cognitive impairments can read and understand.

An accessible document is, typically, also a document that people with no physical or cognitive impairments can read and understand better, and faster.

Also typically, an accessible document is easier for content authors to maintain. Because it uses tools that are baked in to Word and other MS Office applications to support accessibility and improve workflow.

So, here are some tips on creating accessible Word documents.

Continue reading “How to create accessible Word documents”

How capabilities mapping helped us see the bigger picture

Reading Time: 4 minutes

The problem

We have a transformation programme underway across Scottish Enterprise. It was getting harder to see what needed to be done to deliver the bigger picture – rather than just bits of the jigsaw. In addition, many people were focusing solely on ‘the bit you need to build’, rather than seeing the whole service – end to end, online and offline.

Continue reading “How capabilities mapping helped us see the bigger picture”