Friction MapPractical systems for ADHD work & life日本語

Work Systems

Stop rereading everything: build a personal pre-send check

Turn your real error history into a short, repeatable check for email, reports, forms, and handoffs.

A document passes through four simple inspection gates for recipient, attachment, date, and final delivery
Separate creating from checking, then check the same risk points in the same order.
Quick take

See the decision before the details

Use real patterns

Build checks from repeated observable errors, not from a generic list of everything that could go wrong.

Split the pass

Check content, delivery, and handoff as separate questions against the authorized source.

Escalate the consequence

Use formal or independent controls when one person's short check is not a sufficient barrier.

“Be more careful” is not a checking system

ADHD can involve difficulty sustaining attention to details, organizing tasks, and finishing work. Similar mistakes can also happen because of fatigue, unclear processes, excessive workload, or interruptions.

A checklist cannot remove every error. It can, however, make a small set of known risks visible at the exact moment they matter.

Start with your last five errors

  1. List recent mistakes without judging them: missing attachment, wrong recipient, old date, copied number, incomplete handoff.
  2. Circle only the errors that have happened more than once.
  3. Turn each repeated error into a yes-or-no check.
  4. Keep the final list to roughly three to seven checks.

Split content checks from delivery checks

PassAskCompare with
ContentIs the requested answer present, and are names, dates, and numbers supported?The authorized request and source evidence
DeliveryAre the recipient, current version, attachment, and sharing permission correct?The approved destination and access settings
HandoffCan the next person see what changed, what happens next, and what is blocked?The agreed project record and owner
Run three short passes instead of rereading the whole item without a question. Swipe horizontally to see all columns.

Write the card so every check can finish

  1. Start each line with one object: recipient, attachment, date, figure, permission, or owner.
  2. Name the evidence to compare rather than writing “looks right.”
  3. Make the answer yes, no, or not applicable; route a no to a defined correction or reviewer.
  4. Keep the card beside the send or release action, then revise it only when a real pattern changes.

Do not copy client, patient, employee, account, financial, or other confidential details into a personal error list. Keep any required record in the authorized system.

Run the check under better conditions

If possible, separate drafting from checking with a brief pause, change the zoom level, or read critical numbers against the original source. For high-consequence work, use a second-person review or the organization’s formal control process rather than relying on a personal checklist alone.

Workplace context matters

Written instructions, checklists, task-management tools, reduced distractions, and structured feedback are among the supports that may be considered in some workplaces. Accommodation rights and processes differ, so use local official guidance for your situation.

Build one card for the next real send

Choose one ordinary email, report, form, or handoff that you expect to send. Write no more than seven yes-or-no checks from your actual repeated patterns, place the card beside the send action, and run each line once against its source. If a no cannot be corrected safely within your role, stop and route it to the authorized owner or reviewer.

The useful result is not perfect confidence. It is a visible answer to the few questions that most often fail, plus a clear boundary for work that needs a stronger control.

Sources and further reading

Sources support the health and diagnostic context. Practical workflow suggestions are low-risk editorial adaptations, not clinical treatment.