> * Release Often as KPIs for developers Not likely. Release often as a KPI usually just means that a few more bugs get shipped and bugfixes get shipped faster

> * Release Often as KPIs for developers Not likely. Release often as a KPI usually just means that a few more bugs get shipped and bugfixes get shipped faster. Poorly designed features are usually results of poor design and nothing else. > Payment Security and Financial Regulations Not really. Sure, opening a bank account is painful, but setting up the app shouldn't be. I've had three different experiences: Chase (easy), Huntington Bank (security theatre abusurdium), and a Credit Union (easy). It all comes down to 2FA implementation - Huntington has a poorly designed authenticator registration flow. > Patch-work nature of ID & Verification... Captchas, Two-factor SMS, password rules and Authentication Apps have been patched onto the original user/pass system Yes, and it mostly works pretty well. It is telling that no one way has really caught on as the way to do it, but there seems to be broad agreement that a click verified email address is an acceptable identity. I'm not sure there's much better. What does a store know about a buyer in the real world, anyway? Physically present, with cash in hand... good enough. > KPI switch from customer first to business model first When has it ever been anything other than business enablement? Ecommerce has always been "customer self service" and many a support site has been built to reduce headcount in customer service. Some companies are good at this stuff, and others are not. Just like in the real world. What is changing at Google and Amazon is the focus is now squarely on making money, so losing money for long periods of time is no longer acceptable. In fact, their focus on mining profit from their users is creating opportunities around the edges... which will give rise to some very capable competitors over time.