Google Humility or Google Hubris?

Techwriter10 0 Tallied Votes 253 Views Share

This is the mystery of the quotient - Upon us all a little rain must fall.
~Led Zeppelin, The Rain Song.

It's been quite a couple of weeks for Google. First there was the mistake that caused the entire Internet to be flagged as malware. Next came the great Gmail outage earlier this week (which I wrote about in Let's Not Use the Gmail Outage to Trash Cloud Computing). Google has been taking a few lumps and it's not what you expect from a company that has pretty much sailed through its history on a startling growth trajectory. But just when I was beginning to think that Google had lost a bit of its swagger, I read that the company is joining in the anti-trust suit against Microsoft in Europe. It's been a week where we've seen a couple of sides of the complex company that is Google.

Looking a Bit Humble?

In the wake of the Gmail outage this week, Google put up an Apps Status Dashboard to let users know the status of Google Apps at any given time. It also acts as an audit trail of sorts because you can check the status historically. When I saw this, I immediately thought that Google was feeling a bit of pressure, that these problems, prior to them unknown, were smacking them back a little.

The Status dashboard is not a new idea of course. It's something Salesforce.com has done for quite some time as a way to assuage customers who might be concerned about how often the service is up and running. Cloud applications for whatever reason seem to have to pass a higher threshold in this regard than desktop or server applications, which as we know also go down from time to time. Regardless, the fact that Google even felt it had to offer this to users (especially the ones that pay for the service) was telling in its own way.

Looking a Bit Arrogant?

But don't cry for Google just yet because earlier this week it surfaced that Google was around Internet Explorer. Further proof of Google's growing insecurity or perhaps just its incredible arrogance, but either way it seems strange that Google would resort to this tactic to gain market share for its browser, especially as the Information Week article points out, that Internet Explorer has been steadily losing market share.

It's pretty clear that Internet Explorer has become a secondary choice for many users, and if Google creates a decent browser with great features, then people are going to use it. Simple enough. The success of Firefox shows that when presented with a decent alternative, the market responds. It's time for Google to let the quality of its products speak for them and not hide behind law suits in this fashion.

Every company runs into issues from time to time and Google is no exception, but it's certainly interesting to watch how they've handled it. If you think about it, both moves illustrate a company that's no longer on the top of its game, but instead one that's resorting to moves we usually expect from Apple and Microsoft, which just goes to show, that once you get big enough, corporate behavior tends to repeat itself.

Dani AI

Generated

Good framing by — the same incident can look like humility when a company opens its doors, or hubris when it pushes the fight into court. Two practical threads emerge from those events: transparency and operational resilience.

For vendors: a public status feed is a start, not a finished solution. The useful pieces are a reliable live status, historical incident timelines, clear SLAs and credits, and an easy way for customers to subscribe to updates. Internally, treat each public incident as a postmortem opportunity: fix single points of failure, automate failover tests, and practice communications so explanations are timely and factual.

For customers and site owners: assume outages will happen and plan for them. At a minimum, enable offline sync for critical services, export important data regularly, keep an alternate delivery or notification channel, and add health checks that alert your team before customers call. For anyone relying on web rendering for search or conversions, build with progressive enhancement or server-side rendering for core content so a browser or JS issue does not silently kill visibility or analytics.

On the antitrust/legal angle: litigation is a tool companies use to shape market behavior, but it is not a substitute for product quality or distribution. Compete by building useful features, clear upgrade paths, and an easy migration story for users. From an SEO and operations perspective, monitor how browser changes affect rendering and analytics, and keep critical user journeys robust against client-side failures.

Bottom line: expect both humility and hubris from big vendors. Read public status reports, demand measurable SLAs, and prepare your own fallback plans. That combination protects users and forces vendors to improve — which is the practical outcome worth paying attention to.

Techwriter10 42 Practically a Posting Shark

Some Google Humility:

Google Apologizes for Gmail Outage:

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.