Brains trust: notes from my session at UK Healthcamp

A couple of Saturdays ago, still buzzing from a week of NHS website and service manual launches, and the NHS Expo, I took part in my first UK Health Camp.

I learned loads, put faces to names I’d long followed from afar, and posed a question of my own to a windowless basement room full of thoughtful healthcampers: “What do people need to be able to trust a digital health service?”

Trust session at UK Healthcamp

It’s a question I’ve been thinking about a lot, because the fifth of our new NHS design principles is “Design for trust”.

I ran the session as a loose variant of the 1-2-4-all liberating structure. Asking people to think about the question first as individuals, then in growing groups, the format was a great way of eliciting contributions from everyone in the room, then distilling down to some common themes.

At the end of the session, I left the room with a stack of sticky notes on which I had scribbled the key themes as groups reported back. Below is a summary with my own grouping and interpretation of the themes after the event.

The weighing of trust starts before we use a service, as we evaluate it to see if it’s going to meet our needs.

A few groups in the session talked about relevance: will it help me achieve what I need to do? To be relevant, a digital service will likely have to be part of an end-to-end journey, quite possibly including both digital and non-digital elements. Even in this digital world, having an offline presence is one of the things that can give a service credibility.

Once we believe a service might be useful, the next question, not far behind, is “has it been tested – for safety, practicality, and effectiveness?”

We trust things that come recommended by people we trust. Reputation matters, especially when expressed through peer recommendation. We make decisions about services in a web of relationships; a service will be more trusted if it is “culturally embedded”. In the context of British healthcare, there’s nothing more culturally embedded than the NHS.

To earn trust fully, there are things a service has to demonstrate in use.

Is it confidential? People set high standards for data protection, security and privacy. A service shouldn’t collect data it doesn’t need, and must be totally anonymous when you need it to be.

Is it personal? Provided confidentiality is assured, one of the ways a service can gain credibility is by showing information that only it should know. While anonymity is sometimes necessary, so too can be personalisation.

Is it transparent? Transparency of intent and clarity of operation are essential for any digital health service. Why is it asking me this? How did it get to that answer? Is it clear what I’m consenting to?

It is professional? The boring qualities of stability, reliability and consistency should not be underrated. If they go missing, trust in a service will be rapidly undermined.

Finally, there’s a quality of continuous improvement. Without this any trust gained is likely to be short-lived. Does the service take feedback? Is it accountable for its actions? Can you see in its present state the traces of past user feedback? “You said… we did…”

Those were the combined ideas of a self-selecting group one Saturday in Manchester. But tell me what you’d add? What would you need to be able to trust a digital health service?


AI, black boxes, and designerly machines

On my holiday, I started reading into some topics I ought to know more about: artificial intelligence, genomics, healthcare, and the fast approaching intersection of the above. Here follow some half-baked reckons for your critical appraisal. Please tell me what’s worth digging into more. Also where I’m wrong and what I might be missing.

1. Opening the black box

large ribosomal subunit (50S) of Haloarcula marismortui, facing the 30S subunit. The ribosomal proteins are shown in blue, the rRNA in ochre, the active site (A 2486) in red. Data were taken from PDB: 3CC2​, redered with PyMOL.
By Yikrazuul CC BY-SA 3.0, from Wikimedia Commons

Reading Siddhartha Mukherjee’s ‘The Gene: An Intimate History’, I discovered the amazing trajectory of human understanding of DNA, RNA, enzymes, proteins, the genome, and the mechanisms by which they interact. There’s no doubt that this stuff will transform – is already transforming – our relationships with medicine. Crucially this generation of scientists are looking inside a black box, where their predecessors could observe its effects but not its inner workings.

At the same time, fuelled by petabytes of readily available data to digest, computer science risks going the other way in the framing of artificial intelligences: moving from explicable, simple systems to ones where it’s allowed to say, “this stuff is so complex that we don’t know how it works. You have to take it on trust.”

When we apply artificial intelligence (AI) to healthcare, transparency is essential; black boxes must be considered harmful.

It’s not just me saying this. Here are the words of the Institute of Electrical and Electronics Engineers (IEEE):

“Software engineers should employ black-box software services or components only with extraordinary caution and ethical care, as they tend to produce results that cannot be fully inspected, validated or justified by ordinary means, and thus increase the risk of undetected or unforeseen errors, biases and harms.” — Ethics of Autonomous & Intelligent Systems [PDF]

