![]() ![]() Unfortunately, although there’s a lot of guidance and examples on how to conduct and write good postmortems, there doesn’t seem to be much about service status update messages. I haven’t always done a great job with our own status updates at VividCortex, and that’s been a learning experience for me too. The signal I get is avoidance, which erodes my trust in them. I can’t figure out the real situation and what the vendor’s doing about it. Most vendors do an awful job telling me the truth about how their systems are running. From my perspective as a customer, most of their status updates are garbage. I therefore have lots of SaaS vendors running key parts of our business at VividCortex. ![]() I prefer to buy, rather than build, solutions when possible. Doing a better job with status updates is a high-value activity in my book. ![]() Status updates – especially in moments of potential crisis – are a key piece of your relationship with your customers. It’s a shame, really, because a bad status update can be worse than doing nothing at all. Unfortunately, I see more bad status updates than good ones. As Founder and CEO of a SaaS platform for database performance management, VividCortex, I know the power of a great status update to build or destroy trust. I’ve seen my share of terrible status updates. This is a guest post from Baron Schwartz, Founder and CEO at VividCortex. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |