Displaying search results for ""

Digital Transformation: How to make the change in the Banking Industry

Digital Transformation: How to make the change in the Banking Industry

When we talk about digital, it is easy for banks to lose their way in the thicket of buzzwords, fads, and corporate-speak. Digital transformation isn’t about moving traditional banking operations to a new digital home. Instead, it begins by suspending prior opinions about the customer and approaching to know their world in a wholly different way. Walt Disney, Amazon, Google, and Starbucks all ride on great products underlying technologies. They are usually the first to embrace new risks and unveil innovations.

The reason these game-changing companies have been doing that across decades (even before digital technologies were born, or at least the way we know them today) is their legendary focus on customer-centricity.

When it comes to banks – an influential report points out that the top five customer needs – reward me for my business, give me any time anyplace access to my balance, see me not as a data point but a human, educate me on wealth-building knowledge, by analyzing my spends help me save money. Banking leaders can use similar research and first-hand insights, must first work out their vision of customer-centricity and then bring in the power of digital transformation to execute.

Seen either way – the timing is immaculate (or dire)

The inflection point for the banking industry is at hand. For one, 69% of boards of directors think that the pandemic and the economic crisis have already accelerated digital business initiatives. Combine that with large-scale workforce virtualization, a drop in customer cash usage, increased cost optimization initiatives, and heightened pressure on banks to boost responsibility for financial inclusivity worldwide.

Making changes with digital transformation

Once the leadership commits to rethink the entire customer experience, the next area of focus will be automating and personalizing user journeys and actioning friction-less touchpoints; before that, however, a pragmatic step would be to make deep dives into operational and risk processes (front, middle, and back end) and map out possible efficiency and effectivity improvements.

Along with the inward-focused initiatives, digital transformation starts to return rich dividends when banking leaders begin to explore outside-in opportunities. Outside-in thinking can be done in multiple ways – partnering with technology giants as this survey suggests or co-marketing with FinTech’s to collaborate with academia and industry bodies. There is still another way, a daring way through – brainstorming with the competition across the concern areas of – interest rate environment, weak loan demands, dropping credit quality, high customer churn, cost of funds, regulatory burden, and attracting new-age banking – all – are fertile start points for digital transformation strategies.

Sociology and Technology. 

Another talking point for digital transformation is that nothing changes until people’s behavior changes. So, while financial organizations invest millions in profound banking technologies, there must be an equal war-like effort to ensure customers understand the right tools and know-how to use them. Delving deeper into digital literacy patterns will offer bankers valuable insights that will seep into their products and services. A case in point is how DBS bank gained visibility by remaining invisible.

Systematically reinforcing customer behavior changes by employing mass-scale data analytics is one way how the banking industry already is and will create quantum value.

Physical branches gave way to ATMs. Client-server architectures replaced mainframes. Decentralization gained prominence, as did ERP and CRM systems. Cloud and SaaS followed. And now, AI and ML run through data mountains tracing patterns, predicting actions, and offering the next-best offers. If one examines closely, all instances are responses to shifting customer behaviors, societal and value system changes, and the growth of science and technology in our lives. It is the same with digital transformation.

Invert the organization, Exponentialize the value

As the number of inverted firms grows, the way digital transformation creates value changes. Inverting means moving from the value the firm alone makes to the value it helps orchestrate. The most obvious examples are Google, FB, Amazon, Microsoft. Nurturing successful platforms means providing the tools and the market to grow as partners compared to using digital transformation only to improve the efficiency of current operations. A close example of this in the banking industry is platform banking, which is a digital marketplace that provides both banking and non-banking services.

Make the change, but before that, believe in it.

Given their governance mandates, societal function, and cultural perceptions for years now, the banking industry has stayed insulated from the raging digital tsunami.

But if today’s reality is any evidence (banks are embracing AI, Robotic automation, and Advanced Data Analytics), then it is safe to say that the mindset – that’s how things always have been – is finally changing.

View

Microservices I – Microservices vs SOA

Microservices I – Microservices vs SOA

In the recent times, microservice architecture, or simply microservices, has become quite popular. To put it into simple terms, microservices is a characteristic method of developing software systems and applications as a suite of independently deployable, small, modular services in which each service runs a distinct process and communicates through a well-defined, lightweight mechanism to serve a business purpose.

Origin of microservices

Microservices has a profound historical background. The term ‘microservices’ was used for the first time in mid-2011 at a workshop of software architects. After James Lewis laid out  his ideas about microservices in 2012, several IT companies started considering the idea of microservices, and by 2014, large enterprises had started serious discussions about investing in it.

Evolution of Software architecture

In 2014, James Lewis and Martin Fowler collaborated to provide a few real-world examples and presented microservices to the world. The major tenet of a microservice is its ability to take the place of services in a system that function independently from each other, the configuration around business capabilities and using smart endpoints and dumb pipes.

In the original object orientation model from the 1970s, an object is like a little computer that you send messages to and program it to perform tasks. The actor model is established on similar concepts, where the actor is the computer to which you send messages through its mailbox. Both of them are antecedents to the core aspects of microservices.

The idea came from the need of isolation between services. When you run every service in its own process within the same server, it is assured that a contract is followed. If all microservices are run inside the same process, all services will be eliminated if the process is resumed. When each service in run in its own process, it is ensured that only one service is eliminated in case the process is reinstated but if the server is restarted, it will eliminate all the services.

SOA vs Microservices

While many confuse microservices to be another name for Service-Oriented Architecture (SOA), they don’t know that traditional SOA is a broader framework and can mean a wide variety of things. Although they both rely on services as the main component, they vary greatly in terms of service characteristics.

The characteristic SOA model has, for example, more dependent ESBs, with microservices that use faster messaging mechanisms.  SOA also emphasizes on imperative programming, whereas microservices architecture focuses on a responsive-actor programming style.

Microservices Vs SOA

Additionally, SOA models generally possess an outsized relational database, while microservices usually utilize NoSQL or micro-SQL databases.  However, the real variation lies in the architecture methods used to arrive at an integrated set of services in the first place. Also, while SOA places more importance on business functionality reuse, microservices emphasize on the concept of “bounded context”.

Benefits of SOA and microservices over monolithic architecture

Before we discuss the benefits of SOA and microservices over monolithic architecture, it is important to understand what monolithic architecture is. Monolithic architectures work on a single application layer that brings together all the functionalities required by the architecture. It is the simplest form of architecture because it doesn’t involve as many actors as other architectural styles.

The monolithic model works perfectly for small and mid-sized architectures and keeps the complications quite low: the problems usually appear when the architecture needs to scale up feature-wise since the modules are extensively dependent upon each other. SOAs usually incorporate functions into small/mid-sized applications and try to keep the complexity of each app / functionality very low and make them communicate over a set APIs (being them HTTP APIs, asynchronous messaging and so on).

In contrast, microservice capabilities are expressed formally with business-oriented APIs. They compress a root business ability, which are prized assets to the business. The execution of the service, which might require integrations with systems of record, is completely concealed. Dependencies between services and their consumer are diminished by applying the principle of loose coupling. By standardizing on contracts expressed through business-oriented APIs, consumers are not affected by changes in the implementation of the service. This allows service owners to change the implementation and modify the systems of record or service compositions which may lie behind the interface and replace them without any downstream impact.

When positioned properly, a microservices-based architecture or an SOA can bring substantial value to the business. That value can be expressed in both technical debt being avoided and a considerable increase in efficiency.

 

View