Transparency must be the order of the day. It comes in (at least) two flavours: the first is clear intent; the second, understandable operation. Both are under threat, and designers have a vital role to play in saving them.

2. The opacity of intent

It’s a commonplace to say that technology is not neutral. I won’t labour that point here because Sara Wachter-BoettcherEllen Broad and others do a good job of highlighting how bias becomes embedded, “AI-washed” into seemingly impartial algorithms. As the title of Ellen’s wonderful book has it, AI is ‘Made By Humans’.

That doesn’t seem to stop stock definitions from attempting to wall off AI beyond the purview human control:

“In computer science, AI research is defined as the study of ‘intelligent agents’: any device that perceives its environment and takes actions that maximise its chance of successfully achieving its goals.” — Wikipedia

But what goals exactly? And how did the AI get them? The Wikipedia definition is silent about how goals are set, because, in the words of Professor Margaret Boden“the computer couldn’t care less.”

“…computers don’t have goals of their own. The fact that a computer is following any goals at all can always be explained with reference to the goals of some human agent. (That’s why responsibility for the actions of AI systems lies with their users, manufacturers and/or retailers – not with the systems themselves.)” — Robot says: Whatever

When any technology moves from pure to applied science, intent must be centre stage. If we fixate too much on the computer science of AI, and not enough on the context of its application, intent will always be unintentionally obscured.

Many discussions about the “ethics” of AI or genomics are really, I think, discussions about the opacity of intent. If we don’t know who’s setting the goals for the machine, or how those goals are derived, how can we know if the intent is good or bad?

Moreover, true human intent may be difficult to encode. In a domain as complex as health and care, intent is rarely straightforward. It can be changing, conflicting and challenging to untangle:

  • a boy was triaged on first contact as in less urgent need, but has suddenly taken a turn for the worse
  • an elderly woman wants to get home from hospital, but her doctors need first to be sure she’ll be safe there
  • the parents want to help their children lose weight, but know that pester power always leads them back to the burger chain.

In these situations, even Moore’s Law is no match for empathy, and actual human care.

3. Designers to the rescue

Design, in Jared Spool’s wonderfully economical definition, is “the rendering of intent.” Intent without rendering gives us a strategy but cannot make it real. Rendering without intent may be fun – may even be fine art – but is, by definition, ineffective.

It’s time for designers to double down on intent, and – let’s be honest – this is not an area where design has always covered itself in glory.

We know what design without intent looks like, right? It’s an endless scroll of screenshots presented without context – the Dribbblisation of design.  If you think that was bad, just wait for the Dribbblisation of AI. Or the Dribbblisation of genomics. (“Check out my cool CRISPR hacks gallery, LOL!”)

Thoughtful designers on the other hand can bust their way out of any black box. Even if they’re only called in to work on a small part of a process, they make it their business to understand the situation holistically, from the user’s point of view, and that of the organisation.

Design comes in many specialisms, but experienced designers are confident moving up and down the stack – through graphic design, interaction design and service design problem spaces. Should we point an AI agent at optimising the colour of the “book now” buttons? Or address the capacity bottlenecks in our systems that make appointments hard to find?

One of my team recently talked me through a massive service map they had on their wall. We discussed the complexity in the back-end processes, the push and pull of factors that affected the system. Then, pointing at a particular step of the process: “That’s the point where we could use machine learning, to help clinicians be confident they’re making a good recommendation.” Only by framing the whole service, could they narrow in on a goal that had value to users and could be usefully delegated to AI.

4. How do you know? Show your thinking.

School exam paper. Question:

Crucially, designers are well placed to show the workings of their own (and others’) processes, in a way that proponents of black box AI never will.

This is my second flavour of transparency, clarity of operation.

How might we:

  • communicate probabilities and uncertainties to help someone decide what to do about their disposition to a form of cancer?
  •  show someone exactly how their personal data can be used in research to develop a new treatment?
  • involve people waiting for treatment in the co-design of a fair process for prioritisation?

In a world of risks and probabilities, not black and white answers, we should look for design patterns and affordances that support people’s understanding and help them take real, fully informed, control of the technologies on offer.

This is not an optional extra. It’s a vital part of the bond of trust on which our public service depends.

5. Designerly machines

Applying fifty iterations of DeepDream, the network having been trained to perceive dogs CC0 MartinThoma
Applying fifty iterations of DeepDream, the network having been trained to perceive dogs – CC0 MartinThoma

The cultural ascendancy of AI poses both a threat and an opportunity to human-centred design. It moves computers into territory where designers should already be strong: exploration and iteration.

