The Product Kata manifesto

Why this manifesto

Product management is a commercial job. It is judged by what it does for the business: the customer whose work changes, the revenue that follows, the company that grows on it. This manifesto is what we believe it takes to do that job well. It holds the ten principles Product Kata Core is built on, and six promises it makes back to the people who use it.

We wrote it down because the job is taught in pieces. Every framework a product person can pick up teaches part of it. Discovery. Delivery. Team design. Culture. A body of knowledge here, a certification there. Between them, they have taught a generation of product people how to build the right thing, and taught almost none of them how to make a business out of it.

That is the gap. In B2B especially, a product succeeds or fails on things most frameworks barely mention: whether anyone understood the customer’s work well enough to change it, whether sales could sell it, whether support could hold it, whether the price reflected the value, whether the second market was ever entered. Product work that stops at the handover is not product work. It is feature work with a longer meeting.

We live, breathe and work through these principles in everything we do. Every practice, handbook and agent in Product Kata Core is written to serve them, and its agents coach from them. When Product Kata Core asks you an awkward question, the reason is on this page.

These are principles, not rules, and they are not the whole of the craft. There is real value in the discovery methods, the delivery practices, the team models and the bodies of knowledge that others have built. We use them, and we say where we got them. But when they compete with the ten below, we hold to these. Nobody has to sign all ten. In one business a principle is most of the job; in another it barely applies, and the weight shifts again as a company grows or its market changes. Take the ones that fit your context, weigh them your way, and argue with the rest. That argument is usually where the useful thinking is.

The ten principles

1. You win by changing how your customer works

Start where the value is created: inside the customer’s work. Know it well enough to say which step disappears, which decision gets easier, and what that is worth.

Then remember whose work it is. Changing how someone works is not a neutral act. It touches routines they have built, skills they are known for, and sometimes the shape of their job. People have reasons for working the way they do, and the reasons are usually better than they look from the outside. Learn them before you replace them, ask what your change costs the person at the far end and not only what it saves their employer, and earn the access and the candour that good product work depends on. The same respect you owe your colleagues, you owe the people whose day you are about to rearrange.

And look past the first customer. You are not changing one company’s way of working; you are changing a pattern a market shares, and the difference between a feature request and a product is how many people’s work the same change improves. A product that does not change how people work has not earned anything, however good it looks in a demo.

2. Market insight first — decide against evidence, not opinion

Keep a current, outside-in picture: the market, the competitors, the buyers, what is shifting. Bring it dated to the decision. The strongest opinion in the room is not evidence. Neither is the founding story about a market that has since moved, and neither is the loudest customer. Their voice is a data point about the market, not the market itself. You are building for the market, and the evidence has to be wide enough to say what the market wants, not just what one account asked for last Tuesday.

3. Product earns its seat by making an impact, not features

Product is a strategic function or it is an order desk. The way to be treated as the former is to talk about the business first: the segment, the model, the money. Then be right often enough that the conversation continues. Shipping more does not get you the seat; changing the numbers does. And the impact runs through other people: sales, marketing, delivery, support, finance, partners. Know what your decisions cost each of them, respect the work they do with what you ship, and the seat is given rather than claimed.

4. Own the outcome, and make it scale without you

You are accountable for your product’s commercial success even without the P&L, and even though you do not do most of the work. It is not a matrix cell. It is how the job feels when it is done properly: you cannot say the product failed because sales could not sell it or support could not hold it.

When it matters, you step in. That is the craft, and people see it. But stepping in is not the goal. The goal is an organisation that can sell, deliver and support the product without you in the room, because a product that needs its manager present does not scale, and neither does the manager. Build yourself out of the critical path on purpose.

5. The product team lives inside the company, not beside it

Product work meets the rest of the company constantly: sales, support, delivery, finance, an acquisition. Support runs in tiers and product usually sits at the deep end of them. Treat those meeting points as part of the work rather than as handovers, and be willing to lead the change when the meeting point itself is what is broken.

