Outcomes don’t creep

“How do I get my business engaged in the work we are doing with data?”

Many ways to address this challenge. But here’s a simple place to start:

  • Replace Requirements Gathering with Outcome Gathering.

This is a fundamental shift in how data professionals interact with business teams. It changes nearly every question you ask.

It moves you from asking about what they want to asking about what they are trying to accomplish.

Instead of collecting detailed requirements about specific visualizations, data fields, or data latency. You get to ask about desired outcomes.

It shifts the conversation from being about technical details to being about business questions and opportunities. If you want the business team to be more engaged in data, then entering their domain with business-centric questions is a powerful posture.

A powerful side-effect of this approach? Scope creep disappears. No longer are you left fighting about whether a specific data point was included in the requirements gathering. Instead, both parties are focused on delivering an outcome.

And outcomes. Don’t. Creep.

I’m glad you are here,

Sawyer

Previous
Previous

You are getting the results you designed for

Next
Next

A data platform always exists in this tension