APPLIED DATA ANALYSIS MODULE 01 — WORK LOCALLY

LESSON 1: Turn a vague request into a decision brief
 Read  case_brief.txt  and  stakeholder_questions.txt . Write a 120–160 word decision brief with the six headings. Then propose five questions for the manager; explain how each answer could change scope, metrics or interpretation.   Identify the leading phrase in the original request.  Replace it with a neutral, answerable question.  State one decision the extract cannot support by itself.  Separate a confirmed fact from an analyst proposal.   Save your brief in the learner worksheet. Do not calculate a result or promise that the routing process caused an improvement. 
YOUR RESPONSE / CALCULATION / LIMITATION:


LESSON 2: Define scope, grain and fair comparison windows
 Complete the scope section of  analysis_plan_template.txt . Define grain, unique key, two half-open cohort intervals, observation cutoff, channels/queues, exclusions and three out-of-scope claims.   Where does a ticket created 7 June at 23:00 and resolved 9 June belong?  Would a ticket created 14 June at 23:00 have 72 hours of observation by the supplied snapshot?  What would you do with a ticket created two hours before a live snapshot?  Explain why filtering to resolved tickets would bias the resolution denominator.  
YOUR RESPONSE / CALCULATION / LIMITATION:


LESSON 3: Specify metrics, denominators and guardrails
 Complete  metric_contract_template.txt  for response timeliness, 72-hour resolution and satisfaction. State denominator, numerator or aggregation, units, boundary, missingness and one misuse to avoid.   Verify 8/12, 10/12 and their difference by hand.  Explain the 25% relative change without calling response times faster.  Reconcile email/chat counts to each week's total.  Calculate both rates using Week 1 channel weights.  Describe what a zero-denominator result should display.   These checks test definitions; they do not authorize a causal claim. 
YOUR RESPONSE / CALCULATION / LIMITATION:


LESSON 4: Request the evidence and plan quality checks
 Use the data inventory section in  analysis_plan_template.txt . Map five analytical needs to fields or unavailable sources. Write six quality checks with a pass condition and failure action.   Count blank resolution timestamps and ratings; explain whether each requires deletion.  List three missing sources needed to evaluate routing more credibly.  Rewrite “send all customer conversations” as a proportionate request.  State the strongest analysis that can proceed with the current file.  
YOUR RESPONSE / CALCULATION / LIMITATION:


LESSON 5: Write and review a defensible analysis plan
 Complete  analysis_plan_template.txt  and the metric contract, then write a 150–200 word stakeholder handover. Include five execution steps, four acceptance checks and three unresolved dependencies. Use  review_rubric.txt  before opening the worked plan.   Independent extension:  use fixed Week 1 channel weights to compare the periods, then write two sentences explaining why that result is descriptive rather than causal. Save the source, your own plan and the checks locally. Label the case fictional and the solution guided if you include it in a portfolio; do not represent it as client work. 
YOUR RESPONSE / CALCULATION / LIMITATION:
