Does Lipstick work?
summary
Claims that a shiny front-end fixes legacy failings: a savings balance is blocked by an AML alert raised by overnight analytics on shadow bookkeeping that loses transaction context, forcing a branch visit, paper forms and four hours to restore access. The case shows APIs becoming a channel-only lipstick on a pig while silos, missing governance and ad hoc versioning proliferate (one org had ~13,000 undocumented APIs). Recommendation: align internal systems, governance and consumer contracts before surfacing new digital channels.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:40Background
- 2:46Why digital strategies generally fail
- 5:37Lipstick
- 7:46My story
- 11:25Reflections
- 13:45Reasons why digital strategies fail
- 16:11How to craft your career
- 19:10Internal resistance
- 22:21Culture
- 27:23Banks Api Journey
related talks
25mTransforming legacy software
26mMastering API Strategies for Digital Transformation
28mHow To Finish What You Start: Lessons From Actually Shipping..
25mBoost API Success: Key to Transparency & Accountability
29mApps, Stacks, and Frameworks: Avoiding “Shiny Object” Syndrome
50mTactics and strategies on software development: how to reach ...
36mDigital, data-driven financial advisory
45mInfuse customer obsession into your business strategy: Client panel