He noticed it before anyone brought it to him.
A young engineer. A large technical assignment. A deadline that came and went without a deliverable. No questions asked along the way. No flags raised. Just silence where progress should have been.
His first instinct was frustration. The work was not done. The timeline had slipped. As a technical leader he knew exactly what the task required and could not understand why someone would accept an assignment and then disappear into it without producing anything.
Then he had a discussion. He looked at what he might have missed.
He had assigned the work based on the resume. The projects listed were substantial. The scope looked right for the level of the assignment. He had assumed those projects came from a previous company. Professional environment. Real stakes. The kind of experience that prepares someone for exactly this kind of work.
They were school projects.
Different scope. Different stakes. Different everything. The young engineer had never operated at this level in a professional environment. He accepted the assignment because he did not yet know what he did not know. He asked no questions because he could not identify what to ask. He missed the deadline because the gap between what the work required and what he actually had was invisible to both of them until it was not.
The frustration shifted.
Not at the young engineer. At himself.
He had made an assumption where he should have asked a question. He read the resume and skipped the conversation that would have told him what the resume could not. One question before the assignment, tell me about this project, walk me through what you did, would have revealed everything. Instead he assumed and assigned and waited for a result that was never going to come.
That is the part of accountability most leaders miss.
It is not just about holding people to expectations. It is about making sure the expectations you set are ones the person can actually meet. Clear expectations require more than stating what you want. They require understanding what the person in front of you is actually capable of right now, not what their resume implies, not what you assumed, but what a real conversation would have told you.
He rescoped the project. Had the conversation he should have had at the start. Matched the assignment to where the young engineer actually was rather than where he assumed him to be.
The young engineer is thriving.
Accountability runs in both directions. The employee owns their performance. The leader owns the clarity and the conditions that make performance possible.
When a gap appears on your team, ask the harder question first.
What did I assume that I should have verified?
If you are navigating a performance gap right now and are not sure where it started, I am happy to think through it with you. dieleconsulting.com.