How Long Is Long Enough?

When I was writing the events for Last Prompt, I had a feeling I can only describe as a kind of gleeful malevolence.

Each event arrived in my head as a dilemma — rich with options, branching in every direction, full of possibilities the player would have to navigate. I could see the maze from above. I could see all the routes. Some would hurt. Some would be satisfying. Some looked obvious until you followed them three steps forward and realised they weren't obvious at all. Writing them was genuinely fun. The challenge I was designing felt real and interesting and appropriately difficult.

Then I became the player.

And I discovered that obvious from the author's chair is a completely different thing from obvious inside an environment you didn't control when you wrote it. The same event — the same words, the same crisis — lands differently depending on what the stats are doing when it arrives. I had written events thinking "this one will hurt" or "this one's a breeze, just do x." Then I played them, and discovered that just do x doesn't work when the infrastructure is already strained and the cash flow is at three. The event is only half the problem. The other half is the world it lands in. I had shot myself in the foot — and it turned out to be exactly right.

Playing Colony, I can move quickly. The events sit near the base of the pyramid — food, water, shelter, security, health. These are things humans are already evolved to think about. The solution space naturally collapses toward answers, because survival needs are instinctively legible. Even without management experience, most people can form a view about hungry people needing food. Colony asks: what should I do? I can do a chapter in an evening without thinking hard, score mostly Strong, and feel like I've worked well.

Corporate is different in kind, not just in degree.

The events sit much higher — loyalty, trust, ethics, identity, culture, meaning. There is no instinct for those. The solution space doesn't collapse. It expands. Forty-seven employees across three critical departments have submitted coordinated resignations because they believe the company is morally bankrupt. The organiser is a respected senior engineer. Replacing them takes months. Retaining them requires concessions that may be impossible.

Before I have written a single word, I have to decide what problem I am actually solving. Is this a retention problem? A leadership problem? An ethics problem? A communication problem? A symptom of something larger? Each framing opens a different set of options. Each option creates more options. The thinking space grows dramatically — not because the interface is harder but because there is no instinct already waiting to help me.

Two Corporate events in an evening is enough. Not because I failed. Because the cognitive load is genuinely different. This is the leap from primary school to secondary school. Whether the teachers at secondary care what you already learned or not, it makes no difference to the leap. The building is bigger. The class is bigger. The expectations are different. The environment itself has changed. The leap still feels enormous. That's not a problem to be fixed. It's the system working exactly as intended.

Lockwood goes higher still. There the challenge isn't how to retain staff or feed the colony. The problem doesn't yet fully exist — or rather, it exists as potential rather than crisis. The discovery of cast iron, of electricity, of computing, isn't a problem waiting to be solved. It's an open-ended possibility whose consequences are undetermined, interdependent on everything else evolving in that moment. The Traveller isn't choosing between solutions. They're helping to define what kind of problem this will become. You aren't balancing resources or navigating ethics. You're balancing meaning — the consequences of a discovery that nobody in the room fully understands yet. The thinking space doesn't just expand. It becomes conceptual rather than practical.

Colony: what should I do? Corporate: what problem am I actually trying to solve? Lockwood: how will I know if I'm solving the right problem at all?

But this is where I want to be careful.

Because the gap between the skins isn't about intelligence or experience. It's about distance from survival. Colony events are legible because evolution already gave us a framework for them. Corporate events require you to construct the framework before you can construct the plan. Lockwood events require you to question whether the framework you've constructed is the right one.

That's not easier or harder in any simple sense. It's a category shift. The same person who breezes through Colony and scores mostly Strong will sit with a Corporate event for ten minutes wondering what they're actually deciding — not because they're less capable, but because the thinking required is structurally different.

And that thinking time is not wasted time.

When I read a difficult Corporate event, my heart sinks. I want an easy one. I swap tabs. I fiddle with my emails. I let it sit. I come back. I start thinking "I could do that" then "no, that's terrible" then "unless..." then "but what if..." The answer I eventually submit is rarely the first thing I thought of. Often it's significantly better than the first thing I thought of.

Most productivity culture would call the email-fiddling stage procrastination. I'm not convinced it is. The problem was sitting in the background the whole time, being turned over. Different framings were competing for attention. The conscious mind had stopped poking it. The question was still active.

This is what Last Prompt is actually asking for. Not speed. Not certainty. Percolation.

The events are deliberately under-defined. Your first interpretation is often not your best interpretation. The insight comes several minutes later — sometimes after you've wandered off. The players who immediately type the first thing they think often get caught by the Mandate. The players who sit with the event long enough to see the consequences, the trade-offs, the competing priorities, tend to write plans that survive contact.

But here is the thing that makes Last Prompt different from simply "take more time."

The problem doesn't go away while you're thinking.

Most systems give you an out. Wait for more information. Escalate to someone with more authority. Request another report. Bounce it to the appropriate team. The default is: if in doubt, defer.

Last Prompt removes the out. Nobody is coming to rescue you from the problem. No additional report is arriving. No one to escalate to. The forty-seven employees are still resigning. The infrastructure is still failing. The potato is still in your hands.

This is closer to how real consequential decisions work than most training environments are willing to admit. The important decisions are not usually made with complete information. They are made with incomplete information and a deadline — real or implied. The question is not whether you're ready. The question is whether you've spent enough time sitting with the problem to understand what you're actually deciding.

Hot Potato says: get rid of it before it burns you.

Last Prompt says something different. The potato cools. The urgency fades. The emotional reaction settles. The initial panic loses its grip. And the problem is still exactly where it was when it arrived. Nothing around you has changed. Nobody is taking it back.

At some point you realise the challenge was never holding the potato.

The challenge was knowing when you had thought about it enough to finally put it down.

That's not a timer. There's no signal. There's no one to tell you. You have to decide that too.

When I wrote the events, I was standing above the maze — seeing all the routes, enjoying the design of the challenge, knowing which options would hurt and which would help. The player can't see that. The player is inside the maze, in an environment moulded by their own reasoning patterns, with stats they've been building or neglecting for several cycles, holding a problem that arrived uninvited and won't leave until they decide what to do about it.

I didn't understand how different those two positions were until I became the player myself.

And what I learned — in the gap between reading the event and eventually writing the plan — is that the thinking time is not the delay before the real work starts.

It is the real work.

How long is long enough? Long enough to stop seeing only your first interpretation. Long enough for the wrong answers to fall away. Long enough to know what you're actually deciding rather than what you initially thought the problem was.

You'll know. Not because a timer goes off. Because at some point the potato feels different in your hands — not cooler, not lighter, but clearer. The urgency has settled into something quieter and more manageable. The problem hasn't changed. You have.

That's when you write the plan.