Selected work

The output is the dashboard.
The benefit is the capacity.

Three foundational systems I’ve built, told the way they actually happened.

01

Cross-functional foundation

A Product Information Management system four teams could finally agree on.

The before

Product information lived in a Google Doc. Anyone could edit it. It wasn’t connected to the ERP, didn’t have an owner, didn’t have a definition of “complete.” It was the source of truth in name only. People kept asking the supply chain team for product details and nobody could tell them when or how those details would arrive. The work was getting done, but there was no system, no owner, no process holding it together.

What I did

Built an ERP-integrated PIM in Airtable. Field-level ownership so every column had a person responsible for it. Validation rules so the data couldn’t go in wrong. Locked, external-facing views for the teams that consume the data without editing it. A clear, written definition of what “complete” means at each stage of the product lifecycle. Then I trained the four teams who touch it, and documented the SOPs that keep it running once I’m gone.

What changed

The crashing Excel log retired. Three redundant spreadsheets retired. Data completeness moved from 40% to 98%. Product data became something leadership tracks weekly instead of panics about quarterly. The supply chain team stopped getting the same five Slack questions every Monday.

What it gave them: four teams who finally agree on what’s true.

02

Tooling overhaul

A Jira to Asana migration during a live sprint, with zero work dropped.

The before

The company was overhauling its tooling and onboarding everyone to Asana. The systems team was still in Jira. The Unito connectors between the two were technically working, but they were causing real friction in how people across the org requested and tracked work. Engineers got requests through one channel, ops through another, and reporting was happening in two systems with two truths. The connector was a bandage on a deeper disconnect.

What I did

Built a near-mirror of the team’s Jira workspace inside Asana, including their sprint boards and the MD-#### ticket convention they had years of muscle memory around. Migrated every live task in flight without breaking the sprint. Trained the team on the new flow, ran parallel for two weeks while they got comfortable, then turned Jira off. Documented everything so a new engineer joining in month three would never know there had been a switch.

What changed

The annual Jira license retired. The duplicate-tracking nightmare across two tools ended. Engineers stopped getting Slack-pinged at 9pm because someone in another team couldn’t find their ticket. The whole org now requests, tracks, and reports work in one place. The team kept their workflow. They just got it back, in the system everyone else lives in.

What it gave them: one source of truth without losing anyone’s muscle memory.

03

Executive visibility

Leadership dashboards the C-suite actually opens.

The before

Leadership didn’t need to live in Asana day-to-day, but they did need to know how the work was going. Who was overloaded. Which projects were on track. Where the bottlenecks were forming. Without a clean view, they were either pulling people into status meetings or getting filtered updates that took the edge off the truth. Either way, they couldn’t feel confident reporting up.

What I did

Built a multi-tab interactive HTML dashboard that pulls live from Asana every morning. Designed for the way executives actually scan, not the way ops teams document. 100+ active projects rolled up by team, owner, and status. Automated team load tracking so leadership can see who’s drowning before the person says so. A 90-second daily read instead of a 30-minute meeting.

What changed

Status meetings shortened, then mostly retired. Leadership can report up the chain with confidence in what they’re saying, because the data underneath is real-time and self-serve. The team stopped being the bottleneck for visibility, which meant they got their afternoons back.

What it gave them: leadership confidence without leadership meddling.

Other things I’ve built

The work behind the work.

Asana refinement & team training

For teams already using Asana but not getting the leverage from it. Templates, automation, hands-on builds, and training that gets them out of silos and into a system everyone can see.

Notion architecture & SOP libraries

Dedicated team spaces, shared templates, master SOP directories with standardized formatting and ownership. Wikis that survive a year of growth without becoming a graveyard.

Tasks out of Notion, into Asana

Moving active project tracking out of Notion pages and into a system that can actually assign, date, and report on it. Notion stays for what it does best.

Cross-tool sync with Unito

When a team can’t migrate, bidirectional sync that lets them keep their tools without duplicating effort. One source of truth, no forced moves.

Tech stack audits

A clear-eyed look at every tool you’re paying for. What stays, what goes, what gets consolidated. Often pays for itself in retired licenses inside a quarter.

AI integration into ops

Practical AI inside real workflows. Pattern-finding across projects, drafting documentation, accelerating reporting. Leverage, not gimmick.

The thread

The output is the artifact.
The benefit is the capacity.

Every system above is built for the same goal. Hand the team back the bandwidth they were burning on coordination, so they can spend it on the actual work. The dashboard is the artifact, but the benefit is leadership not dreading Monday. The PIM is the artifact, but the benefit is four teams who finally agree on what’s true. The migration is the artifact, but the benefit is engineers who got their evenings back. I build the foundation. The capacity is what shows up after.

Ready to see your stack from this view?

The best way to know what you need is to talk it out.

Book a free 30-min consultation  →

Currently booking retainers for Q2 and Q3 2026