Product thinking / DIJION
Does opening an app mean it delivered value?
A worksheet distinguishing first launch, completed tasks and repeat value, with an activation definition tied to user outcomes.
Counting a first launch is straightforward; understanding whether someone accomplished their task is harder. In an illustrative reminder app, creating an account may only be preparation. Establishing a suitable reminder and trusting its outcome is a different kind of value. Connect an activation definition to the outcome the product is supposed to provide.
Describe the user outcome in one sentence
A definition such as viewed three screens counts behavior without explaining the value assumption. Completed an initial task independently may be more meaningful, but the task still needs definition. Avoid assuming that everyone follows the same sequence. Someone importing existing data may reach the same outcome differently from a person starting with nothing.
Separate intent from a confirmed outcome
Scroll the table horizontally to see all columns.
| Signal | Meaning | Necessary boundary |
|---|---|---|
| Tap Save | Intention to act | Not proof of success |
| Persistent save acknowledged | Evidence for task outcome | Interpret in context |
| Return use | Repeated behavior | Not a complete satisfaction measure |
Define scope and exclusions
Specify treatment of test accounts, retries and repeated events from the same operation. Explain event timing when an offline task synchronizes later. Personal contents or message text are often unnecessary for the decision. Keep permission scope, retention and aggregation rules explicit in the data plan instead of expanding collection merely because instrumentation allows it.
Do not let one metric replace the outcome
Activation can rise while incorrect records or support needs also increase. Read completion alongside quality and recovery signals. Document comparison limits whenever the definition changes. The events in this worksheet are illustrative; they are not a claim about tracking installed in Dijion products or growth results achieved by the studio.
Verify the definition through real flows
- Walk successful, failed and offline tasks separately.
- Retry the same operation and inspect duplicate counting.
- List useful paths excluded by the definition.
- Specify what evidence would change the decision.
The deliverable is a defined outcome and its boundary, not merely an event name. Without that clarity, even a polished dashboard can encourage an unsuitable product decision.