83,580
edits
Sign Here: The Enterprise Guide to Closing Contracts Quickly: Difference between revisions
Jump to navigation
Jump to search
Sign Here: The Enterprise Guide to Closing Contracts Quickly (view source)
Revision as of 11:35, 26 October 2021
, 26 October 2021no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary Tags: Mobile edit Mobile web edit |
||
| Line 42: | Line 42: | ||
But these are superficial advantages, if they are even true at all.<ref>The heady days when nudge solved everything are in the rear-view mirror nowadays: Cass Sunstein and Dan Ariely, and even Daniel Kahneman have been on the wrong end of recent invective.</ref> It will leave you with a portfolio of contracts with variable terms, negotiated at cost and time. | But these are superficial advantages, if they are even true at all.<ref>The heady days when nudge solved everything are in the rear-view mirror nowadays: Cass Sunstein and Dan Ariely, and even Daniel Kahneman have been on the wrong end of recent invective.</ref> It will leave you with a portfolio of contracts with variable terms, negotiated at cost and time. | ||
===Iterative, not revolutionary, change=== | |||
{{Quote|Let go of your inner perfectionist for the first version! Try to adopt an approach of getting something — anything — going and improving it from there. Until you use something in practice, it is adding no value. Only when you use it will you understand what works and what doesn’t.}} | |||
This paragraph — which I’ve just spoiled for you — is worth the cover price alone. Among all the thinkpieces about radical overhaul this is the still small voice of calm. Revolutions don’t stick. They get bastardised, perverted — they turn into grim parodies of what they were trying to fix. But the instinct to reframe your processes to systematically make small tweaks and constant improvements; to invert the usual systemantics that usually complicate a process by engineering a system that by operation makes itself simpler — ''that'' is the revolutionary insight here. | |||
Its implications should be unsettling: it argues against banner IT implementations, and bleeding edge [[legaltech]], which are not only Hail-Mary bids for revolution, they positively make subsequent iterative adjustment harder. A rigid & immoveable contacting process is a ball and chain, no matter how whizzy the contract tech that ossifies it. | |||
{{sa}} | {{sa}} | ||
*[[Legal tech landscape]] | *[[Legal tech landscape]] | ||
{{Ref}} | {{Ref}} | ||