In thirteen years as a mechanical engineer I never once saw a plant run without instrumentation. Nobody stood next to a compressor and guessed whether it was within tolerance. We measured, because the difference between “sounds about right” and “is within spec” is the difference between an opinion and a decision.
Then I watch smart professionals run the most consequential system they own, their working life, entirely on guesswork. They know something is costing them. They could not tell you what, where, or how much. This post is about fixing that, and about why functional impairment, the measured cost of ADHD across your life, is a more useful thing to understand than the symptom list everyone starts with.
The question that actually drives decisions
Most people arrive at this topic asking one question: do I have ADHD? It feels like the foundational question, the one everything else waits behind. But sit with how clinicians, funding bodies and workplaces actually operate and you find they run on a different question entirely: how much is this costing you, and where?
There is a good reason for that. The diagnostic criteria themselves require more than symptoms. Plenty of people are distractible, restless and forgetful to some degree. The diagnosis exists at the point where those traits cause meaningful impairment across multiple settings of your life. Impairment is the load-bearing wall of the whole structure. Symptoms without cost are personality. Symptoms with documented, cross-domain cost are a condition worth treating.
And every practical decision downstream keys off the cost, not the label. How aggressively to treat. Whether workplace adjustments are justified. Whether funding applications succeed. Whether the trade-offs of medication are worth it for you. A person with textbook symptoms and mild impairment and a person with the same symptoms whose career, marriage and finances are quietly bleeding out need entirely different responses, and the label alone cannot tell anyone which of them you are.
So the useful project is measurement. Not “am I bad enough to count”, which is the shame-flavoured version of the question, but the engineer’s version: where are the losses in this system, and what is their magnitude?
Why you cannot see your own costs
Here is the difficulty. If you have been living with these patterns since childhood, you have also been compensating for them since childhood, and competent compensation is precisely what makes the cost invisible.
The report gets delivered. What nobody sees, including mostly you, is that it took eleven hours of which nine happened after 8pm in a panic state, that you cancelled dinner with a friend to do it, and that you spent the following morning too flat to start anything. The deliverable is visible. The invoice never gets itemised. Multiply that across every deliverable for twenty years and you get a career that looks functional from the outside while running at a margin cost that would horrify you if it ever appeared on a single page.
The costs hide in categories no one audits. Hours: the true time-to-complete versus what the task should take, and the after-hours work masking the difference. Energy: the recovery time after white-knuckling something, invisible because it looks like laziness even to you. Avoidance: the tax return three months late, the email unopened for six weeks, the invoice you never sent, where the cost of not-doing quietly exceeds the cost of the task by an order of magnitude. Opportunity: the promotion not applied for, the side project abandoned at 80 per cent, the difficult conversation deferred until the relationship absorbed the damage instead. Money: late fees, subscriptions for a folder of dead productivity apps, the loyalty tax of never switching providers because switching is admin.
None of these show up in how you feel on a given Tuesday. They show up in aggregate, which is exactly why they have to be counted rather than sensed.
Run the audit across domains, not just work
The temptation is to measure only the work costs, because work is where the pressure is loudest. Resist it, for two reasons. First, the diagnostic and support frameworks specifically care about impairment across multiple settings, so a work-only record undersells your own case. Second, the domains subsidise each other, and you cannot see the true system cost from inside one domain.
The pattern I see constantly in coaching: work looks fine because home is absorbing the overflow. Every unit of compensation spent holding it together at the office is borrowed from somewhere, and the lender is usually the household admin, the exercise that stopped, the partner carrying the family logistics, or the GP appointment postponed four times. The professional whose performance reviews are excellent and whose personal life is held up by their partner’s executive function does not have a mild case. They have a fully subsidised one, and the subsidy is someone’s marriage.
So the audit covers at least: work, household administration, money, relationships, and health. In each one, the questions are the same. What takes longer than it should? What gets avoided entirely, and what has the avoidance cost so far? What is someone else silently carrying? What would collapse first if you stopped compensating for one month?
Write the answers down with numbers and examples attached. “I struggle with admin” is a feeling. “My tax return has been late three of the last four years, costing roughly $900 in penalties and one significant argument” is a data point. The second one is worth something. This is exactly what the impact assessment walks you through: a structured pass over each life domain that converts twenty years of vague unease into a document.
What the document is worth in a short appointment
Now the practical payoff. Whether you are seeing a GP, a psychiatrist, a university disability office or a funding assessor, you will have their attention for minutes, not hours, and they must make a decision on whatever evidence crosses the desk in that window.
Walk in with feelings and anecdotes and you force a busy professional to do the evidence-gathering themselves, live, through questions, in a time slot that does not allow it. Some will do it well. Many will do what time pressure makes people do, which is pattern-match to the surface presentation. Articulate, employed and composed reads as coping, and coping reads as mild. The better you present, the worse your evidence looks, which is a genuinely perverse outcome.
Walk in with a structured record of impairment across five domains, with examples and rough magnitudes, and you have changed the transaction. The clinician can now spend the appointment interpreting evidence instead of excavating it. You have also future-proofed yourself: the same document does duty later for workplace adjustment requests and funding applications, most of which ask, in their own formats, for exactly this. If assessment is on your horizon at all, pairing the impairment record with a structured symptom screener means you arrive with both halves of what any assessor is trying to establish.
And if assessment is not on your horizon, the audit is still worth running, because you cannot fix losses you have not located. Every client engagement I run starts, in some form, with this measurement, for the same reason every engineering job I ever worked started with instrumentation. The interventions come second. They have to. Until you know where the system is losing, you are optimising blind.
The next step
Set aside one honest hour this week and run the impact assessment. Do it before any appointment, before any application, before deciding anything. Whatever you choose to do next, you will be choosing it with the invoice finally in front of you.
