The Art of Getting Somewhere Without Knowing Exactly Where You’re Going

We all want to be happy. And if you ask people what their ultimate goal in life is, I suspect happiness would be pretty high on the list.

So why not simply make happiness our goal and pursue it?

Well, perhaps because happiness doesn’t really work that way. If you spend your life chasing happiness, you might actually miss what it is all about. Instead, I believe it is about finding something meaningful to pursue, having goals, exploring, experiencing, succeeding and sometimes failing. And along the way, happiness will occasionally materialise, sometimes when you least expect it.

You will also experience frustration, disappointment and sadness. That’s part of it. But the moments of happiness are not necessarily waiting at the destination. They are part of the journey.. And I think there is a rather interesting parallel to how we approach complexity and uncertainty in general.

The illusion of clarity

I have noticed that people approach complex subjects quite differently. Some prefer to understand the whole picture before taking the first step. They want to map the territory, identify dependencies, understand the risks and establish a plan.. Others are more inclined to just get started, even if they don’t have a complete understanding of what they are getting into.

I’m probably more in the latter category.

To me, a complex subject often resembles a cloud. You can see its outline, but you have absolutely no idea what is hiding inside. The more you start investigating it from the outside, the more layers of complexity you discover. Dependencies, exceptions, unknowns and new questions keep appearing.. And if you insist on understanding the entire cloud before entering it, there is a real risk that you will become overwhelmed and never actually get started.

My philosophy is quite simple: You will never achieve complete clarity. There will always be unknowns, unanswered questions and things you haven’t even thought about yet.. So instead of trying to conquer the entire cloud from the outside, I prefer to look at its surface, identify something tangible and take a first step.

Will it be the right place to start? Probably not. Will I make mistakes and have to redo things? Almost certainly.. But now I’m in the process. I’m learning, adjusting, sometimes taking a few steps backwards, but overall moving forward. And gradually, the cloud becomes less mysterious.

Sometimes you have to enter the cloud to understand what’s inside it.

Five people, a blank piece of paper and a lot of pizza

I remember a rather good example from 2005, when five of us started CLC bio.

Two founders: one business CEO and one PhD in bioinformatics. And three employees: myself, a developer, another developer specialising in bioinformatics, and a system administrator.

The ambition was quite something. We wanted to build an all-purpose desktop application for bioinformatics. Think Microsoft Office, but for bioinformatics..The board had set a pretty clear goal: release version one within six months.. So naturally, we got started by spending the first three months planning!

There were endless discussions about frameworks, architecture, what users wanted, how everything should fit together, and how we would build it all. Everything was carefully documented in Microsoft Project.. But somehow, very little was actually happening.

At some point, I got a bit tired of all the discussions and the endless planning. We had a six-month deadline, and half of it was already gone.. So I decided to just get started.

I didn’t have the bioinformatics expertise to build the actual domain functionality. That was something the other two specialists were much better equipped to do. But I could see something I could contribute. I started building the entire application framework, with one very specific objective: to create a foundation that would allow the others to plug in their features, ideas and bioinformatics capabilities.

I wasn’t entirely sure where this would lead, or whether we had chosen the right architecture. But at least we now had something tangible to work with.

And miraculously, we made it.

It took countless late nights, plenty of pizzas and a lot of back and forth. Things were changed, rewritten and sometimes completely redone. But we got version one out the door within the six-month deadline. CLC bio eventually became a huge success, although I’m certainly not suggesting that my little initiative was responsible for that. It was just one small contribution among many.. But the experience has stayed with me because it illustrates something I have encountered countless times since.

Sometimes the best way to get a complicated project moving is not to figure out the entire solution. It is to identify one concrete thing that can be done, get it moving, and let that create the foundation for the next steps.

From clouds to products

This approach has served me well throughout my career.

I have taken over projects that were so big, fuzzy and complicated that they had been stuck for months, sometimes longer. There were endless discussions about where to start, what the right approach would be and how all the pieces would eventually fit together.

And sometimes the most surprising thing for others was that I would simply advocate getting started. Even when we didn’t know whether we were starting in the right place, or even what the final solution would look like. And this doesn’t mean ignoring complexity or acting recklessly. It means accepting that we don’t have to solve everything upfront.. This is also very much how I think about building products.

We can spend an enormous amount of time trying to understand customers, analyse markets, define requirements and establish roadmaps. Of course, we need to do our homework. But there is a point where additional analysis provides diminishing returns, and where actually doing something becomes the best way to learn.. Build something. Put it in front of customers. Observe what happens. Challenge your assumptions. Learn and adjust.

Discovery isn’t something we complete before starting delivery. It is a continuous process, and often the most valuable insights come from interacting with the problem rather than just thinking about it.

A roadmap should provide direction, not pretend to be a detailed map of a territory we haven’t explored yet.

And what about leadership?

This philosophy also has a significant impact on how I try to manage and empower people.

I sometimes think we put too much emphasis on providing clarity. Managers are expected to have the answers, define the way forward and remove all uncertainty for their teams.

But what if that isn’t always what people need?

Of course, people need to understand the purpose, the direction and the boundaries within which they operate. But they don’t necessarily need a detailed instruction manual for getting there. In fact, I believe that providing too many answers can become a barrier to learning and ownership.

I would much rather encourage people to be curious, explore possibilities, make decisions and occasionally get things wrong. Not because mistakes are the objective, but because learning through experience is often far more powerful than following someone else’s instructions.. Empowerment isn’t about giving people the answers and then letting them execute. It is about giving them the confidence and freedom to find the answers themselves.. And as a leader, that also means accepting that they might find a different route than the one you had imagined. Perhaps even a better one.

Sometimes my role is simply to help people take that first step, even when neither they nor I know exactly where the journey will take us.

Enjoy the journey

Coming back to happiness, perhaps there is a common thread connecting all of this.

We spend so much time trying to obtain certainty, clarity and control. We want to know exactly where we are going, how we will get there and what the outcome will be.

But life, product development and working with people are rarely that predictable.. Perhaps we should spend a little less time trying to eliminate uncertainty and a little more time being curious about what lies ahead.

Set a direction. Find something meaningful to pursue. Take the first step. Learn, adjust and keep moving.. You might not end up exactly where you initially intended. But you will have experienced, learned and hopefully created something valuable along the way.

And perhaps, just perhaps, you will discover that the journey was the point all along.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *