Skip to content
cube4devcube4dev

Theses · Learn early instead of committing early

For new products, the detailed specification is an elaborate form of guessing.

Define first, then develop: that works for familiar tasks. With new products, part of the decisive insight only emerges while building.

Only a working system core shows whether architecture, performance and product logic fit together.

In detail

Software development as an instrument of insight

Software development is traditionally understood as carrying out a decision that has already been made. First it is defined what is to be built. Then it is developed.

For new products that separation is only of limited use. Part of the decisive insight arises during development itself.

Only a real interface shows whether an idea for operating the system holds. Only real data makes it visible whether a data model is appropriate. Only a working system core shows whether architecture, performance and product logic fit together. Only a usable system permits a realistic assessment of what a product idea can actually become.

Development therefore produces more than software. It produces information about the future product.

In an early product phase, a solid state of development can produce more insight than another round of abstract specification.

Software development as an instrument of insight →

More theses