Ask Canopy: Do Faro's First-Time Founders Actually Need Design Thinking?

Ask Canopy is a weekly series where we answer real questions from first-time founders — questions spotted in online communities, written by people building startups right now. Each week we dig into Canopy's own content library to find the most relevant and practical insights we can offer. This week's question comes from the startup founder community on Reddit.

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

"Design thinking might be the most underrated skill to learn in 2026. The capacity to empathise, quickly create prototypes, and refine ideas seems to outweigh any specific tool or methodology. It appears that adopting a designer's mindset is becoming a vital asset in business, technology, and even personal endeavours. What are your thoughts on this?"

Spotted on r/startups, December 2025 — 159 votes and 62 comments from founders weighing in with everything from strong agreement to healthy scepticism.

What Design Thinking Actually Means for a First-Time Founder

Design thinking is often taught as a five-step framework: empathise, define, ideate, prototype, test. In a classroom that sounds clean. In a startup, it's rarely that tidy.

In Canopy's own HOWTO community sessions, the founders and operators who join us talk about something that maps very closely to design thinking — they just call it the "beautiful chaos" of the early stage. The idea is that you're not designing a perfect product from day one. You're iterating your way toward one, led by user reality rather than your own assumptions.

Self-Awareness Is the Starting Point

One of the recurring themes from our HOWTO series is that the best founders begin with an honest audit of themselves — not the product.

"You have to be very self-aware and very open in two aspects: who you are and what you have, but also very aware of who you are not."

That is design thinking language. It's the empathise phase applied inward — understanding the gaps before you start solving problems for others. First-time founders who skip this step often find themselves building something technically impressive that nobody needs.

Build for the Problem, Not the Product

A consistent message across the Canopy community is to stay close to the problem before falling in love with the solution. The design thinking mindset reinforces this directly.

Founders in our sessions talk about going into what one called "survival mode" during the first months — wearing every hat, running on instinct, shipping something imperfect. That's not the absence of good process. That is good process, when it is anchored in constant user feedback.

If you are building your MVP right now, the design thinking question to ask is not "is this well designed?" but "does this solve a real problem for a real person, and have I watched them try to use it?"

The Prototype Mindset

Design thinking's big contribution to early-stage founders is giving permission to be wrong fast. You do not need a polished product to start learning. A rough prototype shared with five honest people will teach you more in a week than six months of building in isolation.

In Faro, as in every city where Canopy operates, the founders who move fastest are not the ones with the best code or the cleanest UI. They are the ones who stay closest to their users and iterate without ego.

Got a Question for Canopy?

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