Explaining your reminders and systems to people around you
Explain the system, not a defense of yourself: state what the reminder is for and what you need from the other person in one or two sentences, like "that alarm means I'm leaving in ten minutes, I set it so I don't lose track of time." You do not owe anyone a full account of why you need it, only enough for them to work with it.
You are explaining a tool, not defending a diagnosis
When a coworker asks why your phone just buzzed for the third time in an hour, or a partner notices you've set an alarm labeled "leave now" fifteen minutes before you actually need to leave, the easiest path is to explain the function, not the reason behind the function. "This alarm means I need to start wrapping up" tells them everything they need to act around it. It doesn't require getting into how your attention works or why you need external structure that other people manage internally. That's a separate, optional conversation, and you get to choose whether to have it.
It also helps to decide this in advance rather than improvising it in the moment a question actually comes. Deciding once, calmly, what your default short answer will be means you're not composing an explanation under mild social pressure while also handling whatever the alarm was for in the first place.
Match the explanation to the relationship
A stranger or acquaintance needs almost nothing: "sorry, that's just my reminder, one sec." A coworker who sees your systems daily benefits from a slightly longer version, since they'll encounter it repeatedly and a little context prevents recurring confusion: "I set timers for most of my tasks, it's how I keep track of what's next." A partner or close friend, someone who's actually affected by the system working or not working, deserves the fullest version, including what you need from them specifically, like not being interrupted mid-timer or not taking it personally when a reminder pulls your attention away mid-conversation.
Somewhere between those two is a new manager or a roommate you've just moved in with, people who will be around your systems often but don't yet have the shared history a longtime friend does. A short, direct version aimed at this middle group works well: state what they'll notice, why, and what you'd like from them, in three sentences, without turning it into a longer origin story about how you arrived at needing the system in the first place.
A worked example: the alarm that goes off during dinner
Say you're at a family dinner and an alarm goes off reminding you to take a medication. You could ignore it and let it look random, or over-explain with a full account of your daily structure while everyone waits. A middle version works better: "sorry, that's a reminder I need to step away for a second, be right back," handled quietly, with the fuller explanation offered later if anyone's curious, on your terms, in a calmer moment. The goal in the instant is to handle the interruption smoothly, not to use it as the occasion for a bigger conversation you didn't choose the timing of.
When someone offers unhelpful advice about your system
People who don't rely on external reminders sometimes suggest you just try to remember things instead, not realizing that's the exact approach that hasn't worked. A short, factual response tends to close this faster than debating it: "I've tried that, this works better for me." You don't need to convince them the system is necessary. You need them to stop suggesting you drop it, and stating that it's already been tried and rejected usually does that without an argument.
If the same person keeps offering the same advice repeatedly, a slightly firmer version can help: "I appreciate it, but I've settled on this approach, and I'd rather not keep revisiting it." This isn't rude, it's a clear boundary, and most people respect a boundary stated plainly far more than they respect one implied through repeated deflection.
Give people a job, not just an explanation
The most useful version of this conversation, especially with a partner or roommate, includes a specific ask: "if you hear my alarm go off and I don't respond to it, that usually means I got pulled into something else, a nudge helps." This turns an explanation into something the other person can actually act on, which tends to land better than information alone, since most people want to help but don't know what helping looks like until you tell them.
Where Drifta fits
Drifta's reminders get firmer as a deadline passes, and a non-negotiable task can keep re-reminding every few minutes until it's marked done. If someone in your household is going to hear those repeated alerts, it's worth explaining once, briefly, what that pattern means: it's not the phone malfunctioning, it's a task you flagged as one that can't quietly slip. One short sentence covers it, and saves you from re-explaining every time it happens.
For the household side of this conversation, see splitting household tasks when one partner has ADHD and replacing reminders from your partner with a system you own. If the audience is a friend group rather than a household, keeping plans with friends when you forget and run late covers a related conversation.
Common questions
Do I have to disclose I have ADHD to explain my reminders?
No. You can explain the practical setup ("I use timers to keep track of time") without naming a diagnosis, if you'd rather not. What matters for the other person is knowing what the alert means and what to do around it, not the underlying reason.
What if someone teases me about how many reminders I have?
A short, unbothered line usually shuts this down faster than a defense: "yeah, it's a lot, and it's the reason I show up on time." You don't need to justify the number, just note that it's working.
How do I explain a system to a partner without it sounding like a complaint about them?
Frame it as something you're doing, not something they're failing to do. "I'm setting a reminder for this so I don't have to ask you to remind me" lands very differently than "I need you to remind me," even when the task is the same.
This article shares practical organizing ideas. It is not medical advice. For diagnosis or treatment questions, talk with a qualified clinician.