Cognitive Systems Engineering is a multidisciplinary field which focuses on designing complex, safety-critical human-machine systems by analyzing cognitive work (e.g., decision-making, planning) and constraints (e.g., memory, time pressure) to enhance human performance.
CSE can sometimes get conflated with traditional UX/UI, because both care about “humans and interfaces,” but they operate at very different levels of analysis—and that distinction often gets flattened in practice.
Traditional UX/UI design would ask whether an SRE can navigate to the right dashboard efficiently.
CSE asks whether the interface (across all the people looking at it during an incident) supports the team in building a shared picture of:
- what’s happening,
- what’s been tried,
- what’s expected to happen next, and
- where the boundaries of their understanding currently are.
Traditional UX/UI tends to view successes and failures through the lens of usability — e.g. the user couldn’t find X, the user was confused by Y, etc.
CSE provides an expanded lens for predicting success and failure: the interface was perfectly usable, and people still lost the plot. This is because usability and cognitive support under pressure are not the same thing.
Imagine you are a pilot in a cockpit during an engine failure.
A traditional UX/UI-designed cockpit would have very clear, easy-to-press buttons and a beautiful, high-resolution map. It’s great when things are normal.
A CSE-designed cockpit recognizes that during a failure, your “bandwidth” is gone. It doesn’t just show you an “ENGINE FAIL” light; it shows you how that failure is affecting your lift, what the autopilot is currently trying to do to compensate, and how much time you have before the situation becomes unrecoverable.
In other words:
UX/UI helps you operate the technology.
- The core stance here is “Don’t make me think.”
- The interface should be so intuitive that the user doesn’t have to struggle with the tool itself
CSE/Joint Activity helps you work together with the system to survive a surprise.
- The core stance here is “Help me think.”
- When things go sideways, the engineer needs to know not just what is happening, but why and how it’s happening, and what the automated parts of the system are doing about it. The engineer needs not only to know how to take actions (push buttons, etc.) that they want to take but get support in deciding what actions they should take.
