How I work
Every one of these cost me something to learn. What they share is an instinct to make a question cheap to answer before it becomes expensive to get wrong.
Find the cheapest question that settles the argument
Most disagreements about product direction are not really disagreements about evidence, they are disagreements about which question is being asked. Reframing it so a small test can answer it is usually faster than winning the argument on its merits.
At Intruder the question was whether to keep onboarding or go self-service, and nobody could settle it. I reframed it as whether removing the flow would cost more than 1% of conversion, which a redirect test could answer in an afternoon. Building it took thirty minutes. Getting agreement to build it took twelve months, and it ended with the CEO's approval, backed by the VP Product.
Agree the approach before opening Figma
Designing against a logic nobody has agreed to produces work that looks finished and settles nothing. I would rather spend the time up front, even when it feels like delay, because a screen is an expensive way to discover that the thinking underneath it does not hold.
With Paideia I refused to design the screens until the extraction layer behind them worked. The interface was only ever going to be a thin wrapper around whether a photograph of a handwritten planner could become structured lessons, and if that failed no amount of screen design would have rescued it.
Automate the rule, keep the judgement
When a process is slow, the useful question is which parts of it are rule-checkable and which need a person. Automating the first and protecting the second scales output without flattening the thing that made the work good in the first place.
At Newsflare the journalists, led by David Hickey, corroborated filmers' accounts with witnesses before a video went out. Rights and safety were checkable against rules, so we automated them. Whether a video was compelling was not, so it stayed with them. Output went from 20 videos a day to more than 80, with a smaller team.
When adoption is stuck, look for the fear before the missing feature
A feature people can use but do not is rarely an interface problem. Something about using it feels costly or risky, and that cost is usually invisible in the product itself.
Intruder customers were not importing their cloud estates, and the obvious reading was that bulk import was awkward. It wasn't. They were afraid of what appearing in the platform would do to their licence bill, so what unlocked adoption was granular sync controls and a clearer licence flow, not a better import screen.
Check whether the thing you are growing can survive its own success
Growth work tends to concentrate on the lever that is moving, which is not always the one holding everything up. It is worth asking periodically which part of the system would break first if the current plan worked.
Intruder's churn was running above benchmark while the attention was on enterprise. The customers actually leaving were the smaller ones, and between them they carried around 80% of monthly recurring revenue. Close to four in five said a version of what Kevin told us, that the value was good but he had no need for continuous scanning at that point. Intruder weighed it against the enterprise push and backed the push. I had argued for spending the year on the base, but it was a defensible call, and once it was made I committed to the enterprise work.
Where these show up
Most of these show up somewhere in the case studies. The clearest two are the Intruder onboarding project, which is the first practice from start to finish, and Paideia, where the middle three were worked out.
What I believe about design
The durable core of design work is research, facilitation, systems thinking, and opportunity framing. Those are not things being compressed by AI or trends. They're worth investing in.
I came to design through making, and I still think of myself as someone who makes things. But the thing I'm making now is usually the context around the work rather than the work itself: the research practice, the decision framework, the feedback loop, the team structure. The hands-on work hasn't stopped, and Paideia, an AI coaching app for home educators that I researched, designed and built on my own this year, is the current evidence of it.
Where I do my best work
I work best in remote, async-leaning product organisations where design already has a seat but hasn't yet realised its full influence, whether that's a scaling company from Series A to C or a smaller team where I can wear both product and design hats in a 0-to-1 context.
The roles I find most rewarding involve building research practice, coaching designers into broader strategic contributors, and doing the connective work between what users need and what the business is trying to achieve.
When to bring me in
The teams I help most are not short of ideas but short of a number they all trust to choose between them. It usually looks like one of these:
- Trials sign up but don't become customers, and the team can't agree why.
- You built a feature customers asked for, and hardly anyone uses it.
- Everyone reports a different number, so priorities go to whoever argues best.
- Growth has slowed and the roadmap has become a list of guesses.
The first three are the onboarding, asset discovery and metrics framework case studies, if you want to see how each one went at Intruder.
How we'd start
-
Step one
A discovery call
Free and 30 minutes long, to see whether your problem is one I can help with.
-
Step two
An Upstream session
£450 for an hour. We work out what your north star could be: the one measure that shows customers are getting value. The fee comes off the diagnostic if you go ahead within 30 days.
-
Step three
The growth diagnostic
I test that north star against your data and your customers, find the signals that move before it does, and tell you which one to focus on first.
To book the first call, pick a time that suits you, or email hello@iamkeithmason.com.