The IT department is probably the single most important contributor to business success for companies in the financial services sector. But for those outside the technology field, IT management often appears to follow its own rules, and make little sense when compared to other silos in the organisation.  Yet potentially costly (and potentially risk-inducing) mistakes and misunderstandings in this area are common, and it’s essential that the non-IT functions within the enterprise understand the workings of this vital “engine-room”.

For those who work in areas other than IT, The Top 10 Mistakes in Financial IT – and How to Avoid Them highlights some of the traps into which non-IT management can fall in the understanding of IT departments, and points out how such mistakes can be avoided. Knowledge is power: and this report enables those outside the IT world who need to understand and work with IT and its often opaque working methods and culture to get under the skin of and engage with this most vital of functions.  

Illustrated with case studies, the report examines common mistakes that potentially lead to risk, such as: falling for hype, wrongly forecasting the future, inertia, promoting the wrong people, mistaken outsourcing decisions, mistaking the biggest brand for best – and its opposite, going it alone, cultural issues around the world, belief in the infallibility of IT, and unreasoning faith in IT project plans.

If any or all of these danger signs sound familiar in your organisation, The Top 10 Mistakes in Financial IT – and How to Avoid Them could save your enterprise from falling into the traps, through analysis of the issues and spotlighting the business, reputational, legal, compliance, and operational risks faced by both retail and investment banking, as well as by more general financial institutions, if these traps are not avoided.

The author has experience of working in the technology departments of several major financial institu tions, and has witnessed many of these management decisions at first hand.

He has also drawn on the experiences of friends and colleagues in the same field, and used these to illustrate the principles involved. The names of the institutions, etc. involved in these case studies are not given – but they are some of the biggest names in the business.

Published March 2012
ISBN 978-1-907720-51-2
106 pages
For full contents in PDF format, click here
For the FREE Introduction,  click here

PDF UK £800 + VAT/ €960 + VAT/ RoW $1,250
Top 10 Mistakes in Managing IT - PDF £960.00 Add to Cart

Euro and dollar prices are illustrative. Euro and dollar prices will be calculated using current exchange rates at checkout. VAT is chargeable on UK and EU orders; prices shown include VAT. This will be applied or deducted at checkout as applicable.

Key issues

There are 10 basic categories of mistake that are often made when attempting to manage IT departments by managers who come from outside the IT field. Not everyone is guilty of all of these, of course, but too many people make at least one of these mistakes.

■     Mistake #1: Falling for the hype. Being too ready to believe the journalists’ stories that appear in non-technical magazines, and thus vulnerable to swallowing the technical hype that appears.

■     Mistake #2: Viewing the wrong channels through your crystal ball. Making wrong guesses as to the future – slightly different from the section above, with an examination of cloud computing – at the time of writing, one of the really hot-button topics in enterprise IT.

■     Mistake #3: Inertia. The opposite is also a mistake – assuming that the past will continue with- out changing. Hanging onto past practices for their own sake is as much of a mistake as embracing change for novelty’s sake.

■     Mistake #4: Promoting the wrong people. Staffing IT departments at managerial level (and even below this) can be a difficult proposition for managers who are not familiar with the ins and outs of technology. Some of the staffing issues discussed in this section are unique to IT departments.

■     Mistake #5: Seeing outsourcing as a cost-cutting silver bullet. Outsourcing  and offshoring are common terms, and these practices are often seen as easy ways to save money within the enterprise. Often, though, a careless implementation  of these can end up costing more, rather than less, money and end up being a liability to the bank.

■     Mistake #6: Mistaking biggest for best: Brand names are big in IT, and the temptation is always to go with the most common names in order to minimise risk. Though there are usually advantages to doing things this way, there are often alternatives that can be more cost-effective than the ‘tradi- tional’ choices.

■     Mistake #7: Going it alone. By contrast, going your own way, rather than following the estab- lished route can also land you in trouble if the common-sense rules are not followed.

■     Mistake #8: Expecting the world to be the same all over. It’s very tempting to assume that the world is just like the place where you have your headquarters. However, there are many differences that you may discover as soon as you start to take your business overseas, and not all of them are listed in the guidebooks.

■     Mistake #9: Believing computers are infallible. Trusting too much in the power of technology to do things right every time can be a terrible mistake. This section explains some of the ways in which the risks associated with over-confidence in technology can be mitigated.

■     Mistake #10: Believing in IT project plans. Projects are notorious for their complexity, their late deliveries and their cost overruns. Many of these undesirable characteristics can be avoided if you know the danger signs.


