The idea in practice

Proactivity is useful when it surfaces a relevant change or supports a routine you asked for. Define what deserves a notification and what should stay quiet so repeated checks do not become repeated interruptions.

Try the distinction on a real task

This is an illustrative request, not a customer result or a promise that every connected service supports every step.

Watch for this specific change and keep quiet while the page remains unchanged.

How to apply it

  • Specify the trigger and source
  • Choose a supported cadence
  • Review whether alerts add new information

What to check

Check notification conditions and channel availability.

A mistake to avoid

Do not describe an unchanged page as a new event or treat every scan as something the user needs to hear about.

Using Bris for this work

Bris supports background work, reminders and requested public-web watches. Define the outcome, timing and notification conditions together. Ask for the status when needed and revise or cancel the task if circumstances change. A progress message is not a completed result.