SECTION 02 | CONSTRAINT ARCHITECTURE
Constraints define the possible.
A constraint is anything that limits possible action. In a single SSO, constraints are evaluated inside the opportunity. Across multiple SSOs, constraints may interact and create tradeoffs.
Inside one objective, constraints are isolated to that objective.
The question is practical: what prevents advancement, what can be changed, and what must be accepted?
SSO
↓
CONSTRAINTS
↓
ADVANCE / HOLD / EXIT
FinancialBudget, ROI threshold, capital availability, payback, cost exposure.
TimingDeadlines, urgency, implementation window, fiscal calendar.
ResourcePeople, capacity, attention, tools, operational bandwidth.
AuthorityDecision rights, approval path, sponsorship, procurement structure.
RiskBusiness risk, technical risk, adoption risk, reputation risk.
TechnicalIntegration, security, reliability, compliance, architecture fit.
Opportunity cost becomes relevant when multiple SSOs compete for the same finite resources.
If there are multiple Sales Objectives under consideration, the pursuit of one may compete with the pursuit of another. This introduces prioritization, tradeoffs, and portfolio-level economics.