Learning organized around judgment, not topics
Each pathway builds a specific kind of decision-making capability. Start wherever your next hard call is coming from.
Evaluating technology before you adopt it
How to tell the difference between a tool that removes real, repeated work and one that only performs well in a controlled demo.
Topics we’ll explore
- What a proof of concept can and cannot tell you
- The hidden operating cost of a “free” tool
Deciding well under pressure
What actually determines how fast an organization recovers, and why the answer is rarely the monitoring stack.
Topics we’ll explore
- Who decides when nobody is sure who decides
Introducing change without breaking trust
Governance that holds up under pressure, without becoming the reason people quietly route around the process.
Topics we’ll explore
- How to say no to a change without stopping the work
- Why change advisory boards drift into theatre
- Writing a rollback plan people will actually use
Knowing what to automate
Recognizing when automation is removing effort, and when it is quietly removing the visibility you depend on.
Topics we’ll explore
- Does automating this solve the problem, or hide it?
- Automation that fails loudly beats automation that fails quietly
- What to keep manual on purpose
“A framework is not there to give you the answer. It is there to stop you skipping the question.”
New pathways as they publish.
One practical lesson a week, written for people responsible for technology decisions.