From Wall Street to Slow Street: Navigating the Differences and Embracing Positive Disruption

For the last 20 or so years, I’ve lived and breathed Investment Banking. I’m used to an environment where the pace is relentless, there is always a sense of urgency and time is money.

So, transitioning from the fast-paced world of Capital Markets to the Property Industry over the last few months has been an eye-opener and I’ve realised just how different these two worlds truly are.

For example, in Capital Markets, the time between trading and ‘settlement’ (the settlement cycle) is just a few days, and there are moves to further reduce this to one, or even zero days. In the property industry, the pace is much slower. For example, and as many of us know, it can take three to six months to sell a property. And it is not just the pace, it’s also expensive. Often, multiple intermediaries are involved, which can drive up costs significantly. It’s very different from the streamlined processes I’ve been used to in Capital Markets.

However, with some analysis, I’ve found out that the housing market is being disrupted and it’s finally starting to see some real change.

Firstly, there is the emergence of iBuyers, which benefits sellers by creating greater liquidity in the market and reducing the time a house stays on the market iBuyers are also helping to enhance the valuations model, with a much greater vested interest in getting a property’s price right.

Secondly, schemes like MyIdentity are determined to streamline the onboarding process. Identity Verification, Know Your Client and Anti Money Laundering KYC/AML processes which can currently take days could be reduced to hours or minutes. This will remove the need for each service provider such as lenders, estate agents, and conveyancers to carry out separate checks, making the process more efficient. However, this means the traditional service providers lose a revenue stream, so they are not supporters.

Next, the lenders’ risk departments are changing their ‘blanket’ property risk evaluation models of properties. This could lead to personalised and targeted approach to lending which in turn should increase the number of loans approved.

Then, to reduce rising conveyancing fraud and payment diversion fraud, the Australian PropTech company PEXA have entered the UK market with their standardised and robust settlements process.

Lastly, messaging platforms such as Coadjute are disrupting the market and adding transparency to all stakeholders in the transaction.

As the property market continues to experience positive disruption and stakeholders receive timely information, we can anticipate a significant reduction in the time it takes to purchase a property. While I’m not suggesting were on the next day settle cycles like we see in Capital markets anytime soon, it’s worth remembering that not too long ago, that timeframe was 1 month, and securities were delivered physically by clerks in the city.

The continuous progress in technology and innovation certainly generates anticipation for what lies ahead in the real estate industry. This will, however, greatly impact the operating model and revenue streams of the established industry players. So, it will be interesting to see how they react to these new disruptors.

Featured Post

Unravelling the silo mentality among banks

Among banks silos are commonplace. That and the legacy systems that siloed departments use. In large organizations where many departments represent specialisms, silos exist and are often counter-productive. Modern systems may go some way to changing this. But there is still resistance to both change and new technology.

In her book, The Silo Effect, Gillian Tett, who is also an Editor at the Financial Times, shared how “gigantic financial companies were split into so many different departments, or silos, the leaders who were supposed to be running the groups did not understand what their own traders were doing.”

Things may have improved, slightly, since Tett’s book was published. The rise of the cloud providers, the embracing of agile methodology by many technology enthusiasts in banks, and the increased rhetoric emanating from key banking figures like Jamie Dimon suggesting banks will become technology companies. All these things give the wider industry sector some hope. But change is still taking too long.

Overcoming silos through simplifying processes

One of the companies helping banks to overcome their digital challenges is Fimatix. The company is focusing on supporting companies from the financial services industry to navigate the increasingly complex regulatory demands and other challenges which they face. To increase the support available to financial institutions, David Beatts has been appointed as Head of Delivery at Fimatix.

David has years of experience working within investment banks, outsource providers and as a consultant. He’s been at the coal face working both in business, operations and IT functions and has witnessed a wide and diverse set of changes over the years.

“Investment banks, be they big or small, have generally have had to contend with the same types of issues problems,” namely:

  1. Cost control has driven down overall headcount, required roles and functions to be offshored and reduced investment in technology
  2. Business change has seen Increased trading volumes, more clients, new products and decreasing spreads
  3. Regulation consumes technology budgets and requires new processes
  4. Risk & Control requires headcount increases to cope with additional processes and their oversight.

