Manish Reddy Katta Open to product roles in

Product Manager · London

I take the wrong answer off the table.

Digital products, enterprise to startup, where a person meets a system that has to answer them.

Case studies

Each one began somewhere nobody had looked. A journey measured end to end, a question counted for the first time, the same job priced twice by two people working blind.

Practice

Four things repeat, whatever the product.

The domain changes and the tooling changes. What does not is the distance between noticing something and being trusted with the answer.

Diagnose

The reported problem is rarely the problem.

What reaches me is a symptom, described by whoever noticed it. I take it apart until I reach the mechanism producing it, and validate that before a solution is scoped.

Instrument

I build the measurement before I make the argument.

The data that would settle an argument usually does not exist, because nobody owns the question. So I create it, and size it so the result survives the obvious objection.

Align

I get dependencies onto roadmaps I do not own.

No team reprioritises because my work matters to me. I show what the dependency is worth and what it displaces, in the measures they are judged on.

Qualify

I mark the edge of what a number proves.

Every result carries whatever else was happening at the time. I say which of that I ruled out and which I could not, and where the number stops being evidence.

About

I do not trust a problem I have not counted myself.

From engineering to product.

Eight years in digital products, the first of them as an engineer. I have taken a product from nothing to live, found work nobody had asked for and got it onto a roadmap, and rebuilt customer journeys that were losing people. Enterprise platforms in regulated financial services, and one startup build where I was the only product manager.

8+ yearsProduct and engineering
MBACranfield
B.TechComputer Science
Product CraftsmanAward, Vasjo

What I bring to a product team.

I follow the quiet signals, because people do not report problems they believe are simply the job. A question that keeps being asked, or a step in a journey where everybody goes silent. I will not put a number in front of anyone if I cannot show how I arrived at it, and I would rather say I did not measure something than imply that I did.

Product strategy and vision Product roadmapping Product discovery User research and voice of customer Backlog prioritisation Agile, Scrum and release management Product analytics and KPIs Customer journey mapping Root cause analysis Stakeholder management

Contact

About what's missing here. I've stripped out client names, internal system names and anything market specific, on purpose. The problems, the decisions and the numbers are all exactly as they happened, and I'm happy to go into the specifics in a conversation.