Part 7 - Roadmap embedded
The tools don't define the journey, the direction does

Part 7 - Roadmap embedded

“It’s not the journey, path or challenges that defeat effort, but the direction. If you have clarity and guidance on the direction, success or failure, each step brings with it a new paradigm. A lesson for life.”

Not everything is about the New look and feel of the shiny new Mobile Application. There is significant work that needs to be done to develop cadence and quality of delivery that Wows! the customer. The building blocks have to be cast with strong foundations. It should be substance and not semantics. Though semantics matter but the degree varies.

The most notorious challenge with technology implementation is keeping people together focused on the path. While Enterprises have used vision and strategy as a guiding principle, more work has to be done at the ground level to ensure that every act or change aligns.

In an very innovative environment you cannot create a roadmap that does not have twists and bends and diversions and rollbacks. These should come a part of the ecosystem and guiding principles. We were able to create some,

Guiding Principles

  1. Prioritize
  2. Simplify
  3. Customer Acquisition
  4. Ecosystem expansion to retain customer
  5. Delivery and change consistently
  6. Fast and better than competition

We had a few factors working in our favor, the business growth and business differentials were adding the ability of the teams to design new elements. Premium and Standard offering were being considered. All of this information started to seep into the Design for the new Mobile Application.


From Business view

  • -????????? Failure was anticipated, recovery procedures were pre-built into release process
  • -????????? Third party integration technology changes were time blocked into 2 week activity
  • -????????? Feature release and Business release were decoupled – A switch to turn on / off a feature was available
  • -????????? Flexibility was offered and made available
  • -????????? All changes were predictable
  • -????????? Beta test data was made available before full release, allowing evaluation
  • -????????? Legacy issues were being addressed and limitations were being addressed with solutions

From Technology View

  • -????????? Infrastructure capacity addition for next level in pipeline
  • -????????? Stack rebuild and addition of platform capability for unique features, scalability and maintainability
  • -????????? API’s were being built for reuse
  • -????????? Standards were being developed to be shared with 3rd party to speed up the integration process
  • -????????? Code clean-up (Which was long overdue) was taking place module wise, improving performance
  • -????????? Bugs were identified and fixed early, Observability additions were supporting investigation
  • -????????? Direct access to customers that were having challenges allowed to fix

Overall View

  • We were nimble in delivering change, with a change every week
  • We are able to respond to market dynamics faster
  • Customer feedback is positive and it is being displayed in volumes
  • We had a long term strategy

The new mobile app building blocks,

  • -????????? Strategy for backend in place and rollout in progress
  • -????????? Technology elements required to build next level of innovation and growth in design and a few elements are in experimentation
  • -????????? New mock ups of user interface being discussed, the look and feel being deliberated
  • -????????? Experimental features being released in the existing mobile application so collect usage and interaction data

Tools:

Priority Sheet

  • An document that had a list of all the changes, requests, requirements and complaints on the mobile application in one place

Delivery Schedule

  • Weekly, every Monday
  • Adhoc for bugs or promotions. Yes, we were now releasing changes for promotions and new feature additions competing with the market

Discussion method

  • Priority – Once a week
  • Release team – Their cadence, generally 30 minute sessions of the technology and operations teams discussing a feature
  • Demo – Twice a week
  • Strategy – Once a month, review the priority and recalibrate

Planning

  • Fixed downtime for changes and maintenance
  • Friday, Saturday and Sunday, Payroll days – Off limits for changes as they were heavy usage periods.
  • Month end and Year Ends – Heightened awareness

Competition

  • Constant evaluation of top 3 banks and their feature list
  • Response time was measured and we maintained a target to be quickest in the market
  • We were not the first in market for many features, but we had the best uptake for many


Tech-stack for Nerds

Programming Language

  • Android: Java, with Kotlin adoption
  • iOS: Swift
  • Web: NodeJS
  • Backend: Java

Software Stack

  • Middleware: Proprietary and Spring boot
  • Core: Flexcube
  • Database: Oracle
  • Infrastructure: Exadata
  • Mobile App Insights: Firebase
  • Mobile App Control Plane: Proprietary
  • Metrics and Observability: Custom inhouse development, Grafana



On a side note, we had some beautiful and simple designs of the Mobile Application, Features, MVP and Documentation. If you need to have a discussion, Do reach out.

#buildvsbuy #bank #mobileapp #customerexperience #chaos #engineering #hiring #process #people #simple

要查看或添加评论,请登录

Rohit Dhawan的更多文章

  • Part 6 - Deploy and Repeat OR Fail and reinvent

    Part 6 - Deploy and Repeat OR Fail and reinvent

    To initiate the redesign of the mobile application, there are many forces that have to align. And certain factors that…

  • Part 5 - Innovate for tomorrow

    Part 5 - Innovate for tomorrow

    "Accepted methods become an established mode of operation in companies but even they often fail to generate the…

  • Part 4 - Leap of Data

    Part 4 - Leap of Data

    When you shed light, you realise that there are many discoveries to be made. We were collecting a mountain of data.

  • Part 3 - Today fixed to build tomorrow

    Part 3 - Today fixed to build tomorrow

    With the positive scenarios all the deviations and spatial challenges were coming to the surface. An environment that…

  • Part 2 - The Outreach

    Part 2 - The Outreach

    Trust is built with continuous reinforcement. Any difference in opinion can create friction and often people become…

  • Part 1 - The Chaos of the Problem

    Part 1 - The Chaos of the Problem

    Technology adoption does not have emotion. But the emotion from Technology failure brings to fore the missed…

  • Prolouge - What does a successful business need? Happy Customers

    Prolouge - What does a successful business need? Happy Customers

    Over a conference for all the banks in the country, at a Dinner table, we had a strong conversation on how do we in a…

社区洞察

其他会员也浏览了