Design / Business
01
Why your beautiful website isn't converting.
A good-looking interface can still fail when the structure, messaging and user journey don't make sense.
Read the thinking →
Resources / Ideas / Experiments
I like understanding how things work.
Thoughts, experiments, breakdowns and lessons from
design, technology, business, digital products and the
occasional machine that refuses to behave.
01 / Why this exists
The work doesn't stop when the project ends.
Every project teaches something. Every problem raises another question. Every system has something worth understanding.
This space is where I explore those ideas — from design and technology to business, digital products, automotive systems and everyday problems.
Some pieces will be practical. Some technical. Some will simply investigate something I find interesting.
Explore by thinking.
Different subjects. The same curiosity.
01
Design
02
Technology
03
Business
04
Automotive
05
How Things Work
Things worth understanding.
Ideas that start with a question and end with something useful.
Technology
02
⌘
When should a business build custom software?
Custom development isn't automatically better. The real question is what problem you're trying to solve.
Read the thinking →
Automotive
03
◉
Why does a car vibrate at certain speeds?
A simple look at wheels, tyres, balancing, suspension and driveline problems.
Read the thinking →
More things to explore.
Archive / 202604
Technology
WordPress vs custom development: what does your business actually need?
↗
05
Automotive
What actually happens when an inner CV joint wears?
↗
06
UX / Product
Why dashboards become complicated.
↗
07
Design
When does a business actually need a brand refresh?
↗
08
Technology
Why adding more features can make software worse.
↗
09
Business
Your business has grown. Has your digital presence grown with it?
↗
Side quest / Automotive
Machines are systems too.
Sometimes the best way to understand a problem is to understand the system behind it.
01
Why does a car vibrate at certain speeds?
↗
02
What happens when an inner CV joint wears?
↗
03
Why can a small sensor cause a major problem?
↗
04
How cooling systems actually manage engine temperature.
↗
02 / Notes from the work
The subjects change. The thinking doesn't.
Whether I'm looking at a website, a dashboard, a business process or a mechanical system, I keep coming back to the same questions.
01
What is actually happening?
Before solving a problem, understand the current state.
02
Where is the friction?
Find the point where people, processes or systems start becoming difficult.
03
What can be simplified?
Complexity is sometimes necessary. Unnecessary complexity usually isn't.
04
What should exist instead?
Only after understanding the problem do we decide what should be designed or built.
Small ideas.
Quick experiments.
Not everything needs to become a 2,000-word article. Some ideas are better explored quickly.
UI
Redesigning a dashboard that has too many numbers.
Experiment
Web
What happens when a homepage is designed around the problem?
Experiment
Brand
How much visual identity does a small business actually need?
Note
System
When should a spreadsheet become an application?
Breakdown
The recurring idea
How I try to understand things.
Observe
→
Understand
→
Question
→
Simplify
→
Solve
The subject might be a website, a business process, an interface, a car or something completely unexpected. The thinking process stays remarkably similar.
Have something worth investigating?
Bring me the problem.
It doesn't have to be a finished brief. It can be a question, an idea, a process that isn't working or something you've been trying to figure out.
Start a conversation ↗