Protect the Security Review Constraint
Verify the current constraint and align exploit, subordinate and elevation actions to completed proposals.
20 minutes
Scenario
BrightBid uses AI to draft enterprise proposals. Draft output tripled, but signed proposals and customer lead time have not improved.
- Your role
- Commercial operations lead
- Method
- Theory of Constraints
Evidence pack
Demand
80 qualified proposal requests arrive monthly.
Drafting
AI-assisted capacity is 120 proposals per month.
Solution review
Capacity is 60 proposals per month.
Security review
One specialist can complete 45 proposals per month.
Input quality
30% reach security without required architecture evidence.
Release
Half the monthly work is released during the final six business days.
Downstream
Legal and pricing have capacity for 70 proposals per month.
Outcome
42 acceptable proposals are completed monthly; 90th-percentile lead time is 18 days.
Constraints
- Security approval cannot be removed from enterprise proposals.
- No new full-time hire is available this quarter.
- AI may assemble cited evidence but may not approve a security claim.
Case steps
Work through each prompt using the evidence pack. Answers and rubric weights stay protected in the interactive flow.
Define useful throughput and identify the most plausible current constraint with evidence.
Define two exploit actions that protect existing security-review capacity.
Define release, priority and upstream preparation rules that subordinate the rest of the flow.
Propose a bounded elevation test and define system measures plus the next constraint review.