Rube Goldberg machine: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 26: Line 26:
You can hardly get rid of the [[negotiator]] — it’s not like they haven't tried ''that'' millions of times already — so pity those poor Romanians: it’s back to wiping tables at Starbucks for them. But good news! we can deploy [[Innovation paradox|innovative]] [[reg tech]] to replace them!
You can hardly get rid of the [[negotiator]] — it’s not like they haven't tried ''that'' millions of times already — so pity those poor Romanians: it’s back to wiping tables at Starbucks for them. But good news! we can deploy [[Innovation paradox|innovative]] [[reg tech]] to replace them!


Here is what they will suggest: get a [[neural network]] to extract the data from the document and populate it into the collateral engine.<ref>It will need [[optical character recognition]] to convert the image back to a digital format of course.</ref>
Here is what they will suggest: get a next-generation [[neural network]] to extract the data from the document and populate it into the collateral engine.<ref>It will need [[optical character recognition]] to convert the image back to a digital format of course.</ref>
 
===4. Setback===
At this point, our hero (the middle manager, that is: always the intrepid hero of any adventure in institutional governance) will suffer a setback: Some curmudgeonly contrarian will ask a difficult question. “hang on: why don’t we change the front end, building a SQL database that our negotiator can enter the data into, rather than a word document? She can then generate the word document from the SQL database, and preserve the digital data in the infrastructure.”
 
Our hero will shake his head. Sadly that is too difficult.
 
Difficult? How is that difficult?
 
It will involve IT spend. Hundreds of thousands of dollars., There is no budget. There is never any budget.
{{sa}}
*[[Innovation paradox]]
*[[Rent-seeking]]
*[[Reg tech]]
{{ref}}