Data ethics canvas: helping us make good data decisions from the start

Being ‘trusted with data’ is something we talk about a lot at the Co-op and part of the Data team’s role is to make sure that every team is thinking about data responsibly. To help, we provide guidance and practical support to colleagues across the business.

Last June we started introducing our Digital teams to the Open Data Institute’s (ODI) Data ethics canvas. The ‘canvas’ is a template. It’s designed to help teams anticipate potential ethical issues associated with data they’re using, or coming into contact with, right from the beginning of a project.

A year on, the canvas has been gladly received and well-used, and now we’re rolling it out further.

Here’s a call to anyone making data decisions to use the Data ethics canvas.

The benefits and why they matter

The canvas allows teams to design with data in mind, making sure we maximise its value and understand associated risks. Tackling data-related questions early, with support from our expert teams at the Co-op can help minimise or even avoid any rework or surprise challenges or unintended consequences. Dedicating time to map out and consider the possible consequences of their data decisions has helped teams move forward quickly and autonomously and feel confident that they’re doing the right thing for our members, colleagues and communities.

Data ethics are here to stay

A clear message is emerging from regulatory bodies: the ethical use of data is a growing priority, and rightly so. The ODI has referred to ‘trust as the new currency’ and responsible technology think tank Doteveryone has launched their ‘Consequence scanning’ event to help tech companies replace the ‘move fast and break things’ culture with a more considered approach.

Using the data ethics canvas for the first time

If you’re working on a new project, product or service, we recommend running a workshop to consider the decisions you’ll need to make about the data you’ll come into contact with.

The sooner in the process you do this, the better.

image (9)

To get the most out of your workshop you should:

1. Scope and prepare it beforehand. You can do this with fewer people but try to include the project expert, the product manager and a delivery manager who can later facilitate the workshop. You’ll need to get a shared understanding of the importance of the canvas, pin down the benefits of working through it in the context of your specific project and decide what you want to get from the workshop.

2. Invite your digital product or service team as well as data experts to the workshop itself. You’ll need to around 90 minutes of their time. The data representatives could be from data management, data protection and information security depending on the project so email co-opdatamanagement@coop.co.uk to find out whose expertise would be best suited.

3. Print out the canvas and the topic headers (you can download them). The bigger you print, the more space you have to write which makes things feel more inclusive. 

4. Enlist scribes from the delivery team. Make it clear that everyone can and should contribute but delivery managers usually feel comfortable being on their feet, taking a lead when it comes to capturing thoughts, encouraging participation and collaboration and generally making workshops more dynamic.

5. Together, work through the 15 topics.

Topics and discussion points  

The canvas has more detailed discussion prompts but here’s an overview of the questions it asks the team to think about.

  1. Data sources (Where does it come from?)
  2. Limitations with the data (Is the data poor quality or does it have a known bais?)
  3. Sharing this data (Who are we sharing it with? Why? How?)
  4. Laws, policies and classification (Are we in line with GDPR; the Data Protection Act 2018; Co-op Information Classification and Handling Policy; is the information confidential?)
  5. Rights over data sources (Do we have permission to do what we’re planning to do with it?)
  6. Existing ethical framework (Does it align with the Co-op ethical values?)
  7. Purpose for using this data (Is there a good, mutually beneficial reason for collecting or using the data? Does collecting the data make things better for members, or, can we gain insights into products from it?)
  8. Communicating your purpose (When we ask for data, are we explaining why, in the most appropriate way?)
  9. Positive effects (How can we increase the positive impact of the project and how can we measure it?)
  10. Negative effects (Are there any points where there’s potential for a data breach?)
  11. Minimising negative impact (Where can we reduce harm and how can we measure the impact?)
  12. Engaging with people (Describe how people can engage with you and your project, are the people affected able to appeal or request changes to the product or service)
  13. Risks and issues (Where are the financial and reputational risks?)
  14. Reviews and iterations (When should we revisit the canvas?)
  15. What happens next (Who’s doing what and where should they go for support if it’s needed?)

Checking in and following up