The impact of this has generally been that after spending technology budgets on regulation, risk & control and revenue generation, there has been little, or no money left for the rest of the organization.

Additionally, David explained, that the way in which the banks grew has created a silo’d structure. Typically, each financial product that the bank offers e.g., equities, rates, FX, and derivatives all grew in a silo’d manner with their own trading desks, technology and support functions. “The focus was growing the business to generate the revenue, with less regard given to overall architecture or any organization efficiencies” Furthermore, these silos are divided into smaller sub-siloes. For example, equities are typically split by cash equities, equity financing, ETF’s and equity derivatives.

The overall impact of this is “a legacy of technology debt, process complexity, inefficient organization structures and lots of manual work. It’s possible to change aspects of a sub-silo, but only making one part slightly more efficient doesn’t change the dial. As a result, many firms are really struggling to unpick the issues and deliver change.”

In short, “Banks are trying to meet 2020’s client and business expectations with 1990’s organizations, processes, data and technology.”

Working efficiently with a digital transformation partner

We are all seeing examples of banks revolutionizing their technology solutions. In the United Kingdom, companies like Thought Machine and Form3 are just some of the firms’ supporting banks in their need to update core banking and other systems. But are they able to overcome the silo effect with these technology solutions?

David shared how digital transformation shouldn’t focus on the role of the CTO exclusively. Yes, the CTO can embrace cloud solutions and agile methodologies, but does that mean that the business has transformed?

“Transformation shouldn’t focus on just the digital aspects and the CTO’s domain exclusively. Technology is certainly a key enabler but it’s not the only pillar that enables change. The technology solution should be identified after you’ve defined what problems you need to solve and how you want to work in the future – not the other way round.”

Why Fimatix can offer the solution

David’s background is a mix of working in, managing and leading operations functions. Working in business management and consultancy. He’s also worked in multiple projects, programs and change functions, not just technology but also business process re-engineering, offshoring, outsourcing, organizational and many others. He’s also a keen advocate of Lean Six-sigma, and believes in the principle of ‘putting the customer as heart of everything you do’.

“I found the idea of building something with Fimatix really appealing,” David highlighted. He pointed out how he could see how the management team at Fimatix wanted to leverage their experience. How they have created products and worked closely with organizations already but want to provide solutions for a wider client-base including financial institutions.

Creating relationships with the business lines and process owners, not just the technology function is the key to helping organisations change. “Asking the CTO to discuss his technology budget is very important. But going to the person that runs the business and helps obtain and direct the technology budget is just as, if not more important.”

David is looking forward to identifying the types of problems that banks have and being able to help them. Not just by giving them another bit of technology, which they have plenty of already, but by helping them create an efficient operating environment. Helping them through the implementation of intelligent automation tools and scalable systems.

This is just one of the opportunities that David feels he will be able to offer clients of Fimatix. Using innovative technology and core transformation capability wrapped around an agile delivery model.

The race to the bottom

The discussion about silos and organizational challenges that banks face has been with us for some time now. Some firms have made some advances, notably delivering silo workflow technology solutions where the processing logic is embedded within the solution. However, in that time those same banks and financial institutions have shed thousands and thousands of employees. They have offshored or outsourced as much as they possibly can. All these factors have led to a situation where real “subject matter experts” are in short supply, making change even harder.

This all against the backdrop of business growth, regulation and risk & control, David voiced his concern about how there is minimal cost saving opportunities amongst many of the investment banks today. “Ask any senior manager and they will say they are running ‘close to the bone’, however, due to the lack of meaningful performance data, this is more a gut feel and not an empirical measurement.”

“So what happens when you get to the bottom of cost saving?” David asked.

The situation calls for a more radical attitude to change, David believes firms will need to employ “a multi-pronged firm-wide approach that addresses all the aspects of the operating model including optimal processes execution, efficient organization structures, a workforce that drives innovation, smart automation tooling and scalable technology. And, at the heart of this will be the understanding of optimum process.”

