An idea or first release
Make the smallest useful commitment.
Start with who needs the product, what can be learned and which choices can wait.

Have a product idea, a first release to shape, or an existing business or product you want to improve? Let's talk it through.
I'm Salman Asif, a Senior Technical Product Manager working across healthcare and B2B SaaS.
Image unavailable. Three connected stages: situation, choices and a named next step.
Start where you are
Choose a starting point. The example and practical next step change with it.
An idea or first release
Start with who needs the product, what can be learned and which choices can wait.
An existing product
Connect customer context, constraints and the next review point before adding more scope.
A process or handoff
Name the operating rule, the exception and the person who can act when the normal path does not complete.
I bring product and technical judgment to the connection between what customers need, what the business is trying to achieve and what a team can realistically do. A feasible solution still needs to be worth doing.
My approach is to question assumptions respectfully, make the trade-offs clear and recommend a useful next step. I care about what follows the recommendation, including where I can contribute and what needs to be understood before moving ahead.
More about meWho is affected, what are you trying to change, and what is getting in the way? An idea needs context just as much as an existing problem does.
Separate what is known from what is assumed. Consider the value, effort and consequences of each option—not just whether it can be built.
Agree what deserves attention next and where I can usefully help. The initial conversation is a place to begin, not a promise of a project or a particular result.
Judgment in practice
Product models, operating workflows and commitments become useful when the next team can act on them.
Image unavailable. A situation connects to choices and an accountable next step.
A requirement worth inspecting
A purchase request, an approval and an inventory record need to tell the same story. The case shows where that handoff was made explicit.
Inspect the procurement case →Work / 01
Connecting how schools are organized to the product model, access, configuration and commercial choices.
Inspect the decisionWork / 02
Connecting inventory work, purchase approvals and reporting requirements in an ERP MVP scope.
Inspect the decisionWork / 03
Supporting transaction-workflow definition, business-rule review and engineering/QA handoffs for a service marketplace.
Inspect the decisionUseful before a conversation
Work through a real choice with a guide, or build a discussion packet from what you know. No account or AI is needed.
Explore your challengeA closer look at one decision: when a shared software investment is justified.

Start a worthwhile conversation
An idea, a product decision, a difficult handoff. Start with the situation and what you would like to change.
Use the short form, or take a little more time with the optional brief below. A finished specification is not required.
Optional: organise your outcome, constraints and questions. Preparing or downloading a brief does not submit this contact form.
Prepare, then choose whether to share
Your answers stay in this tab. Nothing is submitted or saved. Leave out confidential or personal health information.
Start with what you know. You can leave questions open.
Keep a copy, or use it to prepare a conversation. This does not send a message, book time or authorize work.
Continue the thinking
Browse the writing · Follow Salman on Substack
Follow the writing with RSS Subscribe to newly published writing in your feed reader.
Email signup is not connected. Use the public profile above; no email address is collected here.
For a possible guest contribution or collaboration, prepare a short conversation brief. Editorial review and permission come before publication.