The Hidden Signal in How You Write Under Time Pressure

There's a quality of thinking that only shows up under time pressure. In a 48-hour take-home case study, most candidates can produce a polished document with clear structure and well-sourced claims. Under a 90-minute challenge timer, fewer can.

The ones who can are almost always better employees.

What "communication quality" actually measures

When we score a Capability Challenge submission on Communication, we're not checking for grammar. We're looking at something more specific: does this person write the way they think, or do they write around their thinking?

Good writing under pressure is direct. It makes claims before supporting them. It uses short paragraphs. It doesn't hedge every sentence with qualifiers. It's confident about what it knows and explicit about what it doesn't.

Bad writing under pressure is circular. It restates the brief. It uses passive voice to avoid taking a position. It buries the conclusion at the end after three paragraphs of context that don't add information.

These patterns are visible in a first draft in a way they aren't in a polished, edited document.

The unexpected event

Partway through every challenge, we introduce an unexpected event — a message from the AI CEO or colleague that changes a constraint, adds a requirement, or challenges an assumption you've already built on.

How candidates respond to this event is one of the most informative parts of the submission. Some ignore it entirely and continue with their original plan. Some pivot completely, abandoning what they'd already written. The best candidates acknowledge the event explicitly in their deliverable, explain what it changes and what it doesn't, and continue with an updated plan.

This mirrors how real work actually happens. Plans change. Stakeholders add constraints. The ability to adapt without losing the thread of what you were doing is exactly what good senior employees do.

What we score vs. what you can game

You can prepare for a Morrio challenge the same way you'd prepare for any timed case study: practice structuring arguments quickly, practice writing in short direct sentences, practice making decisions with incomplete information.

But you can't really fake the unexpected event response, because you don't know what it's going to be. And you can't fake the overall coherence of a submission — whether the pieces fit together, whether the final recommendation follows from the analysis, whether the deliverable actually addresses the brief.

That's the signal. And it turns out to be a good one.