Loading
Ten years across fintech, cloud, automotive, edtech and retail — defining what a product should be, writing the rules it runs on, and staying close enough to delivery to see it ship.
Four ways of operating that sit under everything below. Not job titles, and not the full list.
Turn decisions into operating rules.
Build, align and measure.
Adapt the solution to its context.
Understand before building.
Find the real problem, map the constraints and cut the ambiguity before execution starts.
Design the service, not the screen.
Customer, operator, admin and vendor in one flow — including the parts no interface ever shows.
Rules that survive contact with reality.
Requirements, states, exceptions and operating models written so engineering can start without re-asking the founder.
Context first, then agents.
Multi-agent workflows with a documented source of truth, so AI-assisted delivery stays accountable.
Five pieces of work, described by what had to come together rather than by a job title.
Product vision, campaigns, user segmentation and the weekly review slides behind them.
A warranty platform built over an after-sales operation nobody had written down.
A design-file audit turned into a 42-process architecture and an input-readiness gate.
A multi-game play-to-earn arena — competitive mechanics and the economy underneath them.
A Persian RTL storefront rebuilt around Iranian payments and an in-country stack.
Core defines the practice, systems support it, execution proves it, and specialised experience differentiates it. Each one is tied to where it was used.
Scope, prioritisation, PRDs, backlog and the KPI and MVP calls that decide what a team builds next.
Challenging the brief, framing the problem space, and deciding what should not be built.
RazhmanaOTeacherGreenRest
Multi-actor systems — customer, admin, operator, vendor — mapped end to end across their touchpoints.
YaravanRazhmanaRenova+
Rules, states, exceptions and edge cases translated into implementation-ready specifications.
YaravanRazhmana
Multi-agent workflows, context engineering and cost control — workflow architecture, not prompt tricks.
YaravanThis site
Process maps, SOPs, RACI and the exception paths an operation actually runs on.
Revenue, cost, incentives and partnership structures modelled alongside the product.
Comfortable across APIs, CMS, databases and deployment decisions with engineers — a technically fluent PM, not an engineer.
Briefs, BRDs, SOPs and execution packets structured so the next person can act without asking.
YaravanRazhmanaCarsparency
Instrumentation, funnels, segmentation and A/B tests feeding dashboards a team can decide from.
User flows, information hierarchy and interaction structure — product direction rather than visual styling.
Aligning product, design, engineering, business, operations and vendors around one decision.
Financial products, their economics, and the trust a payment or an asset balance has to earn.
Persian-first and bilingual interfaces where RTL is the design constraint, not a translation pass.
Progression, competition and motivation designed as system mechanics, using frameworks such as Octalysis.
RP1 ArenaA1Paradise
Standing up a product function where none existed — ownership, process, roles and decision rights.
None of these is the job on its own. The job is what happens where they meet.
Constraints & value
Scope & priorities
Flows & interactions
Data & infrastructure
Processes & ownership
Context & assisted execution
System · Decision · Delivery