Chain Restaurant Executive Self-Audit

Problem it solves

Chain restaurant executives often mistake growth in store count, regional expansion, or one hit product for operational health. The harder problem is diagnosing distorted information, organizational inertia, path dependence, and management blind spots. This skill is aimed at CEO, COO, operations heads, franchise heads, supply chain leads, and similar roles. It frames self-audit around concrete questions: whether same-store trends are truly healthy, whether talent is developed internally or mainly hired, whether customer complaints point to policy rather than single-store execution, and whether expansion pace is supported by data. Rather than giving generic management advice, it breaks self-audit into verifiable questions, a diagnostic structure, and actions that can be completed this week.

How it works

The skill works as a diagnostic workflow:
- Confirm role and scope: identify business format, role, store scale, direct/franchise mix, and current pain points before giving advice.
- Select two or three dimensions: choose from operational efficiency, organizational health, customer perception, innovation capability, and financial discipline, then surface role-specific blind spots.
- Output structured diagnosis: each dimension is analyzed through current-state checks, common blind spots, feedback mechanisms, and action recommendations, grounded in measurable signals such as table turnover, sales per square meter, labor productivity, NPS, and manager retention.
- Use templates and cases: as needed, it can draw on references/self-audit-framework.md, references/quarterly-review-template.md, and other resources to turn findings into checklists, review templates, or executable actions.

Boundaries and cautions

It is best used for internal retrospectives, management diagnosis, and decision self-checks, not as a substitute for formal audits, financial due diligence, or legal compliance review. Output quality depends on the accuracy and specificity of user-provided information. Vague input leads to assumptions and follow-up questions. Users should avoid turning diagnosis into blame-shifting or trying to fix every issue at once. A safer pattern is to start with one or two key dimensions, define a verifiable action for this week, and expand gradually.