Attention Audits at Year Ten: A Gleamcore Sustainability Report

Ten years ago, I started running attention audits with a small group of colleagues. We'd sit in a circle, set a timer, and try to notice where our minds went. It felt awkward at first. But we kept at it, and the habit stuck. Now, a decade later, attention audits show up everywhere—in coaching calls, classroom warm-ups, even in the corporate wellness decks I get forwarded. People ask me: does this actually work? The honest answer is: it depends. This report is my attempt to lay out what I've learned from using attention audits consistently for ten years, what works, what doesn't, and where the whole idea falls apart. If you're new to the concept, start here. If you've been at it for a while, skip ahead to the anti-patterns—you'll probably see yourself.

Where Attention Audits Show Up in Real Work

In the therapy room: a therapist's check-in

The therapist notices the client's shoulders creeping toward the ears. Mid-sentence, she pauses her own listening and runs a silent scan—where did my attention go? Three minutes ago she was tracking the client's grief narrative. Now she's mentally composing a grocery list. The scan takes ninety seconds: body tension, emotional resonance, the thread of the client's last phrase. She names it internally, returns to the thread, and the session deepens. That's an attention audit in the wild—not a spreadsheet, not a meditation retreat, just a deliberate re-anchoring before the moment slips away.

The tricky part is that nobody sees this happening. The client only feels a shift in presence, a subtle re-tuning. But the therapist knows the difference between being there and performing being there. What breaks first is usually the body—a clenched jaw, shallow breathing—before the mind admits it drifted. I have watched skilled clinicians lose whole sessions to this drift, then blame themselves for "poor focus" when the real issue was a missing check-in protocol. Not a heroic recovery. Just a habit, installed and repeated.

In the classroom: a teacher's reset

A teacher stands before thirty students who are, at best, half-present. The lesson plan calls for introducing fractions, but the room feels like static. Instead of pushing through, she sets a timer for two minutes and has everyone—including herself—do a "reset scan": feet on floor, breath counted, one word for where the mind wandered. Then she asks a single question: "What do you need to rejoin this lesson?" Hands go up. Some need water. One needs to share a worry about a sick cat. Two minutes of audit saves twenty minutes of talking to blank faces.

That sounds efficient, but the real cost is hidden. Teachers who skip the reset don't save time; they lose it twice over—once in re-explaining, once in managing the fallout of disengagement. The classroom version works because it's collective, not solitary. The teacher audits her own attention, and the students practice the same skill. Nobody feels singled out.

In your own practice: the 90-second scan

Your version doesn't need a room full of people. A timer, a notepad, and a willingness to catch yourself. The scan: stop whatever you're doing, note your physical state, name the last thought that pulled you away, and decide in one breath whether to return or deliberately switch tasks. Ninety seconds, max. The catch is that most people skip the "decide" step—they either force themselves back with gritted teeth or let the distraction spiral. Both fail.

Wrong order. The audit isn't about judgment; it's about data. "I drifted to email because this document feels ambiguous" is useful. "I'm lazy and unfocused" is not. We fixed this in our own team by making the scan a physical act—stand up, stretch, write one sentence about the drift, then sit down. The body movement breaks the trance; the sentence creates a record you can review at the end of the week. That's where patterns emerge, and patterns are what you can actually change.

An attention audit is not a performance review. It's a weather report for the mind—you can't change the storm, but you can choose where to anchor.

— field note from a Gleamcore practice session, 2024

Is any of this complicated? No. But the simplicity misleads people into skipping the discipline. The real work is remembering to run the scan when you're already overwhelmed, not when you're sitting calmly with a cup of tea. That's the moment it counts, and the only way to get there is to practice it in the boring, low-stakes moments first.

The Foundations People Get Wrong

Attention is not focus

The first mistake is treating attention as a synonym for focus. Focus is the beam; attention is the fuel. You can focus sharply on the wrong thing for an entire afternoon — and many teams do, then call it a win. An audit that measures only “did we stay on task?” misses the deeper question: were we pointed at the task that mattered? I have watched teams celebrate a flawless two-hour deep-work block that advanced a feature nobody needed. The audit caught it only because we asked what got *deprioritized* to make room.

