I didn’t start my career thinking about product mindset. Early on it was all about deliverables — shipping things on time and on budget. In hindsight, that wasn’t a mindset so much as a checklist. Over time, what shifted for me wasn’t tools or titles — it was how I think about why I build things in the first place.

If I had to summarise it in one sentence, it’s this:

A product mindset is about obsessing over real value — not just activity.

And that shift makes all the difference between busy work and meaningful outcomes.

Most teams I’ve worked with — and probably you too — have lived the “checklist life”: task complete, ticket closed, sprint done. That feels good in the moment, but it doesn’t always mean anything to the people who use what we build.

With a product mindset, you start by asking:

What problem are we solving? For whom? And how will we know we’ve actually solved it?

The answer isn’t a feature list. It’s a shared understanding of change — what gets better, what gets easier, what gets solved.

I now help share what I have learned with teams and organisations who want to move beyond delivery for delivery’s sake — and start building with purpose. That doesn’t mean abandoning structure or process. It means using them differently. Roadmaps become hypotheses, not promises. Metrics become signals, not vanity. And success is no longer measured by what we shipped, but by what actually changed.

A product mindset isn’t reserved for product managers either. It’s a way of thinking that applies to anyone involved in creating something for others — designers, engineers, analysts, leaders. Because ultimately, value doesn’t come from roles. It comes from decisions.

And better decisions come from asking better questions.

So whether you’re shaping strategy, building features, or influencing direction, the goal is the same:

Focus less on output, and more on outcome.

Less on activity, and more on impact.

That’s the shift