Colleagues,
This document is not formally issued. It exists in the same way most work gets done here: acknowledged implicitly, denied explicitly, and referenced retrospectively when something goes wrong.
It is a guide to surviving within the institutional architecture described in policies such as MAOCP, PMUEUP, ARR, PPRP, SFCDDM, and others that are currently being reviewed for coherence with themselves.
1. The First Principle: Assume You Are Already Non-Compliant
You will save time by accepting that:
- You are always slightly out of alignment
- Any action can be reclassified after the fact
- Any silence can be interpreted as consent or negligence, depending on context
Therefore:
Do not aim for compliance. Aim for plausible defensibility under retrospective review.
2. The Art of Strategic Acknowledgement
Survival depends on knowing when to:
- Reply “noted, thank you” (no action taken)
- Reply “we will take this forward” (no ownership taken)
- Reply “we are currently aligning this with institutional priorities” (no timeline exists)
These phrases do not communicate meaning.
They communicate administrative survival status.
3. Meetings: A Parallel Reality System
Meetings serve three functions:
- Recording attendance of ideas
- Preventing unrecorded decisions
- Converting uncertainty into action items that will never act
Survival protocol:
- Speak once, early, vaguely
- Nod at key moments to establish epistemic presence
- Volunteer for tasks that will be reassigned before completion becomes possible
If a decision is made, assume it will be:
- revised
- reinterpreted
- or placed into a pilot programme designed to investigate whether it was actually a decision
4. Email Strategy (Critical Skill)
Inbox survival requires mastery of:
- The “looping reply-all closure”
- The “gentle deferral with implied urgency reversal”
- The “attachment that resolves nothing but looks complete”
Recommended phrases:
- “Just circling back on this” (translation: I am still alive in this thread)
- “Happy to discuss further offline” (translation: please do not)
- “Let’s park this for now” (translation: it is already buried but we need ceremony)
5. The Policy Stack Survival Method
You will encounter conflicting policies. This is normal.
Do not attempt resolution.
Instead:
- Identify which policy is most recently updated
- Pretend it supersedes all others
- If questioned, refer to “local interpretive discretion frameworks”
- If further questioned, escalate to a committee that does not yet exist
Remember:
The goal is not consistency. The goal is traceable intent alignment under shifting policy terrain.
6. Work Output Optimisation (Informal Reality)
Officially:
- Quality matters
- Innovation is valued
- Reflection is essential
Practically:
- Deliver what can be easily described in a report
- Avoid outputs that require explanation in meetings
- Ensure all work can be summarised in three bullet points or fewer
If it cannot be bullet-pointed:
It will be considered “emergent complexity” and deferred indefinitely.
7. Emotional Survival Layer
Key truth:
Most institutional stress comes not from workload, but from trying to interpret whether the workload is real, symbolic, or aspirational.
Therefore:
- Treat urgency as performative unless accompanied by a deadline reminder email
- Treat deadlines as suggestions unless accompanied by escalation language
- Treat escalation language as atmospheric rather than literal
8. The Golden Rule
When in doubt, ask yourself:
“Can this be retrospectively justified in a way that sounds like I understood the system all along?”
If yes:
- Proceed
If no:
- Create a working group
If uncertain:
- You are already correct
9. Closing Note
No one fully understands the system.
Those who appear to understand it are either:
- new
- leaving soon
- or actively being scheduled for a review of their understanding of understanding
The system continues to function because everyone agrees, tacitly, not to test it too closely at the same time.
P.S. If you are reading this during work hours, you are probably already in compliance with something, somewhere.
