Before Collecting Data,

To solve a problem, you first need to understand what data was gathered, why, and how the problem was approached.
This is especially true for dashboards in the admin (from a user perspective, the My Page). What you want isn't some movie-worthy, dazzling visualization, but a single metric by which everyone can monitor the state of things. Something like a college entrance exam score alongside its grade table.



Applied to real work,
If the first-stage goal is "collect data," then the core metric in operations must sit not on inflow and retention, but on data validity.
-> We need to review product-validation metrics before market-validation metrics.







Thoughts I jotted down after seeing somewhere the line "handling a tool well and finding meaning to define a problem are two different things," now with a fresh idea layered on top...