liveBook · Manning

Lack of clarity

As explained in Think Like a Software Engineering Manager

Lack of clarity is insufficiently specific instructions, goals, expectations, or success criteria for completing assigned work.

Lack of clarity occurs when instructions, goals, priorities, or success criteria are too vague to guide assigned work. In delegation and expectation-setting, it can create misunderstandings, open-ended questions, misaligned expectations, and poor results. section 5.6 section 11.2.1

Make expectations clearer by checking:

  • What outcome is expected, and how will successful completion be recognized? section 11.2.1
  • What timeline, prerequisites, dependencies, priorities, and supporting documentation apply? section 11.2.1
  • Who can provide guidance, and whether regular progress reports or prioritization help are needed. section 11.2.1
  • Whether the assigned person has the skills required, since a mismatch can make expectations unrealistic. section 11.2.1

A vague deployment request

Asking Bob to deploy code changes may sound straightforward, but it can raise questions about prerequisites, timing, documentation, support, reporting, and the expected result. Asking precise questions turns assumptions into shared expectations. section 11.2.1

How Think Like a Software Engineering Manager covers it

How deep it goes
Explains causes and consequences through workplace examples, then offers a practical checklist of clarification questions.
Examples
Uses vague deployment instructions, skill mismatches, unclear priorities, and clarification questions as workplace examples.
What it assumes
Assumes a task-assignment context and teaches newcomers to surface assumptions by asking precise questions.
What you can do after
Apply it by asking precise questions that establish outcomes, timelines, dependencies, support, and reporting expectations.
How it connects
Connects delegation and expectation-setting with ambiguity, priorities, dependencies, support, and autonomy.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.