Business mistakes exampleWe decided to build a calendar that would instantly display availability without making users wait for the data to be queried and to load. The principal idea was sound, but the technical solution was contrived. This then led to further problems and bug fixes on top of bug fixes.
Impact it hadThe wrong technology choice led to approximately 25 days of development work, analysis and fixes. A basic calendar could have taken only five days.
In retrospectThe calendar technology choice should have been analysed more deeply and alarm bells should have rung after the first couple of rounds of fixes.
Resolution effortWe analysed the calendar performance and architecture comparing it to an old calendar system that we had on another project. This past knowledge steered the revised architecture.
Mistake learningsAt the time when the decision was made we were plowing forward and trying to make a lot of moving parts work together. In retrospect, we were trying to do much too quickly.
Next stepsAnalysis was conducted and the system critiqued six months after creation and extensive bug fixes. When the decision was made to re-architect and redesign the on-demand calendar, the entire team was brought up to speed and all bug fixes halted so as not to burn more time on it.
Our final business mistakes example was so bad it led to the closure of a young company – but the founder has taken the learnings into his latest venture.
Share this story