After a product is ideated and moves through the Peak of Inflated Expectations, the idea has been sold to management or investors, and everyone is on board with pursuing the product. The product now enters the Trough of Disillusionment. During this phase, a viable product really takes its shape, but you’ll likely experience certain challenges—let’s see what they are.
What is the trough of disillusionment?
The third of five phases in the Gartner Hype Cycle, the trough of disillusionment is arguably the most difficult phase. Here, you’ve already explored an original concept and performed some initial fundraising and testing. But your concept has peaked—the idea was over-inflated or a poor fit for the market. Now, you’re back to the drawing board to reframe the concept.
(Source)
The trough of disillusionment is the hype phase that makes or breaks a product. Investors need to do their due diligence to avoid amassing many buried products here in the trough.
This phase of disillusionment is characterized by:
- Humility. After initial expectations failed, your team is feeling humbler about the concept.
- Decreased confidence. Some team members may question the concept’s viability.
- An open-minded approach. With initial failures out of the way, team members are more open to new avenues for the concept.
- Reassurance. The concept owners reassuring investors, researchers, and the public that everything is fine, that your concept will get off the group.
Teams coping with the trough of disillusionment often experience challenges on three fronts: psychological, experimental, and risk management.
Psychological challenges
Among the concept team, depression sets in and humility is embraced. The development team realizes, “I am not there yet. There is more road to come.” Researchers are a strong breed, willfully positing hypotheses and allowing dreams to get tested against the world. Where some would like to linger in dreams and possibility spaces, researchers allow reality to have its way with the dream. Researchers are great to have aboard during this phase.
During this time, concept managers face a different scenario. A manager makes a promise to deliver a product and takes responsibility for that promise. Your reputation, and your team’s, rests on this promise. In this phase, managers require a bit of a performance while they approach bumpy waters and tell everybody—researchers, investors, customers—that their team is doing what they can to make the product happen. Managers must:
- Speak strongly for a product or idea
- Give others the confidence to support the idea
- Walk through product-testing keeping face no matter the results
For everyone involved, humility is a must. After all the excitement around imagining a new product, talk does not make a product. If a product were to live on talk alone, it would exist buzzing only on the peak of inflated expectations. If a product is to be actualized, it must go through this phase of disillusionment. Hard work and repeated trials and errors create a product. All hype must get tested against actual tests. Humility accepts A as A.
Experimental challenges
An idea really gets to see what it is worth when it is ground beneath the mill.
Traditionally, R&D is the place for testing. For example, a machine learning project receives one million dollars in funding. A few qualified engineers are brought together. After four months of trials and tribulations, the project falls flat and must be abandoned because it did not have the datasets required to create the feature that was promised.
The idea may have been a good one, but the data to support creating the feature did not exist. This product feature fails or is delayed—this might be one iteration in the disillusionment trough. Now the team must reassess if it is possible to get the data necessary to create the feature, make the data to create the feature, or redesign the feature to suit the data they do have. If it’s none of these, it might be time to shelve the project and start another.
In experimentation, especially in its beginning stages, expectations tend to be totally, completely shattered. A team’s confidence to reach the goal can fall from 100% to 0% and the goal disappears, impossible to reach. More mature projects, both in time, resources, and experience, won’t see such sways in the team’s confidence, and confidence levels can oscillate at a steady rate.
The feeling here is not unlike the big swings seen in recent college grads. Many have only had schooling that builds and builds inflated expectations, then they go to a company and they themselves enter the trough of disillusionment.
The confidence levels of teams are affected during this period, but it does not necessarily reflect the actual success of the product itself. It is possible that confidence levels fall flat, but the product is making good progress and forming into something usable. It is possible confidence levels are incredibly high, but the team is totally ignorant of what is happening (that’d be a bad team) and the product fails. It is possible that confidence transcends, and confidence is placed in the ability to do research itself. This kind of confidence is the kind that can make good of any situation. Here, no product fails, the goals transform.
Risk management challenges
That wonderful dance between ideation and testing is where investment is needed, and investment gets burned. Reputations are made or lost. If the team loses a battle, trust is lost and an L goes on the track record.
In the era of coding, the depths at which the trough goes can be decreased if there is code already written to prove the concept.
“Code wins arguments.”
The gap between people who know code and people who don’t know code invites an area of dishonesty. To the non-coder, the code looks like magic, and it is all the same. To the coders of the world, there is good code, and bad code. There is code that is novel and research-based, like producing a unique Machine Learning model, and there is code that gets a job done, like having all the elements of a functioning iOS or Android app.
Potential for enlightenment
Lots can be dreamed. Lots can be promised. Someone can say they will rid the world of hunger and poverty. If that is all the project has to go on—hope—the disillusionment trough starts to look a little bigger. If there is code, if there is data, the trough decreases. If the claim is that wild, the project should never reach the trough in the first place. The disillusionment trough grows in proportion to the size of the claim.
Hard work with real, data-driven results might prove your concept enough. If you make it beyond the disillusionment, you will begin to be rewarded in the Slope of Enlightenment.
The Gartner Hype Cycle
Explore every phase of hype:
- The Innovation Trigger
- The Peak of Inflated Expectations
- Trough of Disillusionment
- Slope of Enlightenment
- Plateau of Productivity
Additional resources
For more on product development and innovation, check out these resources:
