5. DISRUPTION IN
FINANCIAL SERVICES (1/3)
A survey by the World Economic Forum
found that just 28% of the millennial
and Gen Z generations trust their banks
to be fair and honest.
Digital Bank
6. According to Gartner and IDC, by 2018,
banks and financial institutions’ clients
will access and contact their banks
mainly through mobile devices.
Digital Bank
DISRUPTION IN
FINANCIAL SERVICES (2/3)
7. According to the 2016 MX Consumer
Survey, clients find it more important to
have an easy digital banking experience
(67%) rather than a friendly teller or
staff (33%) when choosing where to
open an account.
Digital Bank
DISRUPTION IN
FINANCIAL SERVICES (3/3)
8. CONTRAST
FINTECHBANK
➢ FinTech firms focus on
managing the
overarching customers’
experience
➢ Focuses on
functionality,
accessibility, agility,
personalisation, and
convenience
➢ Focus on the
management of
risk
➢ Focuses more on
trust and security
9. DIGITAL BANKING Whenever installing new digital banking
technology, it doesn’t help much unless the
routine processes that are being automated are
first closely examined and streamlined applying
some of the principles of industrialization and
efficiency management to processes and
operations.
Whenever installing new digital banking technology,
14. OUTLINE OF RESOLUTION
FOCUS ON FLOW
MEASURE IT VALUE
PLATFORM
CONSOLIDATION
Being able to
measure from
ideation to
realisation is
essential to DevOps
– how much is that
change worth.
Where is the waste
in your
organisation? How
can you get
delight into the
hands of your
customers at
optimum speed.
Fragmentation
equals fragility and
waste. It also
means it’s hard to
move fast and
increases the risk of
trailing the
competition.
15. GOALS
RELEASE AT
PEACE
Functionality is
released on-
demand,
independent to
release cycles
RELEASE WITH
CONFIDENT
Tests executed in
representative
environments
automatically on
check-in
EXPERIMENT WITHOUT
REGRET
Changes
introduced
realtime and
trivial to revert
16. PROBLEM
A “DevOps” team is created, but it ends
up becoming just another silo. Once it
becomes a silo, communication fails, it
becomes ineffective, and fails.
DevOps
19. DevOps ROADMAP
DAY 1
DAY 2
Gather representatives from
each relevant team to review
key activities
DAY 3
Mapping current technologies
and fill the gap
DAY 4
Ask how / if improved
collaboration or automation
could help
DAY 5
Fine tune and iteratively start
again from point number 1
Breakdown and eliminate
unnecessary process, put it
as Operational Technical
Instruction