In those days, much of the debate was focused on technologies that supposedly supported one or other mode. For example SOA and SOAP (associated with the industrial-strength end) versus Web 2.0 and REST (associated with the agile end).
But the interesting question was how to bring the two modes back together. Here's one of the diagrams I drew at the workshop.
As the diagram shows, the dichotomy involves a number of different dimensions which sometimes (but not always) coincide.
- Innovation versus Core Process
- Different rates of change (shearing layers or pace layering)
- Top-down ontology versus bottom up ontology ("folksonomy")
- Demand-side (customer-facing) versus supply side
- Different levels of trust and security
Even in 2006, the idea that only industrial-strength IT can handle high volumes at high performance was already being seriously challenged. There were some guys from MySpace at the workshop, handling volumes which were pretty impressive at that time. As @Carnage4Life put it, My website is bigger than your enterprise.
Bimodal IT is now back in fashion, thanks to heavy promotion from Gartner. But as many people are pointing out, the flaws in bimodalism have been known for a long time.
One possible solution to the dichotomy of bimodalism is an intermediate mode, resulting in trimodal IT. Simon Wardley has characterized the three modes using the metaphor of Pioneers, Settlers, and Town Planners. A similar metaphor (Commandos, Infantry and Police) surfaced in the work of Robert X Cringely sometime in the 1990s. Simon reckons it was 1993.
Asked "Isn't bimodal new?" ... god no. It's a bad rehash of ideas from a decade or more ago. Even "tri" modal dates back to 1993.— swardley (@swardley) April 27, 2016
Trimodal doesn't necessarily mean three-speed. Some people might interpret the town planners as representing ‘slow,’ traditional IT. But as Jason Bloomberg argues, Simon's model should be interpreted in a different way, with town planners associated with commodity, utility services. In other words, the town planners create a robust and agile platform on which the pioneers and settlers can build even more quickly. This is consistent with my 2013 piece on hacking and platforms. Simon argues that all three (Pioneers, Settlers, and Town Planners) must be brilliant.
absolutely @mjbrender @richardveryard @TheEbizWizard : all three must be brilliant ... https://t.co/DHMtkmrgzs— swardley (@swardley) May 4, 2016
Characterizing a mode as "slow" or "fast" may be misleading, because (despite Rob England's contrarian arguments) people usually assume that "fast" is good and "slow" is bad. However, it is worth recognizing that each mode has a different characteristic tempo, and differences in tempo raise some important structural and economic issues. See my post on Enterprise Tempo (Oct 2010).
Updated - corrected and expanded the description of Simon's model. Apologies for Simon for any misunderstanding on my part in the original version of this post.
Jason Bloomberg, Trimodal IT Doesn’t Fix Bimodal IT – Instead, Let’s Fix Slow (Cortex Newsletter, 19 Jan 2016)
Rob England, Slow IT (28 February 2013)
John Hagel, SOA Versus Web 2.0? (Edge Perspectives, 25 April 2006)
Dion Hinchcliffe, How IT leaders are grappling with tech change: Bi-modal and beyond (ZDNet, 14 January 2015)
Dion Hinchcliffe, IT leaders inundated with bimodal IT meme (ZDNet, 1 May 2016)
Dare Obasanjo, My website is bigger than your enterprise (March 2006)
Richard Veryard, Notes from the SPARK workshop (March 2006)
Richard Veryard, Enterprise Tempo (October 2010)
Richard Veryard, Why hacking and platforms are the future of NHS IT (The Register, 16 April 2013)
Richard Veryard and Philip Boxer, Metropolis and SOA Governance (Microsoft Architecture Journal, July 2005)
Simon Wardley, Bimodal IT - the new old hotness (13 November 2014)
Simon Wardley, On Pioneers, Settlers, Town Planners and Theft (13 March 2015)
Lawrence Wilkes and Richard Veryard, Extending SOA with Web 2.0 (CBDI Forum for IBM, 2007)