I’m critically optimistic because many features of AI processes look uncannily like a repackaging of classic design technique. These are designerly machines.

Dabbers ready, eyes down…

  • Finding patterns in a mass of messy data? Check!
  • Learning from experiments over many iterations? Check!
  • Sifting competing options according to emerging heuristics? House!

Some diagrams explaining AI processes even resemble mangled re-imaginings of the divergent/convergent pattern in the Design Council’s famous double diamond.

Diagram showing how design moves from problem to solution in four stages, shown as one diamond after another. There are two pairs of divergence and convergence: Discover and Define, Develop and Deliver
© Design Council 2014 –

A diagram outlining a forward pass though three 3D generative systems, data is divergent and then convergent
“A diagram outlining a forward pass though our three 3D generative systems.” – Improved Adversarial Systems for 3D Object Generation and Reconstruction [PDF]
The threat is that black box AI methods are seen as a substitute for intentional design processes. I’ve heard it suggested that AI could be used to help people navigate a complex website. But if the site’s underlying information architecture is broken, then an intelligent agent will surely just learn the experience of being lost. (Repeat after me: “No AI until we’ve fixed the IA!”)

The opportunity is to pair the machines with designers in the service of better, faster, clearer, more human-centred exploration and iteration.

Increased chatter about AI will bring new more design-like metaphors of rendering that designers should embrace. We should talk more about our processes for discovering and framing problems, generating possible solutions and whittling them down with prototypes and iteration. As a profession, we have a great story to tell.

A resurgent interest in biology, evolution and inheritance might also open up space for conversations about how design solutions evolve in context. Genetic organism, intelligent software agent, or complex public service – we’re all entangled in sociotechnical systems now.

A community with no mandate, united by our principles – OneTeamGov goes Global


How was OneTeamGov Global?

Pure luxury!

The chance to spend a day in the company of 500+ people who share the same simple, highly motivating principles.

A movement so nicely positioned; both inside and outside; #OfTheGovernment, not owned by the Government.

A show of strength in numbers. We filled the QE2 Centre! Now nobody need ever feel alone, even if they’re the first OneTeamGov participant from their particular agency or department.

Seeing a Liberating Structure in action to fill a 14 parallel track, 70 session unconference grid with minimal faff – amazing! James’ write up of the method is much too modest.

The hard but unobtrusive work of the brilliant OneTeamGov volunteers. Every detail of the participant experience considered, so that everyone else could be fully present and enjoy the day.

Seeing familiar faces again. A who’s who of reform in digital government, including a fair few who passed through the learning and development courses I helped to produce and deliver at GDS and DWP.

Meeting new colleagues and kindred spirits from around the world. In particular those who I’ve followed on Twitter from afar. Also, Canada wins at stickers.

How can we stop disempowering people?

The session I pitched had a deliberately ambiguous title – I wanted to know, when participants saw the word “people,” whether they thought first of the people we serve, or the people who deliver service? It turned out to be both, and a consensus that we can only empower citizens if staff are also empowered. It’s also my contention that it’s not the government’s job to empower anyone – everyone should start with power, our job is not to disempower them.

At the end of the session everyone came up with a thing they could do to stop disempowering people. Sticky notes were as follows:

  • Give people data to help them improve their work. Stop using it to performance manage.
  • Make decisions based in data and evidence
  • Set boundaries to empower people in a hierarchy
  • Consider the impact of small actions in the context of power
  • Ask your team to make decisions and state intent rather than ask permission
  • Use the right language. Team leader -> coach?
  • Key question: What do you think?
  • Inform. Inspire, Empower.
  • Emphasise how the different systems disempower citizens.
  • Empower citizens with familiar systems across borders
  • Share stories of success when people use their initiative
  • Use your power to amplify voice of those less powerful
  • Ask questions that people know the answer to
  • We need to cut out the time we ask people to spend interacting with government. What things can you do in your org to reduce the stress / time people have to spend
  • Managers need clear job descriptions out in the open
  • Redefine management roles – to not make decisions
  • Redefine the role of manager – coaches/enablers
  • Amplify voices of others + seek diversity of views

Just some micro-actions for my to-do list!

Thanks to everyone who made it happen.

See also, post from OneTeamGov 2017.

5 July 1948: A chance and a challenge

Earlier this year I set out to understand more about the history of the National Health Service. As well as reading some books recommended by colleagues, I’ve picked up a few original 1948 documents from online auctions. Some archaic language aside, they’re as fresh and relevant today as they were 70 years ago.