As with all workshops, you’re likely to have a list of actions. Check in with the team on their progress against them. Schedule in another workshop when a product or service enters a new delivery phase.

Wider data support for Co-op colleagues

The Data ethics canvas is an introduction to thinking about data, and there’s more information on our intranet and Confluence pages. Our ‘Privacy by design’ playbook gives teams design considerations at the next level of detail.

You can find more support on running the workshops in our Data ethics canvas guide. Or you can email co-opdatamanagement@coop.co.uk for further support.

Find out more

You can read our commitment to data ethics in the Co-op Way Report 2018, and we’ve recently published our internal data ethics policy. We’ll be sharing our latest news and progress on data ethics to other ODI partners and members at an ODI Fridays lunchtime lecture on 10 May 2019.

Dale Upton
Data education and awareness manager

18 months on: our Digital Technology Operations team

It’s been just over 18 months since we first spoke about our Digital Technology Operations team so it’s time we reflected on how we’ve been helping product teams to deliver, what we’ve learnt and what’s next.

Developing our role as a ‘landlord’

In our first post we explained that our team looks after 3 things:

  1. Service management.
  2. Platform infrastructure.
  3. IT security.

Another way to think of our role is as a property landlord.

The various delivery teams are independent from us in the sense that they look after the direction and design of their digital product or service – in other words, how each household is run isn’t our concern. However, all Co-op products and services have some things in common which make up a shared digital platform. This includes firewalls, a logging and alerting platform and core templates used to build out our infrastructure. This is the part that our team is responsible for. We’ve set the ground rules and make sure all new products and services follow them (like good tenants). It helps teams keep their products and services safe and operational.

How we’ve helped

1.Putting checks in place

We’ve set up a ‘service readiness’ check that new products and features go through before we call them ‘live’. A recent example is when we launched Coop.co.uk on new infrastructure. The check includes making sure:

  • security testing is complete
  • the relevant operational teams know what’s changed
  • the relevant people know what to do if something goes wrong

2.Helping teams manage cost

We now provide a cost management tool for our delivery teams to help them manage their cloud infrastructure cost. Each team has a dashboard that shows their current spend and their forecasted spend. Having visibility over this gives them autonomy over how they manage their budget and lessens the likelihood that they’ll overspend.

Image of the cost management dashboard. It shows a 6 month forecast, a past 6 month spend and the actual spend.

Having a cost dashboard helped the Membership team to see that infrastructure logging was costing more than expected one month. When they investigated they found that the logging was sending data every second rather than every minute. Real-time cost reporting helped them spot the increase quickly so they could fix the configuration and incur only a few days of an increased cost.

3.Improving reliability

Over the last 18 months we haven’t changed the tools such as logging, monitoring and alerting systems, but we have worked hard to make them more reliable. For example, we’ve worked with our monitoring tool supplier to tweak how we configured it. Now it can handle more data easily.

We’ve also put efficient processes in place when there’s a problem. Teams can see the details on a status page and we alert the relevant people to fix the problem through our ‘major incident’ process.

4.Getting buy in from teams

We ask that delivery teams make sure they secure their infrastructure following our guidelines; carry out regular security and disaster recovery testing, and build products and services in line with our approved tech stack.

It’d be easy to say we just provide the tools for them to do this. But in the last 18 months we’ve done much more than that: we’ve successfully explained the importance of good technical standards to teams. We have their trust and their buy in and as a result there’s commonality and consistency between all Co-op products and services.

What’s next

Over the next 12 months we’ll be working with the rest of Co-op IT to shape some of our existing IT management processes, like disaster recovery, to make them work for the new challenges that cloud infrastructure brings. And as our digital teams start to use new technologies like containers and serverless, we’re looking at how our tools and processes can be adapted to support these as well.

Over the next few blog posts we’ll talk in more depth about how we do monitoring, how we manage our services becoming unavailable and how we onboard a new service.

Michaela Kurkiewicz
Head of Digital Technology Operations

Lessons learnt by a non-digital colleague: the benefits of agile ways of working

Last month we introduced ‘Visit’ to 55 Co-op Food stores. Visit allows store visitors to efficiently, and independently, check in and check out on store tablets or customer till screens.