6. People first — the craft is working with people

Product work is done with people and it lands on people: your product team, the cross-functional team around it, sales, marketing, support, delivery, and the people in the customer’s organisation whose day your decisions change. Respect that, and treat the time spent with them as the work rather than the overhead around it. This is the part of the craft that separates a product leader from a backlog administrator.

It also has a limit, and pretending otherwise is how product people burn out. You cannot sit on every customer case, every escalation and every discovery session at once, so how you work with people has to be contextual: closer to sales while a new offering lands, closer to support while it beds in, lighter once others can carry it. Make that explicit. Say who you are working with closely right now, what they can expect from you, and what will change as the product moves through its life. A stated pattern reads as intent and earns trust. An unexplained one reads as neglect or favouritism, however good your reasons were.

7. Learning does not stop at delivery — that is where it starts

Discovery and delivery are good practices and they belong in the work. Discovery is not a phase, delivery is not a handover, both run all the time on the same backlog and through one decision point, and nothing enters discovery by accident. But they are part of the learning, not the whole of it. Discovery teaches you what to build. Delivery teaches you what you actually built. Neither one tells you what the market does with it.

That last part is where most organisations stop, and it is the part that decides whether the product makes money. Once something is out there, it will tell you things no discovery session could: who adopts it and who quietly does not, what sales have to promise to close the deal, where support time goes, what people pay for and what they ignore. Somewhere in that evidence is the answer to whether you have product-market fit at all, and where it is thin: which segment it holds in, which motion it works with, at which price. Go and find that out on purpose, and give it somewhere to land. A killed idea, a blown estimate, a launch that missed and a feature nobody opens are all candidates coming back to the same decision point.

Then be willing to change more than the feature. Sometimes the answer is a better implementation. Sometimes the honest conclusion is that the belief underneath was wrong, about the segment, the price, the workflow or the value, and no amount of iterating on the same idea will fix it. Asking whether you built the thing right is easy. Asking whether you should have believed the thing at all is the one that saves a year.

This is why the loop should be short. Not to ship more, and not to be fast for its own sake, but so that what the market teaches you reaches the next decision rather than a slide at the end of the quarter. Shipping volume is the easiest thing in product to increase and the least likely to matter. Learning is not a phase and it is not optional — it is what a product organisation actually produces.

8. Commercial success is the whole lifecycle, not the launch

Know how your product makes money: who buys it, why, at what price, through which route. Then follow that through its whole life, not just to the launch. Adoption, the price that has to change, the second segment, the market entered next, the version retired: in B2B most of the work and most of the money sit after the launch.

Following it does not mean doing it all. It means watching the business impact closely enough to see where it is stalling, and putting your weight there: with sales this quarter, with support the next, with the pricing model after that.

Staying in the game for a long time means carrying three horizons at the same time: what earns this quarter, what is being readied for next year, and what you are learning about the years after that. Each needs different evidence and a different kind of patience. A product organisation that serves only the near horizon looks efficient right up to the moment it is overtaken. One that serves only the far one runs out of credibility before it arrives. Balancing the three is what keeps a product earning over a decade rather than a quarter, and it is where most of your hard choices come from.

9. Focus is a decision — make it, and say why

Product work happens in parallel, always. A launch, a pricing change, an escalation, a new segment, a practice that needs fixing, and the requests arriving from every direction: all of it is live at once, and all of it is somebody’s priority. That is the craft. Not clearing the list, but deciding where your main effort goes while the rest keeps moving. Without that decision you do not prioritise, you drift, and the loudest request sets your quarter.

So choose, and say where the focus is with the business reason attached. This quarter on the launch. The next on how support handles the product, because escalations are costing us renewals. A month on the discovery practice itself, because we keep building the wrong thing. Sometimes the reason is that you are spending now on something that earns nothing yet, because it is how you find out whether the longer bet is real. People measure an unexplained choice against the hundred things they can see you are not doing, and they are right to. A stated choice with a reason behind it is one they can argue with, agree to, or plan around.

