“Every system I build for them gets ignored.”
You built a good system. They ignored it. You built a better one. Same. This isn’t rejection of you. An imposed system reads to an ADHD brain as one more demand, and demands don’t carry dopamine. A system they design does, because designing is a problem to solve, and problems are interesting. You hold the outcome. They build the route to it.
State the outcome once, then give the method away. Their design will be worse than yours and they will use it, which makes it better than yours.
Frame their system as a one-week experiment. Permanent decisions feel high-stakes to a brain that fears failing; experiments are cheap.
Let the system run without correction, even where you see the flaw. If it fails small, they fix it. If you catch it first, they learn only that you were watching.
For ADHD brains, autonomy is a regulatory need, not a preference. A system they own generates the engagement an assigned system drains. Holding the outcome while releasing the method is not surrendering authority. It’s putting authority where it produces follow-through.
Building systems for a brain that only runs systems it built.
Name the outcome, hand over the design, let version 1.0 wobble.
Your teen carries their own logistics, and you get to watch them handle it.
Your improvement, halfway out of your mouth. Swallow it.
A system that survives a week because its designer defends it. Grumbling maintenance is still ownership.
Let one small failure land and ask a single question: “What does 1.1 change?”
Take a minute to write this down while it's fresh. Be specific. Real moments help us build better moves for parents like you.
What did their system get right that yours would have missed?
By submitting, you agree we may use your answer, with no name or identifying details, in our content.
Can’t tell the non-negotiable from the negotiable in tonight’s standoff? Give Saige the situation and sort it in two minutes.