We began designing Visit in October 2018. Below is a photo of me setting up an early alpha test in store.

Photograph of Nick, middle-aged man wearing a smart coat and shirt holding a paper sign saying 'Visits' above a tablet with the Visit product on there.

Visit is in beta right now meaning that our research and testing are ongoing and we’re making small improvements regularly. We’re hopeful that we can roll it out to all Food stores by autumn and that it will save time and solve efficiency problems.

But this post isn’t really about how we went about researching and prototyping a new product. It’s about the processes and practices associated with agile – a way of working that was unfamiliar to me and many of my immediate colleagues. It’s about the benefits of working in this way and why non-digital teams should be collaborative, open-minded and committed to learning about, and designing for, their user.

The problem: a long, old process

I work in the Risk team. Visits to a store are frequent and essential, and as part of my role I saw a lot of inefficiency when it came to signing in store visitors. The process would often be:

  • ask a colleague at the till for the visitor book and a pen
  • fill in your details
  • listen to the colleague to explain the store fire process
  • wait for a manager to take you to the back office
  • sign on to the PC
  • read the asbestos report
  • sign a paper acknowledgement of the report in the health and safety folder

It shouldn’t have so many steps in the process. It shouldn’t take this long. It shouldn’t involve so many people.

Our Field risk team regularly visit stores to train management on health and safety controls. As a result of the complicated, long-winded visitor flow, this was one of the least followed processes. There was also a lack of visibility around who has visited, so on occasions third parties have claimed to have visited a site but there is no evidence they have been.

I wasn’t the only one who wanted to improve this process.

Learning new skills and different ways of working

At this point, my knowledge of digital design was limited. I knew that digital product Shifts was co-designed for Co-op Food colleagues, and that other pieces of the Leading the way work relied on expertise from Digital, Food colleagues at support centre as well as Food colleagues in stores. I was aware that this coming together of specialists had been successful within the Co-op before.

I signed up for the Digital masterclass, a half-day training session that helps colleagues whose skills are outside digital understand how the Co-op Digital team works (more information at the end of the post). Richard Sullivan who ran the training introduced me to the benefits of agile ways of working.

Getting support

I’d identified the problem around checking visitors in and out but to fix it I needed expertise from the engineers from Retail IT as well as the Digital team including delivery managers Lee Connnolly and user researcher Rachel Hand.

Together, we started to learn more about the problem.

Putting theory into practice and learning more

Working on this project in an agile way, in a multidisciplinary team was very different to how traditional teams would tackle it. That includes the Risk team I’ve been part of. It was a sharp learning curve.

Here are 3 reasons why:

1.Testing over requirements

I’d been used to handing over a list of requirements to a technology team and asking them to find or create a piece of software that might fix a problem. For Visit, we put paper prototypes in front of store colleagues as soon as we knew enough about the problem. Their feedback helped shape the design meaning the product was tailored to their specific needs rather than it being an off-the-shelf solution.

2.Questions over assumptions

I approached the problem (the process of checking visitors in and out is inefficient), with a solution (so we’ll put software on store tablets to make it better). It seemed such an obvious solution to me (and in the end this is in fact our solution) but the Digital team showed me the dangers of assuming rather than questioning. We did an ‘assumption mapping’ session which helped us see if or where we were making assumptions about the desirability, feasibility of the product. Identifying assumptions reduces risk.

Photograph of a whiteboard with many yellow post it notes of notes arranged across a grid. This is an example of assumption mapping. 

3.Build in team time

I’d never worked in a team where we’d schedule regular time to reflect on our progress and our team health. This is what retrospectives are for. Until now, praise and problems were private – not something a team could be part of together. I didn’t realise how essential I’d begun to consider retros until we had to cancel one.

Progress through collaboration and thinking differently

Despite this being my very first digital product, I feel I can say with confidence that when Visits rolls out to all Food stores later this year, it will solve problems and meet our store colleagues’ needs. This is because the product is design-led. We were never tied to a solution, we changed our minds as we learnt more and our understanding of what store colleagues need improves.  

