While the Wise Man Was Looking for a Bridge, the Crazy One Had Already Crossed

There's an atasözü (proverb) in Türkiye: "Akıllı köprü arayana kadar, deli köprüyü geçermiş"  while the wise man searches for the perfect bridge, the crazy one has already crossed the river.

Sometimes you need to be the crazy one.

That's not easy to say. Throughout our careers, we've been taught to analyse, plan, calculate risks, get approvals. We were taught to be "wise." And we did we became so wise that sometimes we couldn't move at all.

But looking back, the most critical turning points in my life and career all came at the same moment: when I said "I'm not ready, but I'm doing it anyway." When I didn't fully know, didn't fully see, wasn't fully sure but trusted my gut and took the step.

In those moments, I was the crazy one. And that craziness carried me to the right place every single time.

Most people read this proverb wrong. They pity the crazy one and admire the wise man. But here's the real question: Who crossed the bridge? The crazy one. Who's on the other side? The crazy one. The wise man is still standing here, researching, comparing, thinking.

When you try to kick off a digital transformation project in the corporate world, here's what typically happens:

Six months of requirements gathering. Proposals from four different consultancies. Twelve-page comparison matrices. Executive presentations. Budget revisions. Another round of requirements gathering.

Meanwhile, your competitor, the "crazy one" has already moved off Excel, spun up a basic CRM application, started collecting real customer data, and is already on their second iteration.

Searching for the "perfect solution" is really just the most polite way of implementing no solution at all.

Here's What the Crazy One Knows: The Bridge Doesn't Collapse

Here's the interesting part: the "crazy one" in the proverb isn't actually taking a risk. He crosses the bridge. And the bridge holds.

In business, we call this MVP: Minimum Viable Product. But naming it isn't enough; you actually have to do it.

Over the past five years, I've led dozens of enterprise CRM and business application projects. I see the same pattern every time: companies that start fast end up with a better system six months later and they know exactly what they need. Because that knowledge comes from using, not from planning.

At Parlon, we've made this philosophy the core of our methodology. We start every project by building an MVP in Figma first. Before writing a single line of code, we show the client: "Look, this is how your system will work." There are screens, there are flows, you can click the buttons. Nothing is "real" yet but everyone can see, touch, and debate what's going to be built.

And every single time, the same thing happens: the client looks at the prototype and, within two minutes, articulates what they couldn't express in weeks of meetings. "This part shouldn't work like that. Move this field over here. Actually, we need this too." That's the moment the real requirements analysis begins, not in PowerPoints, but in Figma.

"But Our Processes Are Complex"

Every time I hear this, here's what I think: Yes, they're complex. But the thing that will untangle that complexity isn't a perfect initial plan, it's confronting a working system.

In a healthcare group's CRM project, here's what surfaced in the first week: the data fields that field teams actually needed were completely different from what the central planning team had assumed. No requirements document could have caught that. But a working application caught it on day one.

We had a similar experience with an asset management system for a heavy haulage firm. The data model that looked "perfect" on paper reshaped itself once it hit the field. Because real operations are always different from theory.

Speed Is Not Sloppiness

An important distinction here. "Cross the bridge like the crazy one" doesn't mean "do shoddy work." Quite the opposite:

Starting fast is a deliberate strategy. Start small, learn, grow. Don't make the first version perfect. But build it on a solid foundation so it can scale. That's where the real craft lies.

On a Microsoft Power Platform project, for instance, you can ship a working module in the first two weeks. Users start interacting with it. Feedback flows in. By week three, that module becomes more accurate than six months of planning meetings could ever produce.

So What Should the "Wise Man" Do?

The wise man should stop searching for bridges. But he should combine the crazy one's courage with the wise man's vision.

In practice, that looks like this:

See the big picture, but start with a small step. Don't try to build your entire CRM in a day but launch the first module this week. Don't wait for perfect data, start working with what you have and clean it up along the way. Don't wait to convince every stakeholder, show results with a small pilot and let the buy-in come on its own.

The projects that created the most value in my career were always the ones that started "before we were ready." The ones that wasted the most time were the ones waiting to start "when everything is in place" most of which never started at all.

That bridge is waiting for you. It might not be perfect. But if you cross it, there are answers and opportunities on the other side.

Are you the crazy one? Maybe a little. But at least you're on the other side.

Which project are you still searching for the "perfect bridge" on? Or have you already crossed?