Unfortunately, the disruption that digitalization has precipitated is not as far along as one might think. Retail banking may be disrupted more than any other sector of banking today, whilst many other financial services sectors are still largely untouched or unchanged. With veterans like David available to help there is every reason to be hopeful though.

Featured Post

The climate reporting challenges facing the financial services sector

In November, digital transformation companies, fund operators and other key stakeholders convened at the annual Fund Operator Summit to consider the major challenges facing the financial services sector in the coming years.

One of the key themes of the discussions that took place emphasised how climate reporting is now more critical than ever. It comes as the Financial Conduct Authority (FCA) progress consultations on additional greenwashing (including restrictions on how terms such as ‘ESG’, ‘green’ and ‘sustainable’ can be used) and climate disclosure obligations, and as the wider regulatory landscape for UK-based financial organisations becomes increasingly complex.

More recently, this included the FCA announcing the formation of a group to develop a an environmental, social and governance Code of Conduct for ESG data and ratings providers, laying the groundwork for the introduction of regulatory oversight over ESG data.

These changes have the potential to significantly improve transparency throughout the financial services sector. Fund operators working in this space will, however, require support – particularly over the immediate term – to develop the systems able to capture the essential data enabling them to stay compliant with the increasingly high standards for ESG disclosure.

This will be particularly important as the greening of the global financial system gathers momentum through initiatives like the independent, International Sustainability Standards Board (ISSB), established as part of the UK’s COP26 presidency, that is developing a global baseline for private sector climate reporting. The publication of final standards for this are expected early 2023.

Digital transformation companies must therefore look to increasingly adapt their strategic approaches with a view to providing these forms of tailored support to fund operators, and companies beyond the financial services sector, helping them to develop an agile approach to data collection. This is a trend that will undoubtedly accelerate as the move towards more robust ESG regulations and reporting continues to grow.

Featured Post

Blue Lights and the Benefits of Digital Transformation

On 7 and 8th of September, Tilly and I had the pleasure of representing Fimatix at the Blue Lights Event in Northampton. The conference marked a fantastic opportunity to catch up, learn from, and share ideas with tech leaders from across our emergency services.

It was brilliant too, to be able to present on the power of digital transformation done right, and on how the pitfalls of projects gone wrong can be avoided. It’s a topic I believe in strongly, so it was great to receive such a positive reception from within the blue lights sector. 

At Fimatix, we’re proud to have built up a successful track record working with blue light and other public and private sector organisations. We know the necessity of ensuring digital transformation is undertaken with the right process and expertise, and just how crucial it can be in modernising, streamlining, and making massive savings when organisations need them most.

We also know how to avoid the sort of project failure that has already led to billions of pounds and thousands of hours lost across the public sector, as well as causing reputational damage when ‘big-bang, go-live’ approaches fall short of expectations. 

For organisations as crucial as our emergency services, this can’t be allowed to happen. It’s why I so valued the opportunity to put forward the benefits of an approach based on diligent preparation, a focus on discovery and innovation, and an agile approach drawn from a deep evidence base, constantly incorporating improvements over the life cycle of a product. 

We know this works. It brought success in our digitisation scheme with the Met Police, which led to over £300m in annual savings. It also ensured we could make critical interventions with the Police National Computer at the Home Office and UK Policing’s Digital Operating Model. 

It’s a huge privilege for us at Fimatix to be able to operate in the blue lights space, and we look forward to continuing our support of the lifesaving work that our police, ambulance, and fire and rescue teams undertake on a daily basis. 

To find out more about how the benefits of blue lights and public sector digital transformation, email Simon Durtnal, CBO at Fimatix, at simon.durtnal@fimatix.com.

Featured Post

Agile Leadership in Practice

I had a great day at Agile Tour London and was humbled to have been asked to present “Agile Leadership in Practice” in the Leadership track of the conference. Drawing from my own experiences of leading Fimatix and client deliveries, I’ve distilled what I’ve learnt (so far)

