stratascratch
  • Interview Questions
    • Interview Loops
    • Analytical
    • Algorithm
    • ML Coding
    • Stats Coding
    • Visualization
    • Concept
  • Data Labs
    • Discover
    • Your Notebooks
  • Mock Interview
  • Learn
  • Blog
  • Pricing
  • About
Log in
  • Interview Questions

    • Interview Loops
    • Analytical
    • Algorithm
    • ML Coding
    • Stats Coding
    • Visualization
    • Concept
  • Data Labs

    • Discover
    • Your Notebooks
  • Mock Interview
  • Learn
  • Blog
  • Pricing
  • About
Log inSign up
Back to Mini Analyses
  1. Assignment
  2. Your Solution
  3. Solution
  4. Solutions from Users
  5. Discussion

Feature Adoption by Tenant

You must be logged in to download the datasets

Microsoft: Define what it means for a feature to be adopted and report adoption for each customer tenant.

Assignment

The Product Analytics team launched a new in-app feature eight weeks ago in a workspace product sold to organizations, and the account managers want to know how well each customer has taken it up. The team has exported eight weeks of per-user usage for six customer tenants, along with the tenant list, and asked you to decide how "adopted" should be defined, apply it to every tenant the same way, and report the adoption of each.

Note: a tenant is one customer organization's account; its users are the people in that organization who have been given a login. A tenant's licensed seats are the number of logins it pays for, which can be more than the number of logins that have actually been created.

Deliverables

  • The adoption of each tenant, with your definition of "adopted" stated.
  • A short closing report of your findings for the account managers: which tenants have taken the feature up and which have not, and what they should know before quoting the numbers.

Data Description

microsoft_feature_usage.csv has one row per user, covering the eight weeks since launch:

  • user_id
  • tenant_id
  • product_active_weeks - number of weeks in which the user used the product at all
  • feature_weeks_used - number of distinct weeks in which the user used the new feature
  • feature_uses - total number of times the user used the feature
  • first_feature_week - start date of the first week the user used the feature
  • last_feature_week - start date of the last week the user used the feature

microsoft_tenants.csv has one row per tenant:

  • tenant_id
  • tenant_name
  • plan - trial, business or enterprise
  • licensed_seats

Practicalities

You can solve this in Python, SQL, or a mix of both — StrataScratch notebooks support both languages in the same notebook.

Assume this data comes directly from the usage telemetry system and hasn't been cleaned, so review it carefully before relying on the numbers. When something looks off, work out what it is and decide how to handle it; when a definition or a final decision is genuinely ambiguous, choose a reasonable option and explain why. There's often more than one valid way to compute a result, so explain the approach you take and the reasoning behind your choices.

What's assessed: whether your definition of "adopted" fits the account managers' purpose, whether you apply it correctly and consistently across tenants, and how clearly you justify it. There is no single correct number: a different, well-argued definition is a valid answer.