If you recognise opportunities for operational improvement, no matter which team you’re in, you can speak to Chris Ward, Product manager for Operational Innovation Store. You can also email Richard Sullivan to arrange a place on the Digital masterclass.  

Nick Bullough
Product owner

Pair writing clear, accurate content for ‘How do I’

This week, the design team held a show and tell to discuss 2 questions:

  1. What is design?
  2. Why should you care?

We’ve been posting some of the examples from different areas of design that we talked about. The posts are aimed at Co-op colleagues whose expertise are in something other than a digital discipline.

Today we’re looking at how pair writing played a huge role in the success of How do I.

In November 2017 we launched How do I so that all Food store colleagues could find out how to do something in their store quickly and easily. ‘How do I’ is a website with up-to-date policies and procedures on it, written in a clear, user-focused way.

It’s all down to great collaboration

To meet colleague and business needs, the guidance on procedures needed to be:

  1. Clearly written and easy to understand.
  2. Accurate and legally compliant.

There wasn’t one set of people with the correct skills to make sure the content did both these things. We needed content designers who are skilled in writing and presenting content for the web, and we needed subject matter experts such as policy owners – in other words people who know their stuff.

Forms and surveys specialist Caroline Jarrett puts it brilliantly here:

Over 6 months we reworded, reformatted and redesigned over 500 Co-op Food store policies and procedures for our store colleagues. The technique we used, in various formats, was pair writing.

What pair writing is and how you do it

It’s as simple as it sounds. Pair writing is when a content designer and a subject matter expert bring their skills and knowledge together to write content that works for users. Working together, on the same thing, at the same time speeds up the process of getting content live because feedback is in real time.

Pair writing best practice

While working on How Do I, content designers from Co-op Digital spent hours pair writing with subject matter experts from the Food business. Here’s what we found worked best.

Our set up

Sitting together allows you to talk and listen, question and clarify without distraction. We found that although this worked well in front of one person’s computer, it worked even better if the pair could take a laptop into a quieter place because the technique often needs quite intense concentration. We found 2 hours was enough and we swapped who was writing every 30 minutes.

If you have access to Google Documents, you can work in the same document at the same time from your respective computers. If you do this, make sure only one person is typing at a time, and you’re constantly thinking out loud and discussing what’s being written so that you’re both pulling in the same direction.  

Talking in real time is what matters

Sometimes it’s not possible to get together in person but that’s ok, you can pair write from afar. The important thing is that you’re getting time together to talk and share your understanding. For How Do I, we had regular phone or video calls with depot managers across the country to create content. It’s also crucial that you remember to get something written down – it doesn’t have to be perfect and it’s never finished. You can come back later and tidy it up.

Our process

  1. We started by setting some ‘acceptance criteria’, in other words, deciding which questions we wanted the content to answer. It’s important to do this so you know when you’re happy for the content to go live. It’s so easy to find yourself in an endless loop of feedback and tweaks until it’s ‘perfect’.
  2. We agreed a sign off process. The content designer signed off on clarity, the subject matter expert signed off on accuracy.
  3. We then looked at the existing content and asked if it did the job. In most cases the information was already there but it was hard to find, hard to read and not structured in a useful way. Together we cut out the unnecessary stuff.
  4. We simplified and reworded once we had the bare bones of what we absolutely needed to include. It’s the content designer’s job to pull out tricky, unfamiliar words and replace with language that research has shown to reflect the words people use.
  5. We tackled the order we should present content in. Together we prioritised information and reformatted it. We figured out the ‘important’ stuff based on the way someone would complete the task in store, how frequently something was asked and whether there were legal compliance issues.

When both of us were happy with what we’d got down, we gave it to Digital and Food colleagues to make sure the content was usable and addressed the user needs we’d developed. Don’t leave it too long before sharing and give a deadline for feedback so colleagues don’t slow down the process. We reacted to feedback and redrafted together if we needed to.

Lengthy detail to task-based content

Image is split down the middle. Left hand side shows how information about 'restricted sales' was presented. It's very copy heavy. Right hand side shows how we present it now. Further description in the post copy.

