Two things are true at the same time. AI is changing what products look like, what people expect from them, and what's worth building at all. And it's changing how product people do the job day to day: how they research, synthesise, and decide, and how the teams and leaders around them organise to keep up. Knowing this isn't the same as being able to act on it. That gap is where you come in.
š¤ What this role actually is
The shape of the work varies by client. Sometimes it's coaching a product team on how they discover, decide, and ship in the AI era. Sometimes it's working with product leaders on how the whole product practice should change, and dropping to team level when that's where the change has to take hold. Often the team hasn't yet named what needs to change, or the client's product leaders disagree about it themselves. Untangling that on the ground, one team and one decision at a time, is where this role earns its keep.
Across an engagement, the day-to-day looks something like:
Working with product leaders and teams to figure out where product work needs to change in the AI era, and what to stop, start, and sequence
Reshaping how product gets discovered, decided, and run, and making the new way easier than the old one
Coaching product people directly, on judgement, on prioritisation, on using AI well, so their capability compounds long after the engagement ends
Driving a change yourself when the client needs a hand on the wheel, not only advice from the side, and showing results fast enough that people believe the rest is worth the effort
Helping the client see where AI is the right tool, and where a well-designed traditional interface still wins, and building that instinct into their teams
Joining early client conversations and helping shape the case and our proposal, so that what we sign up for is the work that will actually change how their product teams operate
Using AI in your own work every day for research synthesis, drafts, analysis, and p