Sadly two “old school” aspects are completely ignored in the analysis. The first is planning. Plans do not survive first contact with reality. Given. But plans are not so much numbers but putting your angle of view towards how things should develop on a paper. You cannot escape what’s written down (unless you ignore it). From looking at the deviation of real life development and plan you can find the gaps in your own thinking and approach, find factors you’ve been missing or whose degree of influence you did not correctly anticipate.
And while there is a “lesson learned” on putting your stuff into people’s hands and watch them, that is not really what qualifies as market research, let alone full market research. All you know is that people have goals and do struggle more or less with achieving them. No clustering into sub-groups whether it is topical based or on how hard the individual finds it to put through with a goal or the psychographic typeologies of those who struggle.
It boils down to what you are coding and for whom. If you got tons of excess code, you probably couldn’t answer these question precisely enough or your idea was so complex that you from the beginning had to provide for 10,000 data points — 9,950 of which will only be filled later in the db.
At Everest to me it looks like a bunch of “I achieve and overcome all obstacles” mindset-people had the unclear “vision” to help those who are different with an APP. Probably a group of people who make plans, have huge ideas, who dream to change the world but never get close there, would have been the better non-technical side of the team (if you have no focus group from market research) to provide coders with input?
Yes, very old-school. But and old-fashioned doesn’t equal bad, useless or clueless because it means sitting down and taking time before starting. Indeed the questions:”Are we the right team to give those struggling with achieving a certain thing a helping hand?”, and:”Is a coded system the help needed?”, seemingly never got asked at Everest before starting-up computers for coding. That probably is the biggest lesson to learn here.
In the end everybody always knows everything better than beforehand. :-)