Together we transformed a copy-heavy page of information on restricted sales into several, task-based chunks of content. Research told us that when store colleagues wanted guidance on selling a restricted item, they would naturally search for the thing that they were about to sell. We left out the unnecessary information and instead gave colleagues the exact information they needed to complete the task.

How pair writing has influenced outcomes

Pair writing has helped us redesign, reformat and reword over 500 policies and procedures for Co-op Food stores.

It’s enabled us to develop content that all colleagues (not just managers) can quickly scan to help carry out a task. They feel empowered. We’ve seen a reduction in time that colleagues spend looking for information and it’s helped to save money too. Calls to our Food store helplines went down by around 40% in some stores, contributing to a saving of over £300k per year.  

Human to human – an extra benefit

Building a relationship with a colleague in person, or at least in real time on a call, builds empathy and breaks down barriers unintentionally set in place by businesses. Subject matter experts have come to me for further writing support because they know what I look like – this is less likely to happen if you’ve only ever spoken on email. They’re also now sharing their content, helping to eliminate unnecessary duplication of work and speed up sign-off processes.

Working collaboratively

If everyone shares an understanding of the benefits of being design-led, it’ll be easier for experts from around the business to work together to deliver value to Co-op customers, colleagues and the Co-op as a business. If you didn’t make the show and tell but would like to find out more, email Katherine Wastell, Head of Design.

Matt Edwards
Content designer

Field research: designing pre-paid plans with Funeralcare

This week, the design team held a show and tell to discuss 2 questions:

  1. What is design?
  2. Why should you care?

If you couldn’t make it, we’re writing up some of the examples from different areas of design that we talked about and we’re posting them on the blog this week. They’re aimed at Co-op colleagues whose expertise are in something other than a digital discipline.

Today we’re looking at how we used field research when we were designing a digital form with Funeralcare colleagues who arrange pre-paid funeral plans in our branches. (You can also make a pre-paid funeral plan online).

Buying a pre-paid funeral plan: how the paper forms process works

Here’s how the process tends to work:

  • a client rings a local branch to make an appointment
  • the client goes into a branch
  • a colleague and the client fill out a lengthy paper form together
  • the client pays at least a deposit to their local branch
  • 3 copies of the paper form are made – one for the client, one is kept in branch and the other is sent by post to head office which often takes 7 days
  • a colleague at head office manually copies the information from the paper form into a customer relationship management system
  • the form is dug out on the request of the client’s family after their loved one has died

The process is expensive, time-consuming and as with all human processes, there is room for error.

What we wanted to achieve

We wanted to create a more efficient, easy-to-use service. We wanted to connect the computer systems that are already being used in Co-op Funeralcare branches and integrate them directly with the customer relationship management system colleagues use in head office.

Where to start?

What we knew was limited. We had an idea what the start of the process was for clients and colleagues because we knew what the paper form looked like. We also had sales data from the very end of the process. But in order to improve efficiency and ease of use, we needed to know a lot more about how things are working in between these 2 points.

For both colleagues and clients we wanted to get a clearer picture of:

  • what a plan-making appointment was like (both practically and emotionally)
  • the paper form filling process
  • whether there were frustrations with the process and where they were

We arranged some site visits for our ‘field research’.

Learning from field research

We visited Co-op Funeralcare branches.

Green image with white copy that says: The approach. Get out of the office to learn and test

Why? Because when people feel at ease they’re more likely to open up and speak honestly. For this reason we spoke to our funeral arranger colleagues in a context they’re familiar with – in the rooms where they regularly create plans with clients. Talking to them here helped them relax, and because they weren’t in a place where their seniors might overhear, they were less guarded than they might be if we brought them into head office.

Seeing mistakes happen, figuring out why they happen

Talking to them was good but seeing colleagues fill out the paper plans was invaluable because we could observe:

  • the order they approached the questions
  • whether they made mistakes and where
  • if and where they used any common work-arounds where the form didn’t meet their needs

All of this helps us see where we can improve the design.

Feeding observations into the design

