Value,
Not
Noise.

Operations architecture for the humans doing the actual work. Find where the process broke, build the architecture that works and then explain it so everyone actually understands what's happening. More than twenty years in journalism taught me how to make complicated things obvious. Everything since is about seeing where the operational infrastructure actually lives... and where it should.

The
Investigation

Most companies hire someone who can talk or someone who can build. They don't usually find both in the same person, especially not one who can spot when the plan on the whiteboard has nothing to do with what's actually happening.

Translating between teams that don't speak the same language is my happy place. Leadership needs someone to explain the strategy without making everyone's eyes glaze over. Engineers need someone to tell leadership what's realistic. I get upstream and get forensic, often in the same meeting.

When I do my job well decisions start getting made. The thing holds. People stop talking past each other. In work like this success is nothing is going wrong. There should be more awards for the fires that didn't start.

Discipline
Operations, GTM, Product Marketing and Getting Everyone on the Same Page
Prior Life
20+ years in journalism... translating complexity for real people
Current Terrain
AI implementation, rev ops, B2B and B2C product marketing, comms
Operating Principle
Reality before theory. Terrain before map.
Debrief
The implementation failed. Not the people.

The
Warehouse

Strategic Operations
Multi-Team
Roadmap Summit
An e-commerce operation running on assumptions instead of architecture. Stakeholders had never been in the same room with a shared operating reality. I built the structural pressure test that forced that reckoning and the 3-year roadmap that came out of it.
Scope: 18 stakeholders, 8 functional domains // Output: 3yr strategic roadmap + 1-6mo execution plan
Decision Infrastructure
E-Commerce P&L Build
No e-commerce P&L existed. Revenue was fragmented across four channels and there was no source of truth. Costs were buried in generic GL accounts and spreadsheets. I built the financial architecture from scratch... structure, data mapping, governance standards and a live Looker dashboard that became the gate for growth decisions.
Scope: 4 channels, 6 functions, 18+ GL accounts // Output: First e-commerce P&L + live Looker dashboard
Delivery Governance
Web Experience
Capacity Expansion
Four strategists feeding 1.25 FTE of engineering capacity through a 159-page backend system. No governance. All scope creep. Built an agile capacity protection model that gave engineering veto power, the team scope visibility and forced ROI-based prioritization into every sprint.
Scope: 4:1 strategist-to-engineer ratio, 1 engineering bottleneck // Output: Custom sprint governance + 115% conversion lift
Ops Management
Post-Acquisition
Integration Launch
An acquisition with no integration model. Eight teams, three vendors, a system architecture nobody had mapped. I built the vendor governance framework, product taxonomy (281 categories from actual SKU data, not inherited guesswork), and the cross-functional workback that sequenced ERP, tax engine, and payment processor into a launch the business could actually execute.
Scope: 3 vendors, zero prior integration model // Output: First acquisition integration blueprint — taxonomy, governance and launch sequencing from zero existing structure
Channel Strategy
Enterprise Newsletter
Launch
The company newsletter had a 9% open rate. Slack only eached 39% of the workforce. 80% of employees worked in the field with no reliable communication channel. I audited the channels, pitched the CEO directly and built the first enterprise-wide weekly communication. From 9% to 95%+ sustained open rate more than two years later.
Scope: 4000+ employees, 4 audience segments // Output: Enterprise newsletter achieving 95%+ open rate, channel audit framework, editorial style guide
Strategic Communications
Crisis Communications
Architecture
A $1B+ industrial technology company had zero crisis communication infrastructure. No escalation framework, no holding statements, no channel strategy for emergencies. I built the system from scratch: severity classification, pre-written messaging for 15 crisis types, three-tier response team architecture and channel-specific protocols.
Scope: 150+ locations, 40+ states // Output: Complete crisis communication architecture with 4 severity levels, 15 holding statements, 3-tier response team
AI Implementation
Workforce AI
Adoption
Built an AI automation program from zero. Identified pain points first, trained on one task at a time and scaled only what stuck.
Outcome: 42+ hrs/month recovered // Adoption: 30% to near-100%
R&D
Thinking Under Construction

The
Verdict

01
Add value, not noise.
Every action either contributes or clutters. There is no neutral.
02
Vocabulary is the barrier.
Most failures aren't technical. They're linguistic. Define the terms and the conflict dissolves.
03
Reality before theory.
The map is not the terrain. Observe the system as it is, not as you wish it to be.
04
Structure is how you protect people.
Good systems prevent harm. Clarity reduces suffering. Organization is care made operational.
05
The implementation failed. Not the people.
Technology serves people. When it stops doing that, blame the system, not the humans inside it.

The
Debrief

I'm building what comes next. Where GTM, rev ops and product marketing collide with innovation, AI implementation and the humans doing the actual work.

Good problems always welcome.

Conversations are way better than page views.