At every point in an engagement, starting on literal day one and updated at every team huddle after that, you should be able to state your current best answer to the client's question in one sentence. Add a candid confidence level and the one or two things that would change your mind, and you have the one-day answer. Always holding one keeps a team's work pointed at the actual question, so it doesn't drift into research for its own sake.
What makes a good one-day answer?
The one-day answer steers between two failure modes. On one side is premature conclusion: treating today's provisional guess as a final verdict and defending it against new evidence. That's confirmation bias wearing an operational hat. On the other side is paralysis, refusing to state any position until "the analysis is complete." It sounds humble, but it dodges accountability. It's also the instinct that produces boiling the ocean, since a team with no current answer can't tell which further analysis even matters. A good one-day answer avoids both. You state it with real conviction, date it, make it falsifiable, and cheerfully discard it the moment good evidence contradicts it.
The practical check is the elevator test. If the partner stepped into an elevator right now and asked "where are we?", could you give a useful answer in the thirty seconds before the doors open, without hedging? "We're still looking into a few things" fails completely. It commits to nothing and could be said on day one or day ninety. Now try this one: "Our best read right now, about 70% confidence, is that the margin decline is concentrated in two SKUs and driven by input costs, not pricing; we'd change our mind if the vendor invoices come back flat." That passes. It's specific, dated and falsifiable. It also tells the partner what to watch for.
Advertisement
How does a one-day answer differ from the final pyramid?
Notice what the one-day answer isn't. It isn't yet Minto's governing thought, key line and support structure. That polished, client-ready pyramid belongs to the synthesis work that comes next, and you build it only once the hypothesis has been tested to destruction. The one-day answer is the team's private compass. The pyramid is the finished map you hand the client. Mixing them up is one of the more common structural errors, and it happens in both directions: treating a one-day answer as client-ready, or refusing to state one until you have pyramid-grade certainty.