,
6 tweets,
2 min read
Read on Twitter
One of @awscloud's biggest weaknesses is that while product teams strive to create great experiences for their services, AWS users have to use many teams' services and there's very little accountability for the cross-AWS-team experience.
AWS is the best in the world at creating autonomous teams. We’re asking AWS to figure out how to scale their customer obsession in a way that cross-team feedback is appropriately prioritized.
We’re glad docs are in GitHub, but we want PRs to get addressed faster. We shouldn’t have to go to 90 individual teams to beg them to do that! There should be customer advocates at AWS that see what we see, and are empowered to help make it happen
Every bit of inconsistency across AWS is a little bit of cognitive drag on us. Does this service use CamelCase or camelCase? Do their CloudFormation resources and APIs traffic in names or ARNs? Where in the docs do they have their IAM policy info?
Coordination interferes with autonomy, I know. And yes, 2 > 0. But we’re no longer talking about 2, we’re talking about 200.
I believe it is possible to require teams to learn a little bit of cross-org context that will inform their decisons, without slowing them down—because by taking that time, their customers will be faster, too.
