Case Study: Staging environment
Unexpected Cascading Failure
+ ANALYSIS + HOW TO SOLVE
Have you ever experienced this???
You have a simple WordPress site that has a little issue. It’s small — you just know it. So you call your developer and explain, that something is off. And they see it right away. You get a verbal confirmation, that it is an easy fix, it will be solved immediately.
The developer requests your credentials or requests separate login rights to your WordPress admin user interface. You comply with the request, giving admin access to your site.
Unexpectedly while trying to fix your initial issue, 3 NEW things fail.
The developer is shocked, and it doesn’t know how it took place. You do not understand why it happened. Both you and the developer look puzzled at the new issues.
You start jumping over hoops while trying to solve these issues. You contact your hosting company. Finally, they advise you, that a roll-back is the best option. A single small issue is better than the 3 new ones. You cave in, accept the restore. Your initial issue remains. You also have a nasty after taste from this experience.
It doesn’t matter WHAT happened. It doesn’t matter HOW it happened. You’re just unhappy because your initial issue is still unresolved. You’re simply dissatisfied with how things progressed. You’re experiencing the exact opposite of the wow effect. Read the ANALYSIS and then find out HOW TO SOLVE this specific case.