|
A flow machine of collaborating robots |
Code connecting humans and machine |
Immediate, fully accounted |
| Endless layers. People in endless dimensions. Process multiplication, on top, around, in addition to. Servers after servers, all very specialized, through three or five inconsistent SDLC layers. In code, a jumble of frameworks, libraries, add-ins, products, carve-outs. | Extra extraneous. Concurrent overlapping methodologies. Much of the work, artifacts, deliverables entirely unnecessary. Every SDLC methodology sandwiched together. | Ancient. Processing solutions and methods from forty years ago. Carried through decades by nameless throngs, moved forward another year after year. Creaking, with incredible effort to keep alive. Solutions for problems that are no longer needed, born from architectures long gone. |
| Disconnected islands. Much ado passing from one to another. Data sync issues all over the place. Dozens of copies. No source of truth. Critical functions outside of the platform. Hardly automatic, more like hand-cranked. | Duplicated processes and data. Data integrity issues. Dozens of copies. No source of truth. | Needless complexity. Difficult to operate and expensive to maintain, tough to move forward. |
| IT organizations plumped up. Low productivity. Nothing ever finishes, everything gets redefined and phased. Expanding "projects" and work estimates. Short-term thinking. | Hazy definitions. Lack of common understanding. Half-hearted, stale documents. Folklore and OJT learning. Poor transitions. No one is really sure. | Business operations plumped up. Padding, warping, layering, and shadowing because of system shortfalls. Filling in gaps and around the edges. Workarounds for system weaknesses. Work with no real purpose. |