I believe Leadership in 2019 is about inspiring, motivating and developing people to achieve their goals and in turn the  goals of the organisation. To achieve this, leadership distills out into four main leadership activities that lead to four outcomes.

Purpose leading to motivation

Motivation is crucial to organisational success as motivated people are more productive. All the research says that people are most motivated by a sense of purpose i.e. what they are doing is valuable to others in non-financial ways.  Vision/mission statements have their place but they are subsidiary to purpose in motivating people.

Feedback leading to growth

This has two aspects; the organisation needs feedback from the marketplace to identify new opportunities and improvements to existing services.  Also the organisation needs people to be the best they can. Constructive and positive, timely, feedback enables people to grow and stay motivated.

Delegation leading to empowerment

The people closest to the customer or citizen are the people best able to understand user needs and react promptly to addressing them.  The best way to do this is to give them empowerment, including financial responsibility. To do so, however, an Agile/Adaptive Leader has to make sure that the team is mature enough to accept the responsibility. The way to do this is using one of the delegation models such as Kenneth Blanchard’s situational leadership.

Organisational design leading to culture

Motivation, growth and empowerment are all aspects for getting the right culture for your organisation to thrive.   To enable this to be embedded and sustained all the structures of the organisation, from job descriptions and performance management to corporate governance, align to authentically support and encourage the right behaviours. These structures don’t emerge, they need to be designed and iterated.  If you don’t redesign, the old ways will re-assert themselves.

The last point, in particular, is likely to be controversial in Agile circles that strongly promote “self-organising teams”.  My view is that self-organisation is a useful concept for competent, stable, mature teams where the delegation has clearly been completed.  In most other scenarios it is risky and could exclude many people who like or need clear structure.

For more detail see the slide deck Agile Leadership in Practice or get in touch.

Featured Post

Creating the conditions for Business Agility

Organisations need to constantly adapt in order to succeed. At Fimatix, we believe that (top down) organisations need to understand their customers evolving needs, and invest in the development and delivery of products and services that best meet those needs. We also believe that (bottom-up) delivery teams using user-centred Agile approaches are best placed to understand users needs and to develop and deliver the right products and services to meet those needs. In this article we outline what we mean by business agility, and consider how business agility is enabled by organisations who create the conditions which allow Agile delivery teams to thrive. We also begin to explore the dimensions to be considered by organisations who want to be truly Agile, from the perspective of the people involved.

The case for Adaptive Organisations

In our view, business agility is about the ability of an organisation to adapt in a fast changing world.

Agile is a well used term in the development of software products and digital services, and Agile approaches can help organisations to deliver better products and services to meet customer needs. Regardless of the methodology used, in order to reap the full benefits from Agile approaches, organisations need to create the conditions for Agile teams to succeed and thrive.

As digital becomes more prevalent, and new technologies transform the way organisations engage with their end-users, customers expect to have more influence over how they interact with organisations. They expect their feedback to be valued, and that providers will react to that feedback through rapid improvements in products and services. When their feedback is ignored, customers will move to another provider. Today’s successful organisations are those that are most capable of responding to the needs of their customers (or the citizens they serve) and the marketplace they operate in. We call these Adaptive Organisations. It is the Adaptive Organisation that will retain and grow it’s customer base.

Adaptive Organisations have the ability to take constant feedback (from clients, citizens, suppliers, the wider marketplace….) and improve their products and services in response to that feedback. In order to be adaptive, we believe organisations need to create the conditions which enable their people to execute rapid cycles of learning and adapting: seeking user feedback, making adjustments to products and services, and delivering those to market in a meaningful timeframe.

The Dimensions of organisational agility

