The “red tape” danger

The problem with too much process and red tape is that it creates excuses for not getting problems solved:

“Our processes dictates that I must do this”, “I am not measured on doing that”, “I cannot do anything about it, it’s the rules”, “We have a policy that…”.

Etcetera etcetera.

Of course there needs to be rules and processes, and sometimes they’re even defined by law.

But having said that it is also important to reiterate that just because you can push a set of rules, a boss or even the law in front of you, it doesn’t mean that you can’t show empathy for the person(s) in the other end obviously experiencing a problem.

One of the reasons why startups even stand a fighting chance against much larger and more resourceful organizations is that they don’t have all these rules, processes and KPIs in place.

They’re just trying to do what they think is necessary to enable them to solve issues and move forward. By showing empathy and some sort of efficient pragmatism whenever they encounter a challenge or – most importantly – a customer experiencing a problem and in need of a fix to it.

When companies grow and more people get onboard, the need for processes, policies and rules will grow – sometimes almost exponentially.

That may be fine in itself. But it should never be an excuse for throwing empathy and the ability to act and fix issues out the window.

If you start doing that you will enable precisely all the behaviour internally in your organization that you DON’T really want. And absolutely don’t need to succeed.

(Photo: Pixabay.com)

The daunting 1st prototype

The last week or so I have been busy building the first simple prototype of our upcoming app – a pre-MVP – for the MedTech startup, we’re working on getting off the ground. We will be getting it out there to get early feedback just after Christmas.

It is a daunting process.

Not only is it daunting to try to find the different pieces that when stitched together could form a somewhat crude but credible first go at what we will initially be trying to bring to market to create value for patients.

No, the most daunting part is that youre airing your idea(s) and inviting feedback from real potential users. And doing so full knowing that they can throw whatever they want in the form of feedback and criticism against you.

The prospects of getting feedback from people – or worse yet; hearing nothing at all because no-one will try it out – is so excruciating it can be a real challenge to push that ‘Publish’ button and get it out there.

But there is just no way around it;

If you never launch anything – not even a very crude, embarrasing prototype – you will by definition have failed completely.

So, reversely, by just getting something out there for people to provide feedback on is infinitely better and an infinitely greater step towards any kind of potential future success.

So just do it.

(Photo: Pixabay.com)

Commercialization as a science

When you’re working with researchers and/or developers, it can be super easy to completely focus on the research, the science and the product it is all (potentially) leading towards and the inherent value herein. And that nothing else matters to your future success.

But that is a flawed assumption. Cool technology doesn’t cut it on its own. It needs a complete ecosystem around it to have any chance of succeeding.

Developing such an ecosystem is super tough. There are many moving parts that changes all the time. And when you account for the human factor, change of opinions, irrational decision making etc, it becomes extremely complicated very quickly.

Navigating and succeeding in that maze outside the lab is a science in itself. And it should be dealt with, rewarded and appreciated in just the same way as we have the deepest respect for those working behind the scenes to develop the technology.

It takes two to tango. It takes tech and commercial acumen to succeed.

One cannot exceed without the other. And vice versa.

(Photo: Pixabay.com)

Startup-life as football fan

People who know me well also know that for the past close to 30 years, I have nurtured a deep passion for Blackburn Rovers Football Club. (Heck, this season our Danish supporters club even have a first team player sponsorship between us).

From a distance I have witnessed ups and downs (and lets face it; the last 10 years have been most on the downslope), and I have felt both the joy and the pain of being so much into something you just passionately want to end up well.

When I think of it, I think that a lot of what you experience on the emotional side as a passionate fan is similar to the emotions you go through when trying to build and be successful with a startup;

A few times the team will be firing on all cylinders, dominate the opposition and score a plethora of goals to the extend that you almost get tired of winning.

Sometimes the team will be playing really well but be unable to get the ball across the line for a goal. Super frustrating times and instead of feeling you at least got a draw and a point, you will rue the two points lost from the win that was not to be.

Sometimes your team plays well for 88 minutes, commits a really howler – or the goalkeeper forgets he can use his hands – and you will loose at the death of the game.

Sometimes you will just get run over by a superior side, and the most important job is how to put it behind you and move ahead with confidence to the next game and the next opportunity.

And sometimes you will be able to pull off the upset of the season, but superior opposition – and have absolutely no idea how you did it but still delight from your triumph.

But most of the times the team will be in there battling back and forth over 90 minutes plus added time, feeling on top in some periods of the game and hugely under pressure during others. And the scoreline most likely won’t reflect the amount of effort put into achieving whatever boring result, you end up with.

But there’s still passion, energy and tenacity to get it right and ultimately win. And you never, ever lose hope that your team will prevail in the end.

(Photo: Blackburn Rovers Football Club)

Attacking a problem

