Steve Leegood

Steve LeegoodSteve is a thought leader and world renowned expert in financial market information. He has developed Bryok's ground-breaking integrity metrics, which provide unique insight into market irregularity and he leads Bryok's anomaly detection research programme.  Steve is familiar with all the main market monitoring tools and applications and has defined the requirements for the next generation of surveillance systems.  He is a speaker at industry conferences and commentator on market developments.  Steve leads Bryok’s campaign for cross-venue and cross asset-class surveillance.

Steve heads Bryok’s research into the next the generation of surveillance techniques.  Bryok's Colucida product pioneers the use of innovative and advanced statistical methods to enrich market data and detect market anomalies.

Steve's 30 year career has seen him involved with some of the most challenging developments at the leading edge of IT.    Steve directed Logica's global business in the finance sector, with responsibility for several thousand staff in 26 countries, covering retail finance, insurance, asset management, funds transfer, central bank systems and all aspects of the securities industry.   He managed Logica's strategic relationship with Reuters and ran Logica's business in trading and exchanges.   With Logica, Steve personally led the development of the first UK electricity trading system (for PowerGen) and provided systems for EMCO (Electricity Markets Co, now M-co) in New Zealand.

Steve is a senior strategic business executive, technical architect and problem solver. He has many years’ experience in successfully making technology work for the benefit of business. He initiates and leads change, identifies opportunities and innovatively solves problems.

 

© Bryok Systems Limited 2013

200 OK

OK

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.