Attention also includes the ambient load — the background chatter, the Slack pings, the half-open tabs that quietly tax your working memory even when you ignore them. Most audits ignore this entirely. They count minutes of “deep work” and call it a day. That's like measuring a river’s health by its surface speed while the silt builds up below.

An audit is not a scorecard

The second misconception: audits exist to grade people. Wrong order. An audit is a diagnostic, not a performance review. The moment you attach a score, the data corrupts — people inflate their numbers, hide the messy parts, and the whole exercise becomes theater. The catch is that most teams can't resist turning it into a scorecard anyway. Leadership wants a number to track quarter over quarter. That's understandable, but it's also how the practice dies.

We fixed this by separating the two. The audit produces raw observations — where attention went, what interrupted it, what drained it. The scorecard, if you must have one, gets built later and only from patterns that show up repeatedly. Even then, the score applies to the *system*, not the person. A team that always loses an hour to status meetings is not lazy; the meeting structure is the problem. Score the structure, not the people.

“An audit is a mirror held up to your environment. Most people want a hammer instead.”

— engineering lead, after two failed audit cycles

The ‘should’ trap

The third and most corrosive misconception is the belief that attention *should* be a certain way. You should be able to focus for four hours straight. You should not check email until noon. You should not feel restless after thirty minutes. These “shoulds” poison the audit from the inside — because now you're measuring yourself against a fantasy instead of observing what actually happens. The audit becomes a shame exercise, and shame is the enemy of accurate data.

What usually breaks first is honesty. People stop logging the embarrassing interruptions — the doomscroll after a hard call, the compulsive tab-switching when a task feels ambiguous. They clean up their logs to match an ideal. The audit then returns glowing results that nobody believes, and the whole practice quietly collapses under the weight of its own fiction.

The alternative is brutal acceptance. Log everything, including the ugly bits. A thirty-minute YouTube hole after a tense negotiation is *real* — it's data about your recovery needs, not a moral failing. Once you accept that, you can actually design around it. That sounds obvious, but I have seen entire audit programs fail because one manager insisted that “should” was a valid baseline. It's not. Baseline is what happens. Everything else is aspiration, and aspiration belongs in a different document.

Patterns That Consistently Work

Keep it short: 90 seconds, not 20 minutes

The longest effective audit I’ve run took ninety seconds. The shortest took forty. That’s the entire point — if an attention audit feels like a meeting, people will schedule around it, skip it, or half-do it while checking something else. Twenty-minute audits are not audits; they’re therapy sessions with a timer. You don’t need to unpack your childhood to notice that your inbox owns your morning.

Set a hard cap. One question, one glance at your calendar, one honest note about where your mind actually drifted. The discipline is the brevity. When teams protest that ninety seconds can’t possibly capture their complex day, they’re usually protecting the right to wallow in distraction rather than name it.

Have a clear question before you start

“How did I feel?” is a trap. Vague prompts produce vague logs, and vague logs get abandoned by week two. Instead, ask something answerable in a breath: Did I choose this task, or did it choose me? Or: What pulled my eyes away from the thing I said mattered? That second one is the workhorse — it turns the audit into a friction log, not a diary.

Flag this for mindfulness: shortcuts cost a day.

The tricky part is that the question changes the answer. If you ask “what distracted me,” you’ll catalog every notification like a crime scene photographer. If you ask “what did I avoid,” you’ll get the real story — the hard task you orbited for an hour before touching. Pick one lens per week. Don’t switch mid-cycle or your data becomes noise.

Log it simply: a dot, a word, a feeling

Most teams over-engineer the tracking. Spreadsheets with color coding, tags, severity scores — that’s not sustainability, that’s a second job. A dot on a scrap of paper works. A single word works. “Email.” “Slack.” “Worry.” “Fridge.” The word doesn’t need to be eloquent; it needs to be honest.