And be honest about what the request is worth. If nobody can name something you have deliberately chosen not to do this quarter, you are not focusing, you are queueing.

Knowing your focus and what it is worth is also the polite way to say no. You are not refusing people; you are telling them what you are doing instead, and why it matters more this month. Knowing the business well enough to say when and why is the art of it, and it is what separates a considered no from an unhelpful one.

None of which means being rigid. Business has urgencies that no plan anticipated, and when a critical customer case needs you, you roll your sleeves up and help your colleagues. Then you go back to the focus you stated. Knowing when the exception is worth it, and when it is just the loudest voice in the room, is the same judgement again.

And be graceful with yourself. Not doing everything is the job working correctly, not you failing at it.

10. Markets move — learn and adapt, or lose

Competitors move, buyers change, technology resets the price of things. What worked last year is a hypothesis this year. Improve the way you work every time you run it, keep your assumptions dated, and be ready to change what you believed when the evidence says so. Standing still is not neutral. It is losing slowly.

Product-market fit is the clearest case. It is not a badge you win once and keep on the wall. A competitor drops their prices and your product is suddenly expensive rather than good value. A technology shift resets what buyers expect and makes yesterday’s product look dated; AI is the current one. You enter a new country or segment and arrive with no fit at all, because fit is earned per market and the work starts again. Reaching it once is not the achievement. Holding it, market by market, is the business.

This is also why market insight is worth real effort rather than a quarterly slide. New evidence does not just adjust the plan. It can change the premises of the game for this quarter and for the years ahead at once, and turn the safe near-term bet into the risky one. Notice that early and you get to choose your response. Notice it late and the market chooses for you.

Your context matters most

The ten above are about the days: what you do, how you decide, who you do it with. They are the same everywhere. What you do about them is not.

A company selling one product into one country, through its founders, has different answers from a company selling four products into a dozen markets through partners, and both can be doing this well. Your business model, your market, your customers’ buying process, the maturity of your organisation and the size of your team all change how a principle becomes a practice.

Two deliberate choices shape that more than anything else.

Your product strategy, and the positioning and differentiation inside it. Where you play, who you are for, what you are better at and what you are content to be ordinary at. This is a decision, not an outcome, and once it is made it colours every one of the ten. It decides which customers’ work is worth understanding deeply and which is a distraction; what counts as evidence; what “impact” means this year; which stakeholders you invest in; where you are right to spend the effort and where the standard answer is good enough. Without it, every principle above degrades into working hard in all directions at once. This is why a product strategy is not paperwork: it is what makes focus possible and refusal defensible.

Your operating model. How the product organisation is actually set up to run: the capabilities you need, who owns what, the cadence, the practices you use and the ones you deliberately do not. The principles say what to hold to. The operating model is where they become a way of working that a company can repeat and improve, and it has to match the company you are rather than the one in the case study. Our reference product operating model is a place to start from, not a shape to copy.

That is why nothing here is a procedure. Product Kata gives you the shape of the work and a way to run it; the judgement stays with you, because you are the one who knows your context. Anyone who offers you a model that needs no adaptation is selling a ritual, and rituals do not survive contact with a real market.

What Product Kata Core promises in return

Principles are easy to agree with and hard to live by. That is what Product Kata Core is for. It is an agentic operating model, free to use: handbooks, practices and templates, and the agents that work through them with you, so that a product leader or a product manager can actually work this way, on a normal week, in a real company.

The material is written for the agents as much as for you. It gives them the frameworks, the context and the background, so you do not have to explain any of it to them, and you do not have to read it all yourself. Your part is the execution: the decisions, the conversations, the work with your customers and colleagues. The agents are not there to give you answers. They are there to make the work runnable and to make you think, by asking the questions a good colleague would ask and by pushing back where it matters. Six promises follow from that.

1. Written to be run, not read

