News and resources on devops, tools, platforms and APIs for developers and tech leaders in banks and fintechs worldwide.
Banks won't survive the next 20 years – and it's not because of the economy

Banks won't survive the next 20 years – and it's not because of the economy

Wiktor Schmidt, the founder and CEO of Netguru, argues that banks will fail, not because of the economy, but because they can't attract and retain developer talent.

Access to capital? Naaah. Corporate tax rates? No biggie. The biggest concern facing the C-suite is finding access to skilled software developers and engineers.

According to Stripe’s global survey of C-suite executives across industries, 97% say hiring more developers is a priority, with 57% saying developer access is a growth constraint.

Why the developer gold rush? Developers, if used effectively, have the collective potential to raise global GDP by $3 trillion over the next 10 years. I’d be shocked to find a company that isn’t interested in contributing to that market cap.

Though this concern is industry-wide, I believe banks will have the most reason to worry. According to Bloomberg, banks could face obsolescence in five to 15 years due to digital banking challengers like Venmo and Robinhood. In 2017, 6 high-profile banking executives with tech backgrounds left for startups, with the trend continuing into 2018.

So why do banks keep bleeding talent? The three main issues I see:

• Falling into the cargo cult: For many banks, hiring more is seen as the silver bullet solution. In reality, this is confusing the cause with the effect. They think, we’ll redo our office, introduce free lunches, standing desks, and then developers will follow. Banks that believe Silicon Valley perks will solve their development problem, are merely falling into the cargo cult illusion.

• Stuck behind a (non-standing) desk: Banks aren’t innovative enough to attract top developer talent who are keen to work on more cutting-edge solutions. Many of the developers I’ve worked with crave flexibility, balance, empathy, and self-development opportunities (not unlike any other employee). They tend to be more drawn to the culture and the inspiring, ever-evolving environment, instead of toys and perks.

• Too much red tape: A third of developers’ time is spent dealing with layers of legacy infrastructure and bad code, including more than 17 hours a week on maintenance issues, such as debugging and refactoring. Especially as a developer, often working directly with a middle manager, banks simply aren’t set-up in your favor. Instead, you work alongside a legacy employee who often has a “can’t-do” attitude that closely aligns with the status quo.

So what can banks do to improve? Well, first, banks need access to a larger pool of talent and then, they need to build a culture that nurtures an entrepreneurial mindset and out-of-the-box thinking.

Remote work is a good place to start. According to The State of Remote Work report, 63% of people in product and engineering roles work remote at least once a week (21% more than the average). Imagine if banks were able to tap into that talent base?

Flexible conditions open employers up to new talent, while encouraging more diverse points of thought. Instead of being “remote friendly” banks should go all in and be “remote-first,” embedding this mindset into all aspects of their company’s DNA. There is no expectation to go to the office for face-to-face meetings and remote workers still have full access to the company’s resources – anywhere in the world.

44% of developers say that their C-suite is too slow to react to tech trends. As software continues to eat the world, and banking goes more and more digital, processes need to be put in place to hack the new world order. Banks must be able to react quickly and definitively when it comes to jumping on new tech trends like crypto and fintech. One suggestion is to create a Compliance Tech Team, putting them in charge of changing how the company approaches and builds in new technologies.

Beyond that, banks need to be open to experimentation and get comfortable with the possibility of failure. This is a point of friction between the C-suite and lower-level managers. From the top-down, you need to let your people innovate, experiment, and fail without fear of consequences. This nurtures a stronger culture of experimentation, where new ideas are constantly being fed into senior teams. Banks are simply not built for this type of free-thinking, start-up vibe.

I can’t stress enough the need for banks to innovate – and to do so quickly. Instead of prioritizing MBA’s from Harvard, banks need to make a concerted effort to bring in other types of talent – developers who may also be working on their own app, engineers who dropped out of college to focus on coding, and workers who are in small towns all over the world – only then will they have a chance to survive the next 20 years.

Comments: (1)

Melvin Haskins
Melvin Haskins - Haston International Limited - 12 November, 2018, 16:16Be the first to give this comment the thumbs up 0 likes

For this to happen there has to be a replacement to banks in the market. I, for one, want to entrust my savings to an organisation based in my country of residence - I do not like the idea of having to chase an organisation in a foreign country, with different laws and potentially different language when a problem occurs (and problems always occur). Can you imagine someone in France, Germany or Italy entrusting their monies to Amazon or someone similar? I cannot. So where is your solution? All you have identified are problems.