Innovation: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
Tags: Mobile edit Mobile web edit
No edit summary
Tags: Mobile edit Mobile web edit
Line 1: Line 1:
{{a|g|
{{a|devil|
[[File:Clarice and Lecter.jpg|450px|thumb|center|No! She ''covers'', Clarice!]]
[[File:Clarice and Lecter.jpg|450px|thumb|center|No! She ''covers'', Clarice!]]
}}:“''Major innovation comes, most of all, from the unexplored no-man’s land between the disciplines.''” — {{author|Norbert Wiener}}, quoted by {{author|James Burke}}
}}:“''Major innovation comes, most of all, from the unexplored no-man’s land between the disciplines.''” — {{author|Norbert Wiener}}, quoted by {{author|James Burke}}


 
If you want to wreak innovation at ''your'' shop, consider yourself Clarice Starling. Face up to your Lecter.
If you are want to wreak innovation at ''your'' shop, consider yourself Clarice. Face up to your Lecter.


:'''Lecter''': First principles, Clarice. Simplicity. Read {{author|Marcus Aurelius}}. “Of each particular thing ask: ''what is it in itself? What is its nature?''” What does she need, this [[legal eagle]] you talk about?
:'''Lecter''': First principles, Clarice. Simplicity. Read {{author|Marcus Aurelius}}. “Of each particular thing ask: ''what is it in itself? What is its nature?''” What does she need, this [[legal eagle]] you talk about?
Line 16: Line 15:
:'''Lecter''': No. ''We begin by covering the arse we see every day.'' OUR OWN ARSE, Clarice. Don’t you see people extemporising to explain why it wasn’t their fault? And don’t your make excuses to avoid responsibility for the things you didn’t pay attention to?
:'''Lecter''': No. ''We begin by covering the arse we see every day.'' OUR OWN ARSE, Clarice. Don’t you see people extemporising to explain why it wasn’t their fault? And don’t your make excuses to avoid responsibility for the things you didn’t pay attention to?


Every story can be boiled down this: once there was a problem and, for better or worse, it got resolved. It mainly be triumphant or tragic, but there must be an outcome.  
Every story can be boiled down this: once there was a problem and, for better or worse, it got resolved. It may be triumphant or tragic, but there must be an outcome.  


Storytellers who don't get to grips with this fundament — who allow something other than ''resolution of the problem'' to drive their narrative — write unsatisfying books. To not resolve the problem — ''eventually'': we all love a bit of will-they-won’t-they suspense as we go — is literally what it means to not satisfy.
Storytellers who don’t get to grips with this fundament — who allow something other than ''resolution of the problem'' to drive their narrative — write unsatisfying books.<ref>This is why some people find the Lord of the Rings so tedious: all that delving into the history, mythology and language of elves is very clever — and yes, it may document the resolution of a whole raft of ''other'' problems, but it still has almost nothing to do do with the immediate problem of the Hobbits’ quest, beyond providing deep historical context. And as for the Hobbit folk songs, just shoot me. Hold your letters. </ref> To not resolve the problem — ''eventually'': we all love a bit of will-they-won’t-they suspense as we go — is literally what it means to not satisfy.


Business administrators retooling their operations to “modernise” might bear this in mind. The goal is not ''to introduce [[chatbot]]s'', or ''to outsource'', or to ''implement distributed ledger technology'' but to solve a problem.  
Business administrators retooling their operations to “modernise” might bear this in mind. The goal is not ''to introduce [[chatbot]]s'', or ''to outsource'', or to ''implement distributed ledger technology'' but to solve a problem.  
Line 24: Line 23:
If someone clutching a hammer assigns you to a [[nail-finding task-force]], consider as you go Marcus Aurelius’ meditation, above.
If someone clutching a hammer assigns you to a [[nail-finding task-force]], consider as you go Marcus Aurelius’ meditation, above.


What is your desired outcome? What is the problem you are trying to solve?
''What is the problem?''
 
What are you trying to fix? We humbly submit it is ''not'' “how to get everyone to use the new document management system we have just imposed on them.”
 