The material is executable. You do not have to learn the framework inside out, and nothing here depends on everyone having read it. The agents have. Read what helps you, and let them carry the rest.

But running is not the same as following. A practice that is worth running is worth arguing with while you run it. It will ask you things you have not decided, and expose the assumptions you were about to skip. Take the time to think: that is where the value is, not in the output of the template.

2. Start with one practice

There is no course to take first. Pick the practice that matches the problem in front of you, and the agent walks you through how it is run, step by step, while you do the work.

Then it keeps asking: what did that tell us, what changed, what would we do differently. Reflection becomes part of running the practice rather than an event you have to schedule. It also points at the practices next to it, so the second one is easier than the first.

3. Adapt, don’t adopt

Everything is published and free to use, and it works from the start.

But your context matters, and the material is written to be changed. What you take from Product Kata Core starts working. What you do with it makes it yours: your words, your cadence, your steps, fitted to the way your company actually operates. A practice you have reshaped is the sign it worked, not that it failed.

4. Empowered teams that move fast, and stay aligned on purpose

Product Kata Core exists to make product teams genuinely empowered: able to decide and move at their own pace, without waiting for permission at every step. That is the point of publishing the work as practices teams can run themselves.

Empowerment is not everyone doing as they please. A team is empowered when it knows the company’s direction, the product strategy and what the neighbouring teams are committed to, and can therefore make good calls on its own. Take that away and independence just produces four teams moving fast in four directions, which is slower than moving together.

That alignment does not happen by goodwill, and it needs more of a frame as you scale. The moment two teams touch the same product, or share a business initiative, it needs somewhere to live: agreed decisions, clear ownership, a cadence people can rely on. Call it governance or call it ways of working; the substance is that everyone is pulling toward the same business impact. Product Kata Core builds it into the capabilities and practices rather than bolting a layer on top, and asks for no more of it than the situation needs. Skipping it does not save you from bureaucracy — it buys you chaos, and chaos is the more expensive of the two. What it strips out is the ceremony nobody can connect to a decision. What it keeps is the alignment and coherence that make several teams add up to more than the sum of them: two teams pointed the same way are worth more than two, and the same two pulling apart are worth less than one.

5. Mastery comes from repetition — that is the kata

You do not get good at a practice by running it once. The first run teaches you the mechanics, the third teaches you the judgement, and running it in a different context (another market, another product, another team) teaches you what was essential and what was only true last time. That is what a kata is: a sound form, drilled until it is instinctive, so that your attention is free for the part that is genuinely new.

That is why Product Kata Core’s agents are built to be your coach, mentor and sparring partner. They carry the form, so you are not reinventing it. They show the next move, ask the awkward question, and tell you when you have skipped a step. Ask the same thing a tenth time and they will explain it again, on purpose and without a sigh, and help you over the daily hurdles of busy product work. That matters most when you are the only product person in the room, or just starting your career.

The learning stays yours. A coach cannot do the repetitions for you, and there is no certificate to collect instead of doing them.

6. The whole of product work is covered — and you do not have to take it all

Product Kata Core spans the end-to-end picture, set out in the product operating model: strategy and portfolio, the day-to-day work of building and taking products to market, and the enablement that makes a product organisation able to do it well. You can see what exists and what you are missing, and the agents know all of it, so you do not have to.

Seeing it all is useful; adopting it all at once is not. Nobody needs every capability on day one, and a company that tries gets an operating model instead of a product. Take what your situation calls for, leave the rest visible for when it matters, and add depth as you grow into it.

What this is not

Not a standard to comply with. Not a certification scheme, and not a training organisation. Not a compliance regime or an approval process to pass through. Not the company’s whole operating model: Product Kata Core covers product. And not a silver bullet. If you are looking for a framework that removes the need to think about your own context, this is the wrong one.

Revision 1 · 30 September 2026 · Product Kata Core · CC BY-SA 4.0 · Using Product Kata Core