Constraint

A constraint is a fixed limit on what the team can propose. It might be a budget, a deadline, a technology, a policy or a brand rule. Concepts have to fit inside it.

For example, SecondBank has a release freeze in Q1, so any new rewards concept must reuse the existing card component. That rule comes from the business and the release calendar, and the team has to design within it.

Why it matters

Constraints that aren't written down tend to surface late. A team spends weeks on a concept, only to learn in review that it breaks a policy, needs a platform change, or can't ship before a freeze. The work is wasted and trust takes a hit.

Naming constraints early saves that pain. Everyone knows the boundaries from the start, and concepts are shaped to fit them. It also makes it possible to ask whether a constraint is truly fixed, who set it, and when it ends, instead of treating every limit as permanent.

Write down each limit, who set it and why, whether it can be negotiated, and when it expires. Then check every concept against it.

How we write one

Every constraint is written as one sentence that names the limit and the reason for it:

Concepts must a limit because a reason.

Concepts must reuse the existing card component because of the Q1 release freeze.

Writing it this way ties every limit to a reason, which makes it easy to tell when the reason has gone away and the constraint can be lifted.

How it differs from similar ideas

  • Business intent is the direction the business wants to go. A constraint is a boundary on how the team can get there.

  • A risk is something that could go wrong. A constraint is a limit that already applies.

  • A user need comes from users and describes what they need. A constraint comes from the business, technology or policy, and limits what can be built.

  • A decision is a call the team made. A constraint is a limit the team works inside, often set by someone outside the team.

A good constraint

  • Names one specific limit

  • Gives the reason for it

  • Says who set it

  • Says whether it can be negotiated

  • Has an expiry date, or says it's permanent

  • Is checked against every concept it affects

What happens to it

  1. Identified. Someone names it, or Ray finds it in a roadmap, policy, brief or email. Constraints are an entry point into the system.

  2. Confirmed. The person or group who set it confirms the limit and whether it's negotiable.

  3. Active. It limits concepts, and every new concept is checked against it.

  4. Challenged. The team asks to relax it, with evidence that it's blocking a better concept.

  5. Lifted or expired. It ends on its expiry date or is removed by whoever set it, and linked concepts are rechecked.


For Ray

This part tells Ray how to find a constraint in an input, such as a roadmap, a release calendar, a brand guide, a compliance memo, an engineering note or a project brief, and how to store it.

How to find one

  1. Mark statements of limits. Read the input and mark every rule, deadline, budget or requirement that limits what can be proposed.

  2. Find the limit. Pull out exactly what concepts must or must not do.

  3. Find the reason. Look for why the limit exists. If no reason is given, leave it blank.

  4. Classify the type. Mark it as Budget, Timeline, Technology, Policy or Brand.

  5. Find who set it. Record the person, role or group, and whether they described it as negotiable.

  6. Find the expiry. Look for when the limit ends, such as the end of a freeze. If none is given, leave it blank.

  7. Write the sentence. Use the format: Concepts must [limit] because [reason].

  8. Fill the record, score it, link it and store it using the rules below.

Cues to look for

  • Limit language: "we can't", "must use", "no changes to", "has to ship by", "only within"

  • Release freezes, launch dates and code cutoffs on roadmaps and calendars

  • Budget caps and headcount limits in plans and emails

  • Compliance, legal and brand rules: "per policy", "brand guidelines require"

What doesn't count

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>If the statement...</p></th><th colspan="1" rowspan="1"><p>Store it as</p></th></tr><tr><td colspan="1" rowspan="1"><p>Describes what the business wants to achieve</p></td><td colspan="1" rowspan="1"><p>Business Intent</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes something that might go wrong</p></td><td colspan="1" rowspan="1"><p>Risk</p></td></tr><tr><td colspan="1" rowspan="1"><p>Records a choice the team made</p></td><td colspan="1" rowspan="1"><p>Decision</p></td></tr><tr><td colspan="1" rowspan="1"><p>Is a team preference with no one enforcing it, such as "we'd rather not touch nav"</p></td><td colspan="1" rowspan="1"><p>Leave it out, or store it as a Hunch if a belief is behind it</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes what users need</p></td><td colspan="1" rowspan="1"><p>User Need</p></td></tr></tbody></table>

The record

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>What to fill in</p></th><th colspan="1" rowspan="1"><p>Values</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>The one-sentence constraint</p></td><td colspan="1" rowspan="1"><p>Concepts must [limit] because [reason].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Type</p></td><td colspan="1" rowspan="1"><p>What kind of limit it is</p></td><td colspan="1" rowspan="1"><p>Budget, Timeline, Technology, Policy, Brand</p></td></tr><tr><td colspan="1" rowspan="1"><p>Limit</p></td><td colspan="1" rowspan="1"><p>What concepts must or must not do</p></td><td colspan="1" rowspan="1"><p>Short text</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reason</p></td><td colspan="1" rowspan="1"><p>Why the limit exists</p></td><td colspan="1" rowspan="1"><p>Short text, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Set by</p></td><td colspan="1" rowspan="1"><p>The person, role or group who set it</p></td><td colspan="1" rowspan="1"><p>Name, role or group</p></td></tr><tr><td colspan="1" rowspan="1"><p>Negotiable</p></td><td colspan="1" rowspan="1"><p>Whether it can be relaxed</p></td><td colspan="1" rowspan="1"><p>Yes, No, Unknown</p></td></tr><tr><td colspan="1" rowspan="1"><p>Expires</p></td><td colspan="1" rowspan="1"><p>When it ends</p></td><td colspan="1" rowspan="1"><p>Date, Permanent, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Concepts limited</p></td><td colspan="1" rowspan="1"><p>Concepts it applies to</p></td><td colspan="1" rowspan="1"><p>Links to Concept</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>The input and exact passage</p></td><td colspan="1" rowspan="1"><p>Link to Input</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Where it stands</p></td><td colspan="1" rowspan="1"><p>Identified, Confirmed, Active, Challenged, Lifted, Expired</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How clearly it was stated and by whom</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>

