The operator's craft. Inside Analytics, Module I — Foundations — this lesson names a specific move the operator-technologist makes when the situation calls for it. The register is institutional: a working understanding of Ask-the-analyst discipline, sized to be reached for in a real conversation, not recited from a slide.
- 01State Ask-the-analyst discipline in the disciplined sense used throughout Analytics, without softening or slogan.
- 02Recognize the situation in which Ask-the-analyst discipline is the right move — and the adjacent situation in which it is the wrong one.
- 03Execute Ask-the-analyst discipline in a live case drawn from your own work or a documented case study, and defend the reasoning in one paragraph.
- 04Connect Ask-the-analyst discipline to using software to compress the ordinary work of the firm so it strengthens the practice rather than replacing it.
The capability, stated plainly
The operator's craft. Read the sentence twice. It is not a slogan; it is the compressed form of the lesson. The rest of this module returns to it, so the sentence is worth learning by heart. When the operator-technologist integrates ask-the-analyst discipline, this is what the move actually is — no more, no less.
Where it lives in the stack
Module I exists because . Ask-the-analyst discipline is one of the enterprise technology moves that lives inside that situation. Notice which earlier lessons this one leans on and which later lessons will lean on it — the sequencing is deliberate, and the module reads differently once you place this piece.
How the operator actually deploys it
In practice, the operator-technologist does not consult Ask-the-analyst discipline the way a novice consults a checklist. The move is trained in until it becomes an available response — something to retires without ceremony when the moment arrives. The mark of understanding is not that you can recite Ask-the-analyst discipline; it is that you catch yourself using it, unprompted, and can explain afterward why you did.
The buyer's misreading, corrected
The most common misreading is to treat Ask-the-analyst discipline as a maneuver you deploy on the other party. It is not. The technology decision survives the founder, the vendor, and the fad cycle — and the professional application of Ask-the-analyst discipline sits inside that criterion, not outside it. When the move is used cynically, the results are short-lived and the reputation cost is high. When it is used cleanly, it compounds.
- Ask-the-analyst discipline is a working move, not a slogan.
- It belongs to Module I — Foundations — because that is the situation it addresses.
- Mastery is unprompted use in the right situation.
- The adjacent lessons in this module are its natural context.
- Used cleanly, Ask-the-analyst discipline compounds; used cynically, it does not.
- Ross, J., Weill, P. — IT Governance. — The disciplined book on enterprise technology decision rights.
- Kim, G., Behr, K., Spafford, G. — The Phoenix Project. — The novelized introduction to modern IT operations.
- NIST Cybersecurity Framework. — The reference standard for enterprise security posture.
- 809 — Analytics, Module I: Foundations. The Anabasis Academy. — The parent module. Re-read the module framing after finishing the lesson.