In order to create the conditions to allow their people to enable business agility, Adaptive Organisations will need to transform and continuously improve the following dimensions:

  • Product and Service Delivery
    • The push for agility is often driven from here, as delivery teams (software developers, testers, user researchers, designers, delivery managers, product owners….) use agile methods to put the user at the centre of product and service development, and apply new technologies and DevOps approaches to improve speed to market
  • Governance (and management)
    • As delivery teams start doing things differently, learning to fail fast and iterating based on proper research and user feedback, ways of governing and assuring are challenged to remain fit for purpose.
    • Governance processes need to be effective enough to allow accountable stakeholders sufficient transparency to ensure that they are making the right investments and delivering them well, but efficient enough to allow the delivery teams to get on with responding to user feedback and delivering value.
  • Organisational Structure and Culture
    • Adaptive Organisations need to empower their people, trusting them to deliver customer value because they are closest to users and most familiar with their needs. They need to allow time and space for people to innovate, to try things out, take feedback, adjust products and services.
    • Adaptive Organisations need to be structured around the delivery of services to customers, and not around the traditional organisation silos (Finance, HR, Operations) – yes these functions need to exist, but their primary focus should be on enabling their people to support the delivery of customer value.

How this impacts people in the organisation

Your perspective on the Adaptive Organisation, and how you can assist in, and benefit from, the implementation of a user / citizen / customer value focus, will be influenced by your role.

Those of you in Delivery Teams using Agile approaches to build products and services, will often feel frustrated, hamstrung by the mechanisms and structures that delay your progress.  You should realise that the leaders in your organisation want the same thing as you – delivery of value early and often in response to customer and market need.  They just want to protect their investment, and they look for assurance about that.  You can help by explaining how, by putting users at the centre of your product or service development initiatives, and spending appropriate time to understand their needs, you can ensure that you are delivering the right thing. You can outline how iterative and incremental delivery, with frequent demonstration (and delivery) of product, protects the organisation’s investment. Providing easy access to your information radiators, and inviting them to visit you often will help with this.

Those of you in Leadership positions want your organisations to be agile and adaptive, to react to the forces of change – better informed customer and citizen needs, reduced budgets and changing legislation.  You may be frustrated by the slow pace and high cost of change.  You will be concerned about the risk of wasted investment, and the consequences of that in terms of investor, regulator and media scrutiny.  So you look for assurance and appropriate governance to safeguard your investment. If you have good Agile delivery teams, their very approach to developing and delivering products and services will be safeguarding your investment.  They will ask you to empower your best, most visionary people to work with them to deliver what you really need. They will ask for time to explore, make mistakes, learn. They will ask for your patience – don’t expect the false certainty of a two year plan – let them know your desired outcome, give them space to figure it out, help them by removing obstacles and blockers that get in their way. Visit them as often as you can – they’ll welcome you.

Those of you responsible for governing and assuring are caught in the middle of this drive for agility and adaptability.  You are expected to be the brokers between the Sponsors and the Delivery Teams,  facilitating the means for ensuring that money is invested appropriately, and is being used effectively to meet real user needs.

You will need to create the conditions whereby leaders can

  • make decisions about the most important things to do
  • allocate skilled, knowledgeable and empowered people to the delivery teams
  • come and see the progress for themselves

Delivery teams will expect that the information they generate as they work should be sufficient to demonstrate progress and control.
And everyone will expect you to ensure that governance approaches add value and don’t slow down delivery.

The potential for Agile to enable organisational transformation can only be fully realised when leaders, managers and delivery teams align behaviours, and organisations mature beyond focusing on the delivery dimension (using Agile practices to deliver a specific product or service) through to the organisation dimension, harnessing Agile mindset and values to create a learning, evolving, Adaptive Organisation.

Featured Post

Crossing the chasm and beyond

The technology adoption lifecycle (Chasm theory) summarises how communities respond to discontinuous innovation, i.e. new products that require the end user and the marketplace to dramatically change their past behaviour to achieve the promise of equally dramatic new benefits. Past examples of this are fax machines, personal computers, spreadsheets and electronic mail.

The original work from as early as the 1950s has been extended by Geoffrey Moore in his books Crossing the Chasm and Inside the Tornado to include his observation of a large gap between the take up of new technology by technology enthusiasts and the majority market.

In this white paper we consider the Chasm Model and its impact on developing strategy for innovation.

