Kim
Inouye

Helping leaders scale design and product teams

I build the operating system your team is missing, and I get them to actually use it.

I bring frameworks proven inside the world’s largest brands, diagnose where your team is breaking, and co-design solutions with them.

The difference is adoption. I stay hands on until the new way of working is the default, not the exception.

Let’s talk.

Where I’ve worked

Engagements

Ways to work together.

2 weeks^*

“We’re missing deadlines and can’t see why.”

Map your team’s workflow from intake to ship and find where it stalls. Built so you can see the root cause, not just the symptom.

4 to 6 weeks^*

“Every request comes through a different channel.”

Establish a shared definition of how work enters, gets prioritized, gets made, and gets seen. Built so the team runs it without you in the room.

One quarter^*

“We bought AI tools but nothing got faster.”

Find where the work actually drags, then test AI against it. Built so adoption comes from relief and curiosity, not from a top-down mandate.

Ongoing

“We need ops leadership, but not a full-time hire.”

Run the ops function while you scale, then hand it over. Built so your first full-time hire inherits a system, not a mess.

* Approximate timelines. Actual scope varies by team and engagement.

Work together

I take on a small number of operations engagements at a time, from a two-week diagnostic to fractional leadership.