Legal is asked to resolve who owns the data, systems, or processes a rival depends on, and the rival's work slows while the review runs.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
A month after losing a budget fight to the forecasting group, the head of the core platform team at a supply chain software company acted on a long-held doubt that the group's training data was clean. It had been assembled over five years from customer feeds, two acquired companies' archives, and a licensed weather dataset. He wrote to the general counsel in his own name, listed the three sources and the contracts he thought were unclear, and asked for a ruling before the model was offered to new customers. Legal froze retraining and new demonstrations while it reviewed. The forecasting team spent eleven weeks reconstructing which customer contracts allowed which uses. The review found two small gaps, which were fixed, and confirmed the rest. Two large prospects had signed with a competitor in the meantime, and the forecasting group's next budget request was smaller.
Why it works
Once ownership is formally in question, the assets lose what makes them useful: outputs cannot be relied on, models cannot be deployed, data cannot be shared, and contracts cannot be extended. The rival also absorbs months of lawyer time, vendor disclosures, reconstruction of where data came from, and remediation, with senior people defending title when they should be shipping product. Tangled provenance is the raw material, as with data assembled across acquisitions or processes documented by departed contractors, along with a referrer who has standing with legal and a rival who cannot work around the assets.
The thinking behind it
Oliver E. Williamson Williamson's The Economic Institutions of Capitalism (1985) describes asset specificity: investments specialized to one relationship lose much of their value outside it, leaving the parties exposed to each other. A forecasting model trained on one company's tangled mix of customer feeds and acquired archives is that kind of asset, and its team cannot easily replace it. Any question about its ownership therefore stops their work, which is why provenance records are their protection.
Jeffrey Pfeffer Pfeffer's The External Control of Organizations: A Resource Dependence Perspective (1978) holds that whoever controls a critical resource gains power over those who depend on it. A rival who depends on contested data or systems is exposed to anyone who can raise a credible question about them. Asking legal to rule turns that dependence into delay without any authority over the rival's team.
When it fits
Platform owners, data stewards, and others with a real question about the provenance of data, code, or processes a rival depends on, and standing to raise it with legal or compliance. It fits where assets were assembled across acquisitions, contractors, or licenses that changed hands, and where using them without clear rights carries real exposure.
How to use it well
Raise the question in your own name, in writing, with the specific concern: which dataset, which contract, which license.
- Ask legal for a ruling, and let it set the scope and the conditions of use during the review.
- Share what you know about the provenance.
- Accept the ruling, including a clean one.
- If gaps are found, offer help fixing them.
The timing is yours to choose. The question has to be real, and it should be one you would have raised about your own team's assets.
What it costs and where it backfires
Questions will follow about why the issue came up a month after a budget fight, and if the answer looks like revenge, your standing with legal and leadership suffers. Deals lost during the freeze are a cost to the company. Everything rests on the question being honest. Once you raise ownership doubts you know are baseless, hide your role behind an anonymous referral, or press legal to freeze use beyond what the exposure warrants, it has become sabotage by proxy.
When it is used on you
Keep provenance records current before anyone asks: licenses, data lineage, signed authorship, especially from contractors. When a review opens, ask for its scope, the specific question, and a target date in writing, request permission to keep using the asset under conditions, and find out who raised it.