work in progress
The mindset 2 min System Scope: authority over the conditions involved

⇄ Nobody asks twice

What you are asking for

“I’d like the questions to arrive before we’ve built the solution.”

You want to know the doubts early enough for them to inform the decision.

What the system hears

“If I ask this question, who will answer, and how long will it take?”

What that produces

A question left without a follow-up can discourage the next one. The person does not know whether they were forgotten, whether they overstepped their role, or whether the answer simply takes time.

The example is common: a question about a project’s goal gets answered in a meeting of three. The colleagues who were not there carry on with a different reading. The problem can lie in the path the answer took, not in a lack of curiosity or in bad intent.

Answering usefully sometimes takes research. An announced deadline lets people organise. A fast but uncertain answer has to keep that uncertainty visible. Depending on the urgency, the person can move on a reversible part, wait, or ask for a ruling.

Making the follow-up visible does not necessarily need a new tool. The document or the thread where the work is discussed can hold the question, who is taking it, and the date it comes back. Personal or sensitive exchanges keep a readership that fits.

The decision

With the team, choose one place for the questions that bear on a decision. On the next one, say who is looking for the answer and when it is needed. If you cannot handle it, say so and agree another route.

At the end of the week, go back over a few open questions. Check whether the answer reached the people affected and what it made it possible to decide. Adjust the deadlines by subject. An acknowledgement helps people organise what comes next; it does not stand in for a real answer.

From where you sit

To discuss

Which question is still waiting for a follow-up, and what would let whoever asked it know how to move?

Discuss this