Read the full white paper: Crossing the chasm and beyond

Featured Post

What is the Dynamic Systems Development Method?

In one sentence, Dynamic Systems Development Method (DSDM) is an agile project delivery framework covering all aspects of change delivery from project initiation to benefits realisation.

At the core of DSDM are similar principles and practices to all other agile methods:

  • Breaking business requirements into small components – user stories
  • Prioritising these components according to the business need
  • Delivering, testing and accepting these components in small time windows
  • Delivery through a collaborative team that includes the end users
  • Regular and transparent feedback on both the solution and the process

DSDM adds a number of useful concepts and advantages to the agile body of knowledge specifically:

  • A framework, practices and guidance for getting an agile project started and governed. Proper initiation and governance processes for change are critical for all large organisations and none of the other agile methods recognise this
  • Detailed definitions of the roles in an agile project team which helps people new to agile to transition effectively
  • In particular, DSDM has 3 roles to represent the business which more accurately reflects how most organisations deliver change. This is more nuanced and practical than the Product Owner concept in Scrum
  • More sophisticated prioritisation through the use of MoSCoW guarantees on-time delivery of the Minimum Usable Subset of functionality
  • It embraces business change aspects of a project rather than just focusing on software development and can be used for projects that have no software

Where DSDM typically needs support from other agile methods is in:

  • The detail of software engineering where techniques such as continuous integration, automated testing and code coverage from XP fit smoothly
  • The detail of testing each User Story and Feature (Epic)

For more information on DSDM go to the DSDM Consortium’s website where the full method is available.

Commentary:

I wasn’t expecting to write this blog entry but recent experiences have pointed out to me that many people don’t know what DSDM is and even if they have heard of the term don’t really understand it. This is true even for many at the centre of the agile community who really ought to know better, given that DSDM has been around since 1994, was a founder member of the agile Alliance and an original signatory to the agile manifesto.

The other linked question is “Why is DSDM not better known?”. In my opinion, there are three answers to this question:

  1. The DSDM methodology was, until 2008, only available to paid-up members of the DSDM Consortium so there was an (unnecessary) barrier to adoption
  2. The DSDM Consortium is not as good as marketing as the Scrum Alliance
  3. The Scrum Alliance has the advantage of being based in the US which is the leading market for software development

At Fimatix we use DSDM as the basic framework because it is the only comprehensive end-to-end agile methodology. We understand its strengths and limitations and use other agile techniques to fill gaps.

Featured Post

Agile delivery: focusing on outcomes

Collaborative working, when facilitated by an experienced delivery manager, keeps the whole team focused on an agile delivery. Fimatix delivery managers keep people focused on delivery by involving everyone in creating and updating plans and prioritised backlogs. Working together, and then keeping everything as visible as possible, helps ensure that the whole team stays completely focused on delivery.

Regular retrospectives are important to ensure that the team continually improves their delivery approach. Retrospectives also help new team members feel included as quickly as possible and help surface any tensions so that they can be addressed before they become issues.

Agile delivery: focusing on outcomes.
Agile delivery: focusing on outcomes.

We are strong advocates of the discipline of “done”. By this we mean that the team defines when a user story or user journey is complete and ready to go into production.  Typically a story/journey is done when it has:

  • passed the tests and acceptance criteria agreed when the story was written
  • signed-off by the product manager
  • automated as far as practical
  • integrated into the build so it’s run each time the code is built
  • refactoring of the rest of the code triggered by the new has been completed and the whole build is “clean”
  • the story/journey can be demonstrated working in a “like live” environment with representative data

Having a robust definition of “done” like this means the new user journey (or story) can go live as soon as the service manager decides that it should go live.

This, to us, is the core of continuous delivery. The software should be able to go live at any point but only actually goes into production when the service manager is happy that all aspects of the service including the non-software parts, e.g. assisted digital, are ready.

To this end, we encourage clients to also integrate business change into the delivery teams that look at the non-software aspects of a particular user journey (story) so that these can be delivered at the same time to ensure continuous delivery of the full service.

Featured Post