Why prototyping?
What an interesting point mentioned in the video above, in the business realms we are trained to execute the best possible plan and punish failure, instead of continuously prototyping and learn from mistake as you go along just like what the kindergarten kids do.
It seems we’ve not learnt our lessons that the best possible plans will always have flaws and there is nothing can substitute the reality. In the software world we tend to create the ultimate plan and concept, which looks good on paper so we can secure funding. This is usually leads to either the result is not fit for purpose or we tend to over complex the situation and not get the basic rights.
In Claromentis, we’re now embracing prototyping worlds, create endless revisions until it’s right, even when the software is developed and deployed the project is not finished, deploy early and quickly learn from it. The whole point is to create a continues improvement, what works in one environment may not works with others, every situation every problem is unique in many ways and we want to create something that fit to that purpose.
This is great.
I just wish there was more exploration of the reason kids do so well.
I wonder – they just focus on the goal – start with the marshmallow and put things under it. So this is indeed a good example of a prototype in our world- working, interactive designs delivered before a line of business logic is developed.
But maybe its also a lack of constraints, the act of playing with the available tools and enjoying the experience.
Maybe playing with ideas is different to prototyping in the software design world. It might be that prototyping a business idea leads to development efficiency and client satisfaction at the expense of missing a truly innovative solution to getting the marshmallow as high up as possible?
What if we had the luxury of truly experimenting with the client’s basic business need.