01Scope & outcomes
Product Manager
Focuses on why and what creates value: which user problem matters, where to invest next and how the team will judge an outcome.
Key decisionWhich problem is worth solving?
PRODUCT THINKING × ENGINEERING
Technical product management starts with the right problem
A good Product Manager does not turn every request into another feature. First, they find out what is actually going wrong and why it matters. I am Moein Ghezelbash, a Senior Technical Product Manager. This page is about the questions I ask, the decisions I make and the lessons I take from building and improving digital products.
B2B product platformsProduct strategyTechnology and data
Four questions. One direction.
01What is wrong?
02Which approach?
03What to build?
04Did it work?
Problem · Decision · Outcome
The problem comes first
“Let’s add this feature” is not a problem statement.
Imagine booking conversions have fallen. Someone suggests a new search screen. Perhaps the interface is the problem. Or perhaps inventory is out of date, the API takes too long to respond, or customers drop out during checkout. Starting with a redesign could mean shipping something new without fixing what is broken.
That is why I see product management as a mix of customer understanding, business judgement, technical decisions and measurable outcomes—not a task-management function.
Before asking “What should we build?”, I ask “What is stopping the user from succeeding?”
By Moein Ghezelbash · Senior Technical Product Manager
Understanding the roles
Product Manager, Technical Product Manager or Product Owner?
These titles overlap from one company to another. The meaningful distinction is the kind of decisions someone makes and the outcomes they are responsible for.
02Systems & integrations
Technical Product Manager
Brings the same product judgement to API constraints, data flows, integrations, architecture and service reliability.
Key decisionWhich solution is valuable and feasible?
03Backlog & value
Product Owner
In Scrum, is accountable for maximising product value and managing the Product Backlog effectively. Some organisations combine this accountability with product management.
Key decisionWhat does the team need to build next?
For the formal accountabilities of the Product Owner, see the Scrum Guide.
How I work
From a useful question to a testable decision
Every product has different constraints. These four steps help me make value, trade-offs and risks explicit before committing engineering time.
- 01Discovery
Discover the problem
I look beyond the request queue to user behaviour, evidence and the current journey. I try to describe the problem clearly enough that everyone on the team is solving the same thing.
- 02Prioritisation
Choose and prioritise
I consider expected value alongside implementation effort, dependencies and risk. A roadmap should explain why something matters now—and why another idea can wait.
- 03Delivery
Shape the MVP
Rather than building the complete vision immediately, I look for the smallest useful release. I work with engineering on the API contract, user experience, testing and release risk.
- 04Measurement
Measure and adapt
Shipping is not the end. Did users complete their task more easily? Did errors fall? Did a workflow become quicker? If not, we revisit the assumption or the solution.
Selected professional experience
What does this look like in real products?
Product work is not always a spectacular growth chart. Sometimes the value lies in exposing a hidden dependency, simplifying a workflow, or deciding not to build something yet.
B2B platforms01
Channelead — hotel booking for organisations
In hotel booking, a polished dashboard is only one part of the journey. Supply, pricing, response times and API contracts directly affect whether a booking succeeds. Working in this environment taught me to evaluate corporate customer needs against actual supply and operational constraints.
Product decisionPrioritise reliability and a clear booking journey over adding more options.
Product building02
Gardesh — a multimedia platform
Building Gardesh means balancing publisher access, content workflows, plan limits, media storage costs and the audience experience. The product roadmap cannot be separated from what it costs to store, deliver and maintain content.
Core challengeBalance publisher freedom, audience value and platform sustainability.
Product discovery03
Farvah Cafe — from internal software to a wider product
When exploring whether café software could serve other businesses, the first question is not what features to add. We need to understand whether ordering, payments, stock management and staff workflows work the same way elsewhere.
Product questionWhich assumptions should we validate with real cafés before scaling?
Meaningful measurement
A good KPI should change the next decision
There is no universal dashboard for Product Managers. I prefer a few measures that tell us something concrete about user outcomes and operational quality.
- B2B bookingSuccessful booking completion, supply errors and response time
- Operations softwareTask completion time, data-entry errors and genuine feature usage
- Media platformsMeaningful content consumption, returning audiences and service reliability
Clear answers
Common questions about product management
What does a Product Manager actually do?
A Product Manager helps a team focus on a valuable problem. Typical responsibilities include understanding customers, setting objectives, prioritising opportunities, working with stakeholders, shaping the roadmap and checking outcomes. The goal is not to own every task, but to make better product decisions.
Does a Technical Product Manager need to code?
Not necessarily. They do need to communicate confidently about APIs, data, architecture and engineering constraints. A technical background makes it easier to understand scope, dependencies and risk without replacing the engineers doing the work.
What is the difference between a Product Manager and a Product Owner?
Product Managers commonly focus on the market problem, product value and overall direction. In Scrum, the Product Owner is accountable for maximising product value and managing the Product Backlog effectively. One person may hold both responsibilities; the job title alone does not settle the question.
How is a Product Manager different from a Project Manager?
A Project Manager usually focuses on planning and coordinating delivery against agreed scope, resources and timelines. A Product Manager keeps asking why the work matters, who benefits and how to evaluate the outcome. The roles are complementary rather than competing.
Which skills matter most in product management?
Listening to users, analysing evidence, defining problems, writing clear requirements, prioritising, negotiating trade-offs, collaborating with engineering and evaluating results. Tools matter, but they are no substitute for judgement.
From the product decision notebook
Explore all product management articles
Two product problems worth exploring
If you want to see this reasoning applied to a specific design challenge, start with these articles.
Let’s work together
When the problem is not yet clear, that is where we should start.
Whether you are developing a B2B platform, reviewing a roadmap or aligning product and engineering, I would rather understand the constraints before recommending a solution.