29 November 2014

John Cant

John Cant - MPI Europe Ltd

36 | posts 146,925 | views 17 | comments

Banking Architecture

A community for discussing the latest happenings in banking IT. Credit Crunch impacting Risk Systems overall, revamp of mortgage backed securities, payment transformations, include business, technology, data and systems architecture capturing IT trends, 'what to dos?' concerning design of systems.

Learning lessons from Murphy at 60

19 January 2009  |  3597 views  |  0

If Murphy’s Law didn’t already exist, they would have had to invent it to help explain what has happened to the financial sector over the past six months or so. Over the years there have been many proverbs or sayings predicting the inevitability of disasters. However, it fell to one Edward Aloysius Murphy Jr. around 1949, whilst working on a series of rocket experiments, to refine it into the Law that bears his name stating that "If there's more than one way to do a job, and one of those ways will result in disaster, then somebody will do it that way.”  Over the subsequent sixty years it has been remodelled through common usage to be closer to “if something can possibly go wrong, it will”. However, what Murphy was keen to promote were the principles of defensive design, for example that one should always assume worst-case scenarios, rather than simply saying disaster was inevitable. So what practical lessons can we learn from this original version of his law given the current market conditions?

Well, it is not a time to cut corners on project or programme management, no matter how tempting it is to see this as a prime area for cost reduction and using fewer, less experienced staff. For example, experience is needed to build scenario analysis (including those worst cases) and mitigation into your risk analysis, and also to follow rigorous issue management and realistic risk based testing regimes for major projects. Take the launch of Terminal 5 as a well publicised example, outside of finance, that shows what can go wrong if this is not done. Also build flexibility into your projects as it is also inevitable that the regulatory regime will change during implementation and, let’s face it, most of your projects this year will have a heavy regulatory influence.

So in conclusion, it is better to do fewer projects, but do them well with experienced staff, rather than attempt more projects with cheaper resources. As Murphy tells us, poor project management and design is simply courting disaster.

TagsRisk & regulationWholesale banking

Comments: (0)

Comment on this story (membership required)
Log in to receive notifications when someone posts a comment

Latest posts from John

Would you ask someone else if they Know Your Client?

26 April 2014  |  1044 views  |  0  |  Recommends 0 TagsRisk & regulationInnovationGroupInnovation in Financial Services

To Tweet or Not to Tweet?

10 November 2010  |  3422 views  |  1  |  Recommends 0 TagsOnline bankingRetail bankingGroupInnovation in Financial Services

Does Cloud reduce operational risk and complexity

04 November 2010  |  5597 views  |  0  |  Recommends 0 TagsRisk & regulationPost-trade & opsGroupFinance 2.0

Do fines change the behaviour of financial firms?

06 October 2010  |  3430 views  |  1  |  Recommends 0 TagsRetail bankingWholesale bankingGroupInnovation in Financial Services

What sport tells us about financial regulation?

01 September 2010  |  4453 views  |  2  |  Recommends 0 TagsRisk & regulationWholesale bankingGroupInnovation in Financial Services
name

John Cant

job title

Managing Director

company name

MPI Europe Ltd

member since

2007

location

London

Summary profile See full profile »
I lead MPI Europe a niche financial sector consulting firm focussing on regulatory driven, risk, ...

John's expertise

Who is commenting on John's posts