Decide what legal should own
The sharpest move here sorts legal roles by the work involved, the judgment required and the trust placed in the person, before any outsourcing decision. A sourcing strategy that starts from cost gives judgment away by accident. One that starts from this map gives it away only on purpose. This seat has the most to gain in the first two futures, where the company keeps the power to change the system’s answer, and the most to lose in the third, where the recorded worry is data handed to others. The map is how it decides, one sourcing choice at a time, which of those futures its contracts are building.
Proposals expected to hold up across several possible futures. Their effectiveness still needs to be tested.
Map roles by work, judgment and trust. Use that map to decide what to retain and what to outsource.
Proposals that only make sense under particular circumstances, such as a failure or access to necessary data.
Build an override switch in case of failure.
Proposals aimed at preserving the ability to respond as conditions change.
Promote “minimum standards of legal engagement.” The record does not specify the standards.
See proposed actions and concerns in each future
| Possible future | Recorded proposal | Concern raised |
|---|---|---|
| 1. The company builds the system | Build a legal service the business can trust, with clear responsibility for its decisions. | A machine cannot carry accountability. |
| 2. Legal directs the network | Keep assembling technology that advances business outcomes with legal judgment. | Continually having to justify spending. |
| 3. Providers own the infrastructure | Choose partners the company can trust and who remain aligned with the business. | Losing control of data handed to others. |
| 4. People own the final say | Encourage new licenses for different kinds of legal practitioners. | The balance between embracing automation and holding human authority is left open, on purpose. |
