Smoke Test Team: Support is the binding constraint
Created May 23, 2026, 9:52 AM
Identify the top blocker each team member named. Pick the one with the lowest cost to remove. Remove it this week, publicly. Repeat.
This is a scaffold plan — generic intervention steps keyed off the recommended action. The science-backed engine that replaces these steps lives in performance-science-library; it'll fill the same slots once it ships.
Share this insight with the Smoke Test Team lead. Ask: does the binding-constraint pick (support) match what they're seeing on the ground? Capture their reaction before committing resource.
One name. Owner is responsible for sequencing the steps below and for the 30-day follow-up review. Avoid committee ownership at this stage.
Translate the recommended action into the smallest reversible step you can take this week. Resist scoping it as a quarterly program — the point is to test the diagnosis, not to commit to a plan.
Re-run the relevant subconstruct on a narrow item set. If the score moved, you have evidence the binding constraint is what you thought. If not, revisit the diagnosis before scaling the intervention.
Block the calendar now. At the review, mark the insight Reviewed (if the binding constraint resolved), Follow-up-needed (if it moved but isn't closed), or Closed (if the binding constraint shifted to another dimension).