--- title: "The Questions Nobody Wrote Down - In Parallel" description: "Open questions are the most under-managed objects in any company. Not a task, not a decision — so they fall through the gap between them, until a launch slips." url: https://www.in-parallel.com/insight/the-questions-nobody-wrote-down --- Intelligent Management System # The Questions Nobody Wrote Down In Parallel answering “What’s still unanswered before launch?” — surfacing the unresolved open questions in the Holiday Peak Readiness workspace. Published July 23, 2026 Kristian Luoma Co-founder, CPO kristian@in-parallel.com [LinkedIn](https://www.linkedin.com/in/kluoma/) Contents > The questions nobody wrote down > `❓ Open questions` — _“What’s still unanswered before launch?”_ Jordan raises it in week two, in passing, near the end of a planning call: “Do we need legal to review the new terms?” Nobody owns it. It isn’t a task, because there’s nothing to do yet — just something to find out. So it doesn’t become an action item, doesn’t land on a board, doesn’t go anywhere. It sits in a transcript, unanswered, until week nine, when it becomes the reason the launch moves. Open questions are the most under-managed objects in any company. Decisions get recorded because they feel important. Tasks get tracked because someone has to do them. A question — an honest “we don’t know yet” — has no natural home. It isn’t a decision and it isn’t a task. It’s the thing that has to be resolved _before_ either of those can happen, and it routinely falls straight through the gap between them. ## Why the gap exists Tools are built around things you can act on. A task has an owner and a verb. A decision has an outcome. A question, by contrast, is defined by its lack — you raise it precisely because you don’t yet have the answer. There’s no checkbox for “find out.” So the question gets spoken, acknowledged, and orphaned, because the system has nowhere to put a thing whose entire status is _unresolved_. This produces a particular kind of organisational blindness. Ask a team mid-project what they’re still unsure about and you’ll get a thoughtful pause and a partial list, assembled from memory. The real list — every open question raised across every meeting, still unanswered — exists nowhere. It was never written down as a list. If it was written down at all, it was scattered lines in scattered transcripts, each invisible to the others. And open questions have a nasty timing property. They’re cheapest to resolve when they’re first raised and most expensive when they’re discovered late. Jordan’s legal-review question costs an email in week two and a slipped launch in week nine. Same question. The only variable is how long it sat unowned. ## The move: hold the question until it’s answered The capability does something simple: it treats an open question as a record that persists until someone resolves it. Not a task. Not a decision. A question, held as a first-class object, with its own life and its own states — asked, assigned to whoever will answer it, being answered, answered, closed. That persistence is the whole point. A question that is a record can’t be orphaned, because the record doesn’t disappear when the meeting ends. It stays open — visibly, queryably open — until it moves to answered. The status _unresolved_ finally has somewhere to live. Two things follow. **You can see the real list.** “What’s still unanswered before launch?” stops being a question you answer from memory and becomes one shared context resolves from its records. Every open question raised across the project, in whatever meeting, still unanswered — surfaced as one list. The blindness came from the questions being scattered. Holding them as records is what un-scatters them. **A question can be assigned without being a task.** A subtle distinction, but a real one. You can hand someone an open question — make them the answerer — without pretending you already know what the work is. The thing that was un-trackable because it had no verb now has an owner anyway. Resolution becomes someone’s job before the answer is known, which is exactly when it needs to. ## The discipline of asking out loud There’s a cultural effect worth naming here. When open questions have a home, raising one stops being a small admission of ignorance and becomes a normal, even valued, act. “I don’t know yet, and here’s the question” is a contribution, not a gap. Amy Edmondson’s research on psychological safety found that teams perform better partly because people surface what they don’t know early. A substrate that holds open questions as respectable, trackable objects gives that instinct something to lean on. The question gets recorded instead of swallowed. The reverse is the failure we started with. In a team where there’s nowhere to put a question, the safest move is to stay quiet and hope someone else owns it. Multiply that across a project and you get a launch full of things everyone half-wondered about and nobody asked. ## What this is not It is not a way to defer decisions by relabelling them as questions. Some things presented as “open questions” are actually decisions someone is avoiding making. The capability holds genuine unknowns; it can’t tell the difference between “we need to find this out” and “we’re scared to decide.” That discernment stays with the team. Nor is it a guarantee of an answer. Holding a question makes it visible and ownable. It doesn’t produce the legal review, run the experiment, or make the call. An open question that sits in “assigned” for six weeks is still unresolved — better seen, but not yet answered. Visibility is necessary and not sufficient, and there’s no point pretending otherwise. ## The honest limit What this removes is the orphaning: the question that falls through the gap between tasks and decisions, the launch derailed by something someone asked in week two, the partial list a team assembles from memory because the real one was never written down. What it can’t remove is the discomfort of not knowing. A company that surfaces all its open questions is a company looking squarely at everything it hasn’t figured out yet, and that list is sometimes longer than anyone would like. We think that’s the right discomfort to have. The questions are there whether or not you write them down. Written down, at least, they can be answered before the launch — not after. The fourth of six pieces on what a shared record holds, after [Action Items That Outlive the Meeting](https://www.in-parallel.com/insight/action-items-that-outlive-the-meeting). ### Get insights like this in your inbox One email per week on execution intelligence, team coordination, and enterprise AI. No fluff. By subscribing you agree to our [Privacy Policy](https://www.in-parallel.com/privacy-policy). Unsubscribe anytime. [Back to all insights](https://www.in-parallel.com/insight) [Book a demo](https://www.in-parallel.com/demo) ## Related articles The Coordination Tax — Richard H. Carson on how change actually works Leadership Insights · Oct 20, 2026 ### You Either Manage Change or It Manages You: Richard H. Carson on how change actually works Richard H. Carson, PhD — 40 years inside county governments, regional planning agencies, nonprofits, and the state of Oregon — on why every organization has a risk manager but almost none has a change manager, and what that asymmetry costs. A rope suspension bridge over a dark river towards the fells, drawn in pen and watercolour AI in Business · Oct 9, 2026 ### AI-Assisted or AI-Native: The Bridge Is Shared Context At a CIO data event in Espoo, HumanX in Amsterdam and a post-merger integration forum, large companies explained how they brought AI in by mapping processes and fitting AI into the gaps. That keeps a structure built around human limits. Getting to AI-native means rebuilding information flows into shared context first. The Coordination Tax — Adam Christing on humor as leadership Leadership Insights · Oct 7, 2026 ### You Can't Fix Culture With a Mission Statement: Adam Christing on humor as leadership Adam Christing — professional master of ceremonies, founder of Clean Comedians, and author of The Laughter Factor — on why culture is a feeling rather than a statement, and why humor is the fastest way for a leader to shift it. The Coordination Tax — Jennifer Recla on the urgency mindset breaking your team Leadership Insights · Sep 22, 2026 ### Urgency Isn't Leadership. It's Addiction: Jennifer Recla on the mindset breaking your team Jennifer Recla — leadership coach who has worked with hundreds of leaders across nonprofits, mission-driven organizations, and large financial institutions — on the urgency mindset behind most organizational chaos, and why most leaders have no idea how much of it they're creating themselves. The Coordination Tax — Barry Wolfe on value-centric leadership Leadership Insights · Sep 15, 2026 ### HR Is the Last Line of Defense Against Chaos: Barry Wolfe on value-centric leadership Barry Wolfe — HR consultant, founder of Argos HR, and author of It's All in Your Head — on why HR is the last line of defense against organizational chaos, why every role needs 3–5 clear value outcomes, and why the foundation of a well-run company is one document under 300 words. Two colleagues sharing one open binder — context handed over at the resolution the other person needs Leadership Insights · Sep 9, 2026 ### Your Job Is Already Context Management On The Coordination Tax, Stanford's Robert E. Siegel put it as an equation: truth equals facts plus context. Facts are cheap now. Context is not. Read the manager's week against that equation and the 16.5 hours a week lost to coordination stop looking like overhead — they are context management, performed manually, by the most expensive person in the room. The Coordination Tax — Alberto Torres on surviving disruption Leadership Insights · Sep 8, 2026 ### You Can't Sword-Fight a Bullet: Alberto Torres on surviving disruption Alberto Torres — former Nokia executive, ex-McKinsey partner, and author of The Z Curve — on what actually happened at Nokia, why great peace-time leaders quietly fail in war-time, and what every company facing AI right now should learn from the companies that got disruption right. The Coordination Tax — Olivia Montgomery on why decisions belong lower in the org Leadership Insights · Sep 1, 2026 ### Your Leadership Doesn't Know What's Going On: Olivia Montgomery on why decisions belong lower in the org Olivia Montgomery — principal analyst at Data Frame and former Gartner researcher — on why every layer up the org chart knows less about what's really going on, and why the fix isn't more visibility for leadership but pushing decisions down two or three levels. The Coordination Tax — Craig Denison on the founder's hardest transition Leadership Insights · Aug 25, 2026 ### You Don't Get to Be the Rock Star Anymore: Craig Denison on the founder's hardest transition Craig Denison — head of growth at The Table Group (Patrick Lencioni's firm) and founder of Green Thumb Consulting — on the transition every founder hits when execution stops running through their brain, and why 99% of the time the founder is creating the dysfunction they are trying to fix. A manager mid-explanation, watch visible — the hour spent re-explaining context AI in Business · Aug 24, 2026 ### AI Saves a Day a Week. The Coordination Tax Collects It. BCG's fourth AI at Work survey found 42% of regular frontline AI users save at least a full workday every week, and that two-thirds get little or no guidance on what to do with it. The usual reading is that leaders forgot to give direction. The better reading is that the hours were already spoken for. AI compresses the work; it doesn't touch the work about the work.