22 Claude Skills for Operations Efficiency

Use these first. Every improvement program needs a factual baseline before selecting levers. These skills build the current-state view: performance, cost, capacity, and waste, before any solution is chosen.

Built for the person about to start an efficiency program who does not yet have a numbers-based view of the current state, and knows that whichever lever gets picked first will be judged against a baseline nobody has written down yet.

It refuses to jump to a lever before the fact base exists: a five-dimension health-check scorecard, a lead-time-versus-processing-time gap from the value stream map, a utilization profile from the capacity model, and a driver-based cost waterfall. None of the four skills recommends a fix; they hand back the numbers a fix will later be judged against, which is what stops a program from spending its first quarter defending a lever nobody can prove was the right one.

Use these to identify the specific blockers and waste sources once the baseline is clear. Theory of Constraints, Lean eight wastes, root cause analysis, and statistical process control.

Built for the team that has a baseline and now needs to name the actual binding constraint, the one that keeps recreating itself every time a different step gets fixed, rather than the step that generates the most complaints in a status meeting.

Theory of Constraints logic runs underneath the Bottleneck Diagnostic: find the binding constraint, exploit it before adding capacity anywhere else, and forecast where the next one will appear once this one is fixed. The Waste Audit applies the Lean TIMWOODS categories to build a priority matrix instead of a grab-bag of complaints, Root Cause Analysis forces a 5-Whys chain through to a corrective action rather than stopping at the first plausible cause, and the Variation Profiler separates a metric that is genuinely out of control from ordinary noise a team is reacting to for no reason.

Use these once the wastes and constraints are identified. These skills design the future state, build the improvement program, identify automation opportunities, and lock in gains with standard work.

Built for the team that knows the constraint and the waste and now has to design the fix, sequence it against every other improvement idea competing for the same budget, and write it down so it survives staff turnover.

Process Redesign takes the current-state map and the Domain 2 findings and produces a future-state design with a performance estimate and a named transition risk, not just a diagram. The Lean Initiative Builder scores every competing idea against the same criteria and phases them into a program, because most organizations have more improvement ideas than budget and no consistent way to rank them. Automation Opportunity Screen separates a genuine automation candidate from a task that only looks repetitive, and Standard Work Builder writes the method down with error-proofing and version control so the gain does not evaporate the day the person who designed it changes roles.

Use these when the inefficiency is structural: spans and layers that are too narrow or too deep, functions duplicated across divisions, activities performed in-house that should not be, or a strategy that needs translating into how work actually gets done.

Built for the leader whose problem is not a single broken process but the organization built around it: too many layers between a decision and the person who executes it, the same function run three different ways in three divisions, or a strategy that was agreed on a slide and never translated into who does what.

Org Efficiency Review flags spans that are too narrow to justify a layer of management and recommends where to remove one. Shared Services Design scopes a consolidation across divisions that each run their own finance, HR, or IT function today, and builds the target model and the migration plan rather than just the case for change. Make vs. Buy Analyzer builds the total cost comparison an outsourcing or insourcing decision actually needs, including the strategic fit question a pure cost comparison misses. Operating Model Redesign is the broadest of the four: it takes a chosen strategy and produces a five-dimension target model with the delta from where the organization sits today.

Use these to build the management infrastructure that makes improvements visible, accountable, and sustainable. A redesigned process without governance regresses within months.

Built for the person who owns the scorecard after a program has already delivered a result, and who has watched a good process quietly drift back to the old way of working once nobody was measuring it weekly anymore.

KPI Dashboard Builder retires metrics that do not drive a decision and builds a three-tier hierarchy with named owners and a review cadence, instead of the twenty-metric dashboard nobody actually reads. SLA Architect writes a bilateral agreement between an internal service function and the teams it serves, with real breach consequences rather than a target nobody enforces. Continuous Improvement Governance is the one that most engagements skip entirely: it sets a daily, weekly, and monthly cadence, assigns roles, and builds the visual management and A3 pattern that keeps a gain from reverting once the consultants or the project team have moved on.

Use these to manage the human side of the transformation. Most operations programs fail not because the technical design was wrong but because implementation ignored readiness, resistance, and communication.

Built for the person who has a technically sound redesign and a launch date, and knows from the last program that the reason it might still fail has nothing to do with the process diagram and everything to do with who was never told, and why, before it changed their job.

Change Readiness Assessor runs an ADKAR assessment by stakeholder group rather than treating the organization as one audience, and turns resistance into a named intervention plan instead of a general communications push. Stakeholder Comms Plan builds the message matrix and channel strategy for groups that need different information at different times, with a feedback loop rather than a one-way announcement. Benefits Tracking closes the loop that most programs never close: a benefits register, a milestone schedule, and a program ROI report that lets leadership see whether the value that justified the program is actually materializing.