ImpactMS

Run like you're staffed.

An Atlanta design practice that builds the operating systems small teams run on, so a handful of people can carry the work of a department.

Start a conversation

✓ Operations mapped

✓ AI installed with your team

✓ Results you can measure

The Framework

I design the systems, the intelligence, and the visibility that keep small teams moving, starting in Atlanta and built to travel.

◆

Design

I map how the work actually moves through your organization, including the parts no one ever wrote down. Design starts with the people inside the system rather than the org chart above it.

⌁

Systems

Twenty years inside complex systems, building, shipping, and measuring. I build the layer that carries your work, with AI options doing the repetitive middle and your people keeping the judgment.

▣

Measurement

I capture where you started, so at the end you can see what changed with proof points and documented outcomes.

The Journey

Get in touch →

I followed the work upstream from projects to root causes, and what emerged was a design practice: people, systems, and measurement as one framework. ImpactMS is the container for what I am here to build.

Twenty years inside other people's systems

A computer science degree, years as a Unix administrator, then two decades of product leadership. I spent most of it building systems that served the people who owned them more than the people who used them, which taught me exactly where that goes wrong and how early it starts.

The same failure, in every kind of organization

Nonprofit or production company, the pattern holds. The route between a product and its customer is designed. Work falls into that gap.

Now I build it with you

Your team builds it alongside me and keeps running it after I go. The goal is simple: fewer things falling through, more of the work carrying itself.

Ways to Work Together

Map the Gap

A half day with your team. We take one process that keeps breaking, map it in the room, and name the three changes worth making before anyone leaves.

Book a workshop

The Operations Map

Two weeks. I interview your people, follow the work end to end, and hand back what is actually happening along with what to build first.

Start a map

The Install

Several weeks of building the operating layer together, with your team using it while I am still there to fix whatever does not fit.

Talk about an install

Tell me what keeps breaking.

Thirty minutes, no deck. I will ask how the work moves now and where it last fell apart, and I will tell you honestly whether there is something here worth building.

Start a conversation