Behind the portfolio
About my work
I work at the point where a problem, a product decision and a delivery team meet. This site brings that professional path together with the things I write and build independently.
How I approach a problem
Good product work starts before the solution. I want to know who is facing a problem, what they are trying to accomplish, what breaks in their current process and what evidence would tell us that a change helped. That means translating conversations into testable requirements instead of beginning with a feature list.
My background spans software development, research-oriented moderation work, digital marketing, business analysis and product management. Those experiences make me attentive to the details that often fall between disciplines: language in a requirement, edge cases in a workflow, the cost of a manual exception and the handoff between a client and a developer.
A practical working method
- Frame the decision. Write the user's objective and the outcome the product needs to achieve. Separate what is observed from what is assumed.
- Make the workflow visible. Sketch the current steps, roles, inputs, decisions and failure points before proposing a new screen.
- Scope the smallest useful release. Define boundaries, dependencies and acceptance criteria, then prioritize the risky uncertainties.
- Check the result. Use task-level outcomes, qualitative feedback and defects to refine the next version rather than treating shipment as success.
From code to product work
I began in backend development and later worked as a business analyst on healthcare-related products. The portfolio timeline documents my roles, including work on epics, user stories, backlog coordination, stakeholder discussions and sprint reviews. My focus in product management is on making the gap between a client request and a useful delivered product as small as possible.
Some professional work is confidential. Case studies on this site describe public projects or general methods; they do not reproduce client data, confidential specifications or unverified performance results.
Publishing and building outside work
I have published ten books across AI, practical technology and reflective writing, presented in the books section of my portfolio. I also build independent websites, including Ninth Post and Indian Anime Club. These projects provide a place to explore editorial structure, discoverability, content quality and community experience.
See the project notes for the public-facing design decisions, or read my product essays for reusable ways of thinking through product problems.
Have a specific problem in mind?
Share the rough version, the uncertainty or the workflow you want to improve.
Email me