What they do well — Identifier-first login: you enter your email, then Amazon decides the next step (password, OTP, or passkey) based on your account.

Why it works — It keeps the first screen minimal and lets Amazon route millions of accounts with different security postures through one flow without overwhelming any single user.

What to learn — A single identifier field can carry a lot of routing logic invisibly — Partenamut's login could branch to itsme, CSAM, or password based on the member's registered method, instead of showing every option at once.

What they do well — Passkeys are offered proactively but never forced — Google prompts enrollment after login and keeps password + 2-Step Verification fully available as fallbacks.

Why it works — By pairing the prompt with a visible, dismissible benefit statement, adoption grows without anyone being cut off from access.

What to learn — Passkey prompts should be tied to a specific, positive moment (successful login) rather than shown as a generic settings banner nobody opens.

What they do well — Face ID / Touch ID unlock is the default expectation across every app on the platform, with passcode as an always-available, equally fast fallback.

Why it works — Consistency across the entire OS means users never have to relearn the pattern between apps — trust is built once, system-wide.

What to learn — A member portal that behaves the same way across web and mobile — same method names, same order of options — reduces the relearning cost members currently face jumping between CSAM, itsme and password.

What they do well — A single 'Security info' screen lists every method on the account — password, authenticator app, passkey, phone — with clear add/remove controls.

Why it works — Centralizing methods in one place removes the guesswork of 'how did I sign up' and makes account takeover attempts easier for users to spot.

What to learn — Partenamut members juggling CSAM, itsme and a portal password would benefit enormously from one consolidated 'login methods' view instead of separate flows per method.

What they do well — Mobile-first authentication built around biometric unlock, in-app push approval instead of SMS codes, and instant device-trust decisions.

Why it works — Removing app-switching (no copying codes from SMS) makes the flow feel instantaneous while push approval remains phishing-resistant.

What to learn — A push-to-approve pattern via the Partenamut app could replace weaker fallback channels for members who already have the app installed.