Innovation vs Improvement

March 03, 2019 in

A few years ago, being an "enterprise developer", I attended a meeting about the IT strategy up to ⌚2020. Here we heard about "innovating by consolidating".

I thought of this statement as a contradiction (I suspect I didn't voice my concerns back then, after all, I was on layer 6 of the organisation while the CTO was on layer 2 or 3). To me, innovating also means having the freedom to do things differently, being the rebel, thinking something else - quite the opposite of consolidating. Innovating by consolidating sounded to me like the decades old Cuban regime talking about revolution.

Innovation is fickle company, too, as I had to learn last week.

The experiment week

Last year at ahead we did about two experiment weeks, external activities and stories - both were quite successful and valuable to our customers and on one of them we have iterated quite a bit already. Naturally, we wanted to repeat the experience by bringing all team members to Basel and kick into high gear.

We started off by writing all ideas that had been gathered in our prodpad instance, and doing some dot-voting to get our contenders for the week. From lunchtime onwards we kind of gravitated towards an idea, and 2 hours later we had something that seemed shippable within the week's timeframe.

But nobody seemed really happy with it.

We decided to go on with those stories already planned and prioritised and rather expriment with the way we tackled stories and pulled work into the current development.

Get well soon!

It turns out that the sales pipeline is growing and more and more customers are convinced that our product can be useful for them. This is great! On the other hand we know that a number of areas, while working, are far from polished. We were reluctant to start something new.

xp week 1

By lunchtime everything on the left had been discarded.

If you look around the internet for a definition of innovation, you will find many different attempts at explaining it - here's one page giving a couple of definitions from people. My personal definition (subject to change) would be along the lines of

An experiment that proved successful by providing value

What I take away from that, um, unexpected start into the experiment week is that innovation can hardly be forced, and in order to walk unexpected alleys, your mind must be freed from the daily strive for incrementally creating value. I've come to understand that even brilliant people (and hence companies) can fail to innovate because they are too busy improving on those features that are already there.

Improving is valuable. Consolidating is valuable. Innovation, too! However, it is the last one that may be the hardest to attain, especially as your products matures and finds those people who find it valuable.

Would we consider this week a failure? Hell, no!

  • We can see now how to bring some elements of Kanban into our way of working
  • We are almost done with a particularly boring feature which nonetheless slashes our customer onboarding time by a wide margin
  • And, as always, it is great fun and very intensive to work in close proximity with all of your team members!
Writing azure functions with typescriptUse react's context to display an error message somewhere else