Next

Launches

Document Storage

Google

Enablement

Blog Article

How NOT to Communicate a Product Change

How NOT to Communicate a Product Change

Communicate changes clearly to avoid customer chaos

Communicate changes clearly to avoid customer chaos

This is an example of how NOT to handle a product change.

Google recently had to claw back a “secret file cap” that it put in place a couple of months back. It was such an abrupt and significant change that it brought down the systems of many customers. The issues could have been avoided if Google had simply communicated its plans.

So the lesson here is to always ask the question “how will this impact our customers” before determining what launch tier and communication plan to apply to a release.


Example

Gallery

See similar resources

See similar resources