
Product Management
Deciding what will not be built, not what will.
A roadmap is not a wish list. Most of the job is turning down good ideas and being able to say why.
- Roadmap
- Discovery
- Prioritisation
Technology consultant
Product management, exchange infrastructure, banking, artificial intelligence, strategy, brand. It looks like six separate professions. Sit at the same table and it turns out to be one job.
Straight to my phone. No forms, no waiting on email.
Each has its own logic, its own tempo and its own colour.

Deciding what will not be built, not what will.
A roadmap is not a wish list. Most of the job is turning down good ideas and being able to say why.

Thousands of orders a second, zero tolerance.
Matching engine, wallet infrastructure, liquidity. There is no such category here as “works most of the time”.

Building something usable inside the regulation.
Compliance requirements do not have to kill the product. Usually what is bad is not the regulation but the lazy answer given to it.

Not the demo. The thing that survives production.
An impressive demo takes a week. Working out what happens when the model is confidently wrong is the actual job.

A strategy that produces no decision is not a strategy.
The output is not a deck. It is who does what by when, and what was given up to make that possible.

The sentence people use when they describe your product.
Brand is not a logo. It is the one line a customer uses to explain you to a friend. If you do not write it, someone else will.
It is no accident that they share a handle.
I have watched the same scene play out for years. A team ships something genuinely good and nobody knows how to talk about it. Or there is a flawless strategy with no engineering underneath to carry it.
My work happens in that gap. Between product and engineering, between engineering and the market, between the product and the sentence that explains it.
Every piece is correct on its own.
What is wrong is the gap between them.
A pocket knife is not worth its sharpest blade. It is worth being able to open the right tool at the right moment.
Working principle
Fig. 01The gap
Every engagement runs in the same order. Change the order and the work gets longer.
Most briefs arrive as a proposed solution: “we need a mobile app.” The first job is finding the real question underneath. Half of all projects change shape here and some of them end here, which is also a good outcome.
Not a deck. A working piece. If there is nothing you can open and try within two weeks, the problem is the plan, not the team.
Good consulting makes itself unnecessary. If it stops working once I leave, the work was not finished.
Forty-seven systems in production, across six disciplines. Money, movement, and the systems that keep both honest.
in the field
in production
one body
fintech to health
Closing
Either works. In my experience the second one goes faster.
or write to mail@berketok.com
I usually reply the same day.