Exhibit 1: a variant of the wonderfully clear and concise leaflet sent to every household to explain the new service. The version I have was for service men and women, a reminder of the NHS’s roots in, and proximity to, the horrors and the heroic national collaboration of the Second World War.

‘The New NATIONAL HEALTH SERVICE’ leaflet, 1948

As a value proposition, the introduction to this leaflet is hard to beat:

It will provide you with all medical, dental, and nursing care. Everyone — rich or poor man, woman or child — can use it or any part of it. There are no charges, except for a few special items. There are no insurance qualifications. But it is not a “charity”. You are all paying for it, mainly as taxpayers, and it will relieve your money worries in time of illness.

See the radical ideas packed into those 6 short sentences?
  • Comprehensive coverage – medical, dental and nursing
  • For everyone – rich and poor alike
  • Coverage of women and children equally with men (pre-World War II, many men were in work-based insurance schemes, but their wives and children had no such coverage)
  • Emphatically not a “charity”, but rather a collective endeavour by us all
  • It will relieve your money worries – because the stress of illness can only be compounded by financial hardship.

Every recipient of the leaflet also had a thing to do: “Choose Your Doctor Now”. Despite the scale of this national undertaking, the NHS took flight on the wings of millions of individual choices – people registering themselves and their loved ones with a family doctor. (Whether those GPs would take part at all was a close-run thing demanding give and take from Nye Bevan on one side and the GPs’ leaders on the other.)

Exhibit 2: fast forward a few months to this booklet, published by the Ministry of Health (loving that logo) soon after the NHS’s creation.

00 cover.jpg

A thicker, more reflective read than the first leaflet, this one was produced not long after the foundation, when most people had chosen a doctor, but the new system was just finding its feet. The first of many attempts to show who does what…


Compare with this 2017 version from the King’s Fund…

The final, and most forward-looking, chapter of the second booklet is my favourite.

17 copy.jpeg

THIS BOOKLET has tried to explain the reasons for the new deal in medical care, and the organisation created for it by the Act. It has described what the medical services look like in the beginning, soon after the Act is in force. What will they look like in ten years’ time? The Act is only the means of getting the new deal started. In what direction will the new partnership of the professions and the ‘consumers’ work to carry out their purpose of meeting the medical needs of the people adequately, everywhere?

See how the new partnership comes with scare quotes around the word ‘consumers’? Perhaps the authors hoped we’d find a better noun some time in the next decades. We’re still working on that.

The “six main aims” bear repeating – all having been reprised many times in the last 70 years…

(1) Up-to-date material resources. A large programme is needed as soon as it becomes practicable, for rebuilding and re-equipping hospitals and clinics and for constructing health centres.

(2) Adequate human resources. More health workers of most kinds will have to be trained as soon as possible.

(3) Better distribution of resources. The aim must be to bring more of the services to the places where the patient can conveniently use them.

(4) Greater team work in serving the patient. This is necessary among family doctors, within the hospital service, and between all the services, to avoid the departmentalising of medicine which prevents doctors from seeing the patient as a ‘whole person’ rather than as a ‘case’.

(5) Encouragement of variety and experiment. Medical needs must be adequately met everywhere, but it would be wrong for them to be  met everywhere in the same way. Medicine thrives on experiment and comparison of different ways of doing things; uniformity of method or belief is its enemy.

(6) Encouragement of a preventive and ‘positive’ outlook on health. All agree that the nation will not be using its doctors to the best advantage so long as they are confined so much to healing and have so little time for preventing illness.

In places the language of this booklet is breathtakingly modern. I had to do a Google Books search to confirm that the phrase “whole person” was indeed contemporaneous. Also note…

  • The emphasis on adequacy as an ambitious but attainable goal
  • The need to bring services closer to where people are
  • Team work across departments and parts of the service
  • My favourite: variety and experiment! “uniformity of method or belief is its enemy.”
  • The first of many pleas to prioritise wellbeing and prevention of illness

There’s a sober assessment of the nascent service’s chances. Transformation takes time, costs money and is inherently uncertain…

In the hospital and specialist services the pursuit of these aims will take time. There are still too many awkward and out-of-date buildings; even the existing accommodation cannot be fully used for want of nurses and domestic workers. There are too few of many kinds of specialists, and the few there are are not always well distributed in different parts of the country. The work of the specialist has to be carried beyond the hospital doors more than in the past.