What’s in the report?
A cautionary tale
The moral of this story
The purpose of this report

Mistake 1:     Falling for the hype
The myth  generation machine
The world is smaller than we think
Social media
Lessons from social media
Smoke and  mirrors?
Product leaking
Beware the “good idea”
The seduction of new ideas
Example – a bank bites the Apple
Early adoption – The dangers of 1.0
Risk aversion  can pay off
Key points summary  

Mistake 2:     Inertia  
Transient  technology
Hard disks
Backup technology
Changes in management and  development practices
Database systems
Farewell Novell
Application  development – changes to the model  
The dilemma of change
Example: Bank looks through wrong Windows
Vendors drop support
The 2008 challenge and  beyond
IT staffing issues
Potential  IT  budget issues
Key points summary

Mistake 3:     Viewing the wrong channels on your crystal ball
Seeing the future
Example: A bank backs the wrong technology horse  
Expensive blind alleys
Cloud computing
Advantages – flexibility, efficiency, cost
Risks – security,  compliance, business,  operations, reputation
Worst-case  scenarios
Continuity management
Example: A sudden break in continuity
Key points summary

Mistake 4:     Promoting the wrong people
Why does  IT not  follow the rules?
Mismatching competences: technicians vs. managers
Wider effects
Certification is not  necessarily  the answer
Non-technical certification  
Particular issues for the financial sector
Advanced  IT requirements and  their implementation
Industry  scrutiny  and  oversight .
One solution: Microsoft’s “Distinguished Engineers”
Lessons for financial services  
Promotion “creep”
Key points summary  

Mistake 5:     Seeing outsourcing as a cost-cutting silver bullet
The three  types of outsourcing
Specialist consultants
Project teams  
Routine functions
The individual consultant  
The job security trap
Example: The embedded consultant  
Bringing in a specialist team  
Potential  problems
Language skills
Ultimate  responsibility
Outsourcing the whole function  
Security issues
Chain of command issues  
Differences in business style and customs
Example: Bank’s systems lost in translation  
Key points summary  

Mistake 6:     Confusing biggest with best   
Case study: Microsoft Word
A technical Indiana Jones
Other “big” dinosaurs
Microsoft vs. Apple
Pricing models
Vendor inducements
Alternatives can offer a better deal
Some implications for financial institutions
Other minority  supplier  issues
Key points summary  

Mistake 7:     Going it alone  
Financial institutions and IT innovation
Invent the wheel, but not  the bearings  
Disadvantages to carving  your own path
Example: Reinventing a bank’s payroll system  
Why do people do it?
“Off-the-peg” can be a good fit  
Open source  is not  a sticking plaster
Beware the “dead end”  trap
So where  does  innovation come  from?
Innovation carries responsibilities for banks
Key points  summary

Mistake 8:     Expecting the world to be the same all over
Living and working  abroad
Local differences in the IT world
External suppliers
Just because they speak English, it doesn’t mean you should  hire them
Example: A little local language difficulty
Global standards
What’s in a name?
Different ways of working
Example: Fire regulations
Asia ex-Japan
Key points  summary

Mistake 9:     Believing computers are  safe  and reliable
Computers can cause  their own problem areas
Example: The Tokyo Stock Exchange  
The case for IT audit
Documentation is vital  
Programming prototyping and language
The dangers of objects
Objects – an example
Excel errors
Key points summary

Mistake 10:     Trusting IT project plans
“Creeping featuritis”
Bill padding  
Example: Bank’s application too complex for purpose
Is programming an art or a science?
Throwing programmers at project overruns
Speed  for its own sake
Scheduling testing and  debugging into the project
Don’t forget  documentation
Key points  summary

Summing up
Scaling up
Understand the other side


Hugh Ashton has lived in Japan  since 1988, when  he arrived from the UK to take up a position with a Japanese documentation  company. Since then, he has worked with a variety of financial institutions, both international and domestic, chiefly working as a consultant documenting and assisting with the definition and implementation of processes and procedures governing IT operations in those institutions.

He is the author of several reports on retail financial operations in Japan, as well as wealth management operations in Japan and Asia. His reports on Japanese industry and business are regularly published on Web sites and in print. His techno-financial thriller, At the Sharpe End, set in 2008 Tokyo against the background of the Wall Street crash, has received critical acclaim.
Published in Current Titles
Thursday, 08 March 2012 10:02

The IT impact of a Euro crisis

Published in News and Views
Sunday, 18 December 2011 11:19

Social mobile payments

Published in News and Views
<< Start < Prev 1 2 Next > End >>
Page 1 of 2