Seattle, WA
I help SaaS and Technology organizations turn complex implementations into systems people actually trust. My background bridges project management, customer success, and AI-augmented business operations, with hands-on fluency deploying modern AI tooling into real workflows. Currently leading the PMO at Ripple Treasury.
About Me
I lead the PMO at Ripple Treasury, where I manage a team of project managers delivering enterprise client implementations. My day-to-day brings together what I've built across project management and customer success, driving on-time delivery, acting as the senior point of escalation when programs hit friction, and making sure teams hit the OKRs and KPIs that move the business forward.
What sets my approach apart is a customer success foundation. Before moving into program leadership, I spent years on the client-facing side, learning that the difference between a "completed" implementation and a successful one is rarely in the project plan. It's in how the team communicates, escalates, and protects the customer experience under pressure.
Today I bring that lens to every program I run. I care about predictable delivery, but I care more about how it feels to the people on the other side, our clients, my team, and the leaders who depend on PMO visibility to make their next move.
My Values, Leadership, and Soft Skills
The strategic and human capabilities behind PMO leadership at scale.
Translate organizational strategy into a portfolio plan PMs can execute against. North-star outcomes, multi-quarter roadmaps, sequencing tradeoffs.
Multi-level OKRs that link strategic objectives to initiatives, projects, and individual KRs. Standing review cadence with crisp decisions.
Drive org adoption of new processes, tools, and operating models. Manage resistance with empathy. Align people, processes, and platforms from day one.
Board-ready communication. Translate operational complexity into the one slide a CFO or COO can act on. Influence without authority across functions.
Mentor PMs into Program-level leaders. Quarterly check-ins, structured feedback, On/Off Track decisions, and a path for each report to grow.
Make the call when the data is incomplete. Escalate the right things, absorb the rest, and protect the team's focus while leadership iterates.
Capabilities
Modern PMO leadership operates at three nested levels. Project skills are the foundation. Portfolio skills are where strategy gets translated into outcomes. I work across all three, proven in treasury today, applicable to any SaaS or enterprise tech delivery tomorrow.
Project answers "is this single delivery on track?", scope, schedule, budget, quality. The tactical foundation of the craft.
Program answers "are these related projects delivering benefits together?", multi-project coordination, dependencies, mentoring PMs, resource flow.
Portfolio answers "are we doing the right work?", strategic prioritization, OKR alignment, capacity decisions, executive partnership.
Single project, end-to-end, on time and on budget.
Multiple related projects, shared dependencies, one outcome.
All initiatives, prioritized against strategy, delivering measurable business outcomes.
Projects
Real implementations drawn from treasury delivery, but every case demonstrates patterns transferable to any SaaS or enterprise tech context: stakeholder coordination, data-driven decisioning, and AI-augmented operations. Every story follows the same arc: Problem · Insight · Build · Outcome · Compounding. Click a tile to expand its case study inline.
What this proves:Decision systems that move leadership reviews from reading to deciding.
How do you move PM ideas from "submitted" to "decided" on a predictable monthly cadence without manual triage?
A monthly cadence that turns Google Form submissions into a ranked, decision-ready leadership artifact.
PM ideas surfaced through Slack, email, and 1:1s. No ranking, no cadence, no path from idea to decision.
One intake. One deterministic priority formula on Impact and Effort. One fixed monthly review cadence.
A Google Form feeds an 8-tab leadership workbook. OKR tab holds 3 KRs per initiative. Monthly Review logs every decision.
Q1 2026 ran the loop three months straight. Approved initiatives have a measurable home and a structured review.
Same template every cycle. New ideas no longer compete with old ones. The pipeline absorbs them.
Replace meeting reading with a decision-ready artifact.
Deterministic formula on Impact and Effort removes subjective debate.
Same template every month builds an operating rhythm, not just a backlog.
What this proves:Scaling a PMO's people operations with a reusable AI skill that codifies coaching and prep.
How do you give every direct report the same quality of quarterly prep without rebuilding the process each cycle?
A reusable AI skill that runs every quarter to produce manager prep, the 1:1 script, and the post-conversation shareable summary.
Same conversation, 4 PMs, 4 quarters. Each cycle rebuilt from scratch.
Encode the quarterly process as a reusable AI skill. Run it on demand.
ripple-process, scripts.md, template.md.
Off-Track justification drafted before the 1:1. Live message stays consistent.
New hire? Add name and start date. No redesign, no template hunting.
Skills capture how, not just what. Lets the system flex per PM.
Drafting Off-Track justification ahead keeps the live message honest.
New hires plug in as a name + start date. The process never changes.
What this proves:Org-wide change management — retiring a ritual and scaffolding adoption with a 4-doc framework.
How do you get every implementation team off the weekly slide treadmill and onto a single live source of truth, without leaving adoption to chance?
A new dashboard alone doesn't change behavior. The work was an org-wide rollout backed by a change management framework: rollout plan, training, ownership matrix, FAQ. Piloted first, scaled second, documented so the next adoption can reuse the playbook.
Every implementation team rebuilt the same weekly status slides. Different formats per PM. Data stale by the time leadership read them.
A new dashboard alone doesn't change behavior. Pair it with a change framework that gives teams a clear path off the old way.
Live cross-team dashboard. Rollout plan, training, ownership matrix, FAQ. Piloted with one team before org-wide scale.
Teams stopped building weekly slides. Adoption landed across implementation teams. Leadership shifted from reading slides to deciding on signal.
The 4-doc framework became the playbook for the next tool adoption. New teams onboard onto the dashboard template by default.
A good change replaces work, not just adds tools. Kill the slide ritual outright.
Adoption isn't a launch event. The framework keeps the new behavior alive after week one.
Prove with one team, learn, then roll out broadly. Risk down, adoption up.
What this proves:End-to-end project planning with phased delivery, RACI, and risk callouts across three banks.
How do you keep TMS implementations on time when bank connectivity sits across three parties with different SLAs?
Eleven phases, ~150 tasks, three banks, explicit handoffs. One spreadsheet that serves both internal teams and prospects.
TMS go-lives slipped at bank connectivity. Three parties, unclear handoffs.
11 phases. 5-step bank connectivity pattern: Pre-enroll → Cutover.
BoA / USB / MUFG tracks. Internal v0 + Sales v1 from one spreadsheet.
Source of truth for live implementations. Credibility doc for prospects.
Swap banks per prospect. Risk callouts already in place.
Sequence by dependency. Bank connectivity gets its own 5-step pattern.
Internal team and prospects work from the same spreadsheet.
Risk callouts live in the template so the next prospect inherits them.
What this proves:Program orchestration across 48 banks with tool-selection discipline and AI-augmented stakeholder alignment.
How do you keep 48 bank implementations on track when no single tool serves internal teams, technical owners, and leadership at the same time?
Across seven months, the tracker outgrew its tool five times. Each swap-in came from a trigger: a question the current tool couldn't answer fast enough. The final dashboard is deployed via Apps Script behind a go/ short link.
Kantata · 720 tasks
Excel · per-bank
Excel · Jira-anchored
HTML · AI-built
PPTX · 8 slides
Match the tool to audience and cadence. Right tool on each job.
PM ships the artifact in a working session. No engineering tickets needed.
Tracker-vs-Jira reconciliation surfaces team misalignment before review.
My Process
The stated ask is rarely the actual problem. I push back early, restate the question, and confirm what decision the work needs to enable.
Pull from raw exports, transcripts, and current state. Use real signal to decide what's truth, what's noise, what's missing. Flag every assumption out loud.
Ship the smallest version that gives the stakeholder a real signal. Iterate from a working artifact, not a blank page.
Encode the workflow so it runs again next cycle with no rebuild. Scalability is what turns a one-off win into a system that compounds.
Credentials
PMP and Forrester FXC-I certified for project management, plus Anthropic AI Fluency credentials covering modern AI-augmented operations. Future certifications mapped along the Project → Program → Portfolio path.
PMI's flagship credential, proof of fluency across PMBOK frameworks, Agile, and Hybrid delivery. Maintained through ongoing PDUs.
Forrester credential validating customer-experience leadership, governance, and operating-model fluency. View the official certificate via the link below.
The next credential along the Project → Program → Portfolio path. Validates multi-project program leadership at scale.
Anthropic certification covering the 4Ds of AI fluency, Delegation, Description, Discernment, and Diligence. Co-developed with UCC, Ringling College, HEA, and the National Forum.
Foundational Anthropic certification on using Claude effectively, including prompt engineering, tool use, and integrating Claude into real workflows.
Anthropic certification on Cowork, the desktop tool for non-developers to automate file and task management with Claude. Covers skills, scheduled tasks, and connector workflows.
My Career
From customer success roots to leading a global PMO. Each chapter builds on the one before.
Lead Ripple's global customer-facing PMO. Direct governance, methodologies, portfolio oversight, and a team of 6 PMs delivering on-time implementations across Sales, CS, Product, and Engineering in complex fintech environments.
Built the PMO from the ground up. Standardized governance, reporting, and cross-functional collaboration. Led the Kantata PSA implementation end to end.
Stepped from delivery into program operations. Won Top #1 Alida Deal of the Year (2020), then led the PSA tool migration to Monday.com and shipped business-optimization plays across global ProServe.
Where I learned to read clients. Grew from Customer Success Associate through Manager to Enterprise CSM, building the foundation of client-facing work.
Education
Toolkit
The methods and platforms I bring to every engagement, mapped to current PM-market expectations.
Frameworks I run delivery on
Platforms I run live programs on
Turning exports into decisions
2026 PMO differentiator
Achievements
Four standout moments from the work, drawn from real outcomes across my time in CS, Program Management, and PMO leadership.
Grew a contract 260% from $500K to $1.8M ARR in a four-month negotiation
Led business optimization plays across Alida's Global ProServe, yielding $2.2M annual savings and a 15% efficiency boost
Launched Monday.com Work OS to automate 9,000+ monthly actions across 500+ boards, saving 25 hours per week in admin time
Sustained a 95% renewal rate at Vision Critical, generating $277K in research service revenue and a 15% ARR increase