Product management

I run theproduct, notonly the pixels.

Product management across every domain on this site: strategy, discovery, roadmap, specification, delivery and the numbers after launch. The artefacts below are samples of how I work.

What I own
Strategy

Where to play, and the bets we refuse.

Market read · positioning · one-page strategy

Discovery

Evidence before opinion, mine included.

Interviews · field visits · data · opportunity map

Roadmap

Now, next, later. Outcomes, not features.

Themes · sequencing · trade-offs in writing

Specification

A PRD an engineer can build from.

Problem · scope · states · acceptance criteria

Delivery

In the room with engineering until it ships.

Rituals · cut lines · release notes

Measurement

What people did, not what they said.

North star · drivers · review cadence

Roadmap

Now, next, later. Outcomes, not features.

Now

TrustOne-sentence review stepMistaken actions ↓
TrustEvidence on every AI answerSigned decisions ↑
GrowthOnboarding rewriteActivation ↑

Next

GrowthUrgent booking alertsFill rate ↑
PlatformDesign system v1Time to first screen ↓
TrustPlain-language labelsSupport contacts ↓

Later

PlatformRole templates for identitySetup time ↓
GrowthPartner marketplaceNew revenue line
PlatformCustom dashboardsParked. See the matrix.

Sample roadmap. Every card names the number it is meant to move.

Prioritisation

Saying no, with a reason.

Impact against effort. Select any point to see the call I would make and why.

CutCustom dashboards

Three customers want it. Nine months of work. No.

Impact ↑Effort →Do nowPlanMaybeCut
Metrics

One number the whole company can repeat.

North starDecisions signed with evidence, per week
DriverQuestions asked
Onboarding completionTeams invited
DriverAnswers trusted
Answers with sourcesRejections with reason
DriverTime to sign
Missing-data rateReview queue age

Sample metric tree for a governed AI product. Drivers are owned by teams. Inputs are what we can change this quarter.

Specification

A PRD that fits on one page.

PRD · sampleSend money, in plain languageOwner: product · Reviewers: design, engineering, risk
Problem
Customers abandon transfers at the review step because the screen describes the ledger, not their money.
Who
Retail customers sending money to a person for the first time.
Success
Fewer abandoned transfers and fewer “where is my money” contacts, measured for 30 days after release.
In scope
Review screen, confirmation, the three failure states, final copy in two languages.
Out of scope
Scheduled payments, international transfers, business accounts.
Risks
Legal wording. Mitigation: risk and compliance co-write the strings, not review them at the end.
States
Default · new recipient · limit reached · declined · pending review · sent.
Done means
Every state drawn, every string final, acceptance criteria written, instrumented before launch.
Every domain

16 industries. The method travels.

FinanceRobinhood→Banking→HealthcareBarnabus Care→ConsumerAmazon · Safeway→SemiconductorPDF Solutions→Developer toolsCTO.ai→EnterpriseBarnabus Labs→EducationBarnabut — Future Minds→AI productsBarnabus Labs→Design systemsPDF Solutions · Barnabus Labs→MarketplaceLocuPedia→InsuranceConcept→TravelConcept→FinanceQeepem→Arts and cultureTirgan · Connected Dots→MobilityFuelTrip→Food and restaurantsPizza Hut→