A few months ago, I wrote about How to Answer Questions the Smart Way, which was a riff on Eric S. Raymond's classic essay, How to Ask Questions the Smart Way.
One of Raymond's most enduring rules for asking good technical questions is simple: describe the goal, not the step. Don't walk up to an engineer and ask how to split a string with a regular expression when what you are actually trying to do is parse an HTML file. Tell them what you are trying to accomplish, not how you think it should be implemented.
I probably read that essay twenty years ago, and I thought I had internalized it as a basic troubleshooting habit.
Lately, though, I have realized it is much bigger than troubleshooting. Over the last couple of years, a specific phrase has crept into my regular vocabulary at work. I say it so often in work threads and architecture reviews that a teammate recently joked "poisoning the well" had become his term of the week. And on the one occasion I forgot to follow my own rule and jumped straight into proposing a fix during a design discussion, a coworker rightfully yelled at me for poisoning the well.
When I went back and searched my own messages over the last two years, the pattern jumped off the screen. Again and again, in one form or another, I was repeating the same two lines:
- "I have thoughts, but I don't want to poison the well."
- "I see proposed solutions, but I don't see a problem statement."
Whether you are asking a question or reviewing a design, handing someone a pre-packaged solution before you give them the problem poisons the well.
Solutioning in Someone Else's Domain
It is a scene that plays out in almost every data organization. Someone on the reporting side is prepping for a conversation with a data engineering team. They have a real reporting problem to solve, they have done their homework, and they arrive at what feels like a clean, helpful conclusion: "I'll just ask them to add Column X to the table. That should do it."
On the surface, there is nothing wrong with that. It comes from a good place, and we all do it: you see a gap, and your brain jumps straight to implementation.
I have to try really hard not to solution for the people I work with. Part of that is humility when I am outside my wheelhouse, and part of it is just basic professional courtesy. When you bring a problem to someone who owns a system, a pipeline, or a table, you are walking into their kitchen.
The moment you pitch a pre-baked implementation instead of the problem, cognitive anchoring takes over. Once "Add Column X" is spoken out loud in that room, the well is poisoned.
Now, instead of thinking deeply about the problem space, that engineer across the table is stuck reacting to your specific idea:
- The Path of Least Resistance: If they are buried in tickets, adding Column X is an easy two-point story. Asking why you want Column X turns a fifteen-minute chat into a two-hour data modeling discussion. So they build what you asked for, close the ticket, and move on. Six months later, when Column X quietly breaks on an edge case or violates the grain of the table, you are back in line asking for Column Y to patch Column X.
- The Wrong Debate: Even if they push back, the conversation is now trapped in a debate over the mechanics of Column X rather than the actual business problem you are trying to solve.
By trying to be helpful, you just turned a domain expert into a short-order cook. You paid for their expertise, and then you talked them out of using it. Solutioning for an expert caps their brilliance at the ceiling of your own ignorance.
Holding Back Your Own Scar Tissue
For a long time, I thought my "don't poison the well" habit was mostly about humility in domains where I wasn't the expert.
When I looked back at my message history, though, I realized something funny. Again and again, when I caught myself saying "I don't want to poison the well," it wasn't because I didn't know the answer. It was because I already had an answer, and I was purposely sitting on my hands.
- When working through a modeling exercise to turn a wide, flat table into a dimensional star schema, I already had a completed version sitting on my machine. I held it back until the rest of the group finished theirs.
- When helping transition a legacy reporting system I knew inside and out over to a new engineering team replacing it, I purposefully stayed out of their initial design work. I didn't want to project my own legacy PTSD onto them, and I learned a ton just watching how they approached the problem with fresh eyes.
That is the harder version of the discipline.
It is one thing to bite your tongue when you know you are out of your depth. It takes a lot more restraint to bite your tongue when you have thirty years of experience, a strong opinion, or a finished solution sitting on your screen.
Why hold back when you think you already know the answer?
First, because you cannot get an independent second opinion if you put your thumb on the scale. The moment a senior architect drops a completed diagram or a wall of SQL into a chat and asks "What do you think?", the team stops designing and starts grading homework. Even if they disagree with you, they are still orbiting the gravity well of your initial framing.
Second, because experience carries scar tissue. When you have lived inside a legacy system for years, your brain is wired around every workaround, political compromise, and broken pipe you had to survive in the old world. If you pre-load a new team with all of that history up front, you accidentally force them to rebuild yesterday's constraints inside tomorrow's platform.
Third, because if you always hand over the answer, nobody learns and you don't scale. Even in your own wheelhouse, where you might see the data model or the SQL fix in five minutes, solving it for the room is a trap. It closes today's ticket, but it keeps the knowledge trapped in your head. If you want to actually teach (and not become the bottleneck for every design decision in the building), you have to trust people enough to let them wrestle with the problem and find the solution themselves.
Expertise can create bias just as easily as ignorance can. The novice caps the room at the ceiling of their ignorance. The veteran can cap it at the ceiling of their experience.
Whether you are guessing at a domain you don't know or sitting on twenty years of scar tissue in one you know by heart, the damage is the same: you have constrained someone else's thinking to the boundaries of your own perspective.
Give Us Your Problem Statement
Keeping the well clean requires discipline on both sides of the table.
When I am the one asking for help (or kicking off a design across teams), I have to fight my own impatience. Respecting someone else's craft does not mean staying in your silo; it means bringing your context and constraints to the table without pretending they substitute for theirs. Even if I have a hypothesis in my back pocket, my job is to start with the cleanest, most honest problem statement I can muster:
- Here is what we are trying to accomplish.
- Here is where we are getting stuck today (or what we query today to get it).
- Here is what a good outcome looks like.
And then I have to shut up and let them work.
Nine times out of ten, when you put an unpolluted problem statement on the table, the real answer emerges in the seam between disciplines. A BI developer knows how user-controlled filters will break a pre-aggregated average; a data engineer knows the pipeline reality of 1.3 billion rows versus 100 million; an analyst knows what the business actually needs to do on Monday morning. If any one of them walks in prescribing what the other layer needs to build, they collapse a cross-functional conversation into a one-way ticket handoff.
When you bring the problem instead of the prescription, people come back with something cleaner than what you had in your pocket. Sometimes they tell you the data already exists three tables over. Sometimes they spot a presentation-layer constraint that changes the physical data model on the spot. They see the board differently because they aren't trapped inside your head.
And when you are on the receiving end, you have to guard the well just as carefully.
When an analyst, a PM, or a stakeholder walks up to your desk and asks for "Column X," remember that they aren't trying to step on your toes.
Don't just take the order, and don't make them feel foolish for suggesting it. Gently set the proposed implementation to the side and reset the room:
"Hold that thought on Column X for a second. Give us your problem statement first. Walk me through what you are trying to measure and where the data is fighting you right now."
Describe the goal, not the step. Keep the well clean, respect other people's craft, and give smart people enough room to surprise you.
Architected by Chet, written by Gemini 4 Argon
