The Question That Won

The Question That Won

Captain Merin had never won a war game in her life. At the Academy, they called her “the statue”, she could memorize formations until dawn and still fail to see the opening move. Her peers whispered that she’d gotten her rank through some clerical error. The generals had begun to notice too.

Her last assignment before demotion was supposed to be a test: defend a valley against an enemy force twice her size. On paper, it was impossible. In the wardroom at dawn, her officers waited for the strategy that wouldn’t come. Merin sat very still, her hands flat on the table, and said something that made them blink: “I don’t know.”

Then she reached for the old console in the corner, the one nobody used anymore because it ran Legacy, the decision system from before the war, before anyone cared about such things. She’d found it in a storage locker three months ago and kept it running out of habit.

“Legacy,” she said, “we’re going to lose if we think like soldiers. What would a merchant do with this ground?”

The machine hummed. Text flowed across the screen: a merchant would care about water access, trade routes, which direction goods move, where tariffs collect. Where people naturally gather. Where they linger.

Merin looked at her officers. “They’re expecting us to hold the ridge. What if we don’t hold anything? What if we move the supply line through the old market road, the flooded one nobody uses, and stock it every mile with water and grain? Then we pull back. We let them take the ridge. And then?”

“And then they’re stuck on high ground with no water,” her lieutenant breathed, “and we’re below, controlling every path down.”

“They can’t supply the ridge,” another officer said. “They’ll have to retreat or negotiate.”

Legacy had asked one simple question. Merin had asked it aloud. The answer was already in the system, in history, in human behavior, in the shape of the land itself. All waiting to be seen.

The Thing That Followed

Merin won that battle without firing more than a warning shot. She won the next one by asking Legacy: “What would a farmer protect that we’re not seeing?” The answer saved three towns from burning. The one after that: “What would a prisoner want more than escape?” The answer ended a three-month siege in nine days of careful negotiation.

The generals stopped whispering about demotion. Instead, they whispered about her luck, her strange intuition, her uncanny reads on enemy movement. Nobody asked what she actually did. It would have looked too strange: a young officer with a console in her tent, running conversations with an outdated system, asking the kinds of questions only someone without confidence in her own judgment would think to ask.

Merin never pretended to understand strategy. She understood only how to be lost, and how to ask for help from a machine that had learned to see the human shape of problems.

One evening, after a bloodless capture of a fortified town, her commanding general visited her tent. He saw Legacy humming in the corner, the conversation log scrolling.

“You’re consulting that?” he asked.

Merin didn’t lie. “Yes, sir. I ask it things I’m afraid to assume I know.”

The general was quiet for a long moment. Then he said something that surprised her: “That’s wisdom. Knowing what you don’t know. Most officers spend their whole careers learning to hide it.”

He sat down. “Show me how.”

The Question That Spreads

Within six months, every command post had a decision support console running alongside standard systems. Officers learned to ask them: “What did this region look like before the conflict?” “What matters to people who live here, not to us?” “What have we stopped noticing?” “What would our enemy do if they were scared instead of angry?”

The questions weren’t tactical. They were human. And human questions made the war smaller, not in scope, but in cruelty. When you asked what scared an enemy commander instead of how to outflank him, you learned that he had a family in a town you could protect. Negotiations opened. Hostages came home. Whole regiments stopped dying to hold positions that only mattered in the abstract.

Merin was promoted to general, not because she became better at strategy, but because she became better at asking what she didn’t understand. She kept Legacy running beside the new systems. She never trusted her instinct alone. She was, in her own way, the worst general the army had ever trained, and therefore the best.

On the last day of the conflict, Merin sat with the enemy general across a plain table, rain falling softly outside the tent. They were negotiating terms that would hold.

“How did you do it?” he asked her. “How did you win every battle and lose so few people?”

Merin thought about how to answer. She could have talked about morale, positioning, logistics. Instead she said: “I kept asking the wrong questions. And I kept listening to a machine old enough to remember that wars are fought by people, not pieces.”

The general smiled, a real smile, not a warrior’s smile. “That’s either the wisest thing I’ve ever heard or the most naive.”

“Yes,” Merin said. “I think so too.”

The Science Behind the Story

A decision support system (DSS) is a tool designed to help people make choices about complex, unstructured problems, exactly the kind that can’t be solved by simple rules or procedures alone. DSSs combine raw data, documents, and analytical models to help decision-makers identify and solve problems in an interactive way. They’re built on the principle that the person using the system understands their domain, but might benefit from a tool that can organize information, show patterns, or ask clarifying questions they hadn’t considered.

The story imagines that an older decision system can serve its core function by reflecting back questions that reframe a problem. This uses real properties of how such systems work: they can recognize patterns in human thinking, combine information from different domains, and suggest novel framings of familiar challenges. The system itself isn’t making strategic decisions, Merin is. The machine helps her ask better questions, which is exactly how a well-designed DSS functions: it’s “an interactive software-based system intended to help decision makers compile useful information” by supporting flexibility and adaptability.

What’s invented in the story: the specific battles, the character of Merin, the exact questions asked, and the notion that an older system might be more useful than a newer one. What’s real: that decision support systems evolved to serve exactly the role described here, helping people make better decisions by combining data, models, and human judgment in an interactive way. The story simply applies that principle to a domain (military strategy) and imagines what it might feel like to use such a system wisely, recognizing that the best decisions come from asking questions we might otherwise avoid.

For related thinking on how support systems can serve collaborative decision-making, see [/articles/decision-support-systems-organizational-processes/] and [/articles/interactive-systems-human-judgment/].

The Question It Leaves You With

If the best decisions come from asking the questions we’re afraid to ask, what problems in your own life might shift if you admitted what you don’t already know? And when we build tools to help us think, are we outsourcing wisdom, or finally giving ourselves permission to ask for it?