A freight brokerage's sales team wants to use shipment and customer contact data collected by the operations team to power an AI-driven lead-scoring tool. No policy currently governs whether data collected for one purpose, dispatch operations, can be reused for another, sales outreach. What should the brokerage do before the sales team proceeds?
Select an answer to reveal the explanation.
Short Explanation
Think of it like borrowing your roommate's car: just because it's sitting in the driveway doesn't mean you have permission to drive it. Data collected for one job, like dispatch, needs a reuse policy before another team, like sales, can put it to work.
Full Explanation
The brokerage should define a data strategy that addresses ownership and cross-department reuse, since the scenario explicitly names the missing piece: no policy governs whether data collected for dispatch operations can be repurposed for sales outreach. Letting the sales team begin using the data immediately, on the theory that it already exists within the company, treats internal existence as automatic permission, but data gathered for one purpose can carry different expectations and constraints when applied to another, and that gap is exactly what's unresolved here. Requiring the operations team to manually approve every individual data request is a workaround that might function case by case, but it doesn't scale and substitutes ad hoc approvals for an actual reuse policy, leaving the underlying gap unresolved. Waiting until the next annual planning cycle introduces unnecessary delay; defining a reuse policy doesn't require waiting for an unrelated planning process to come around. The principle: a data strategy addressing ownership and permissible reuse across departments is foundational and should be established before data collected for one business function is applied to another, rather than relying on informal assumptions or one-off approvals.