Seeing like a bank
Modern retail banking is portrayed as a maze of fragmented systems, tiered support, and rigid compliance processes that routinely frustrate customers and frontline staff alike. Commenters highlight how cost-cutting, regulatory pressure (especially anti–money laundering rules and secretive Suspicious Activity Reports), and the split between “profit centers” and “cost centers” produce brittle workflows, poor service, and opaque account closures. Several argue that while these structures enable low-cost, mass-market financial products, they systematically advantage the well-connected and financially literate, and are extremely hard to reform without unintended consequences.
Organizational structure and cost centers
- Many commenters agree large orgs are really collections of constrained teams and “money-saving entities,” not a pool of unlimited resources.
- Being in a cost center vs. profit center shapes status, resourcing, and career paths; IT and ops often treated as second-class even when revenue depends on them.
- Partitioning into teams is driven by politics, egos and constraints, often far from optimal. Segregation of duties for fraud control is another driver.
Tiered support, customer experience, and inequality
- Strong consensus that tiered support is structurally here to stay: it’s cheap and shields scarce experts from “DoS by confused users.”
- Many see the model as biased toward affluent or “professional-managerial class” customers who know side channels (executive letters, regulators, social media escalation, premium banking).
- Some defend it as enabling low-cost mass services (credit cards, discount brokerages); others argue the U.S. is uniquely bad at basic UX (hold times, call-backs).
AML, SARs, and civil-liberties worries
- Extensive debate on Suspicious Activity Reports and AML rules:
- Critics call AML a costly, ineffective “tyranny” that hits immigrants and unsophisticated customers while serious criminals route around it.
- Defenders say deterrence and easier prosecutions may justify low direct “catch rate,” but effectiveness is unclear.
- People highlight Kafkaesque account closures with no explanation, lack of due process, and chilling effects on open discussion of SAR-avoidance.
- Structuring is widely misunderstood; many innocently suggest behaviors that are technically felonies.
Technology, legacy systems, and workflow pain
- Multiple anecdotes of brittle core systems, acquisitions leading to many incompatible stacks, and ops staff living in “constant firefighting” and blame-avoidance.
- Learned helplessness is common: front-line staff and ops accept broken workflows as immutable; trivial fixes never get surfaced.
- Offshoring and underfunded cost centers degrade reliability and institutional memory.
Standards, mergers, and interoperability
- Question: why no common banking OS / data model to ease mergers?
- Responses: historical divergence over decades, coordination problem among all banks, vendor lock-in, and limited incentive to make switching easy.
- Payment delays often driven by liquidity management and central-bank rails, not just IT.
Comparisons, neobanks, and crypto
- Several note better UX in EU and other countries (instant IBAN transfers, phone-number payments), versus U.S. friction for large moves.
- Neo-banks can be even worse in support and AML-driven freezes, despite slick apps.
- Some hoped crypto would force competition and eliminate arbitrary freezes; others note crypto has largely recreated traditional risks plus new ones, and serious use still runs into regulation.
Practical coping strategies
- Suggestions include: multiple bank relationships, separate “risky” vs. operating accounts, using wires for big transfers, learning escalation side-channels, and sometimes preferring big banks’ clear “no” over small banks’ friendly incompetence.