Nevertheless, the Service must be run with proper regard for economy, and capital expenditure has to be kept down to a minimum. Only the most urgent schemes for the extension or repair of hospitals can be permitted. Nor is the building of comprehensive health centres possible on any scale while so great a part of our building resources has to be locked up in urgently needed houses, factories and schools. More study is also needed of the kinds of centres most worth trying out before any large-scale experiments are launched. The building and testing of health centres in action, in different forms and circumstances, in large towns and small, in suburbs and country areas, is a task for the next few years. During that time a great many, perhaps most, family doctors will continue to practise outside health centres, though various looser forms of ‘grouped’ practice and other means of improving the efficiency of the family doctor without comprehensive health centres may prove valuable especially in country districts.

For the time being the main thing is to get the Service into good running order and to keep on improving its efficiency. All big social changes start with a certain amount of uncertainty, until people get used to the new way of doing things; and this Service cannot be comprehensive in the fullest sense until the country is farther along the road to prosperity and a rising standard of life.

Implicit trust in the public as active participants, on whose wise decisions success depended…

The public has still to learn how to use the new facilities properly and economically; and those who are actually running the Service have to get used to new conditions and changing needs. But if the various professions really join forces with the laymen in the organisation described in this booklet, they can carry out a progressive new deal in medical care which will redound to the benefit of all.

A look back, as well as forwards…

The National Health Service represents the completion of the work which was started just over a hundred years ago with the first Public Health Act. Then the emphasis was on environmental conditions — pure water and proper sewerage.

Finally a chance and challenge that stands to this day…

Now the National Health Service brings together the personal services. It offers a chance — and a challenge — to build the most efficient health service in the world, and one which as the years go by will add steadily to the nation’s fitness, happiness and working capacity.

Both documents were subject to Crown Copyright for 50 years, so are now in the public domain. I have scanned and shared them on Wikimedia Commons:

Bonus feature: Halas & Batchelor’s lovely 1948 animation for the Central Office of Information…

Your very good health!

“Look after the water” – reflections 1 year into my work at NHS Digital

Other people’s jobs are endlessly fascinating. At a birthday celebration a couple of years ago I got talking to Johnny, a family friend who works as an aquarium curator. He told me a surprising thing about his work: how little of his time he spends actually looking after the fish. Johnny’s job is to look after the water. “Look after the water,” he said, “and the fish will take care of themselves.”

So it is with design leadership. Our designers have different specialisms – service, interaction and graphic design. They’re embedded across a wide range of endeavours, both public and professional facing. They’re the ones who see users in research, and stakeholders in show and tells. My role is not to tell them how to design; it’s to create the safe and supported conditions in which they can do their best work, individually and collectively. When those conditions come together, it’s a wonderful thing.

This week it’s one year since I joined NHS Digital to lead the design team. I’ve been thinking about what has changed, and what we have yet to achieve. As ever, views all my own.

Growing a team

Our third whole design team event took place a couple of weeks ago in Leeds. We ran two rounds of rapid fire show and tells: 14 designers showing their work in the space of 90 minutes. I was massively impressed that every designer who presented was so good at telling their story, under time pressure, to a room of 35 people.

We’re lucky to have two excellent lead designers. Tero heads our growing service design practice, while Dean has taken on interaction and graphic design for the NHS website. Design-minded product managers Emma, Ian, and Sophie join us in our fortnightly design leadership meetings. Stephen, who left a couple of months ago, was always insightful, knew his way around the organisation, and took on the unglamorous task of writing job descriptions. I miss our Friday morning coffees.

Hiring for designers in both London and Leeds has been a long journey but rewarding in the end. Over the past few months, it has been great to see the new seniors settling in. I believe we now have talent at every level, and a good foundation for design leadership here in the future. If my bike went under a bus on Chapeltown Road tomorrow, weekly design huddles would still happen in Leeds and London. I count that as a win. Having designers who talk to and trust each other is the foundation of a coherent experience for our users. The designers and I are rewarded on the same pay scales as nurses, doctors, and other NHS professionals. That’s a sobering reminder of the value each new recruit to the team is expected to add.

A year of recruitment in numbers:

  • Just over 50% of the design team are now newer than me to NHS Digital
  • Of the permanent staff, 11 are still here from the team when I arrived, 8 are new recruits, and 3 have left
  • Among contractors, it’s 1 still here, 7 new, and 3 left
  • On top of that are a dozen or so supplier staff with whom we work closely as members of our extended team
  • Permanent team, contractors and supplier staff alike, 100% of them want to do their best for users and the health service.

