Diagnose stalled enterprise multi-workload workspace expansion
Broadening use is rarely just a product question or just a workflow question.
The same usage pattern can reflect readiness, value, friction, or a deliberate choice to remain focused.
“We have plenty of activity, but I can’t tell whether we’re expanding or just busy.”
Thin Prasert · Head of Data Platforms
Runs a central data platform whose teams use different workloads with uneven adoption.
What pulls against what
- activity growth vs. meaningful expansion
- speed to action vs. causal learning
- common metric vs. customer-context variation
- product interpretation vs. workflow reality
What is at stake
Without a shared definition of expansion, teams can optimize activity that does not deepen customer value. The first decision is what outcome deserves to be learned toward
Why Databricks
At Databricks, this can matter because enterprise value often develops through connected analytics workloads rather than a single isolated use case.
Written for
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.