Put down your PowerPoint and write this on a piece of paper.


Put down your PowerPoint and write this on a piece of paper. What function are you seeking to change and why?  
''What is wrong? ''


Some ideas that might occur (there will be a lot of overlap):
Some ideas that might occur (there will be a lot of overlap):
Line 32: Line 35:
*This process is too complicated.
*This process is too complicated.
*This process is too expensive.
*This process is too expensive.
*This process requires too many people and too much oversight.
*This process is too manual.
*This process is too [[waste]]ful.
*This process requires too many people and too much oversight. The overheads are too high.
*This process is too fragile. It keeps breaking.
*This process is too fragile. It keeps breaking.
*This process is is too hard to understand. People keep getting it wrong.
*This process is is too hard to understand. People keep getting it wrong.

Revision as of 09:43, 5 December 2020

No! She covers, Clarice!
In which the curmudgeonly old sod puts the world to rights.
Index — Click ᐅ to expand:
Tell me more
Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.
Major innovation comes, most of all, from the unexplored no-man’s land between the disciplines.” — Norbert Wiener, quoted by James Burke

If you want to wreak innovation at your shop, consider yourself Clarice Starling. Face up to your Lecter.

Lecter: First principles, Clarice. Simplicity. Read Marcus Aurelius. “Of each particular thing ask: what is it in itself? What is its nature?” What does she need, this legal eagle you talk about?
Clarice: To innovate!
Lecter: No! That is incidental. What is the first and principal thing a lawyer does? What needs does she serve by “innovating”?
Clarice: Er ... chatbots? ... document assembly? ... legal reference data? ... MIS... Sir —
Lecter: NO! She covers! That is her nature.
Clarice: Covers? Covers what?
Lecter: ARSE Clarice, ARSE! And how do we cover arse, Clarice? Do we seek out arse to cover? Make an effort to answer now.
Clarice: No. We just...
Lecter: No. We begin by covering the arse we see every day. OUR OWN ARSE, Clarice. Don’t you see people extemporising to explain why it wasn’t their fault? And don’t your make excuses to avoid responsibility for the things you didn’t pay attention to?

Every story can be boiled down this: once there was a problem and, for better or worse, it got resolved. It may be triumphant or tragic, but there must be an outcome.

Storytellers who don’t get to grips with this fundament — who allow something other than resolution of the problem to drive their narrative — write unsatisfying books.[1] To not resolve the problem — eventually: we all love a bit of will-they-won’t-they suspense as we go — is literally what it means to not satisfy.

Business administrators retooling their operations to “modernise” might bear this in mind. The goal is not to introduce chatbots, or to outsource, or to implement distributed ledger technology but to solve a problem.

If someone clutching a hammer assigns you to a nail-finding task-force, consider as you go Marcus Aurelius’ meditation, above.

What is the problem?

What are you trying to fix? We humbly submit it is not “how to get everyone to use the new document management system we have just imposed on them.”

Put down your PowerPoint and write this on a piece of paper.

What is wrong?

Some ideas that might occur (there will be a lot of overlap):

  • This process is too slow.
  • This process is too complicated.
  • This process is too expensive.
  • This process is too manual.
  • This process is too wasteful.
  • This process requires too many people and too much oversight. The overheads are too high.
  • This process is too fragile. It keeps breaking.
  • This process is is too hard to understand. People keep getting it wrong.
  • This process is mostly routine and tedious but has a risky component and therefore requires an expert to carry out the whole thing.


Agents of innovation

The flip side to the perils of complexity and normal accident theory, is convexity of benefit. Innovation, benefit, boon, fiesta is just as hard to predict as catastrophe. But just as likely, if the people you have spotting weights in the gymnasium of disaster are experienced, clever, imaginative, problem solving people.


See also

  1. This is why some people find the Lord of the Rings so tedious: all that delving into the history, mythology and language of elves is very clever — and yes, it may document the resolution of a whole raft of other problems, but it still has almost nothing to do do with the immediate problem of the Hobbits’ quest, beyond providing deep historical context. And as for the Hobbit folk songs, just shoot me. Hold your letters.