In every planning session, there is a set of things the team treats as fixed. The budget. The headcount. The platform. The partner relationship. The geographic scope. The org structure.
Some of these are genuinely fixed. The budget is approved and cannot change before the next cycle. The platform is contractually locked for 18 months.
But many of them are not fixed at all. They are decisions from a previous cycle that hardened into constraints because nobody put them back on the table. The headcount cap was set during a downturn that ended a year ago. The geographic focus was chosen when the product wasn't ready for a broader market. The org structure was drawn around a product line that has since been merged.
These are assumed constraints: limits that feel structural but are actually choices that nobody has revisited.
Why they persist
Assumed constraints survive because they are never discussed as decisions. They enter the room as context, not as agenda items. "We have 12 engineers" is presented as a fact, not as "we decided not to request additional headcount because last time we asked it was denied, and we haven't asked again since."
They also survive because re-examining them is politically expensive. Questioning a constraint often means questioning the person who set it. If the VP of Sales defined the territory split two years ago, reopening it feels like challenging their judgment, even if the market has changed. So the constraint stays, and the team plans around it.
The result is that goals get set against a map of the world that is partly real and partly inherited. The team treats the inherited parts with the same weight as the real parts, and nobody notices the difference because both are presented the same way: as givens.
How they distort execution
Assumed constraints don't just limit ambition. They distort the entire goal structure.
When a team believes it cannot hire, it sets KPI targets that fit the current headcount - even if the actual bottleneck is not people but the assumption about people. When a team believes the partner channel is the only go-to-market motion, it builds goals around partner-sourced revenue - even if direct sales would outperform, and the partner-first decision was made before the product had the brand strength to sell directly.
The most dangerous form is the constraint that shapes what initiatives get funded. If leadership assumes a certain cost structure is immovable, it will never invest in the work that could change that cost structure. The constraint becomes self-fulfilling.
This is why intentional goal setting has to start with a constraint audit. Not "what are our goals?" but "what are we treating as fixed, and is it actually fixed?"
Separating real from assumed
A simple test: for each constraint, ask when it was last validated. If the answer is "it's always been that way" or "I think it was decided before I joined," it is a candidate for re-examination.
A harder test: ask what would change if the constraint were removed. If removing a headcount cap would not change any goals because the team has other bottlenecks, the constraint is real but irrelevant. If removing it would unlock an entirely different strategy, the constraint is load-bearing and needs to be confirmed as intentional, not inherited.
The planning session should produce two lists: constraints we have verified and accepted, and constraints we have identified as assumed and will either re-validate or remove. The second list is where the strategic upside lives.
The Vindaris view
When goals and KPIs are mapped in the Work Graph alongside the projects and resources supporting them, execution risk surfaces wherever effort is misaligned with targets. Often the root cause is not poor execution but a constraint that was never real. Vindaris makes the gap between planned capacity and actual investment visible, so teams can ask whether the plan's assumptions still hold - before the quarterly review reveals that they don't.