Playbook: Difference between revisions

160 bytes added ,  30 August 2019
no edit summary
No edit summary
No edit summary
Line 1: Line 1:
{{G}}{{A|negotiation|}}
{{G}}{{A|negotiation|}}
A [[playbook]] is a comprehensive set of guidelines, policies, rules and fallbacks 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 negotiations. She will need it because, being a school-leaver from Bucharest, she won’t have the first clue about the subject matter of the negotiation, and will need to consult it to decide what do to should her counterparty object to the terms of the contract, as it will certainly do.
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 to any of the preposterous terms your [[risk controller|risk]] team has insisted go in the first draft of the {{t|contract}}, as it will certainly do, to all of them.


[[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 and stupid human being run that process rather than a machine.<ref>Assumption two in fact falsifies assumption one. If it really is entirely mechanistic, there is absolutely no reason to have a human operating 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 and stupid human being run that process rather than a machine.<ref>Assumption two in fact falsifies assumption one. If it really is entirely mechanistic, there is absolutely no reason to have a human operating the process.</ref>