Rewrite a Data Request Into a Purpose-Limited Spec

A team requests 'all customer data' to build a churn model for proactive retention offers. Move from broad availability to minimum justified use: name the decision, trim the fields, limit access, set retention, and document what is out of scope. The common trap is to approve a warehouse-scale extract first and ask whether the fields were necessary only after analysts have started experimenting with them. Before Pull profile data, support transcripts, location history, account notes, and marketing interactions for everyone. After Use only the operational fields needed for the retention decision, restrict analyst access, and explicitly exclude free text until…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in