I don’t believe in big reveals. I believe in listening closely, reading the signals, making a careful change and checking whether it helped. Then doing it again. Here is the cycle I bring to every product.
Choose a step to read more. Use the arrow keys to move between steps.
Step 1 of 7
Before I change anything, I want to hear how people actually use the product: where it helps them, where it gets in their way and what they have quietly stopped trying to do. I listen patiently and let their experience set the direction, not my assumptions.
See it in practice: Cybersmarties
Step 2 of 7
What people say and what people do are both true, so I check one against the other. Analytics, search trends, sales data and market sentiment show patterns early. I use AI to work through large amounts of behaviour and market data quickly, then decide with my own judgement.
See it in practice: horsesales.ie
Step 3 of 7
Every product has an essence, the one job it exists to do. I work out what that is, then shape features and flows around real behaviour and usability. That is also how I prioritise: the roadmap follows the user, not the loudest request in the room.
See it in practice: Cybersmarties
Step 4 of 7
I spent many years as a developer, so I can talk through trade-offs with engineers and designers without translation. When it is faster, I design and build a feature myself, which turns an insight into something people can use in days rather than months.
See it in practice: Hubbard Broadcasting
Step 5 of 7
I take products to market across every channel that matters: SEO, paid advertising, content shaped to what people are searching for, and visibility in AI search such as Google AI Overviews, ChatGPT and Perplexity, which is fast becoming a real source of traffic.
See it in practice: horsesales.ie
Step 6 of 7
I measure whether each change improved engagement, satisfaction or revenue, and I am happy to roll back what did not. Cost matters too: at Cybersmarties I ran load and stress tests and showed management the cost per user per month before they decided how to scale.
See it in practice: Cybersmarties
Step 7 of 7
I keep a picture of where the product could grow, then move toward it gradually. Small, measured steps keep the product steady for the people relying on it today while it becomes what it needs to be tomorrow. Then the cycle starts again, with listening.
See it in practice: AI financial analysis
The cycle is how I work. These are the convictions underneath it.
Most product managers hand a spec to engineering and wait. I can sit with the team, understand the cost of each option in real terms and, when it’s quicker, build the first version myself. Insights become working features sooner, and nothing gets lost in translation.