All posts by Arjen Lentz

Dad, parallel entrepreneur, cook, gardener, explorer, philosopher, tinkerer....

Drive: The surprising truth about what motivates us

This lively RSA Animate (10 mins video), adapted from Dan Pink’s talk at the RSA, illustrates the hidden truths behind what really motivates us at home and in the workplace.

One key lesson is that more pay does not motivate, it just needs to be enough to take the money factor off the table.

Modularity vs Integration

Modularity is about business processes as well as software or system design. The Innovator’s Solution (Clayton Christensen, Harvard Business School Press) analyses this very well, identifying modularity as a phase, or more accurately, a state in the going development cycle.

Choosing modularity as a core objective, as many appear to do these days, does not appear to be effective. Trying to make something modular when the subject is not fully understood and the interfaces not clearly defined and predictable can be fatal.

When, in order to make a product or process good enough in the current state of its market, it needs to be tightly integrated… then that’s the way to go. The system will evolve to a point where modularity at that point makes sense (for a period of time), with tightly bound sub-systems.

Looking at products (including software), consider the business processes in the market. For instance, the packaging (not necessarily physical, but documentation, support and other services) and other logistics are also part of the whole, and may well be suited to modularity (e.g., one company offering support for a product that’s built by another) even if the product itself is tightly integrated at that point in time.

In summary, modularity is not better or worse than integration. Each has its place, depending on the state of the market/ecosystem where the process/product/service operates. Part of a system can be in a modular phase, where another part of the same system needs integration.

Time to Market

At a user group meeting last week I got talking with someone who was working on an interesting PhD project. It was not IT related, but as part of the PhD he was developing a website offering a really useful service to people. When I asked “so when will the website go live?” he answered “mid next year”: PhDs are a three-year thing and he needs to span the time.

What a pity. That site should go live as soon as possible! Also, there might be some business in it, but with a longer time-to-market you run a serious risk of “entering obsolete” or at the very least encountering seriously changed market conditions. The world moves faster these days.

And think about it… once online, there’ll be data to collect and analyse that’ll also contribute to the thesis, that in itself will take considerable time. You’d want to get the site up as early as possible, for this reason and to have more time to learn from the real world and fine-tune the service.