Skip to content
ale@portfolio:~/portfolio$ cat README.md

portfolio

Every case study here answers one question: measurable outcome.

README.mdportfolio

portfolio

Every case study here answers one question: measurable outcome.

How to read this

Case studies are split into two views:

  • Internal Tooling: built for internal teams, ops/support/data, never seen by a customer
  • Customer-Facing: shipped to end users, the product they actually touch

Same PM work either way. Problem, mechanism, outcome. The view just tells you who the thing was for.

Structure

Internal Tooling/
├── Monitoring & Governance
│   ├── Data Catalog in Looker
│   ├── In-House Data Catalog App
│   ├── Self-Serving Monitoring Data Tool
│   ├── Detect and Remove PII from GA
│   ├── Data Pipeline Validation Gateway
│   ├── Data Guardrails
│   └── Enrichment Data Accuracy Index
├── Optimization
│   ├── Events Salad Bar
│   ├── Namespace & Events Taxonomy
│   ├── Events Playbook
│   ├── Lighter Tracking Library
│   ├── Events Migration
│   ├── Lost and Found Challenge
│   └── AI Data Enhancement
└── Revenue & Operations
    ├── Revenue Partner Share Attribution
    └── Signup Conversion Tracking and Insights

Customer-Facing/
├── API
│   ├── IP Intelligence Data: Internal Initiative
│   ├── IP Intelligence Data: Customer-Requested Initiative
│   └── API v2 Bug
├── Integrations
│   └── Stabilizing a Third-Party Integration
└── AI Driven
    ├── IP Intelligence MCP
    └── dparents

The template

Every case study follows the same shape. TL;DR up top if that's all you need, full breakdown below if you want it.

  • TL;DR: one line, what changed and by how much, plus the outcome metrics
  • Saw It: the problem, in plain terms. What was broken and how I know, evidence, not a hunch
  • Figured It Out: how I got to the fix. Constraints, tradeoffs, who I looped in
  • Did It: what I shipped, including the miss if there was one, and the fix that followed
  • My Role: what I actually owned vs where I partnered
  • Full breakdown: problem & risk, discovery evidence, context, timeline (git log style), what we did, a rough sketch, who benefits, next steps

A note on the sketches

The visuals in each case study are sketches I drew myself, not screenshots. The products belong to companies I worked for, their UI and data aren't mine to publish. What you're seeing is my own redrawing of the workflow, accurate to how it worked, not a leak of proprietary design.

Want the real thing? Ask me in an interview, I'll walk through it live.