The Constraint Trick

Here's something counterintuitive: the best way to get better advice is to limit what that advice can be.

Most people approach decision-making tools the way they approach Google — type in a broad question, hope for a useful answer. But the difference between generic advice and genuinely useful guidance almost always comes down to one thing: constraints.

Constraints aren't limitations. They're the edges that give your decision its shape.

The same question, two ways

Let's look at an example. Say you're trying to decide on a go-to-market strategy.

Without constraints:

> "What's the best go-to-market strategy for my B2B SaaS product?"

You'll get a perfectly reasonable answer. Content marketing. Outbound sales. Product-led growth. Partnership channels. A little bit about each one, a recommendation to "consider your resources and target market," and a nudge to test and iterate.

It's not wrong. It's just useless. You already knew all of that.

With constraints:

> "What's the best go-to-market strategy for my B2B SaaS product? Budget is $3K/month. Team is just me and a part-time contractor. Sales cycle needs to be under 14 days. I can't do outbound — I've tested it for 3 months with zero results. Target is mid-market HR teams, 200-1000 employees."

Now the expert panel has something to work with. The finance expert immediately eliminates strategies that don't fit the budget. The growth strategist focuses on channels that work for mid-market without a sales team. The operations persona flags that the contractor's time is the real bottleneck and recommends prioritizing async channels. There's a real debate about whether content marketing or community-led growth is the better bet given the constraints.

The advice is specific. Actionable. Tailored. And it happened because you told the system what it couldn't do.

The 7 types of constraints

Through thousands of meetings, we've identified seven categories of constraints that consistently produce sharper advice:

1. Budget constraints. Not just "we don't have much money" — specific numbers. "$5K/month for the next 6 months" gives your expert panel something concrete to optimize around.

2. Time constraints. When does this decision need to produce results? "We need to see traction in 90 days" is a fundamentally different problem than "we're building for the next 2 years."

3. Team constraints. Who's available to execute? What skills do they have? A strategy that requires a senior data engineer is worthless if you don't have one and can't hire one.

4. Technical constraints. What does your current stack support? What integrations are non-negotiable? What technical debt will block certain paths?

5. Market constraints. Regulatory requirements. Competitive dynamics. Customer expectations that can't be ignored. Geographic limitations.

6. Values constraints. Things you won't do regardless of ROI. Privacy commitments. Sustainability requirements. Cultural non-negotiables. These matter more than people admit.

7. Historical constraints. What you've already tried and what happened. This is the most underused constraint type, and often the most valuable. "We tried outbound for 3 months and it didn't work" eliminates an entire category of recommendations.

You don't need all seven for every meeting. But the more you provide, the more specific your expert panel can be.

How Marcus uses constraints to run pricing experiments

Marcus leads a 12-person growth-stage startup. When he first started using Board of One for pricing decisions, he asked broad questions: "How should we price our product?" The advice was textbook — value-based pricing, competitive benchmarking, willingness-to-pay surveys.

Then he started adding constraints:

• Current MRR: $47K
• Can't raise prices on existing customers for 6 months (contractual)
• Need to increase ARPU by 20% within one quarter
• Engineering can ship one pricing change per sprint (2 weeks)
• Primary competitor just dropped their price by 15%

The meeting that followed was completely different. His expert panel debated whether to introduce a new tier (low engineering effort, uncertain uptake) or add usage-based pricing to the existing plan (higher engineering effort, more predictable revenue). The finance expert modeled both scenarios against the ARPU target. The strategy expert argued that responding to the competitor's price drop with a premium tier was a better signal than matching.

Same topic. Radically different — and more useful — output. The constraints did the work.

The over-constraining trap

There's a failure mode on the other end of the spectrum: adding so many constraints that no viable solution exists.

Priya, a middle manager at a large enterprise, once ran a meeting about reorganizing her team's workflow with these constraints: no budget for new tools, no headcount changes, no changes to the reporting structure, no impact on current project timelines, and approval needed from three different VPs.

Her expert panel essentially told her: there's no meaningful change possible within these boundaries. And that was actually the most useful output — it surfaced that the real problem wasn't the workflow, it was the organizational constraints preventing any change at all.

If your expert panel keeps circling back to "this isn't feasible given the constraints," that's a signal. You're either over-constraining, or the constraints themselves are the problem you need to solve.

The under-constraining trap

This one's easier to spot but harder to fix, because it feels productive. You ask a question, you get a long, articulate answer, and you nod along thinking "yes, that makes sense."

But then you try to act on it and realize the advice could apply to basically any company in your category. There's nothing specific to your situation, your resources, or your moment in time.

Sarah, a solo pre-seed founder, noticed this pattern in her first few meetings. She was asking things like "How should I think about product-market fit?" and getting answers that were smart but generic. When she started adding her specific constraints — bootstrap budget, technical skills but no design skills, a niche audience she already had access to — the advice shifted from "general frameworks" to "here's what you specifically should do next week."

The test is simple: could this advice apply to 100 other companies? If yes, you're under-constraining.

Constraints as a thinking tool

Here's the deeper point: the act of defining constraints is itself a form of decision-making.

When you sit down to list your constraints before a Board of One meeting, you're forced to articulate things you might otherwise leave vague. How much can you actually spend? What's the real deadline, not the aspirational one? What has your team actually demonstrated they can execute?

Most people skip this step when making decisions on their own. They carry a fuzzy sense of their constraints without ever writing them down. And fuzzy constraints produce fuzzy thinking.

Board of One makes constraint-setting a natural part of the process. You're not filling out a form for the sake of it — you're giving your expert panel the edges they need to give you advice worth following.

The trick isn't complicated. Tell the system what you can't do, what you won't do, and what you've already tried. Then watch the advice get specific.

---

Want to master constraints? Read our Constraints help article for a detailed walkthrough of each constraint type with examples.