New constraints start as Identified. Only the person or group who set it can move one to Confirmed or Lifted. When the expiry date passes, Ray marks it Expired automatically.

Scoring confidence

Confidence measures how clearly the limit was stated and whether it came from someone with the authority to set it.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Level</p></th><th colspan="1" rowspan="1"><p>When to use it</p></th></tr><tr><td colspan="1" rowspan="1"><p>High</p></td><td colspan="1" rowspan="1"><p>Stated in writing by whoever owns the limit, with a reason and an expiry or Permanent</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Stated by its owner, but the reason, negotiability or expiry is missing</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Passed along secondhand, or stated by someone who doesn't own the limit</p></td></tr></tbody></table>

If any part of the record can't be filled from the source, leave it blank and lower confidence by one level.

Linking

  • Check for duplicates first. If an existing constraint names the same limit, add the new source to it instead of creating another.

  • Link to every concept it limits, and to its source input.

  • Link shared constraints. Several decisions often share one constraint. Link them all to the same record rather than copying it.

  • Note conflicts. If a concept breaks an active constraint, or two constraints can't both be met, link them as conflicting.

  • Note replacements. When a constraint is extended or changed, store the new version, link it as a replacement, and recheck linked concepts.

When to store and when to ask

  • Store automatically when confidence is high.

  • Add to the review digest when confidence is medium or low, when an active concept breaks it, or when it conflicts with another constraint.

When to flag

  • An active concept breaks a constraint

  • A constraint has no owner recorded

  • A constraint has expired but concepts are still being shaped around it

  • A constraint marked negotiable is blocking a concept that tested well

  • Two constraints can't both be met

Worked example

Input: a message from the engineering manager in the rewards project channel.

"Heads up for anyone sketching rewards ideas: we're in release freeze for all of Q1. No new components until April 1. If it can be built with the existing card component, we can ship it. That's not up for debate this quarter."

What Ray finds:

  • "If it can be built with the existing card component" is the limit: concepts must reuse the existing card component.

  • "Release freeze for all of Q1" is the reason, and the type is Technology, driven by a Timeline.

  • "No new components until April 1" gives the expiry date.

  • "Not up for debate this quarter" means it isn't negotiable.

Stored record:

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>Concepts must reuse the existing card component because of the Q1 release freeze.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Type</p></td><td colspan="1" rowspan="1"><p>Technology</p></td></tr><tr><td colspan="1" rowspan="1"><p>Limit</p></td><td colspan="1" rowspan="1"><p>Reuse the existing card component; no new components</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reason</p></td><td colspan="1" rowspan="1"><p>Q1 release freeze</p></td></tr><tr><td colspan="1" rowspan="1"><p>Set by</p></td><td colspan="1" rowspan="1"><p>Engineering manager, rewards platform</p></td></tr><tr><td colspan="1" rowspan="1"><p>Negotiable</p></td><td colspan="1" rowspan="1"><p>No</p></td></tr><tr><td colspan="1" rowspan="1"><p>Expires</p></td><td colspan="1" rowspan="1"><p>April 1, 2027</p></td></tr><tr><td colspan="1" rowspan="1"><p>Concepts limited</p></td><td colspan="1" rowspan="1"><p>Points progress bar</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Project channel message, October 2026</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Confirmed</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: stated by the owner, with reason, expiry and negotiability</p></td></tr></tbody></table>

Next step: stored automatically, and the points progress bar concept is checked against it. It fits, because the bar can be built inside the existing card component.

Edge cases

  • Two types at once. A freeze is both a timeline and a technology limit. Pick the type that best describes what concepts must do, and note the other in the reason.

  • Preference dressed as a rule. "We never use progress bars" with no owner or policy behind it stays at low confidence until someone with authority confirms it.

  • One constraint, many decisions. A brand rule may limit every concept in a quarter. Store it once and link it to each concept and decision.

  • The constraint lifts. Don't delete it. Mark it Lifted or Expired and flag concepts that were shaped around it, since better options may now be open.

Identify where decision quality breaks down

The Glare Design Assessment helps teams spot weak validation, stakeholder friction, alignment gaps, and assumptions that scale without measurable learning—so you have a clearer starting point for improvement.

About 5 minutes · Team-based · Diagnostic snapshot you can act on

Take the Design Assessment