There are two types of problems, you can pursue solving, when you’re trying to build a startup:

You can go after a problem that is really obvious and outspoken. Or you can go after a problem that is non-obvious but nonetheless exists.

If you go after the first, chances are that you will be far from alone in pursuing it. Especially if the problem is big, painful, and the market opportunity is big enough. While competition is by no means bad per se, it adds another level of stress to your journey than those that are already inherently present.

If you go after the latter, you may be more alone in the space of your choice. On the other hand you might also need to spend more time and energy activating the market, as your target market will be so accustomed to nothing happening that expectations that anything will ever materially change are low.

Both choices of direction of the journey comes with opportunities and pitfalls for you. You can succeed in both – and you can fail in both. It is mainly a question about what ends up becoming the decisive factors.

What you however can always do is to make sure that you understand your market, your future customers and their pains related to the problem, before you just dive head in to create your solution.

No matter your approach it will de-risk the journey immensely for you.

(Photo: Pixabay.com)

The problem with OKR

I love OKR’s as a concept. And God knows I have been trying time and time again to make them and associated tracking apps and services work for me and my team.

But alas; I have failed every single time.

It is not that setting up OKRs is super hard; everybody can define and objective and a set of results to get to the objective. But sticking with it and having the discipline to work with it? That’s a whole different ball game.

For a startup context I think one of the reasons for this is that startup life is inherently messy; while you may have objectives, goals and other variations of KPIs (you should always have some of these) the journey towards them are never linear.

In practical terms what this means is that while you were addament you had it right, when you set your goals, they rarely survive when you fast forward to a future date. In fact, everything at this point in time might look substantially different.

I am fully aware that with OKR it is entirely possible to define your time periods, number of OKRs etc entirely as you wish. But if you’re changing them every other day what’s the point of having them to track against in the first place?

What I have found to work better is to have some pretty non-negotiable KPIs that are pretty specific but at the same time broad to enable all sorts of paths and journeys leading up to them.

1-2 on a six months basis is enough, I would argue. Especially at a super early stage, where having too many objectives will most likely only result in a lack of focus.

Agree on those and agree on providing a weekly or bi-weekly short status mail where you mention the points, the most important developments since last time, your confidence and actions until next update, and you’re set.

Forget everything else.

(Photo: Pixabay.com)

Feel the problem

When you’re trying to solve a problem for someone, it helps a lot if you can empathize – even feel – the problem yourself.

Because it’s when you have a real sense of the problem, you release all those creative juices that allows you to not only look at the problem from different angles but also come up with ideas for how to try out different solutions in easy, creative and quick ways.

On the other hand, when you don’t feel the problem, it can be hard to not over-strategize and overcomplicate how you go about trying to solve it.

It just doesn’t feel natural to you, and when you’re stuck creatively, your only fallback option is the complex process, you bank on to see you well through to the other side.

When you do feel the problem, what you need to do next becomes more natural to you. You have an easier time setting the necessary wheels in motion, getting people onboard to help you and in general just get s*** done.

So make sure you can feel the problem before anything else. It will make the road ahead so much easier.

(Photo: Pixabay.com)

What’s in a co-founder?

Not so long ago I met for the second time with a potential co-founder for our MedTech startup. It was a really good and interesting meeting, and the conversation was really good.

One of the things we talked about was what it means to be a co-founder of a startup.

“What does being a co-founder mean to you?”, he asked me. So of course I had to give him my best shot with an answer.

Here goes:

There are very big differences between being a co-founder and being a key employee in my book. And while in the following it may seem so, I wish no disrespect to key employees at all, and their contributions should be deeply valued. They’re just not co-founders.

Back to how I see a co-founder compared to a key employee:

While key employees may be some of the first to head for the lifeboats when your startup ship takes in water and set off for the safety of dry land, a co-founder goes down the ladder to the very bottom of the hull to man the pumps and start pumping away.

In the same way when the shit hits the fan, and the house is on fire, a key employee may try to call for the fire brigade. The co-founder grabs the nearest fire extinguisher, heads into the flames and starts putting the fire out.

You get my drift.

While the key employee may get excited about the professional challenge for a period of time, the co-founder falls in love with the problem and pictures herself digging in until the problem is either solved (or at the very least seeing good traction) or the startup has run out of steam and is beyond any salvation.

While the key employee may choose to focus more on his job at hand and personal goals and KPIs, the co-founder is always ready to step in and help the team, where the need arises.

And so on.

The biggest overall difference between a co-founder and a key employee is a mental one. It’s about WANTING it and being willing do back up that desire by running the extra miles needed for the team and startup to succeed.

Often, when you meet people, you can tell whether they are co-founder material or not.

Some are naturals. Some may grow into it over time. Some will never get there.

Nothing wrong with that. Just be able to spot the difference.

(Photo: Pixabay.com)