Navigating ambiguity is an essential skill for staff-plus engineers and executives. It involves tackling deeply ambiguous problems that span cross-functional boundaries and have significant consequences.
Examples of deeply ambiguous problems include navigating data locality regulations and interpreting HIPAA requirements, where there is no clear right answer and multiple stakeholders need to align.
The process for navigating ambiguity involves:
a. Mapping out the state of play - understanding the problems, gaps in cross-functional awareness, and key stakeholders
b. Developing potential options and their trade-offs
c. Driving a decision through a documented process, while aligning on criteria to reopen the decision
Challenges include trying to solve the problem too early, before the organization is ready to make a decision, and lacking an executive sponsor to back the process.
The key advice is to not get stuck - escalate when needed, slow down if the timing is off, and avoid alienating stakeholders even if you can't make progress.
Navigating ambiguity is a rare skill, but a critical one for staff-plus engineers and executives to develop in order to drive important decisions in the face of uncertainty.
https://lethain.com/navigating-ambiguity/
Post #556
759
Forwarded from Software Engineer Updates
Lethain Navigating ambiguity. Perceiving the layers of context in problems will unlock another stage of career progression as a Staff-plus engineer, but there’s at least one essential skill to develop afterwards: navigating ambiguity. In my experience, navigating deeply ambiguous problems…- 👍 3