JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES
JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES
JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
160<br />
automatic freeze or unwinding of positions. 882 The CIO used the same approach. If a risk limit<br />
were breached, CIO traders were expected to express a view about the risk in the portfolio and<br />
what should be done, but not to immediately reduce the portfolio’s holdings to end the breach. 883<br />
Over the course of 2011 and 2012, the SCP breached every risk limit that the<br />
Subcommittee examined, but none of those breaches led to an analysis of whether the portfolio<br />
was engaged in overly risky trading activities. Instead, CIO personnel, including Javier Martin-<br />
Artajo, head of the CIO’s equity and credit trading operation and the first line manager of the<br />
Synthetic Credit Portfolio, repeatedly challenged and downplayed the significance, validity, and<br />
relevance of the various metrics used to quantify the risk in the SCP. 884 Ms. Drew and Mr.<br />
Macris held Mr. Martin-Artajo in high regard, and put a great deal of confidence in his<br />
analysis. 885 The CIO’s risk personnel did not express a countervailing view. 886<br />
With hindsight, the JPMorgan Chase Task Force provided this negative assessment of the<br />
CIO’s risk management structure:<br />
“For a significant period of time prior to the first quarter of 2012, CIO was<br />
subjected to less rigorous scrutiny than client-facing lines of business. The lower<br />
level of oversight engendered weak risk management and infrastructure within<br />
CIO, which performed ineffectively at a time when robust, effective controls were<br />
most needed. Granular limits were lacking, and risk managers did not feel<br />
adequately empowered.” 887<br />
C. CIO Risk Management Personnel<br />
Although the CIO was not a client-facing business, it managed as much as $350 billion in<br />
assets and oversaw a trading book that was among the largest in the industry. 888 Yet the CIO did<br />
not have a Chief Risk Officer until 2012. The position of CIO Chief Risk Officer was vacant<br />
through 2011. 889 During the key months of January through March 2012, Irvin Goldman was<br />
new to the position, still learning the ropes, and did not respond in a vigorous way to CIO<br />
breaches of various risk metrics. Peter Weiland, the CIO’s senior market risk officer, told the<br />
Subcommittee that it was not his job to enforce the risk limits. 890<br />
When he was informed of limit<br />
882<br />
Subcommittee interview of Jamie Dimon, JPMorgan Chase (9/19/2012).<br />
883<br />
Subcommittee interview of Ina Drew, CIO (12/11/2012).<br />
884<br />
See, e.g., 3/8/2012 email from Javier Martin-Artajo, CIO, to Ina Drew, CIO, and others, “CIO CRM Results,”<br />
JPM-CIO-PSI 0008773-8775, and discussion below.<br />
885<br />
Subcommittee interview of Ina Drew, CIO (9/7/2012); JPMorgan Chase Task Force interview of Achilles Macris,<br />
CIO (partial readout to Subcommittee on 8/28/2012).<br />
886<br />
See 2013 JPMorgan Chase Task Force Report, at 100, and discussion below.<br />
887<br />
2013 JPMorgan Chase Task Force Report, at 94.<br />
888<br />
Subcommittee interview of Michael Cavanagh, JPMorgan Chase (12/12/2012). See also testimony of Jamie<br />
Dimon, Chairman & CEO, JPMorgan Chase & Co., “A Breakdown in Risk Management: What Went Wrong at<br />
JPMorgan Chase?” before the U.S. Senate Committee on Banking, Housing, and Urban Affairs, S.Hrg. 112-715<br />
(June 13, 2012), http://www.cq.com/doc/congressionaltranscripts-4105471 (“Here -- here are the facts. We have<br />
$350 billion of assets in CIO.”).<br />
889<br />
Subcommittee interview of Irvin Goldman, CIO (9/15/2012).<br />
890<br />
Subcommittee interview of Peter Weiland, CIO (8/29/2012).