Helping leaders and teams make progress where decisions are slow, unclear, or contested.

In software development, a spike is a short, focused piece of work used to reduce uncertainty before committing to delivery. It is deliberately bounded, analytical, and decision-led. I use the term in the same way.

A Spike is a focused product strategy intervention with clearly defined aims.

It is used to address a specific strategic question, for example, clarifying direction, testing a set of options, examining a competitive landscape, or resolving an area of uncertainty that is blocking progress.

Each spike is scoped around agreed objectives and outcomes. It may involve analysis, working sessions, and synthesis over an appropriate period of time, rather than a single event. The emphasis is on producing insight and clarity that leaders can use to make informed decisions and take next steps with confidence.

This includes work on how AI should shape your product strategy and the way your product function operates. For many organisations, that question is no longer whether to engage with AI but how to build it deliberately into the way the team thinks, prioritises, and works. Getting that right requires the same clarity and structure as any other strategic question.