Ask Canopy: Does Design Thinking Actually Work for Porto's First-Time Founders?

Ask Canopy is a weekly series where we take real questions from first-time founders — the kind being asked right now on Reddit and Quora — and answer them using insights from the Canopy community. Each week we pick a city, find the question that's keeping founders up at night, and draw on what our founders, mentors and investors have learned the hard way.

About the Author

Stewart is the co-founder of Canopy Community, and a regular host of demo nights. He's also the Chair of the Board in Residence, providing coaching and mentoring to CEOs and Founders in the community each week. In 2026, Canopy Community was recognised as one of the top European Startup Hubs by the Financial Times. You can connect with Stewart on LinkedIn at linkedin.com/in/stewartnoakes.

This Week's Question

"Does design thinking actually do anything, or is it just corporate jargon?"

Spotted on r/UXDesign, where a frustrated founder asked the question many first-time founders quietly wonder but rarely say out loud.

The Buzzword Problem

It is a fair question. Design thinking has been packaged into five-step frameworks, sold as corporate training, and blamed for everything from analysis paralysis to bad products.

But strip away the jargon and what you find is simple: talk to real people about real problems before you build anything. At Canopy, we have watched hundreds of founders succeed or fail based almost entirely on whether they did this one thing.

The Build Trap

The most common mistake first-time founders make is what we call the Build Trap. You are designing a logo. You are writing code. You are registering the company. It feels productive. But without talking to customers first, it is just innovation theatre.

Research from CB Insights shows that 42% of startups fail because there is no market need. Not because the founders were not clever. They built something nobody wanted.

The design thinking mindset exists to stop you falling into this trap.

Customer Discovery in Practice

The practical version of design thinking is not a workshop exercise. It is a conversation. And the first rule of that conversation is: do not ask anyone whether your idea is good.

Instead, ask about their life.

"Tell me about the last time you tried to solve this problem. What did you do? What got in the way?"

Questions like this reveal how painful the problem actually is — and whether anyone is trying to solve it already. At Canopy, we guide founders through this in our Ideation Programme, because twenty honest conversations are worth more than months of building.

Testing Before Building

Design thinking at the early stage is really about proving demand before committing resources. A landing page for a product that does not exist yet. A manual service that mimics what the software will eventually do. Anything that generates evidence before you write the code.

The founders at Canopy's Demo Nights who get the strongest audience response are rarely the ones with the most polished product. They are the ones who can show they have spoken to real customers and found a real pain point.

"The biggest risk isn't that your code won't work. It's that you'll build something nobody wants."

Design Thinking Is a Habit, Not a Framework

For first-time founders in Porto — or anywhere else building something from scratch — the value of design thinking is not the five steps on the poster. It is the habit of asking before assuming.

Talk to the people you are building for. Build the smallest possible thing that tests your riskiest assumption. Watch real users try to use it. Then iterate.

That habit, practised consistently, is what separates the founders who find product-market fit from the ones who run out of runway still wondering why nobody came.

Got a Question for Canopy?

If you are a first-time founder with a question you would like us to dig into for a future edition of Ask Canopy, we would love to hear from you. Send your question to [email protected].