Ask 'do you need the DATA or the STORY of extracting it?' before grinding a hard reverse-engineering path
Decision-forcing question that scopes a reverse-engineering project correctly: when a user wants data that's reachable both via a hard self-extraction (decrypt the BLE channel, firmware dump, key capture) AND an easy official route (vendor cloud OAuth API), explicitly ask whether they need the DATA itself or the STORY/capability of having cracked it themselves. If they just need the numbers, the cloud/API path wins in minutes with identical data. If the 'we did it ourselves without the vendor' angle is the actual deliverable (a security demo, a privacy/offline requirement, a hackathon hook), the hard path is justified. Users often conflate the two and sink hours into cracking something when they only needed the values. Surface the fork before committing effort - especially after a long session where sunk cost is clouding the choice.