Your first 90 days in an ops role, neurodivergent edition

The first 90 days are the highest-risk period: new systems, new names, new unwritten rules - and maximum pressure to seem effortless. Here's a plan that lowers the load without lowering your standard.

Week one: build your external memory

Set these up before you're busy, because you won't do it after:

• A personal wiki/notes page per system you touch: what it is, who owns it, where the docs are, the one command you always forget.
• A names-and-faces note. Photos from the org chart, names, what they own. Reading it before meetings removes a whole category of stress.
• Your accessibility basics on your machine: TTS, dictation, font/zoom settings, dark mode. Do it quietly on day one - it's configuration, not a request.

Weeks 2–6: control the input firehose

• Ask for the documentation map, not documents. "Where does this team keep its runbooks, diagrams and decisions?" is a strong question that also reveals how organised they really are.
• Convert meetings to notes. If the team doesn't take minutes, volunteer a summary in chat after meetings you attend. You get to process at your own speed and look proactive - the compensating strategy that reads as a strength.
• One question rule. Batch small questions and ask them in scheduled 1:1s rather than interrupting constantly - protects your focus and theirs.

The disclosure question during probation

There's no universally right answer. Practical observations from the community:

• Formal accommodation processes are slower than probation in some companies. If you'll need substantive adjustments, earlier beats later.
• Many people run probation on self-built accommodations (route 3 in our disclosure guide) and decide afterwards from a position of proven value.
• If the environment is actively hostile to the idea, that information is worth having during probation, while leaving is cheap.

What to postpone

• Fixing their documentation culture (note the gaps; propose in month four)
• Every optional social event (pick the ones with structure - lunches beat pubs)
• Certifications (unless contractual - learning the actual environment comes first)

You are done with onboarding when

• You can trace a request from user to backend without asking
• You've closed tickets in every queue you own
• You know who to ask about anything in under a minute - because it's in your notes