Thread by @outlandishjosh

In addition to #serverless (see link), my other new favorite piece of hashtag-compliant vocabulary for Pantheon is #WebOps

Let me explain.

https://twitter.com/outlandishjosh/status/1154442154984394754

The default short-hand for what we do is, of course, "hosting." The dreaded H-word. It's part of our story for sure, but it misses out on the value Pantheon provides.

It's an incomplete "what" that thoroughly misses out on the "why."

Don't get me wrong. Hosting is super important, and if your hosting setup is bad or broken, it's really hard to see past it.

A burning platform is an all-consuming emergency. If that's your situation you should call us; we can help!

But hosting is also, kinda, let's be honest, a solved problem. There's a correct way to do it, and plenty of vendors can offer you that, including Pantheon.

"We've got the best damn hosting in the world," I like to say, but we're best among a bunch of good options.

However, solving your hosting problem doesn't give you want you need from the web. It's a textbook "necessary but insufficient" condition.

If you want to deliver results via the web you need to be able modify your website quickly, and with confidence, and not just by publishing content.

That's why you need #WebOps.

You will not make the impact you want if you only refresh your website every two to three years.

First off, the market moves way faster than that.

More importantly, greatness is achieved via constant iteration, not a bi-annual hail mary.

The status quo of the "big relaunch" is insane. Burn through all your budget, burn out your team, and then grit your teeth and just live with whatever comes out until the next cycle.

Stop the insanity. Start doing #WebOps.

This is where it gets back to hosting, and what makes Pantheon unique.

If you want to start doing #WebOps, hosting can be the enemy. Hosting wants stability. Hosting wants uptime. Hosting has to restrict access. Hosting doesn't like change.

And that's understandable! Most businesses don't have the luxury to "move fast and break things," especially when it comes to their public face to the world.

The fear of crashing has been a driving force for Hosting since the beginning. "Can you handle the hits?"

#WebOps is past that. We ask, "what would you do if you weren't afraid?"

#WebOps is shipping on your own schedule, controlling your own roadmap. It's a game-changer:

1) Break out of the multisite-vs-megasite catch-22
2) Iterate your way to the CMS you need
3) Optimize based on real user data

It's literally not possible to win the web with a master plan. It's a complex system.

Your website can't be down, it's true. But if your website is the same as it was a year ago, it can't possibly be *right* either.

TL;DR: the web moves fast and so should you. Embracing #WebOps is a people and process change (much like #DevOps, "it's a culture"), but it's also impossible without a platform.

And Pantheon! Teams that embrace our way of working are up to 4x more productive.

Ugh typo. Should be, "And _that's_ Pantheon!"

Typical Koenig move, fumbling on the close. 😜

Here's the reference for the 4x productivity thing, btw: pantheon.io/resources/stre…