Not Every Project Should Be Built

I turned down three projects last month.

Good money. Interesting technical problems.

Wrong fit.

After 28 years in tech, here's the pattern I've learned:

Most projects don't fail because they can't be built.

They fail because they shouldn't have been built.

The Real Failure Isn't Technical

The projects I passed on had a lot in common:

"Growth hacking" that felt manipulative
AI features that added noise, not value
Technical roadmaps no one could clearly explain

Plenty of "Can we build this?"

Almost no "Should we build this?"

That's the difference.

Technical capability is rarely the bottleneck anymore.

Judgment is.

The Expensive Mistake

When teams focus only on feasibility, they create:

Feature-heavy products no one uses
AI layers that confuse customers
Short-term spikes that damage long-term trust

It's easy to get excited about what's possible.

It's harder to slow down and ask what's meaningful.

But that pause that discipline is where leverage lives.

What I Say Yes To Now

Today, I work with founders who ask better questions:

Will this actually help people?
Are we scaling responsibly?
Are we solving a real problem or just shipping features?

The companies I say yes to are building:

Healthcare technology that improves patient outcomes
Climate technology that reduces measurable emissions
AI systems that amplify humans instead of replacing them

Not because it's trendy.

Because it's durable.

Intentional > Fast

There's a myth that purpose-driven work is slower or less profitable.

It isn't.

In fact, it's often more profitable long-term because:

Trust compounds
Customers stay longer
Talent retention improves
Regulatory risk decreases

Intentional companies make clearer decisions.

Clear decisions build stronger architecture.

Strong architecture scales.

The Filter That Changes Everything

Before committing to any major initiative, ask:

What real problem are we solving?
Who benefits and how?
What happens if we don't build this?
Would we still build it if no one praised us for it?

If those answers are fuzzy, the roadmap probably is too.

This isn't about being idealistic.

It's about building companies that last.

Because the market eventually punishes noise.

It rewards substance.

Serious Leadership for Meaningful Work

I no longer work on projects just because they're technically interesting.

I work on projects that matter.

If you're building something meaningful and want strategic guidance from someone who's seen every phase of the journey.

👉 Schedule a call

Purpose-driven tech deserves serious leadership.