Operational Systems Audit

A CEO of a 50-person manufacturing company is three months from private equity due diligence. The PE firm's preliminary questions exposed gaps in his operational documentation. He can describe production capacity and quality metrics but struggled to answer questions about supplier dependencies and business continuity planning.

Frame this as due diligence preparation, not self-assessment. 'PE firms will ask about operational resilience in detail. This audit maps what you can document versus what you know informally.' Expect resistance to the contingency row - many manufacturing leaders see business continuity planning as pessimistic rather than prudent. Position it as investor confidence, not disaster planning.

Production and delivery rows fill quickly with technical detail. Legal, payment terms, and contingency rows get surface-level responses or 'handled by our accountant' deflections. If the client writes 'good' or 'covered' without specifics, they're working from assumptions, not knowledge. Time spent per row is diagnostic.

Start with the rows that took longest to complete. 'Walk me through what you wrote for suppliers.' Then ask: 'What would a PE firm want to know about this system that isn't captured here?' The gap between what they documented and what investors will probe reveals the coaching work.

The owner of a consulting firm is dealing with the sudden departure of their operations manager, who handled client delivery, vendor relationships, and administrative systems. The owner realizes they don't know the details of how several critical systems actually work and is scrambling to maintain service quality.

Position this as a knowledge recovery exercise, not a performance review. 'Before you hire a replacement, let's map what systems need immediate attention versus what can wait.' Clients in crisis mode often want to rush to solutions. The audit forces them to slow down and assess what they actually know versus what they assumed the departed employee was handling.

The client will want to skip rows where the former employee had primary responsibility. That avoidance is exactly where the vulnerabilities are. Look for phrases like 'Sarah handled that' or 'I need to check the files.' If multiple rows reference the same departed person, the dependency pattern is broader than the client initially realized.

Start with the rows that reference the former employee. 'You mentioned Sarah handled suppliers. What do you know about those relationships right now?' Then move to: 'Which of these systems could fail in the next 30 days if you don't act?' This creates a triage list, not just an inventory.

A SaaS startup founder is preparing for rapid hiring after a Series A funding round. The company has grown organically with informal processes, and the founder knows they need to systematize operations before doubling headcount. They're concerned about maintaining culture and quality during fast growth.

Frame this as a scaling readiness check, not a process audit. 'Informal systems that work at 15 people break at 40. This audit identifies which systems need formalization before you hire.' Expect the founder to focus heavily on production systems (their comfort zone) and rush through HR and administrative functions.

The founder will describe production and delivery systems in detail but struggle with HR, legal, and payment systems that have been handled ad hoc. Look for responses like 'we just handle that as it comes up' or 'everyone knows how we do things.' These informal approaches don't scale and will create bottlenecks during rapid growth.

Start with the systems that are currently informal or person-dependent. 'You wrote that HR is handled case-by-case. What happens when you're hiring 5 people per month?' Then ask: 'Which systems need documentation before your next hire, and which can wait until you hit 25 people?' This creates a scaling timeline.

A second-generation family member is transitioning into the COO role of a retail business their parent built. They've worked in sales and marketing but never managed operations, suppliers, or administrative systems. The parent is stepping back gradually but hasn't documented how key systems actually work.

Position this as a knowledge transfer tool, not a competency assessment. 'Before your parent steps back further, let's map what operational knowledge needs to be transferred.' The successor may feel defensive about not knowing systems they haven't been responsible for. Frame gaps as natural rather than deficient.

The successor will be confident about customer-facing systems but vague about back-office operations, supplier relationships, and financial processes. They may write 'Dad handles that' or 'I think we...' for multiple rows. The uncertainty pattern shows where knowledge transfer is most urgent.

Start with the rows where the parent has primary responsibility. 'Walk me through what you wrote for suppliers. What would you need to know to manage those relationships?' Then ask: 'Which systems would you be comfortable taking over next month, and which need more knowledge transfer time?'