Designers work best as part of multi-disciplinary teams. After a year here, I’ve had the privilege to see a few of those teams go through the delivery cycle from discovery, through alphas and on to release private and public beta versions. It hasn’t always been straightforward. Some teams have got stuck. Some things have stopped when we realised they would not achieve the outcomes we hoped for. But it does feel that teams are getting slicker at this – learning about user needs, and learning how to work together as true multidisciplinary teams. I’m fortunate to be part of a senior leadership team with brilliant product, delivery, technology and content leaders too.

As a design team, we have access to two larger communities of practice. NHS Digital’s Digital Service Delivery profession includes design along with user research, product management, delivery management and content design. We’re also part of the amazing cross-government user-centred design community, giving us access to Government Digital Service (GDS) training and community events. I especially appreciate my meetings with Lou Downe and the other government heads of design.

Here are some things I’ve learned…

Power is a big theme in health and care.

My focus has been with teams designing and delivering for patients, carers, and families – users who don’t work for the NHS or social care. There’s good evidence that people in control of their own health and care have better health outcomes. But I can see from our research how people’s power is diminished – by illness or disability, by social circumstances, and (though we don’t mean to disempower) by us, in the way we design and deliver health and care services.

Digital information and service have the potential to make people more powerful again. This can only happen when people can get them, trust them, understand them, decide with them, and act on them. For people to take power in the NHS, we need to work across the whole system, a partnership of patients, families, professionals, and service providers.

Sometimes we need to diverge before we can converge.

A healthy tension between divergent and convergent working should be part and parcel of any design approach.

Soon after I arrived a year ago, I worried that, in some areas, we were trying to converge prematurely on solutions that had not been tested against a wide enough range of user needs and contexts of use. To reach the required quality, we had to go through a phase of divergence in which teams went off to solve their own problems, while sharing their work and looking out for common patterns. (Patterns, by the way, are never designed; they can only emerge when teams are empowered to work independently, but transparently.)

Now, we’re back to a phase of convergence around design for the NHS website, led by teams explicitly tasked with redesign and standards creation. I have greater confidence that we’re building on firmer foundations this time, because we’ve tried more things, and understood more user needs.

I’m a design system sceptic (but we’ll probably end up with a design system anyway).

Everyone seems to be talking about design systems right now. I caution that explicit efforts to create a system can easily tend towards design for its own sake, disconnected from validated user needs and contexts of use. I hope we can keep ours rooted in reality by rotating designers through the overall redesign and standards teams, in and out of squads working on specific health condition categories and services. Nothing should get into the design system without being researched with users in multiple need states and contexts.

Rather than all swarming on the same problems, we need to conserve our energy and focus. Like birds flying in formation, each team can take a turn to lead on a design challenge, before falling back to let others fly ahead for the next stage.

Critical optimism is the order of the day.

When I wrote my 6-month update, the always-perceptive Stefan Czerniawski noted:

There is a sweet spot in any job, or more generally in understanding any organisation, when you still retain a sense of surprise that anything could quite work that way, but have acquired an understanding of why it does, and of the local application of the general rule that all organisations are perfectly designed to get the results they get.

Since then I’ve tried to bottle that feeling. Healthcare certainly proves Dr Deming right: that the same system can at once be brilliant at some things and terrible at others. There can be world class care, medical and technological innovation side by side with the shocking failure waste that comes from poorly designed service. Being a permanent member of staff, I feel a responsibility to work with the grain of the system, while retaining a sense of urgency to make things better.

One of my objectives is to grow the whole organisation’s commitment to human-centred design. This definitely feels like a multi-year commitment, but I’m confident that we have director-and-above-level support for improving the quality, consistency and accessibility of digital services for NHS patients and professionals. Our head of profession Amanda has been the definition of an empowering manager. Our portfolio director Alan has an exceptionally user-centred vision for someone in a such high-profile delivery role.

Update on some things I committed to do at the 6-month point:

  • Develop my own capability – I am investigating leadership courses that might be right for me. Ideally, I’ll do something that brings me into contact with a more diverse range of health and care leaders, not just the ones focused on digital.
  • Reflect and plan – I started by block booking Friday afternoons as a meeting-free zone in my diary. Clearing emails and weekly reporting always swallowed them up. Now I’ve blocked out the whole day. I don’t always keep to it, but it’s a good reminder of the value of meeting-free time.
  • Listen better – There’s a bit almost at the end of David Marquet’s ‘Turn the Ship Around‘ video, in which he says you will fail repeatedly at giving control to your team, but get up and go again. That’s where I feel I am with my coaching practice right now. After some conversations, I come away kicking myself. When it goes right though, it’s so much more rewarding to hear a colleague solve their own problem than to hear myself offering my solution. Ultimately this is the only way that a design capability is going to scale.
  • Influence more – Lots more to do here. There are so many opportunities for improvement that our small team will never be able to address them all. By sharing standards and setting clear expectations of good practice, we can multiply our impact and give power to the many other people across the health and care system who want to make a difference with design.
  • Say no to more things – One of the adjustments in moving from a micro-business to a biggish organisation was appreciating that lots of things get done even if I don’t do them. Every week or so, I look through my to-do list for the things I really ought to delegate, and the things I’m just never going to do. Adding a “Not Going To Do” column in Trello has done wonders for my sense of productivity.
  • Say yes to more things – I’ve been lucky enough to be invited to some brilliant events and conversations. A recent highlight was working with Victoria Betton and Lenny Naar to deliver a hands-on user-centred design session at HIMSS e-Health week. In October, I’ll be speaking at Interact London, and the conference theme is “Intelligence in Design”. Fingers crossed I’ll have something intelligent to say.

Weeknote: 14 to 18 May 2018

I started writing weeknotes soon after I joined NHS Digital as head of design in June 2017. I find it a good discipline for me to reflect on my week, and to make sure I’m making progress against my own and my team’s objectives. Because groups of colleagues congregate in different virtual places, I settled on posting them simultaneously to our #design channel on Slack and an internal “blog” on Sharepoint. As an experiment, I’m posting a lightly redacted version here too. Views: my own. Publication status: experimental.

Started the week with the Empower the Person portfolio Monday morning call.
Later in design team office hours there was a discussion about examples of well functioning multi-disciplinary teams. We have these working well in some parts of our organisation, and in others… less so. Lots of learning we can do from each other.
In the afternoon, I spent some time preparing for the session at e-Health Week (see Wednesday).

A catch up with one of the designers who has been working on the connecting to chlamydia testing service beta and is now moving across to join the NHS website redesign team. While it’s good to have stability on teams, it’s also important that the redesign work is done with input from designers who have worked across a wide range of content and services.
Lunch with a colleague from NHS England. We chatted about how human-centred design matches up with the personalised care programmes that he looks after.
Back at Bridgewater Place, a short intro meeting with one of our product development directors. I’m trying to work out how best design can support each directorate in NHS Digital’s new organisation structure, and he gave me some useful context.
Fortnightly design leadership meeting. We confirmed the agenda for the team event (see Thursday), talked about on-boarding some new starters, and generally tidied up the actions in the “doing” column of our design leadership Trello board.

A packed day at HIMSS UK e-Health Week in London.
On arriving, I dialled into a quick phone call I had scheduled with Chris who leads the 111 Online programme. (Only after the call did we realise we were both dialling in from different places at the same venue.)
I watched a main theatre presentation by Juliet Bauer, NHS England’s Chief Digital Officer, and the Senior Responsible Owner (SRO) for Empower the Person portfolio. While I know what’s going on across the portfolio, it’s always good to hear Juliet tell the story of the work we’re doing. I tweeted a couple of quite of special interest to me and my team.

After that, I was onto another phone call, with colleagues pulling together our response to the GDS consultation on accessibility of public websites and apps. Sarah, one of our digital graduates did a great job of keeping us on track as we worked through the questions in the consultation.
The e-Health Week session I ran with Victoria Betton of m-Habitat Lenny Naar from the Helix Centre was intended to be a hands-on taster of some key human-centred design principles. We asked people to work in pairs, one of them as the “user” of a page on the NHS website with a particular scenario in mind (we picked paracetamol as an example). The other half of each pair was the researcher, watching what their user did, and noting down any points about the experience. Later in the session, we asked them to sketch their own potential solutions to improve the page. Always nice to get a mention in someone else’s weeknotes.
Also at e-Health Week, I saw a session by NHS Digital’s Eve Roodhouse, David Corbett and Phil Nixon, and finally met (on her very last working day here!) our wonderful Chief Nurse Anne Cooper.

On the way into work I picked up on a sketchnote of a #OneTeamGov meetup by Sam Villis at GDS, and got into an interesting conversation about the power of duplication.

