logic-constraint-mapping

Constraint mapping distinguishes hard limits from soft preferences by inventorying stated and implied requirements, reassessing their hardness based on real consequences, and summarizing degrees of freedom to clarify negotiability.

Uncover hidden constraints by surfacing load-bearing blockers like approvals, irreversibility, dependencies, and cultural or political factors that act as unstated walls preventing your process from moving forward.

Resolve constraint conflicts by explicitly mapping incompatible requirements to name what must be traded, identifying who owns the decision, and documenting the trade-offs to establish final degrees of freedom.

You need constraint mapping before committing to an approach when a process is stalled by unexpected walls, when negotiability is unclear, or when you need ground-truth boundaries to prevent optimizing for assumptions that aren't fixed.

Separate hard limits from soft preferences by performing a stepwise inventory of stated and implied constraints, then reassessing the hardness of each limit based on the real consequences of violating it.

Projects optimize for false assumptions because hidden constraints and soft preferences are treated as non-negotiable limits; constraint mapping exposes the true negotiability landscape to prevent wasted effort.