A busy week that kept me entertained during working hours, the evenings slack and empty though. This week I
- went over a spike to change how we do testing with our Frontend squad
- met with folks from the Office for National Statistics to go over the brief for a service assessment I’m leading
- prepared and delivered the first half of a presentation on how to hack your career
- prepared and delivered an ecocycle planning workshop to refresh ways of working with our Frontend squad
- met with Cabinet Office Digital to go over the plans to trial a paid version of cross-government Slack
- chatted over team sizes and design systems maturity with a product manager from Sainsbury’s Digital
- talked through our branching and release strategy for version 5.0.0 of govuk-frontend
- went to an all-directorate meeting in which deputy directors presented their teams’ roadmaps
- chatted over preliminary plans for publishing the Exit this Page component and pattern
- kicked off a spike for the Frontend squad
- reviewed work done on looking at the GOV.UK brand, its aesthetic and purpose
- prototyped a survey that will allow service teams to establish the impact of WCAG 2.2 on their services, and
- discussed plans for adding guidance on apps to the design system.
Short notes follow below.
Design systems maturity and team size
This week I chatted to a product manager from Sainsbury’s Digital about their design system. They look after several design systems under the Sainsbury’s group of companies and their team is merging a couple of those design systems now. It sounded as though their team was slightly less mature/established than ours, but most notable was their size – only 6 people. A much smaller unit with a comparable output to us.
Originally I was going to use a sailboat workshop to review the Frontend squad’s ways of working, looking at what we might change or add to better meet our goals, but I went with ecocycle planning instead.
They’re similar workshops but ecocycle planning is oriented around taking actions rather than simply identifying what might be holding us back. It encourages people to think about which activities we’ll redesign and how. I’m more in favour of action-oriented workshops because they’re more productive and proactive – other structures promote complaining without suggesting remedial actions.
Constraints, compromise and creativity
This week I’ve been thinking a lot about constraints, compromise and creativity: creating the conditions that make it safe to fail or get things wrong, that enable quicker decision-making and lower risk-aversion, as well as supporting the creative endeavours of the team.
Product teams are staffed with creative people who work inside constraints and have to make compromises. This is true of all the disciplines on a cross-functional team: designers, developers, researchers, specialists and managers alike. Design the right stuff and build it right. Balance user needs with organisational demands. Make something valuable that’s feasible to implement. Weigh up competing priorities and commit to what will deliver the most value for the least effort.
When you look at the neuroscience behind creativity, it’s a muscle that needs to be exercised, playing off the Imagination and Salience networks against the Executive Attention network. These are neural pathways in your brain that will only get better through exercise. So while you can partly rely on team members to exercise these parts of their brain, it’s only fair to shape their working environment to encourage that exercise too.
The Double Diamond model balances creativity with constraints by creating a space for divergent ideas and encouraging convergence on a small set or mix of ideas. Agile phases allow us to work through risk mitigation activities, and a bunch of factors contribute to the compromises we need to make.
Anyway, all of that research led me to look into how psychedelic drugs impact the brain and encourage new neural pathways to fire up, hence the hallucinations. We experience images or modes of thinking that our Executive Attention network might inhibit. I guess this is how some people are utilising large language models, as a kind of hallucination without needing to do shrooms, acid, mescaline or DMT.
- Sometimes you need an editor more than you need a writer A shortcut to clarity, 2 mins
- Fixing the ladder: How UK businesses benefit from better social mobility, 12 mins
- Bing: “I will not harm you unless you harm me first”, 16 mins
- Don’t bother me now I’m waxing my phone, 3 mins
- 10 things to remember when preparing for a service standard assessment – iterate, 11 mins
- Existential tensions put open source on the warpath to crisis point, 7 mins
- Please let me fail: failure, vulnerability and creativity, 6 mins
- Why Compromise Is the Great Design Superpower, 5 mins
- Design thinking was supposed to fix the world. Where did it go wrong?, 18 mins
- Slouching towards Britcoin, part 1: Threadneedy Street, 8 mins
- Slouching towards Britcoin, part 2: Quids Game, 8 mins
- A comprehensive critique of “Britcoin”. You’re welcome, 17 mins
- Twitter Drops SMS-Based Two-Factor Authentication for Unpaying Accounts, Effective March 20, 2 mins
- Never use a URL shortening service - even if you own it, 3 mins
- 2023/02/17, 3 mins
- Metaverse got torment-nexused just as robot did a century before, 3 mins
- Week 48/52, 3 mins
Got comments? Contact me, let’s talk.
A busy week that caused me to review my task management system. But ended on a high with my first marathon.
You’ve not heard from me since April, but here’s what I’ve been working on at a very high level.
Meetings vs workshops. Synchronous vs asynchronous. Broadcast vs engagement.