top of page

FIELD NOTE | 

July 1, 2026

A No Can Be a Design Decision

Not every opportunity worth considering is a commitment worth making.

I've walked away from vendors I could have bought from and relationships I probably could have made work.

Sometimes the product was good. Sometimes the economics were defensible. Sometimes saying yes would have been easier in the short term.

There wasn't necessarily a dramatic red flag.

More often, I noticed a mismatch in how we expected the relationship to work.

What transparency meant. How problems would be handled. Whether pressure was part of the sales process. Whether the vendor understood the system surrounding the purchase or was interested only in completing the transaction.

None of those things necessarily made the vendor bad.

They made me question whether we were right for each other.

Business language tends to treat a no as lost value. A deal that didn't close. An opportunity that didn't convert. Revenue that could have been captured.

I think that's an incomplete way to understand a decision.

Every yes creates a future

A contract doesn't end when it's signed.

It creates meetings, integrations, invoices, dependencies, expectations, switching costs, and future decisions.

The vendor becomes part of the operating environment.

So when I'm evaluating a purchase, I'm not only deciding whether I want the product.

I'm deciding whether I want the relationship that comes with it.

How much attention will this require? What happens when something breaks? How do we resolve a disagreement? What dependencies are we creating? What will it cost to change our minds?

Those questions matter even when the price is reasonable and the product works.

The same is true of clients, partnerships, hires, and opportunities.

Every yes commits some portion of the future.

Not necessarily forever, but long enough that the consequences deserve consideration.

Alignment becomes visible when something goes wrong

Values alignment can sound abstract until there's a problem.

Then it becomes practical.

How quickly does someone tell you bad news? Can they acknowledge a mistake without turning the conversation into a negotiation over blame? Are they willing to explain a constraint that might cost them the sale? Can both sides say something isn't working before it becomes expensive to address?

I'm less interested in whether a partner uses the same language I do than whether our operating assumptions can coexist.

And I pay attention to how we treat one another during evaluation.

Sales is often the first opportunity to observe how a future relationship might function.

A vendor who avoids direct questions may be revealing something about how information moves through the company. A buyer who withholds important constraints may be creating conditions for a difficult implementation.

Or either party may simply be having a bad day.

One interaction isn't necessarily a pattern.

But the evaluation process gives both sides information that doesn't appear in the contract.

Can we tell each other the truth early enough to do something useful with it?

Can we disagree without making the disagreement personal?

Can we recognize when the fit isn't right?

Those things matter to me because the relationship will eventually encounter circumstances neither side anticipated.

I want to know something about how we'll behave when it does.

A clean no can protect a future yes

Some of the best professional relationships I've had included a moment when one of us said no.

The no clarified the boundary of the work.

It prevented resentment from becoming part of an agreement. It allowed us to recognize that a particular opportunity wasn't right without deciding that the entire relationship had failed.

Sometimes a different opportunity emerged later.

Sometimes it didn't.

I don't think a no needs to produce a better opportunity in order to have been the right decision.

That's part of what I've had to reconsider.

When every opportunity must become revenue, every available hour must become utilization, and every promising relationship must become a contract, there's very little room left for selection.

And selection is part of design.

The things we choose not to build, buy, accept, or pursue shape the systems we eventually have.

A no can preserve money, time, attention, credibility, and capacity.

It can also preserve the possibility of doing something different with those resources.

I'm not interested in saying no simply because something is difficult. Good relationships require work, and meaningful opportunities rarely arrive without complications.

But I am interested in distinguishing the difficulty that belongs to worthwhile work from the difficulty created by a commitment that never really fit.

Sometimes the right decision is to negotiate.

Sometimes it's to redesign the relationship.

And sometimes it's to decline.

A no isn't necessarily a failure to create value. Sometimes it's how we avoid building a future we don't want to operate.

bottom of page