The article, Unveiling the Project Soul: Navigating the Journey of "Why", contains an example to get to the core benefit. This table provides more details about this approach. It is originally referenced by Eddie Shleyner.
Product / Feature | New data pipeline |
|
“So what?” | Existing data pipeline is old and monolithic | Surface benefit |
“So what?” | Inflexible to adapt to new data types | dimensionalize |
“So what?” | New products were bypassing the existing pipeline and only sending a fraction of the data into the pipeline, sending the rest to a separate data store and dashboard | dimensionalize |
“So what?” | Data from the different products were on multiple dashboards | dimensionalize |
“So what?” | Adds development time parse and filter appropriate data, make a new dashboard, and takes weeks to train the entire customer-facing team to detect incidents and dev support could not always be centralized | dimensionalize |
“So what?” | The time-to-market for new data types is very long | dimensionalize |
“So what?” | Can take a long time for the company to be “best in class” when there are these very long delays in adding these products/data types | Core benefit |
Member discussion