When we were talking through the paper forms with arrangers, they told us they often found there wasn’t enough space to capture a client’s personal requests. Because they’d come up with a reasonable work-around, it might not have been something they would have mentioned to us if we hadn’t been there, in their office, looking at the forms together. Being there helped us make sure we didn’t miss this. They showed us examples of when they had worked around a lack of space by attaching an extra sheet to the paper form they were submitting.

In the example below the client has requested to be dressed in ‘Everton blue gown with frill’ and they’ve been very particular about the music before, during and after the service.

Every funeral is different – just like every life they commemorate and the paper form didn’t accommodate for the level of detail needed. The work-around they’d come up with wasn’t hugely painful but good design is making processes pain free. We fed our observations back to the digital team and designed a form that allowed for individuality. It has bigger open text boxes to record more detail as well as including drop downs and free text boxes for music on the day.

Paper versus digital forms

The benefits of moving across to digital forms include:

  1. Having easier access to more data, for example, numbers on couples buying together and numbers on people buying for someone else. This is useful because we can direct our efforts into improving the experience where the most people need it. 
  2. Saving time for colleagues who manually copy paper plans to the head office system. Digital plans are sent directly to system and are instantly visible to colleagues in head office.
  3. Reducing the number of errors in paper plans. Common mistakes include allowing people over 80 to spread their payment over instalments and the client’s choice of cremation or burial not being recorded. The design of the digital form doesn’t allow arrangers to progress if there are mistakes like these.
  4. A significant yearly saving on stamps used to send paper forms from a branch to head office.

Field research helped get us to this point

We’re now testing the new digital forms in 15 branches. We’ll be rolling them out to more and more branches over time but we’re starting small so we can iron out any cracks.

So far, the feedback from colleagues is positive. But without observing colleagues in context, there’s a certain amount of assumption about the way they work on our part. Field research contributes to the fact the pre-paid funeral plan service is design-led.

If everyone shares an understanding of the benefits of being design-led, it’ll be easier for experts from around the business to work together to deliver value to Co-op customers, colleagues and the Co-op as a business. If you didn’t make the show and tell but would like to find out more, email Katherine Wastell, Head of Design.

Gillian MacDonald
User researcher

Using ‘sacrificial concepts’ to explore the direction of a product

Yesterday, the design team held a show and tell to discuss 2 questions:

  1. What is design?
  2. Why should you care?

Everyone was welcome but if you couldn’t make it, we’re writing up some of the examples from different areas of design that we talked about. We’ll post them on the blog this week. They’ll be aimed at Co-op colleagues whose expertise are in something other than a digital discipline.

First up: product exploration in the digital offers team.

Exploring the desirability, feasibility and viability of digital offers for members

In September last year we posted an update about our work around digital offers. In summary, we want to create personalised, paper-free offers for Co-op members. We think it will save money for them and create value for the Co-op.

Start somewhere: the format we tried first

We allowed a trial group of 6000 members to choose and use digital offers. Every Monday for 6 weeks, each of these members received 8 personalised offers based on their transaction history. Using our website or app, they could choose to add 2 of those 8 offers to their membership card so that when they swiped their membership card at the till, the offers were applied to their shopping.

At this point, we’d established that giving members digital offers in this way was technically possible which was great news. However, we didn’t know whether giving members a choice of 2 offers from 8, once a week, on a Monday was best for them and/ or good for the business. Would choosing 1 offer from 4 be better for them? For us? How about new offers every 2 weeks? How could we give members an enjoyable experience that would keep members using offers?

Ultimately, we wanted to increase their visits to Co-op food stores and nudge them to consider products that they might normally purchase from another retailer.

Our next piece of work was to find out how we might do this.

Exploring potential product directions through ‘sacrificial concepts’

We looked at the different ways we could give members personalised offers that could cultivate continued, enjoyable use.

‘Sacrificial concepts’, a method developed by design company IDEO, helped us gain insight into customers’ beliefs and behaviour. Here’s an example of a handful of sacrificial concepts that we put in front of a small group of members we visited in their own homes.

slide shows a range of sketches or what we refer to as 'sacrificial concepts'

They’re sketches of ideas.

