Don’t ever assume that someone will “know what you mean”.
- Be specific
- Define metrics
- Specify time boundaries
How many people actively use Sushi?
How many addresses have transferred SUSHI on Ethereum in the last 90 days?
Good answers come from good questions. Here’s an example of a question that is seemingly simple but can be improved:
v0: How many people actively use Sushi?
The original question has many interpretations: SUSHI the token? SUSHI the dex? What is a person? Are we talking Ethereum? What about Polygon?
v1: How many addresses actively use the SUSHI token on Ethereum?
What is "active"? What is “use”? These terms can (and will) mean different things to different people. It doesn’t matter what definition you use as long as you communicate your expectations. Alternatively you can ask for the metric to be defined as part of the question.
v2: How many addresses have transferred SUSHI on Ethereum?
Specify time frame.
We still haven’t fully defined “active”. Specifying time makes the result easier to understand, don’t rely on the person answering the question to specify time for you if you didn’t ask them to.
v3: How many addresses have transferred SUSHI on Ethereum in the last 90 days?
Bonus: Add context in details.
Atomic level specific questions may look generic. It would be easier for the community to understand the impact and insights the metrics can reveal behind. Giving more context for the question you proposed can enlighten and interest more hashpower from analytical minds!