Work

15+ years shipping digital products.

Campaigns, launches, and rebuilds across consumer, tech, and lifestyle.

How I work

Turning any ask into a shipped, refined result

Intention gets used constantly in this line of work — a personal value, a client promise, a project mandate — but it's rarely defined past a feeling. This is the operational version I actually run on every project: three pillars, each with a required artifact, so you can point to whether it happened instead of just trusting that it did.

Intention = Ideation + Investment + Innovation

The three pillars

1
Ideation — define the problem
Artifact: a problem statement with a stated bar for success
Active listening and discovery that turns a vague ask into something worth solving, with feasibility confirmed directly with the people who'd have to build it.
2
Investment — size the commitment
Artifact: a resourced plan with a stated ceiling
Team, time, and budget sized to the idea before work starts — with the plan for how the result gets validated built alongside the plan for how it gets built.
3
Innovation — refine the core
Artifact: a version measurably tighter than round one
Refined against real usage across more than one pass, tracking what changed between rounds instead of stopping at 'good enough.'

When something breaks mid-build

A vendor slips, scope shifts, a stakeholder pushes back — the same three moves re-run at compressed scale: what's actually threatened, what fixing it right actually costs, the sharpest move available right now. Same discipline, escalation speed.

The full definition

AIPilotCross-functional

Proof case

A rough idea, three pillars, a 90% acceptance rate

Role: Sr. Project Manager, Old Republic Title
Outcome: 90% UAT acceptance → permanent deployment, customer-facing expansion
Team: 7-person pod: 2 Business Analysts, 3 Developers, 1 UI/UX Designer, 1 Scrum Master
Timeline: One-month pilot, two UAT rounds — three weeks, then one week

Ideation — defined what success looked like before building anything; confirmed backend feasibility directly with dev/IT leads.
Investment — assembled the 7-person pod sized to the pilot window; built the UAT plan with the BA before development began.
Innovation — ran two UAT cycles, three weeks then a tighter one week, tracking issues in GitHub between rounds — proof it improved, not just that it shipped.

This is the same thinking behind every result on the Work page — here's where it shows up in the numbers.

See the case studies