Week 5 Session: Week 5: Information Arrives on Someone's Schedule
Timing as a lever that some people in a process control and others don't — and why that is not, by itself, evidence of manipulation.
22 March 2027
Before the session#
Think of a time you received information “just in time” to act on it — a schedule change, a budget update, a policy revision. Note who released it, and how much time you actually had to respond once you had it.
The case document for this week#
Memo, drafted 17 March, sent 21 March, Beatrix Oyelaran (Finance and Risk Lead) to the LSS Rollout Working Group — one day before the Working Group’s next scheduled meeting, at which budget sign-off for Phase 2 was expected:
Risk Register Addendum: Engagement Signal Retention
Flagging for the record ahead of tomorrow’s meeting: ClarityPulse’s default configuration retains individual-level engagement scores for 24 months, not the 6 months referenced in the original proposal. Confirming this required a written answer from the vendor, received today. Recommend the Working Group consider a contractual retention cap before Phase 2 spend is approved.
In the session#
Whoever controls when a document lands controls, in part, how much scrutiny it gets — not because the content changes, but because reading speed doesn’t scale with meeting length. This week separates two things that are easy to collapse into one: releasing information late, and releasing information in a way designed to foreclose response. The first is often just how organisations actually work — a report waits on a final sign-off, a figure isn’t confirmed until the day before. The second uses that same ordinary-looking lateness as cover.
Working from the memo above, the session asks what would distinguish the two readings in a paper trail this thin: whether the same pattern of lateness recurs regardless of who benefits, whether an earlier draft existed and was held back, and whether the recipients had any standing way to ask for more time and didn’t take it. The memo itself does not settle this — it states only that the confirming answer “was received today,” and whether that is the honest shape of when Finance actually learned the fact, or a convenient thing to say, is exactly the gap you cannot close from this document alone.
After the session#
Bring one example of timing-as-leverage — real or from the case — to Week 6, where the focus shifts to what a record’s silences can and cannot tell you.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- can name who controlled the timing of at least one document release in the running case, and what that person could and could not do with that control
- can articulate one legitimate operational reason information arrives late, distinct from a deliberate attempt to shrink the time available to respond to it
Teaching team
- Marisol Quaye — convenor