constraint

To determine if a project constraint is real or just an assumption, apply constraint hardness testing. This diagnostic process classifies stated limits as genuinely fixed, technically changeable, organizationally soft, or merely assumed habits blocking progress.

To reduce project scope to minimum viable requirements, separate what you want from what you actually need. This scope reduction workflow helps identify the simplest version of a plan that still satisfies the real operational requirement.

The best way to design around a hard technical limit is constraint-to-design conversion or rule inversion. This method reframes the limit as a requirement, identifying solution directions and workarounds that become uniquely possible because of that constraint.

To map workarounds for fixed operational limits, use workaround mapping. This technique maps viable paths that achieve the same goal without removing the constraint, while estimating the effort and value for each alternative route.

When product strategy is blocked by a hard constraint, diagnose the limit's true hardness first. Then route the strategy through scope reduction, rule inversion, or workaround mapping to bypass the obstacle and confirm the chosen direction with user intent.