Here’s my process for using questions to navigate ambiguity: Start with a “question dump” Organize by power Seek answers systematically Iterate and refine Document and share https://alifeengineered.substack.com/p/the-art-of-dealing-with-ambiguity

Using natural language (or diagrams) to describe how to break down and precisely solve a novel problem (scalably and securely) is not easy and never will be easy. The key skills needed for software engineering are: requirements gathering / analysis, abstraction, data modelling / ontology building, algorithms, modularity / separation of concerns, team building / communication, threat modelling / security, debugging / problem determination, operations and monitoring, and ultimately… Not Building The Wrong Thing.

You can get to the real cause of an issue by asking why 5 times.

When a customer brings a complaint, there are always two tokens on the table: “It’s no big deal” and “It’s the end of the world”. Both tokens are always played, so whoever chooses first forces the other to grab the token that’s left. Don’t force your customer into taking the “It’s the end of the world” one. https://brunopedro.com/