Maintain SOPs

Maintain SOPs in Notion — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
Update the SOP for customer escalation to include the new 24-hour SLA, add the escalation phone…
Update the SOP for customer escalation to include the new 24-hour SLA, add the escalation phone number and the three-step email template, and notify Support and Customer Success to review and sign off by Thursday.

Improve — make it easier to accept

+
Before I publish the revised SOP for incident response, make it easier to follow under stress:…
Before I publish the revised SOP for incident response, make it easier to follow under stress: surface the SLA and first two actions at the top, add a short checklist for the on-call engineer, mark which steps require external comms, and highlight any places where decisions need manager approval.

Decide — diagnose the stuck moment

+
I rewrote the incident response SOP and added a 24-hour SLA, but I don't know if the on-call…

I revised the SOP but can't tell if the on-call will follow it during incidents.

I rewrote the incident response SOP and added a 24-hour SLA, but I don't know if the on-call engineers will actually follow the checklist under pressure. I own the docs, Kiran owns on-call rota, and Ops leads incident response. I'm afraid the SOP is too wordy and will be ignored when an incident hits. How should I validate and simplify this so the on-call will use it in a real incident?

Become — change the pattern

+
We keep updating SOPs but the on-call teams rarely follow the latest version when incidents happen.…

SOP updates repeatedly fail to be adopted by teams on call.

We keep updating SOPs but the on-call teams rarely follow the latest version when incidents happen. I write the SOPs; Kiran schedules the rota; Ops leads the response. This costs time and risks customer impact. What habit in how we publish and socialize SOPs should I change to drive adoption so the right steps are followed under pressure?

Next to this one

Other docs and databases work people do in Notion.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.