Playbook: Difference between revisions

33 bytes removed ,  29 March 2020
no edit summary
No edit summary
Tags: Mobile edit Mobile web edit
No edit summary
Tags: Mobile edit Mobile web edit
Line 2: Line 2:
[[File:Lear.jpg|thumb|center|A [[playbook]] yesterday]]
[[File:Lear.jpg|thumb|center|A [[playbook]] yesterday]]
}}
}}
A [[playbook]] is a comprehensive set of guidelines, policies, rules and fall-backs for the [[legal]] and [[credit]] terms of a {{t|contract}} that you can hand to the school-leaver in Bucharest to whom you have off-shored your [[master agreement]] {{t|negotiation}}s. She will need it because, being a school-leaver from Bucharest, she won’t have the first clue about the [[Subject matter expert|subject matter]] of the [[negotiation]], and will need to consult it to decide what do to should her counterparty object<ref>As it will certainly do, to all of them.</ref> to any of the preposterous terms your [[risk controller|risk]] team has insisted go in the first draft of the {{t|contract}}.
A [[playbook]] is a comprehensive set of guidelines, policies, rules and fall-backs for the [[legal]] and [[credit]] terms of a {{t|contract}} that you can hand to the itinerant school-leaver from Bucharest to whom you have off-shored your [[master agreement]] {{t|negotiation}}s. She will need it because, being a school-leaver from Bucharest, she won’t have the first clue about the [[Subject matter expert|ISDA]] [[negotiation]]s, and will need to consult it to decide what do to should her counterparty object, as it certainly will, to any of the preposterous terms her [[risk controller|risk]] team has insisted go in the first draft of the {{t|contract}}.


[[Playbook]]s derive from a couple of mistaken beliefs: One, that a valuable business can be “solved” and run as an [[algorithm]], not a [[heuristic]];<ref>This is a bad idea. See {{author|Roger Martin}}’s {{br|The Design of Business: Why Design Thinking is the Next Competitive Advantage}}.</ref> and two, that, having been solved, it is a sensible allocation of resources to have a cheap, uninformed human being run that process rather than a machine.<ref>Assumption two in fact falsifies assumption one. If it really is mechanistic, there is no reason to have a costly, capricious human “helping to manage” — i.e., ''interfering in'' the process.</ref>  
[[Playbook]]s derive from a couple of mistaken beliefs: One, that a valuable business can be “solved” and run as an [[algorithm]], not a [[heuristic]];<ref>This is a bad idea. See {{author|Roger Martin}}’s {{br|The Design of Business: Why Design Thinking is the Next Competitive Advantage}}.</ref> and two, that, having been solved, it is a sensible allocation of resources to have a cheap, uninformed human being run that process rather than a machine.<ref>Assumption two in fact falsifies assumption one. If it really is mechanistic, there is no reason to have a costly, capricious human “helping to manage” — i.e., ''interfering in'' the process.</ref>