One engineer I worked with taped a 3×5 card to his monitor and drew a small slash every time he caught himself doomscrolling. He didn’t write context, didn’t timestamp, didn’t categorize. After three days he had forty-seven slashes and the evidence was damning enough to change his notification settings. That’s the whole mechanism — the audit doesn’t fix anything by itself, it just makes the invisible visible. And once visible, you can’t unsee it.

The audit is not the intervention. The audit is the mirror. The intervention is what you do the next morning.

— field note from a two-person design studio, third month of weekly audits

Do it regularly, not ‘when you remember’

Irregular audits are worthless. Worse than worthless — they give you a flattering fiction of your attention, because you’ll naturally audit on good days and skip the chaotic ones. The schedule must be boring. Same time, same trigger. First coffee sip. Right after standup. Last thing before lunch. Anchor it to something that already happens, because willpower is a terrible calendar.

What usually breaks first is the “catch-up” mentality. Miss a Tuesday and suddenly it’s Friday, and you think “well, I’ll do a big one Monday.” That’s the drift pattern. The fix is ugly but effective: if you miss the slot, skip it entirely. No make-up audits. The gap itself is data — it tells you the week ate you alive, which is exactly the information you needed. Half of sustainability is learning to let the missed beat stand as evidence rather than padding it over with guilt.

Anti-Patterns and Why Teams Quit

The paperwork spiral

Attention audits die the moment they become another form to fill. I have watched teams start with genuine curiosity—what actually pulls us away?—and within six weeks they're copying last month’s numbers into a spreadsheet nobody reads. The ritual outlives the reason. That sounds petty until you count the hours: forty minutes per person per week, multiplied by twelve people, for a document that changes exactly one decision per quarter.

The psychological trigger is obligation without agency. When the audit feels like homework, the brain classifies it as threat, not signal. People start writing what they think compliance looks like. Vague entries. Safe answers. The data goes sterile, and the team quietly resents the thing that was supposed to free them. Wrong order: the form arrived before the trust.

Turning it into a performance review

Another pattern guarantees a quiet revolt: attaching scores to attention. The moment someone’s focus time becomes a metric with a target, the audit becomes a game. People inflate deep-work hours, hide interruptions, and schedule fake buffer blocks. You're no longer auditing attention—you're auditing impression management.

The trade-off here is brutal but simple. Accountability feels good to the person designing the system and corrosive to everyone inside it. I have seen managers say “we’re just measuring patterns” while the team hears “prove you’re not lazy.” That mismatch is why teams quit. Not loudly—they just start filling the form with lies and checking out emotionally by month three.

“We didn’t need more data about our attention. We needed permission to change how we worked. The audit just gave us a way to delay that.”

— engineer, post-mortem conversation after abandoning a quarterly audit program

The guilt loop

Then there is the shame spiral. The audit reveals that you spend three hours a day on email, and instead of fixing the system, you just feel bad about it. Guilt is a terrible motivator for sustainable change. It produces short bursts of performative efficiency followed by collapse—because the underlying assumption is that your attention is broken, not that your environment is badly designed.

What usually breaks first is honesty. If every audit session ends with self-flagellation, people start skipping the reflection and jumping straight to action lists. That misses the point entirely. The audit is not a confession booth. It's a map. And maps don't judge the terrain.

Doing it only when things are chaotic

The most seductive anti-pattern is treating the audit as fire extinguisher. Crisis hits—deadlines compress, Slack explodes, everyone feels scattered—so you run a one-off audit to “find the problem.” Fine, except you have no baseline. You can't tell what is abnormal because you never measured normal. The results arrive after the storm passes, the recommendations feel stale, and the whole exercise gets filed under “didn’t help.”

Odd bit about mindfulness: the dull step fails first.

