.jpg)
There is a distinct tension that arises when we are stuck. It is that familiar, muddy feeling of knowing something is wrong but lacking the vocabulary to fix it. We flail. We search for vague phrases online. We ask colleagues half-formed thoughts, hoping they can read our minds and provide the magic solution.
We obsess over the solution, often ignoring the mechanism that gets us there: the question itself.
The Victorian critic and social thinker John Ruskin offered a piercing insight into this struggle. He didn't focus on the intelligence required to find an answer, but rather the discipline required to frame the inquiry.
"To be able to ask a question clearly is two-thirds of the way to getting it answered." - John Ruskin
This isn't just a nice aphorism. It is a fundamental truth about human cognition, software development, and strategic problem-solving. When we are confused, it is rarely because the world is hiding the answer. It is usually because we haven't yet done the hard work of defining what we are actually looking for. As various resources suggest, the ability to ask the right questions is a crucial skill for finding solutions and fostering curiosity. Books like "The Art of Asking: Ask Better Questions, Get Better Answers" delve into this very skill, highlighting its often underappreciated importance.
The Fog of Vague Inquiry
Most of us move through our professional and personal lives asking lazy questions. In the technology sector, we see this constantly.
Why isn't this system working?
How do I get better data?
What should we automate next?
These questions are emotional reactions rather than strategic tools. They are too broad to be actionable. When you ask a vague question, you force your brain (or your development team) to search an infinite dataset for a specific needle. It is exhausting, and it rarely yields a satisfying result.
Ruskin's quote suggests that the answer is often hiding in plain sight, camouflaged by our own lack of specificity. As we work with clients to interpret complex workflows at FlowDevs, we often find that the technical solution is simple. The hard part is framing the business logic clearly enough to build it. Journalist and innovation expert Warren Berger, in his book "A More Beautiful Question," emphasizes that successful people are often expert questioners who raise questions no one else is asking, ultimately finding answers everyone else is seeking.
Why Clarity Is Two-Thirds of the Work
Ruskin assigns a specific value to clarity: two-thirds. This implies that the majority of the heavy lifting happens before the investigation even begins. Why is the setup so valuable? It comes down to three factors.
1. It Eliminates Noise
A clear question acts as a filter. If you ask, "How can we grow our business?" you invite a thousand distracting answers about marketing, sales, hiring, and product features.
However, if you ask, "How can we increase retention among customers who have been with us for less than three months?" the noise vanishes. You have narrowed the field of view. You know exactly where to look. In the realm of AI and data, this is the difference between a hallucination and an actionable insight.
2. It Reveals the Gap
Often, the act of trying to formulate a clear question reveals that you do not understand the problem yet. You cannot ask a precise question about a system you don't understand. The struggle to articulate the question is the learning process. By the time you can say it clearly, you have already mapped the territory. This discovery process is key to what some educators refer to as creating a "culture of inquiry," where students and professionals alike chase their own curiosity to find answers.
3. It Invites Collaboration
Have you ever tried to help someone who couldn't explain what they needed? It is frustrating. Conversely, when someone comes to you with a razor-sharp inquiry, you can usually help them in seconds. Clarity respects the listener's time. It turns a plea for help into a solvable puzzle.
This is central to how we approach partnerships. Whether we are consulting on Power Automate flows or building custom apps, we start by refining the question until the answers become obvious.
How to Sharpen Your Questions
Applying Ruskin's philosophy requires a shift in habit. It means pausing before you speak or type. It means treating the question as a draft that needs editing. The skill of "asking questions" itself is a very important skill, as highlighted in online discussions about the art of asking.
The "Five Whys" Technique
Originating from the Toyota production system, this method involves asking "Why?" five times to get past the symptoms and down to the root cause. A surface question gets a surface answer. A deep question gets a solution. This is particularly useful when debugging broken processes.
Constraint-Based Inquiry
Add constraints to your questions to force creativity. Instead of asking, "How do I make more time?" try asking, "What are three low-value tasks I can delete from my schedule this week to reclaim two hours?" Constraints force you to prioritize.
The "So That" Test
Append "so that" to the end of your question. If you can't finish the sentence, your question isn't clear enough. "I need to know X, so that I can decide Y." This connects your inquiry to a specific outcome.
The Quiet Power of Precision
We live in an age of instant answers. We carry the sum of human knowledge in our pockets, and we have AI assistants ready to generate content at the click of a button. Yet, confusion seems more prevalent than ever. Access to information hasn't solved our problems because information is useless without the correct query.
In the era of AI and intelligent automation, prompt engineering is essentially the technical application of Ruskin's logic. The output is only ever as good as the input.
When we stop flailing and start defining, the panic subsides. The mud settles. The path forward appears, not because we found a magical new map, but because we finally figured out where we were standing.
The next time you face a digital wall or a process bottleneck, don't throw yourself against it. Stop. Breathe. And ask a better question. You might find you are already two-thirds of the way home.
If you are looking for a partner to help you ask the right questions and build the systems that answer them, we are here to help. You can schedule a time with our team at https://bookings.flowdevs.io so we can start untangling your improved digital future.
There is a distinct tension that arises when we are stuck. It is that familiar, muddy feeling of knowing something is wrong but lacking the vocabulary to fix it. We flail. We search for vague phrases online. We ask colleagues half-formed thoughts, hoping they can read our minds and provide the magic solution.
We obsess over the solution, often ignoring the mechanism that gets us there: the question itself.
The Victorian critic and social thinker John Ruskin offered a piercing insight into this struggle. He didn't focus on the intelligence required to find an answer, but rather the discipline required to frame the inquiry.
"To be able to ask a question clearly is two-thirds of the way to getting it answered." - John Ruskin
This isn't just a nice aphorism. It is a fundamental truth about human cognition, software development, and strategic problem-solving. When we are confused, it is rarely because the world is hiding the answer. It is usually because we haven't yet done the hard work of defining what we are actually looking for. As various resources suggest, the ability to ask the right questions is a crucial skill for finding solutions and fostering curiosity. Books like "The Art of Asking: Ask Better Questions, Get Better Answers" delve into this very skill, highlighting its often underappreciated importance.
The Fog of Vague Inquiry
Most of us move through our professional and personal lives asking lazy questions. In the technology sector, we see this constantly.
Why isn't this system working?
How do I get better data?
What should we automate next?
These questions are emotional reactions rather than strategic tools. They are too broad to be actionable. When you ask a vague question, you force your brain (or your development team) to search an infinite dataset for a specific needle. It is exhausting, and it rarely yields a satisfying result.
Ruskin's quote suggests that the answer is often hiding in plain sight, camouflaged by our own lack of specificity. As we work with clients to interpret complex workflows at FlowDevs, we often find that the technical solution is simple. The hard part is framing the business logic clearly enough to build it. Journalist and innovation expert Warren Berger, in his book "A More Beautiful Question," emphasizes that successful people are often expert questioners who raise questions no one else is asking, ultimately finding answers everyone else is seeking.
Why Clarity Is Two-Thirds of the Work
Ruskin assigns a specific value to clarity: two-thirds. This implies that the majority of the heavy lifting happens before the investigation even begins. Why is the setup so valuable? It comes down to three factors.
1. It Eliminates Noise
A clear question acts as a filter. If you ask, "How can we grow our business?" you invite a thousand distracting answers about marketing, sales, hiring, and product features.
However, if you ask, "How can we increase retention among customers who have been with us for less than three months?" the noise vanishes. You have narrowed the field of view. You know exactly where to look. In the realm of AI and data, this is the difference between a hallucination and an actionable insight.
2. It Reveals the Gap
Often, the act of trying to formulate a clear question reveals that you do not understand the problem yet. You cannot ask a precise question about a system you don't understand. The struggle to articulate the question is the learning process. By the time you can say it clearly, you have already mapped the territory. This discovery process is key to what some educators refer to as creating a "culture of inquiry," where students and professionals alike chase their own curiosity to find answers.
3. It Invites Collaboration
Have you ever tried to help someone who couldn't explain what they needed? It is frustrating. Conversely, when someone comes to you with a razor-sharp inquiry, you can usually help them in seconds. Clarity respects the listener's time. It turns a plea for help into a solvable puzzle.
This is central to how we approach partnerships. Whether we are consulting on Power Automate flows or building custom apps, we start by refining the question until the answers become obvious.
How to Sharpen Your Questions
Applying Ruskin's philosophy requires a shift in habit. It means pausing before you speak or type. It means treating the question as a draft that needs editing. The skill of "asking questions" itself is a very important skill, as highlighted in online discussions about the art of asking.
The "Five Whys" Technique
Originating from the Toyota production system, this method involves asking "Why?" five times to get past the symptoms and down to the root cause. A surface question gets a surface answer. A deep question gets a solution. This is particularly useful when debugging broken processes.
Constraint-Based Inquiry
Add constraints to your questions to force creativity. Instead of asking, "How do I make more time?" try asking, "What are three low-value tasks I can delete from my schedule this week to reclaim two hours?" Constraints force you to prioritize.
The "So That" Test
Append "so that" to the end of your question. If you can't finish the sentence, your question isn't clear enough. "I need to know X, so that I can decide Y." This connects your inquiry to a specific outcome.
The Quiet Power of Precision
We live in an age of instant answers. We carry the sum of human knowledge in our pockets, and we have AI assistants ready to generate content at the click of a button. Yet, confusion seems more prevalent than ever. Access to information hasn't solved our problems because information is useless without the correct query.
In the era of AI and intelligent automation, prompt engineering is essentially the technical application of Ruskin's logic. The output is only ever as good as the input.
When we stop flailing and start defining, the panic subsides. The mud settles. The path forward appears, not because we found a magical new map, but because we finally figured out where we were standing.
The next time you face a digital wall or a process bottleneck, don't throw yourself against it. Stop. Breathe. And ask a better question. You might find you are already two-thirds of the way home.
If you are looking for a partner to help you ask the right questions and build the systems that answer them, we are here to help. You can schedule a time with our team at https://bookings.flowdevs.io so we can start untangling your improved digital future.
Related Blog Posts
From “Can We Build It?” to “Should We Build It?”: Product Strategy After AI
