Tag: CriticalThinkingTraining

Posted on

Field notes: operating the Decision Engine

I’ve written lots of posts this week on decision-making, and that’s because I have run three rounds of The Decision Engine workshop — part three in our Critical Thinking programme. 

The Decision Engine imagines decision-making as a production line that we build and operate. A decision travels through this system — starting with how the question is framed, moving through decision criteria, weighing subjective and objective factors, and arriving (eventually) at a decision.

It’s a model I first helped develop at Think Up during our 2015 collaboration with Arup on the Conceptual Design Mastery programme. Since then, I’ve developed it to account for everything from emotional data and gut feel to AI and emergent behaviour.

But the point is not to turn decision-making into a laborious stepwise process, but rather to build critical insight into our personal and group decision-making. 

Interesting questions that have fallen out of this week’s workshops include:

Should you start with developing ideas or agreeing your decision-making criteria?

Are we deciding — or are we building the mechanism by which other people decide?

What’s the role of subjectivity, and how do we get better at working with it?

When is a good time to decide?

And how do we continuously learn from our decisions.

Plenty to chew on, including whether we could run a day-long, stand-alone course on decision-making in future. Watch this space. 

Posted on

Sleep, subconscious and napping at work.

This week we ran an online session in our Critical Thinking series exploring a topic not usually found in professional training agendas: sleep and the subconscious.

We often ask the question: When do you get your best ideas? Unsurprisingly, no one said “at my desk.” We usually use the question to explore idea generation, but here it opened the door to a deeper conversation about how insights often arise when we’re not consciously trying—on walks, in the shower, while dozing off.

We introduced the idea that our subconscious is always working, quietly filtering, sorting, and remixing our experiences. But like a party next door, we can only hear it if we turn the mental volume down.

We looked at:

  • The role of sleep cycles (NREM for data sorting, REM for pattern generation)
  • The value of unstructured time in creativity
  • Whether we should actually be paid to nap at work
  • How all this supports critical thinking at every stage of the OODA loop

Perhaps surprisingly, we started with a short guided meditation—done in the middle of a busy office—helped participants notice just how noisy their minds are, and what might be waiting underneath.

Sometimes our best thinking begins when we stop.

Posted on

The Map Room – mapping systems, horizons, and change

This week we ran The Map Room, the second workshop in our Critical Thinking for Engineers (and Other Humans) programme. If the Observatory was about looking outwards, this session was about making sense of what we’ve seen—mapping the system, tracing its logic, and finding out where we might start to make change.

We explored:

  • The Systems Bookcase model: a tool for organising system layers, from what gets built through to the values and paradigms that shape it.
  • The Three Horizons framework: helping participants spot signs of long-term change—and understand their own role in it.
  • The Library of Systems Change: a way of recognising how future practices are already quietly present in today’s systems.

Some of the most powerful insights came when participants started applying the tools to parts of their work they hadn’t considered “design” before—like internal policy, comms strategies, or team culture. It was a reminder that systems thinking isn’t just for buildings or infrastructure—it’s for how we work, organise, and evolve.

We also talked about system boundaries, shifting roles, and what it means to design something that doesn’t just meet a brief, but changes the system the brief sits inside.

The Map Room builds on the Observatory, taking data and analysing it in readiness for the Decision Engine, where we decide on the next course of action to take. That will come later in June.