That experience poisons future attempts. The team concludes audits are reactive busywork, not a practice. The real cost is not the lost hour—it's the lost credibility. Next time someone proposes a sustainable attention rhythm, the collective memory says “we tried that during the crunch and nothing changed.” The fix is boring: run the audit when things are calm, treat the crisis data as noise, and build the habit before you need it. Not sexy. But it works.

Odd bit about mindfulness: the dull step fails first.

The Long-Term Cost: Maintenance, Drift, and Fatigue

Audit fatigue: when the tool becomes the distraction

Ten years in, the most common failure isn't abandonment—it's zombie compliance. Teams still block the calendar slot, still open the template, still produce the color-coded summary. But nobody reads it. The ritual survives because canceling feels riskier than performing. I have watched this happen to groups that started with genuine curiosity; the audit becomes a tax they pay to keep leadership off their backs, and the original impulse—to see where attention actually goes—drowns in formatting consensus.

Odd bit about mindfulness: the dull step fails first.

Odd bit about mindfulness: the dull step fails first.

Odd bit about mindfulness: the dull step fails first.

Odd bit about mindfulness: the dull step fails first.

The cost is double. First, you lose the hours spent preparing and sitting through the review. Second, and worse, you train everyone that attention work is bureaucratic theater. That conditioning persists long after you fix the format. Wrong order. A team that hates the audit will sabotage the next three attempts at real reflection, even if you strip the process down to a single question.

Fatigue also hides in individual meetings. When every week produces a fresh "where did your focus go" worksheet, people start gaming the answers. They report what sounds healthy. They trim the embarrassing tabs, the doomscroll sessions, the half-hour rabbit holes that actually defined their week. The tool becomes a mirror that everyone agrees to look at sideways.

Drift: losing the original question

The tricky part is that drift feels like improvement at first. You begin with a sharp, narrow probe: "Which three tasks consumed the most unbroken attention this week?" That question reveals real allocation patterns. Then, because teams love frameworks, someone adds a second question. Then a rating scale. Then a "strategic alignment" column. A year later you're scoring your attention against corporate OKRs, and the original observation—what did you actually do—has vanished under interpretation.

I have seen a team spend forty minutes debating whether "responding to Slack" counts as deep work or shallow work. The debate is not pointless; it's a symptom. The audit was supposed to surface where time went, not adjudicate the moral purity of every interruption. When the practice drifts toward self-judgment, people stop showing up with honest data. They show up with a defense brief.

What usually breaks first is trust in the numbers. Once someone catches a colleague retrofitting their log to look better, the entire dataset becomes suspect. And that suspicion is often correct—drift encourages performance over accuracy. The fix is not more precise categories. The fix is deleting the categories entirely for a quarter and returning to one blank page: "List what you actually did. No labels."

The cost of skipping: does it decay?

Yes, it decays—but not linearly. Skipping one month is fine. Skipping two feels like relief. Skipping three makes the past audits look like artifacts from a different workplace. The decay is social as much as cognitive. New hires arrive and see the old templates in the drive; they treat them as historical documents rather than living practice. Nobody explains why the ritual existed, so the next generation reinvents it badly or abandons it.

Maintenance requires a designated skeptic—someone whose job is to ask "why are we still doing this?" every six months. Not to kill the practice, but to pressure-test it against the original question. If the answer becomes "because we've always done it" or "because the report looks good in the quarterly review," the audit is already dead. You're just embalming it.

An audit you can complete without thinking is an audit that has stopped thinking for you.

— field note, long-term tracking group, year six

The honest math is simple: ongoing attention auditing costs about one percent of your team's hours, forever. That sounds trivial until you multiply it by the silent erosion—the meetings that creep back, the templates that bloat, the ritual that hardens into obligation. The teams that sustain this practice for a decade are not the ones with better discipline. They're the ones that allow the audit to be ugly, incomplete, and occasionally wrong. That hurts. And it's the price of keeping the question alive.

When Not to Use This Approach

In acute anxiety or panic