Sam reflected on that in her weeknote too.
The main thing of the day was our design team event – the third time we’d got all the designers together from across NHS Digital since I started here last June. This time we welcomed guests, Helen and Lindsay from the NHS Business Services Authority. Everyone enjoyed hearing their honest account of simplifying the complex world of help with health costs. We ran a couple of rounds of rapid fire show and tells – 14 designers showing their work in the space of 90 minutes. In the event feedback, this format divides opinion – everyone likes hearing about lots of different services, but some say the 5 minute time limit feels rushed. I was just massively impressed that every designer who presented was so good at telling their story to a room of 35 people under time pressure.
Over lunch, some of us discussed the work in progress on changes to our cookie consent as part of the GDPR implementation.
The team day also gets a mention in Andrew’s weeknote. Andrew’s weeknotes are always worth a read.

I spent a big chunk of the morning with the Citizen Identity programme, chewing over naming and language in the service. Then an afternoon catching up with emails and planning for the week ahead.

Weeknote: 7 to 11 May 2018

I started writing weeknotes soon after I joined NHS Digital as head of design in June 2017. I find it a good discipline for me to reflect on my week, and to make sure I’m making progress against my own and my team’s objectives. Because groups of colleagues congregate in different virtual places, I settled on posting them simultaneously to our #design channel on Slack and an internal “blog” on Sharepoint. As an experiment, I’m posting a lightly redacted version here too. Views: my own. Publication status: experimental.


Straight back from the bank holiday weekend into NHS.UK programme show and tell day. In addition to the team’s showing their work, Marc, our head of products, gave an update from the senior leadership team. We plan to make these a regular fixture at fortnightly show and tells in future.

I joined a presentation by Helen Petrie of York University, who specialises is research with users with access needs, including older people. It gave me lots to think about. Thanks to Rochelle, Tanja, and the other user researchers for making it happen.

Dean, the lead designer on the NHS website, shared the team’s stance on accessibility with our NHS Digital Ability Network, which supports staff with disabilities, long-term conditions and carers, and got some encouraging feedback.

I also had a call with Victoria from m-Habitat and Lenny from the Helix Centre about a session we’re doing together as part of HIMSS e-Health Week.


A day in London. I had a chat with Louise, the service designer on apps & wearables. I met a service designer working in a well-respected design agency, who was interested in how we work as an in-house team.


A call with Amanda, our head of profession.

Then I headed over to the Government Digital Service event, Sprint 18, where I managed to persuade Andrew to sign my copy of the My takeaways from the event:

  • Cross-government collaboration works. For example, to make their emergency travel documents service, Foreign Office reused appointment booking from Ministry of Justice, GOV.UK Pay from Government Digital Service, and photo upload from Home Office.
  • Making things simple is hard work (but worth it in the end). It took new legislation, a multidisciplinary team, with policy and digital, from two departments, co-located, to make it possible for you to ‘check your state pension’.
  • The Digital Service Standard is no more! It has been rename the Government Service Standard to reflect the fact that it’s not just digital, but a standard for the whole of government.
  • There’s lots we can do to raise awareness and build capability around accessibility: “Interest can’t be the only motivating factor, you need some goals and management support.” – James Buller, one of two access needs leads at the Home Office.

I missed the presentation of advances on the GOV.UK platform to head over to Parliament for an NHS Digital event on diversity inclusion. Nicola, who leads on Widening Digital Participation talked about her programme’s work with partners Good Things Foundation. There were also great talks by Stan, experts by experience lead at homelessness charity Pathway, and Jonny, of social enterprise charity Turning Point.


Catching up with emails, and following up on the process to bring a designer on board, having made them an offer some time ago. I followed up on the accessibility and inclusion work, including clarifying how we’re approaching the GDS consultation on accessibility of public websites and apps.

For the last couple of hours, I looked again at one of the job descriptions we’re putting through the Agenda for Change grading process. It’s a valuable exercise because it forces us to describe the work of a designer against a set of generic competencies that have to be broad enough to fit the massive range of job roles in the NHS. If we get it right, designers will get recognition for their key roles in:

  • Policy and Service Improvement – our job is to design new services, or substantially improve existing ones, on nationally important areas of health policy and performance.
  • Research and Development – we spend much of our time exploring and learning in the discovery, alpha and beta phases of service development.
  • Equality, Diversity and Rights – the designer is the primary advocate in the multidisciplinary team for the principles of inclusive design.


I wrote a blog post reflecting on the Leeds Digital Festival event I was part of a couple of weeks ago: No more electric woks!