Historically, we’ve used Google Analytics to measure usage of this website.
GA has some advantages: it’s free, for a start, and it’s also the default industry standard. Even gov.uk uses it.
But it also has some, in my opinion, fairly major drawbacks.
So I’ve been thinking for some time that it would be good to be able to find an alternative that addresses at least some of the issues.
Most people think product design is everything.
It’s not.
Product design is what users interact with. Service design is how everything works behind it.
Great companies don’t just design products.
They design systems that make products work.
That’s the real leverage.
Follow Upslide for daily UX insights.
#UXDesign #ServiceDesign #ProductDesign #DesignSystems #UpslideDesignStudio
Imagine you work for an organisation where, on average, people have six things on the go at any given time.
Let's assume that, on average, each of those things takes a week to get done.
Given that – and it doesn't feel too outrageous – we should be able to deliver a thing a week, shouldn't we?
But that doesn't seem to happen in real life. Why not?
Well, essentially, we have two choices: we can do things, or we can get things done.
https://design.scotentblog.co.uk/you-can-do-things-or-you-can-get-things-done/
Opportunity cost is invisible. You can never see the road not taken.
But decision-makers think in opportunity cost constantly. When your project gets cut, they're not saying the work is bad. They're saying something else generates more value per pound spent.
If you want your work to survive prioritisation, make the comparison legible. What does this cost? What does it generate? What's the best alternative?
What's the best alternative to your current project?
Boundaries are chosen, not given.
Where you draw the line between "inside" and "outside" determines what solutions you can see.
What have you left out of scope that might actually matter?
Lou Downe is coming out with a sequel to the excellent Good Services book, Bad Services: How to Fix Services That Don't Work.
This is an exercise I like to run at the start of any project.
The exercise is simple; get the whole team – devs, testers, writers, designers, stakeholders, literally anyone you can round up – together, in-person or virtually, and ask the question:
Who are we willing to exclude?
#Inclusion #accessibility #serviceDesign
https://design.scotentblog.co.uk/who-are-we-willing-to-exclude/
Historically, we’ve used Google Analytics to measure usage of this website.
GA has some advantages: it’s free, for a start, and it’s also the default industry standard. Even gov.uk uses it.
But it also has some, in my opinion, fairly major drawbacks.
So I’ve been thinking for some time that it would be good to be able to find an alternative that addresses at least some of the issues.
People keep using tools they openly complain about. Why?
Switching costs. Not just money. They include:
- Data locked in proprietary formats
- Muscle memory and habits
- Integrations with other systems
- The cognitive cost of learning something new
A better service doesn't automatically win. It has to be better enough to overcome all of that friction.
What switching costs are your users carrying?
David O'Brien
Upslide Studio
Martin Jordan
Simon Whatley
Chris Oliver