They’re not presented in the context of a computer or device screen as we might do with designs that already have a substantial amount of research behind them. They’re just ideas, they’re abstract and open to interpretation because we put them in front of potential users to provoke conversation.

The sketches above helped us elicit honest feedback about offers, shopping and their interactions with the Co-op.

Cheap and quick feedback through sacrificial concepts

We wanted to quickly and cheaply test a few ideas with potential users.

Screen Shot 2019-03-12 at 15.39.43

Existing research suggests uncertainty and mystery motivates people. Would revealing an offer affect a member’s perception of it?

The feedback we heard gave us confidence that there was something appealing about this mechanic: it seemed to peak people’s curiosity. They found it exciting.

We know that people are influenced by social groups and communities. How would voting and social participation affect their interaction with the product?

Screen Shot 2019-03-12 at 15.40.02

The feedback we heard here was that this idea simply didn’t fit with how members plan their shopping. They didn’t plan their meals far enough ahead to know what they would want a week later.

We were also wanted to find out whether the way we presented the information about how much money members saved by using offers might affect their enjoyment. We explored whether there were any opportunities in terms of how we could show members the value of their offers.

Screen Shot 2019-03-12 at 15.40.13

The feedback we heard from some people was that they were more interested in savings in the context of their bank, not a specific retailer. But it was interesting to see how members reacted to us reframing the amount saved, so we learnt that there may be potential in this idea but it shouldn’t be the first thing we build.

What the sacrificial concepts told us

We took everything from the concept cards that we felt had potential and incorporated them into a prototype to put in front of members. This time, our designs had the research from the sacrificial concepts behind them but at this point, nothing was built in code. We used the prototype to get more feedback so we can iterate and improve for our members.

We’ve now identified 3 potential features for Co-op members digital offers. We’ll test them with larger volumes of users in May this year and we’ll listen to their feedback and make small improvements regularly.

The benefits of this technique

We started off with a lot of ideas and directions and through talking to potential users we’ve be able to quickly and cheaply ‘sacrifice’ the concepts that our research identified as having little potential. We’re left with the things we have a good idea will meet the needs of our members or at the very least are appealing to them.

If everyone shares an understanding of the benefits of being design-led, it’ll be easier for experts from around the business to work together to deliver value to Co-op customers, colleagues and the Co-op as a business. If you didn’t make the show and tell but would like to find out more, email Katherine Wastell, Head of Design.

Louise Nicholas, lead product designer
Joel Godfrey, product manager

What is design, and why should you care?

Today the Co-op Digital design team held a 90-minute show and tell to address 2 questions:

  1. What is design?
  2. Why should you care?

3 posters. each one is red and has white and green copy that says: what is design and why should you care?

Like all show and tells, this one was open to everyone. We wanted to give Co-op colleagues whose expertise are outside digital disciplines the opportunity to find out how the design process works. If everyone shares an understanding of the benefits of being design-led, it’ll be easier for experts from around the business to work together to deliver value to Co-op customers, colleagues and the Co-op as a business.

orange card with black copy that says: we're in this together. making good products is everyone's responsibility

We need people from all areas of expertise to work together if we want to make successful products and services.

In the show and tell we talked about:

  • why design-led companies perform better
  • what service design is and how it aligns user needs with business goals
  • how the design process begins with research, before testing and iterating and testing again
  • the importance of designing products that meet people’s behaviour, and grow according to market and behavioural shifts
  • why we need to focus on the outcome of design, not the way things look
  • the difference between functional design and playful visual design and when to use each one

Showing examples of design

We also used the session to pull out examples of design at Co-op Digital from the past year. User researchers, content and interaction designers talked about:

  • product exploration in Co-op digital offers
  • content design and pair writing when designing How do I
  • field research for Co-op Guardian
  • service mapping in Co-op car insurance
  • proposition testing and design sprints in Co-op Food e-commerce
  • one Co-op online and the design system

We’ll post about some of these examples later this week.

Co-design is everyone’s responsibility

We need people from all areas of expertise to work together if we want to make successful products and services.

Thank you to everyone who came along. We appreciate your time. If you didn’t make it today but would like to find out more, email me.

Katherine Wastell
Head of Design