An attention audit assumes you can observe your own mind from a safe distance. That assumption collapses when your nervous system is screaming. If someone is mid-panic, asking them to categorize their thoughts by energy level or trigger type is like handing them a clipboard during a house fire. The audit becomes another demand, another place where they can fail. I have seen this backfire badly—someone forced into a structured review during a spiral, then spiraling harder because they couldn't even do the simple logging.

The fix is not a better audit. It's ground. Breath, body, movement, anything that doesn't ask for cognitive effort. An audit needs a stable platform; panic removes the platform. Wait until the wave passes, then look at the debris.

During a crisis (just execute)

When the server is down, the contract is lost, or the client is screaming, the last thing you need is a reflective pause. Crises punish deliberation. Your team already knows the priority; the bottleneck is action, not awareness. Running an attention audit mid-crisis tells people that meta-cognition matters more than the thing on fire. That message lands poorly.

Wrong order. Execute first, audit after the dust settles, when the post-mortem can actually teach something. The tricky part is that crises feel like the perfect time to "check in" on how everyone is doing. Resist that urge. You're not helping; you're adding latency to an already overloaded system.

If you're already hyper-vigilant

Some people don't need more monitoring—they need less. Hyper-vigilant folks track everything: every flicker of distraction, every body sensation, every micro-delay in their workflow. An audit for them is redundant at best, fuel for obsessive self-surveillance at worst. I have watched this turn into a loop: audit reveals a small distraction, which triggers anxiety about the distraction, which becomes the next audit's finding. That hurts.

The contraindication here is subtle. You're not looking for people who are curious about their attention. You're looking for people who are already punishing themselves for lapses. For them, the audit is a hammer. The tool is fine; the user is not ready for it.

When the team is exhausted

An audit is inherently a bit of work. Not monumental work, but real work—logging, reviewing, discussing, adjusting. If your team is running on fumes, that work lands on cracked ground. Fatigue makes the audit feel like another assignment, another thing to fail at, another meeting that could have been a nap. The results will be garbage too. Exhausted people don't self-report accurately; they report what is quickest, which is usually "I'm fine" or "everything is distracting."

Odd bit about mindfulness: the dull step fails first.

Odd bit about mindfulness: the dull step fails first.

Rest first. Rebuild the energy floor, then introduce the audit. The data you collect from tired minds is worse than no data—it gives you false confidence in a system that's already broken. That said, the opposite error is just as common: waiting for the "perfect" calm moment that never arrives. Use a threshold—if the team has had one decent week, start. If they have had three brutal ones, don't.

Odd bit about mindfulness: the dull step fails first.

Odd bit about mindfulness: the dull step fails first.

An audit measures a system that must already be stable enough to be measured. Otherwise you're just adding a mirror to a storm.

— field note from a team lead who learned this the hard way

The through-line is simple: audits are for healthy systems, not rescue operations. If the baseline is acute, chaotic, or depleted, the audit is not the medicine—it's a diagnostic test run on a patient still bleeding out. The real move is to stop the bleeding first, then ask questions.

Open Questions and Common Concerns

How Long Should an Audit Take?

Longer than you think, shorter than you fear. A proper attention audit—one that actually changes behavior—needs at least ninety minutes of uninterrupted focus per person. Not forty-five. Not a lunch break. The first pass always takes longer because you’re building the baseline, not just logging time. I have watched teams try to compress this into thirty minutes and produce nothing but guilt lists.

The trap is mistaking the audit for a calendar dump. You aren’t just counting meetings. You’re tracing energy, drift, and the moment your brain starts pretending to work. That requires candor, and candor needs room to breathe. If you’re auditing a whole team, block three half-days across a week. Spread it out. The gaps between sessions reveal more than the sessions themselves.

What If I Keep 'Failing'?

You will fail. That’s the point. An audit that shows perfect attention is either a lie or a life without friction—both useless. The real metric is whether your failures shift month to month. Same mistake in March and May? That’s a system problem, not a willpower problem. Different failures each time? You’re learning where the seams actually are.

