HKSM

A systematic approach to improving delivery by locating the resource, activity, or rule that caps performance and managing work around it. In resourcing, it targets bottleneck skills or equipment to raise throughput and shorten cycle time. It focuses improvement where it matters most.

Key Points

• At any moment, one dominant constraint governs overall throughput and flow.
• Constraints can be physical (equipment), human (skills, availability), process (policies, approvals), or external (vendors, compliance).
• Improving non-constraints rarely improves system performance; protect and optimize the constraint first.
• Use flow metrics (throughput, cycle time, queue length, WIP) to see where work stalls.
• Expect the constraint to shift after improvements; re-check regularly.
• Buffers and WIP limits help stabilize flow and shield the constraint from variability.

Purpose of Analysis

• Spot the resource or rule that is throttling delivery so staffing and sequencing decisions target the real lever.
• Reduce queues and handoff delays around scarce skills or equipment.
• Guide short-term reallocations, cross-training, or supplier actions that unlock schedule gains.
• Provide objective evidence for change requests or management escalation tied to flow impact.

Method Steps

• Identify: Use data and observation to locate the step or resource with persistent backlog or longest queue.
• Exploit: Make the constraint as effective as possible without major investment (clear priorities, remove interruptions, standardize work, ensure readiness).
• Subordinate: Align non-constraint work to support the constraint (set WIP limits, sequence work to its pace, avoid starving or overfeeding it).
• Elevate: Add capacity or capability if needed (hire, automate, cross-train, add vendors, invest in tools).
• Repeat: After elevating, reassess because the constraint often moves elsewhere.

Inputs Needed

• Resource calendars, assignments, and utilization reports.
• Skills inventory and competency matrix.
• Work-in-progress counts, queue lengths, wait times, and handoff data.
• Throughput and cycle time trends by team, role, or work type.
• Backlog and dependency map highlighting where work accumulates.
• Process policies and approval steps that may limit flow.
• Schedule baseline, current schedule, and milestones at risk.
• Vendor SLAs, turnaround times, and contract constraints.

Outputs Produced

• Constraint log naming the current constraint, its type, evidence, and impact.
• Short-term action plan to exploit and subordinate around the constraint.
• Capacity change proposals to elevate the constraint, with effort, cost, and expected benefit.
• WIP limits, buffer sizes, and priority rules aligned to the constraint.
• Updated resource allocation, schedule adjustments, and change requests if required.
• Monitoring dashboard showing buffer consumption, queue trends, and throughput.

Interpretation Tips

• Look for persistent queues, not just busy people; queues reveal the true constraint.
• Protect the constraint’s time by stopping interruptions, unplanned work, and multitasking.
• Measure before and after; small cycle-time improvements at the constraint can yield outsized schedule gains.
• Do not chase 100% utilization everywhere; optimize end-to-end flow.
• If buffer consumption is erratic, expect variability to overwhelm the constraint; add stability first.

Example

A cybersecurity review step has one qualified analyst, and features queue for days, delaying releases. The team maps queues and confirms the review is the constraint.

• Exploit: Set clear intake criteria, schedule focused review blocks, remove ad hoc requests, and ensure complete packages arrive ready.
• Subordinate: Limit upstream WIP, sequence work so high-value features hit the review at the right cadence, and pre-check artifacts.
• Elevate: Cross-train a developer for basic checks and contract a part-time external reviewer for peaks.
• Repeat: After improvements, test environment access becomes the new constraint and the cycle continues.

Pitfalls

• Pursuing local efficiency (higher utilization) that worsens overall lead time.
• Skipping exploitation and jumping straight to costly capacity increases.
• Allowing upstream teams to overproduce, flooding the constraint.
• Ignoring policy constraints such as batching, approval cadences, or release windows.
• Assuming the constraint is permanent and failing to re-evaluate after changes.
• Not instrumenting flow, leaving decisions to opinion rather than data.

PMP Example Question

A project manager observes long queues before a specialized testing station while other teams are underutilized. What is the BEST immediate action using the theory of constraints?

1. Add more testers by submitting a change request for additional headcount.
2. Reduce upstream WIP and schedule work to match the testing station’s pace.
3. Have underutilized teams start more tasks to keep everyone busy.
4. Re-baseline the schedule to reflect the current throughput.

Correct Answer: B — Reduce upstream WIP and schedule work to match the testing station’s pace.

Explanation: First exploit and subordinate to the constraint by aligning flow and preventing overloading. Capacity increases or re-baselining may come later if needed.