To frame a question properly, we must first assign it context. Instead of asking, “Should designers code?” we could ask, “Should product designers learn to code prototypes to improve the product process?” It does not elicit a yes or no answer because it depends upon settings and qualification. The question is clear, open, and invites reflection.

“Should designers code?” is usually asked without facts that have been agreed upon. “The more you agree about the question’s framing, the clearer the answer can be,” says Niels Ebdrup.

If people don’t agree upon the question’s context, how can they provide a clear answer? For instance, we wouldn’t want to only ask: “Should designers code?” because it assumes designers want/can code in the first place. Before asking the question, we should set up prompt describing why a certain type of person might be motivated to code in the first place.

A good question does not sacrifice specificity for brevity, but it is concise and focused. We can tell if a question is effective by how people attempt to answer it. A hiring manager once asked me if I thought designers should code. I didn’t know what to say. If he asked, “Should designers code the front-end of their designs to reduce development workload?” I could provide an answer. The context and scenario would have been established, and I would have felt confident supplying a thoughtful answer.

Good questions are researchable: a person can answer the question with evidence. They address a real need or problem. Their framework is not too general or too narrow. Most importantly, they challenge our own assumptions about the world. They hold our interest and inspire us to learn — including code.