Most teams quit after the second audit because they expect a fix, not a diagnosis. Wrong order. The audit is a mirror, not a surgeon. If you keep seeing the same distraction, stop auditing and start editing—remove the trigger entirely instead of asking people to resist it. The catch: resistance is a strategy, but only for about three weeks. After that, you need structural change.

An audit you fear is an audit you need. Repeat it until the fear becomes boredom.

— facilitation note, gleamcore practice circle

Can I Do This With a Remote Team?

Yes, but the signals change. In person, you watch someone’s eyes glaze over. On video, you watch their cursor wander into Slack. Remote audits must account for invisible switching—the tab you can’t see, the second screen parked to the left. That sounds fine until you realize your team is reporting "meeting focus" while ordering groceries.

Fix this by making the audit public but anonymous. Share aggregate patterns, never individual logs. Remote teams drift differently—more fragmentation, fewer obvious interruptions. The audit should capture both active time and passive time, the minutes spent half-listening while responding to unrelated pings. No shame. Just data.

Is There a Best Time of Day?

Morning, but not for the reason you think. The best audit window is your second peak—usually 10 AM to noon—when the brain has warmed up but hasn’t crashed. Not 8 AM, when everyone is still running on cortisol, and not 3 PM, when the afternoon slump turns every honest log into a recovery narrative. That said, the best time is the time you can repeat weekly. Consistency beats the perfect slot.

The open question, the one we still haven’t solved after a decade: does the audit itself change the behavior you’re measuring? Some teams report that the act of logging attention creates better attention—a Hawthorne effect that never fully fades. Others say the opposite, that the audit becomes another chore, another obligation, another thing to feel guilty about. I lean toward the former, but I have seen both. What matters is collecting data long enough to separate the signal from the shame.

Next Experiments for the Next Ten Years

Try a weekly 'audit of audits'

Block out fifteen minutes every Friday. Pull up your calendar, your browser history, your chat logs, and ask one question: where did attention actually go versus where I planned for it to go? Most teams skip this because it feels like meta-work, but the meta-work is the work. I have seen a two-person startup keep this habit for six months and catch a pattern where every Tuesday was lost to a recurring meeting that nobody wanted. Wrong meeting, not wrong people. The fix took one email.

Keep the threshold low. A notebook works. A shared doc works. The tool matters less than the ritual of looking at the raw material of your week.

Pair it with a kindness check

Attention audits can turn punitive fast. You start counting hours and suddenly you're grading yourself on a curve that nobody else sees. That's the trap. So add a second question to the weekly review: where did I give someone else my focus without expecting anything back? A colleague's messy problem, a friend's rambling story, a stranger's directions. This balances the ledger.

One team I consulted added a "generosity score" to their audit. Nothing scientific—just a gut rating. They found that weeks with high scores on both metrics felt sustainable; weeks with high focus but low kindness felt like burnout brewing. The experiment isn't about being warm and fuzzy. It's about noticing that attention has a social dimension, not just a productivity one.

Audits reveal what you did, not who you were while doing it. The second part matters more for the long haul.

— field note from a mindfulness facilitator, Gleamcore community call

Make a seasonal theme

Pick a quarter, not a year. Spring for deep work, summer for collaboration, autumn for pruning, winter for reflection. Assign each season one question to test. For example: "Can we do our best thinking before noon?" or "Which meetings would we miss if they vanished?" Seasonal themes keep the practice from becoming wallpaper. You get three months to try something, fail, adjust, and move on.

Share your data with one other person

Privacy matters, but secrecy kills the audit. Find one human—a partner, a peer, a therapist—and show them what you found. The catch is explaining it in plain language, not jargon. That forces you to understand what the numbers mean. In my experience, the first sharing session is awkward; the third one becomes the most honest conversation you have all month.

What usually breaks first is the habit itself. You skip a week, then two, then you're back to guessing. That's fine. The experiment isn't perfection—it's recurrence. Try one of these for a month. Observe what shifts. Then adjust and try again. The next ten years are built from this month's small, repeated attention choices.