Most organizations that call for an audit already know something is wrong; they just cannot say what, where, or how badly. The product team ships (somehow, eventually), the roadmap moves (somehow, however slowly), everyone is busy (but busy-ness does not equate to value), and yet the thing the business has been expecting from the venture does not show up in the numbers. An audit exists to convert that unease into a list of findings with evidence, a plan of action, and a realistic view of what turning things around will cost in time and people.
This service covers the three things that usually go together in that process: finding out what is actually wrong (audit), making the organization better at the relevant capability (improvement), and building up the people who have to carry it going forward (upskilling).
When it makes sense
- The product organization is not pulling its weight, and you need to know why. Product is OVERBRING Labs primary focus, and the organizational setup around it is its home turf, because nothing can be created ex nihilo. When your product development or product management team seem to be stuck in a quagmire, when things are not moving as fast as expected, or where in general you have a gut feeling that more could be done with what you already have at your disposal, the question is not a bromide like “are we Agile enough?” that subjugates your business to a flavor-of-the-month process/framework/consulting-product, but boring diagnostic questions such as: what is the team actually doing day to day, what are the real sticking points, and which of them are process problems, capability problems, or mandate problems? Those three require completely different approaches, and they are routinely confused.
- You are about to scale the product side, and the current setup cannot take the load. A pipeline that worked for five products will not work for fifteen, and the gap shows up as heroics, attrition, or both. An organizational setup (usually, “that guy who knows how to code”) that was sufficient for creating an MVP either by coding-by-hand or with agentic coding does not translate to turning that prototype into a product, let alone a value stream, i.e. a business.
- You want to build or improve organizational capabilities that match your strategy. Sometimes the answer to “we need product management” or “we need a (better) product development process” is not a hire. I would even say that it is increasingly not the case that building the engine that delivers the value requires bringing in the infamous “X” or “Deft”. Instead, it is building on the competencies of the very same people who know your business best, with all its strengths and weaknesses and path dependencies: the people you already employ. Upskilling everyone who dances around an existing product or a new venture is cheaper, slower, and usually more durable. Plus, it does not devolve into following rituals just because (e.g.) Toyota or Spotify allegedly did it.
- You need a neutral and unabashedly blunt second opinion before a big decision. Whether it’s about a technology migration, a reorganization, a new team, or a new venture: an organization can navelgaze hard enough that it convinces itself that bad ideas, no matter how well (allegedly) pursued, will deliver positive outcomes. As soon as three people are involved, there is polarity, and therefore politics and vested interests and agency issues that prevent a hard look at factual reality and a grounding of expectations. So, before the money goes in, someone who is not inside the political system can help you look at what the evidence actually says, and unveil the unstated hypotheses that will ruin your day long after you’ve committed to spending (and have spent) money.
What I bring to the table
I ran a three-month product-management audit and consulting engagement for a Zurich-headquartered multinational manufacturer of software-enabled sensor and diagnostics equipment, as consultant at Noito: observing the daily operations of a team of product experts, compiling findings with plans of action, and working the team towards a setup fit for an ambitious pipeline and a push into more digital offerings. See the project entry for more.
I also coauthored the IMD article “Agile vs. death-by-committee” with Prof. Carlos Cordonl; which is to say: I have been paid to be skeptical of change-management fashions on both sides of the aisle, and I bring that skepticism to your audit instead of importing it.
In practice, an engagement covers some or all of the following:
- The audit itself. Structured observation and interviews with the team, not just about it; producing findings tied to evidence: what the team actually does, where work stalls, what the mandate really is, and where the capability gaps are.
- The plan of action. Sequenced, owned, and cost-estimated. The deliverable here is not a fancy slide deck of twenty recommendations that every business “should” do but nobody really puts into practice, but a short list of what matters, in what order, with the trade-offs made explicit.
- Upskilling. Working with the existing people, be they product experts, product managers, product developers, technical managers, team leads, to close the specific gaps the audit found, rather than importing a training catalog.
- Improvement that outlasts me. The measurable target is that the organization runs better after I am gone. Engagements are scoped so that the last deliverable is your team not needing the next one. You and I are both interested in setting things right and getting me out of the way, because that’s the only way it works without you becoming dependent on an external service provider like OVERBRING Labs for things that are your own business to master and run.
What an engagement looks like
Audits are typically the sharpest instrument in this service: four to twelve weeks, ending with the findings, the plan, and a working session where the organization commits to the first steps, because a plan of action that was never agreed to is just a report. Upskilling and improvement work then follow at the organization’s pace, in bounded phases with their own success criteria.
If you are not sure whether you need an audit or something else, that is exactly what the first conversation decides.
Start with a conversation about what is not working.