Consistency at scale

I keep wondering how come huge businesses like Google fail to get teams and processes in place to create consistecy of features at scale.

Here’s a quick example.

Google Calendar recently introduced ‘Goals’.

That’s dummy data, I don’t work out at all.

Goals setup is a pleasant experience in Google Calendar app, not so much in other places you get to see and interact with your agenda (I personally use Google calendar for Web, iCal, MacOS calendar).

What Goals ends up creating is a series of events in your calendar. Problem is that only Goodle Calendar native app knows they’re related.

So if you want to modify or cancel a batch of recurring Goals events, you can only do so effectively in the native app. Bummer.


What prevented Google from supporting Goals feature across the board? At least in web version of calendar?

I don’t think it is the issue with not having enough human or cash resources. We’re talking Google, right.

Very likely, the product team thought they’ll just try it in the app and only in the app first. To later propagate proper feature support to other Google calendar instances. If the feature succeeds t all.

Now, if that’s the case, do warn users that the feature is ‘beta’, has limited support and can be controlled from the app only. Explain.

But for businesses the scale of Google MVP, the definition of ‘lean’ should be different compared to what MVP & ‘lean’ is in a small startup. Overall the cost of entering the market for some features and products just gets higher with the ever growing and cnanging landscape of devices & platforms to support.

For me personally, limited support of that goal feature in ust one app killed the feature.

The learning

Do consider how deep the support for a feature really needs to be when you launch it. If you just can’t support a new cool thing broadly, do explain yourself not to let users down and reduce the rist of failure.

Designing experiences

Love podcasts or audiobooks? Learn on the go with our new app.