The question you ask before the answer
One practice for the meeting where you usually have the answer
On the 23rd July’s the last essay asked who you are without the answer. Not as a thought experiment. As a diagnosis.
Essay asks → Practice moves → Patching explains
This is the practice that moves it from something you read to something you can feel. Not in a workshop. In your next meeting.
Before the end of this week.
The setup
The wallpaper was still peeling at the corner where we had rushed the last strip.
I remember being in an architecture review. The team had the diagram. They had the trade-offs. They had the recommendation. I had seen this meeting a hundred times. The pattern was clear. The senior person in the room, usually me, would listen for two minutes, spot the flaw, name it, and offer the fix. The room would nod. The decision would be made. The meeting would end on time.
This time I did something different. I did not say the flaw. I asked a question instead.
The question was not “have you considered X?” That is a dressed-up answer. The question was “what would make this fail in six months?” And then I waited. The silence lasted eleven seconds.
I counted. Someone who had not spoken in three reviews said something that changed the decision.
I am telling you this because I almost did not do it. The answer was in my head before the question was. The answer was faster. The answer was safer. The answer would have ended the meeting with my expertise confirmed and my identity intact. The question risked making me look like I did not know.
That is the point. The practice is not about better meetings. It is about locating your professional identity somewhere the machine cannot reach.
The practice
In your next meeting where you would normally provide the answer, do this instead.
The sentence to try
What would make this not work?
Not “what are the risks?” That invites a list. Not “what could go wrong?” That invites reassurance. “What would make this not work?” invites the room to think against the proposal. And it invites you to listen.
The boundary to hold
Do not answer your own question. Not with a follow-up or with a hint. Not with body language that steers toward the flaw you already see. The practice is the restraint. The machine can produce the answer. It cannot produce the silence that lets someone else find it.
The time to wait
Count to ten. Out loud in your head. One Mississippi. Two Mississippi. The silence will feel like failure. It is not failure. It is the space where judgment begins to replace function.
The debrief
What you are looking for is not whether the team finds the same flaw you saw. They might. They might not. What you are looking for is what happens in you during the ten seconds.
If you feel anxiety, that is the identity talking.
The part of you that is still paid to be the person who knows. The part that believes worth flows from having the answer ready. That anxiety is not a signal to abort the practice. It is the signal that the practice is working. The anxiety is the old identity leaving the room. Let it stay for the ten seconds too.
If the meeting runs longer, that is cost. The practice has cost. Efficiency is not the goal. Formation is.
I tried this in three meetings last week. I failed in two of them.
In the first, I asked the question and then answered it myself four seconds later. I told myself I was clarifying. I was performing. The room nodded. The decision was made. The meeting ended on time. My identity was intact. Nothing changed.
In the second, I held the silence for eight seconds. Someone started to answer. I interrupted with a refinement of their answer. I could not let the imperfect thought finish. I needed the answer to be good because the answer reflected on me.
That is functional expertise dressed as collaboration.
The third meeting was the one I described. Eleven seconds. A voice I had not heard in three reviews. A failure mode I had not named. The decision changed. Not because I was wise. Because I was present in a way the machine is not present.
I am still the person who sees the flaw first. That has not changed.
What I am practicing is whether my identity requires me to say it.
That is not a title. That is a way of being. That is the verb.
If you want the full argument behind this practice, “Who Are You Without the Answer?” is the why behind this how. It is free, in your inbox every other Tuesday, and the link is below.
If you have tried this practice and want the mechanics beneath it, why the silence works, what the anxiety signals, how to build the restraint into a habit, that is what Patching the Verb is for. Paid subscribers find it in their inbox.
You can join them here.
About the Author
Diamantino Almeida is a tech leader, coach, and writer reshaping how we think about leadership in a burnout-driven world. With over 20 years at the intersection of engineering, DevOps, and team culture, he helps humans lead consciously from the inside out. When he’s not challenging outdated norms, he’s plotting how to make work more human, one verb at a time.
I personally, think and build decision systems, to determine how decisions are classified, who’s involved, what information is used, and how learning loops work. And these are things are brain is excellent in doing and if we wisely coupled with automation systems, following some structured methods, we are in a great place to be. There are many more, but keep it simple.
What most people don’t talk about is how much this speed-first culture is built on denying us leaders and teams the time and permission to not know, to think, and to design better ways of deciding in the first place.