Help Prevent User Abuse

Cagan argues that 'user abuse' happens when product teams ship changes that users didn't ask for, didn't expect, or can't absorb, and that it is largely caused by the natural human resistance to change. He explains that the shift to server-side web applications made change instant and free for the vendor, so teams often ignore the cost borne by users who depend on the product. Agile iteration cadence can make this worse if every small iteration is shipped. He concludes that the answer is not to stop changing but to deploy change thoughtfully, and that goodwill is a limited reserve best saved for moments that truly need it.

01Key takeaways

• Users generally resist change, so every release should be justified by real value to them, not just internal convenience.
• Communicate significant changes in advance with previews, newsletters, education and tutorials.
• Invest extra testing in reliability, scale and performance so rollbacks, which damage trust, are avoided.
• Use parallel, progressive, geographic or incremental rollouts to contain the risk of significant changes.
• Adapt agile practices for commercial products by batching iterations into releases instead of shipping every one.
• Treat user goodwill as a limited reserve and avoid spending it on unnecessary or poorly managed changes.

02Key sections

What user abuse is

User abuse is releasing changes that users don't appreciate, whether through surprise, lack of time to adapt, broken functionality, incompatibility, or perceived gratuitousness.

Why it happens

Users generally resist change, yet products must keep changing as needs, technologies and markets evolve. The real issue is deploying change without considering users.

How web applications changed the stakes

Server-side deployment lets vendors change software for millions of users at once, removing the scheduling and preparation that enterprise software traditionally involved.

The trap of agile iteration

Frequent small iterations are valuable internally, but teams with active user communities should group iterations into deliberate releases rather than shipping each one.

How to deploy change responsibly

Communicate changes in advance, test heavily for reliability and performance, and use gentle rollouts such as parallel, progressive, geographic or incremental deployment for significant changes.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.