


Overview
Something feels off. The team is working hard but shipping slow. The roadmap doesn't match what customers are asking for. Stakeholders are losing confidence. You can't point to one thing. It's a bunch of things, and you need someone from outside the system to name them.
That's what a product audit does. I come in, dig into your product, processes, and people, and give you a clear-eyed assessment of what's working, what isn't, and what to do about it.
Who this is for
- Teams that feel busy but can't show meaningful product progress
- Leaders who suspect the roadmap is disconnected from customer needs
- Organizations where product, engineering, and design feel misaligned
- Companies preparing for a funding round who need to demonstrate product discipline
How it works
Week 1: Discovery. I review your roadmap, backlog, analytics, customer feedback, and key artifacts. I interview 8-12 people across product, engineering, design, leadership, and customer-facing teams. I attend existing ceremonies as an observer.
Week 2: Analysis. I map what I found against what a healthy product org looks like at your stage. I identify the root causes, not the symptoms everyone is already complaining about.
Week 3: Readout + reset plan. You get a written report with:
- What's working and should be protected
- What's broken and the root cause (not just "communication is bad" but why and where)
- A prioritized reset plan with specific actions, owners, and timelines
- Quick wins you can implement in the first week after the audit
What I typically find
Every audit is different, but the patterns repeat:
- Ritual debt. The team outgrew its processes 6 months ago and nobody adjusted. Standups are status reports. Retros are venting sessions. Planning is a negotiation, not a decision.
- Unclear ownership. Three people think they own prioritization. Zero people own discovery. Product and engineering have different definitions of "done."
- Roadmap theater. The roadmap exists for stakeholders, not for the team. It hasn't changed in two quarters even though the market has.
- Missing feedback loops. The team ships but doesn't know if it worked. No one talks to customers regularly. Analytics are set up but nobody looks at them.
Typical engagement
- Duration: 2-3 weeks
- Commitment: 15-20 hours total
- Format: Remote, with optional on-site readout session
- Deliverable: Written report + 90-day reset plan
Frequently asked questions
Impact in practice
Measured outcomes from engagements like this one
Delivery Leadership, Kaiser Permanente
One portfolio cut 12 weeks of delivery cycle time, traced directly to blockers value stream mapping surfaced. Coached 70+ teams across 9 portfolios. Aligned 300+ product org members on roadmaps, roles, and rituals. Rated 'Excellent' by leadership and called 'a visionary and a person of action.'
US Space Force SLD45 Capabilities Development Division (CDD)
MVP cycle time fell from 6 months to 2 weeks, a 92% reduction, because the OA bottleneck was broken once for everyone rather than worked around team by team. First app reached production. Trust restored across engineering, security, and leadership.
B Lab
Shifted B Lab from feature-driven to outcome-driven product thinking, with success defined as time-to-progress, abandonment, and NPS 70+ rather than ship count. Delivered org-wide alignment, a clear product vision, and one roadmap that connected tech, brand, review, and regional teams for the first time.
Related work
Case studies from engagements like this one
Delivery Leadership, Kaiser Permanente
Delivery Transformation: Reduced Cycle Times
One portfolio cut 12 weeks of delivery cycle time, traced directly to blockers value stream mapping surfaced. Coached 70+ teams across 9 portfolios. Aligned 300+ product org members on roadmaps, roles, and rituals. Rated 'Excellent' by leadership and called 'a visionary and a person of action.'
US Space Force SLD45 Capabilities Development Division (CDD)
U.S. Space Force - Platform Delivery Modernization
MVP cycle time fell from 6 months to 2 weeks, a 92% reduction, because the OA bottleneck was broken once for everyone rather than worked around team by team. First app reached production. Trust restored across engineering, security, and leadership.
B Lab
B Lab: Driving Global Impact with Clarity
Shifted B Lab from feature-driven to outcome-driven product thinking, with success defined as time-to-progress, abandonment, and NPS 70+ rather than ship count. Delivered org-wide alignment, a clear product vision, and one roadmap that connected tech, brand, review, and regional teams for the first time.
What clients say
RichExecutive Director, Delivery, Kaiser Permanente“Kate has amazing ideas, is very creative, and highly productive. She brings a lot of great energy, thinking, and leadership to our Delivery practice and is helping me establish and run an effective system for continuous improvement and upleveling our Delivery practices.”
StevenProduct Delivery Coach, Kaiser Permanente“I learn something new every time I get to work with Kate. I've been impressed with her way to push through complex topics in a fun and engaging way. She did a tremendous amount of ground work to help our OKR metrics exercise go smoothly, and her work with the annual planning team required perseverance, patience, and tact.”
MahilAgency Office Director, Pivotal Labs“Kate's work was impressive. Placing a PM on a technical App Modernization project was an experiment - she demonstrated that a good PM can provide massive value here. Her ability to focus and prioritize helped our team meet the OKRs in just 3 weeks. The client feedback was stellar and I strongly believe Kate's contributions played a big role. Her teammates shared positive feedback, too. Thank you Kate!”
From the playbook
Practices I use with teams during this type of engagement
Try it yourself
Free tools related to this service
Related writing
Posts that go deeper on this topic
The Bottleneck Is Bureaucracy, Not the Work
Most product teams are not slow because the work is hard. They are slow because the system around them is designed for control, not delivery. AI just made that gap visible.
What I Look for in a Product Team (And What I Build When It's Missing)
When I join a team as a fractional product leader, the first two weeks are diagnostic. Here are the signals I look for to understand what is working, what is broken, and what to fix first.
The Roadmap Nobody Reads (and How to Fix It)
Most roadmaps fail before anyone reads them. Not because the strategy is wrong, but because the story is missing. Here's how to build roadmaps that actually land.
You might also need
Services that pair well with this one
Sprint Engagement
A focused 2-4 week engagement to unblock a specific problem: stuck roadmap, team misalignment, AI strategy gap, or delivery stall.
Fractional Product Leadership
Your team gets a seasoned product leader who ships, coaches, and builds operating rhythms, without the 6-month search or the full-time commitment. Best for startups seed through Series B.
Strategic Comms & Roadmapping
Not just a slide deck. I help you tell the right story—through roadmaps, vision docs, and quarterly plans that unlock decisions.