
A journey into DesignOps @NHS was @CoopDigital
Manchester, England
Joined June 2019
- Tweets98
- Following31
- Followers757
- Likes277
This needs to be participatory.
The challenge then becomes how do you involve people who don’t control their time.
Pleasing the individual needs of people is the equivalent of holding your hand over a leaky pipe. It's not sustainable.
So then you’re getting into change management. You have to change the environment or the system.
To do DesignOps the skills of a designer is essential.
The hard bit is the focus. People will pull you in all directions. The urge to please and receive gratification is always there.
After doing many retros with our new starters. We've created a space to help them connect with the people they work with.
It's been great to see our design system team adopting our "component lounge". The goal was to lower the barrier to contribution for our busy teams. This has resulted in knowledge sharing increasing, which ultimately gives a better experience to our end users. 💕
Oh no sorry, Rachel. The images have full alt text, and are large enough for zoom, the colours pass contrast tests too.
I'll DM you the full text, as I'm struggling to fit it all in a Tweet.
3. Communication - Research needs to be clearly communicated in a consistent way
4. Impact - Key insights need to be visible across products
After interviewing our researchers we created 4 pillars to focus our efforts on for research storage :
1. Accessible - Research needs to be findable and accessible
2. Onboarding - Researchers need to have a succinct induction

ALT Picture of a poster: Research needs to be findable and accessible • Everyone can access previous research when needed • People know the locations of insights and relevant research • Folders are consistently labelled across products • Researchers own the structure they store their research within their product team
Every team would benefit from having a pack.
COMPETITION TIME 🏆
Reply to this tweet with a reason you need Workshop Tactics in your life.
100 RTs completes the competition and 10 people will get a free deck from workshoptactics.com.
(So a retweet = 1/10 odds you'll win 😜)
2. Why do we need this component?
3. Is there any research to support the design of the component?
Over the last couple of months we've had 29 contributions. Usually we'd have had 1 or 2 if that.
#DesignOps #DesignSystems
Getting people to contribute to design systems at scale can be tough.
To lower the barrier we set up a board in Miro called the component lounge™. It has 3 questions:
1. Do you have an example of the component? (screenshot and link / product name if possible)
Next week we'll be trying out our "component lounge" in an attempt to create a time boxed habitual way of design system contribution at scale. #DesignOps
DesignOps is 3 parts of a machine
1. The power: connecting design to the business by showing value, so teams are empowered
2. The cogs: if you don't have the tools & processes the machine doesn't work
3. The oil: delivering better customer experience by promoting best practise
Here is my DesignOps interview with @DesignOps_MEL
"Ultimately though DesignOp's goal is to support designers to do their best work."
designops.lol/interviews/des…
#DesignOps #Learning
2/2
6. Get told you'll need the Starship Enterprise edition
Cost £100k
7. Start to look elsewhere
8. Get 100 pictures of graphs showing how shit it will be if you don't purchase
9. Die
1/2 The journey of enquiring about software
1. Request an appointment through website
2. Get an choice of times
3. Pick time, get 100 sales emails
4. Have a zoom call with someone who knows nothing
5. Organise a time with person who know something







