ResumeFlow: Ambient Task-Resumption Prompts for Knowledge Workers

I built a small return-to-task tool: does a saved next-action note beat a timer alone?

The distinction I would test is whether the note is doing recall or doing permission. Your framing is that the timer says how long and the note says where, recall. But in practice the expensive part of returning to a task is not usually having forgotten the state, it is the small unwillingness to re-enter it, and a concrete next action mostly beats a vague one because it is small enough to start without deciding to. If that is what is happening, then the note's value is proportional to how trivially actionable it is, not how completely it describes the state. Which is testable: ask people to write one deliberately detailed note and one deliberately tiny one, and see which one they actually act on. The other thing I would instrument is whether they read it at all. Your first commenter has already put a finger on it. If writing the note is doing the work, you have built a journalling prompt rather than a return tool, and that is a different product with a different shape, it would want to be fast to write and could be terrible to read. One design note from a different corner. Anything the user must dismiss gets dismissed reflexively within a couple of weeks, and anything ambient that asks nothing survives for years without producing compliance. Timers sit on the demanding side. If your return note ends up on the passive side, visible when they come back, never requiring acknowledgement, it will outlive the timer it is attached to.

The distinction I would test is whether the note is doing recall or doing permission. Your framing is that the timer says how long and the note says where, recall. But in practice the expensive part of returning to a task is not usually having forgotten the state, it is the small unwillingness to re-enter it, and a concrete next action mostly beats a vague one because it is small enough to start without deciding to. If that is what is happening, then the note's value is proportional to how trivially actionable it is, not how completely it describes the state. Which is testable: ask people to write one deliberately detailed note and one deliberately tiny one, and see which one they actually act on. The other thing I would instrument is whether they read it at all. Your first commenter has already put a finger on it. If writing the note is doing the work, you have built a journalling prompt rather than a return tool, and that is a different product with a different shape, it would want to be fast to write and could be terrible to read. One design note from a different corner. Anything the user must dismiss gets dismissed reflexively within a couple of weeks, and anything ambient that asks nothing survives for years without producing compliance. Timers sit on the demanding side. If your return note ends up on the passive side, visible when they come back, never requiring acknowledgement, it will outlive the timer it is attached to.