Sometimes non-technical superiors (matrix managers) from other departments spot something that didn't work as expected or are annoyed that we cannot deliver a project by a certain deadline; or cannot push harder.
This may be due to a technical limitation, a bug or similar.
Instead of accepting the revised feedback or new proposed timelines, they insist that they want to know "everything" about the process so that they can try and see how they can help make things faster or ensure we don't repeat the "mistake".
But in most cases it is indeed a technical reason, often something we still need to explore, or other times, something that never happened before and will rarely happen again. I have witnessed how this kind of managers just nod when we try to explain them the technical details. After explaining, they ask something like "So can't we get this done faster?"
In reality, I feel like it is just a technique to put pressure on us rather than try to understand, and often just ends up taking away more time from actually addressing the issue - but I might be wrong.
Anyway, what should I do when a non-technical manager asks that they want to know and understand "everything" about why something went wrong or cannot be delivered by deadline?
CLARIFICATIONS - just wanted to make sure it is clear to all that I want to help and cooperate as much as possible; I would like to be more effective in what exact information I share.
However, the main point is that as I am given projects and deadlines by multiple superiors (matrix managers again!) I need to decide and prioritize what is more important for the day: e.g. work towards meeting deadline of manager A or discuss with manager B, when I could instead both fix B and meet the deadline of A if I skip the discussion. I cannot meet deadline of manager A and discuss B and fix B. In such a case, what would you chose?
The other point is that sometimes I myself don't know and require action from other technical experts to help clarify the situation.