๐ฅย ๐ ๐ผ๐๐ ๐ฝ๐ฟ๐ผ๐ฑ๐๐ฐ๐ ๐๐ฒ๐ฎ๐บ๐ ๐๐ฝ๐ฒ๐ป๐ฑ ๐บ๐ผ๐ป๐๐ต๐ ๐ฏ๐๐ถ๐น๐ฑ๐ถ๐ป๐ด ๐๐ผ๐น๐๐๐ถ๐ผ๐ป๐ ๐ณ๐ผ๐ฟ ๐ฝ๐ฟ๐ผ๐ฏ๐น๐ฒ๐บ๐ ๐ฐ๐๐๐๐ผ๐บ๐ฒ๐ฟ๐ ๐ป๐ฒ๐๐ฒ๐ฟ ๐ฎ๐ฐ๐๐๐ฎ๐น๐น๐ ๐ต๐ฎ๐ฑ - ๐ฏ๐๐
๐ฅย ๐ ๐ผ๐๐ ๐ฝ๐ฟ๐ผ๐ฑ๐๐ฐ๐ ๐๐ฒ๐ฎ๐บ๐ ๐๐ฝ๐ฒ๐ป๐ฑ ๐บ๐ผ๐ป๐๐ต๐ ๐ฏ๐๐ถ๐น๐ฑ๐ถ๐ป๐ด ๐๐ผ๐น๐๐๐ถ๐ผ๐ป๐ ๐ณ๐ผ๐ฟ ๐ฝ๐ฟ๐ผ๐ฏ๐น๐ฒ๐บ๐ ๐ฐ๐๐๐๐ผ๐บ๐ฒ๐ฟ๐ ๐ป๐ฒ๐๐ฒ๐ฟ ๐ฎ๐ฐ๐๐๐ฎ๐น๐น๐ ๐ต๐ฎ๐ฑ - ๐ฏ๐๐ ๐๐ต๐ฒ๐ฟ๐ฒ’๐ ๐ฎ ๐๐ถ๐บ๐ฝ๐น๐ฒ ๐๐ฎ๐ ๐๐ผ ๐ณ๐ถ๐ ๐๐ต๐ถ๐.
๐ถ When I walked through Barcelona last week, I spotted something that made me stop dead in my tracks…
๐ ๐ฑ๐ผ๐ผ๐ฟ ๐๐ถ๐๐ต ๐ฎ ๐ณ๐ผ๐ผ๐-๐ผ๐ฝ๐ฒ๐ฟ๐ฎ๐๐ฒ๐ฑ ๐ต๐ฎ๐ป๐ฑ๐น๐ฒ.
๐ก Here’s what blew my mind: Instead of just slapping metal plates on doors to prevent kick damage (the lazy solution), someone actually designed for the real behavior.
They turned “unintended usage” into a feature.
๐ This is exactly what’s broken in most companies: โข We design products for imaginary customers in conference rooms โข We add band-aids instead of solving root problems โข We launch first, then wonder why adoption sucks
At Amazon, we use the “๐ช๐ผ๐ฟ๐ธ๐ถ๐ป๐ด ๐๐ฎ๐ฐ๐ธ๐๐ฎ๐ฟ๐ฑ๐ ๐ณ๐ฟ๐ผ๐บ ๐๐ต๐ฒ ๐๐๐๐๐ผ๐บ๐ฒ๐ฟ”-mechanism [1] to ensure we’re solving real problems from day one.
๐ The key insight? When we actively listen to customers throughout the design process, we build products that actually serve their needs.
AWS services go through preview phases specifically to gather customer feedback and shape the final product before general availability. It’s a simple approach that makes all the difference.
๐๐ผ๐ ๐ฑ๐ผ ๐๐ผ๐ ๐ฒ๐ป๐๐๐ฟ๐ฒ ๐๐ผ๐๐ฟ ๐ฝ๐ฟ๐ผ๐ฑ๐๐ฐ๐๐ ๐ฎ๐ฐ๐๐๐ฎ๐น๐น๐ ๐ณ๐ถ๐ ๐ฐ๐๐๐๐ผ๐บ๐ฒ๐ฟ ๐ป๐ฒ๐ฒ๐ฑ๐ - ๐ฎ๐ป๐ฑ ๐๐ต๐ฎ๐ ๐บ๐ฒ๐๐ต๐ผ๐ฑ๐ ๐ฑ๐ผ ๐๐ผ๐ ๐๐๐ฒ ๐๐ผ ๐ด๐ฎ๐๐ต๐ฒ๐ฟ ๐บ๐ฒ๐ฎ๐ป๐ถ๐ป๐ด๐ณ๐๐น ๐ณ๐ฒ๐ฒ๐ฑ๐ฏ๐ฎ๐ฐ๐ธ ๐ฒ๐ฎ๐ฟ๐น๐ ๐ถ๐ป ๐๐ผ๐๐ฟ ๐ฑ๐ฒ๐๐ถ๐ด๐ป ๐ฝ๐ฟ๐ผ๐ฐ๐ฒ๐๐? ๐ค
[1] Andy Jassy explains the Leadership Principle “Customer Obsession” and in this context the “Working Backwards”-mechanism - 5min well invested: https://lnkd.in/eQ5rYzjp
#AWSomeVoices #LeadershipPrinciples #WorkingBackwards #Barcelona
Cross-posted to LinkedIn