Oct 21, 2026 · 30 min · 9 segments
The riskiest object is the one everyone forgot exists. In this episode of The Conference Insights Engine, David Dysart looks across Slate Summit 2026 sessions to examine the hidden operating system…
Every Slate instance has an operating system, whether anyone designed it intentionally or not.
When a student submits a form and a field changes, that's part of the operating system.
When an application lands in a reader bin, that is part of the operating system.
When a counselor receives an assigned population, that is part of the operating system.
When a staff member can see one kind of data but not another, that's part of the operating system.
When an old exception still changes behavior for one population and nobody remembers why, that's part of the operating system too.
Roles, workflows, assignment structures, and permissions are how an institution makes work repeatable.
The issue is whether the hidden logic is known, owned, documented, and reviewed.
That is where, behind the music, the hidden rules powering your instance becomes a useful starting point.
But a rule can also preserve an old assumption long after the reasons disappeared.
It explains what the rule does, what triggers it, which population it affects, which fields or processes it changes, who owns it, when it was last reviewed, and what could break if it stopped running.
Every Slate instance has an operating system, whether anyone designed it intentionally or not.
When a student submits a form and a field changes, that's part of the operating system.
When an application lands in a reader bin, that is part of the operating system.
When a counselor receives an assigned population, that is part of the operating system.
When a staff member can see one kind of data but not another, that's part of the operating system.
When an old exception still changes behavior for one population and nobody remembers why, that's part of the operating system too.
Roles, workflows, assignment structures, and permissions are how an institution makes work repeatable.
The issue is whether the hidden logic is known, owned, documented, and reviewed.
That is where, behind the music, the hidden rules powering your instance becomes a useful starting point.
But a rule can also preserve an old assumption long after the reasons disappeared.
It explains what the rule does, what triggers it, which population it affects, which fields or processes it changes, who owns it, when it was last reviewed, and what could break if it stopped running.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.