By what method?

Goals without a method are just wishes with a deadline. Deming's three-word question is the fastest way to expose whether a leader has a plan or just a slide deck.

W. Edwards Deming had a habit of asking an uncomfortable question. Whenever a leader declared an ambition (improve quality, reduce defects, increase customer satisfaction), Deming would lean in and ask: “By what method?”

It’s a deceptively simple challenge. And most leaders, then and now, don’t have a good answer.

The Principle

Intention without method is just wishful thinking. “By what method?” is the discipline of making your approach explicit — before you act, before you measure, and certainly before you declare success.

Deming argued that most organizational problems are system problems, not people problems. When outcomes fall short, the instinct is to blame individuals or demand more effort. But effort applied without method doesn’t improve the system. It just wears people out.

It is not enough to do your best; you must know what to do, and then do your best. — W. Edwards Deming

To know what to do, you must be able to describe your approach as a process — something repeatable, observable, and improvable.

If you can’t describe what you are doing as a process, you don’t know what you’re doing. — W. Edwards Deming

Why We Advocate for This

At Nerd/Noir, we use “By what method?” as a leadership diagnostic. When we work with executives and product leaders on transformation, we find that organizations frequently set ambitious goals — be more agile, ship faster, become customer-centric — without articulating how they will actually change the system of work to achieve them.

The question cuts through ambiguity in a few important ways:

It separates goals from plans. A goal describes where you want to go. A method describes the road you’ll take. Without a method, a goal is just a wish.

It makes assumptions visible. Articulating a method forces the underlying logic into the open — the theory of change, the dependencies, the handoffs. That’s where the real conversation begins.

It creates a basis for learning. You can only improve what you can describe. When you can articulate your method, you can inspect it, challenge it, and refine it. Without a method, failure is just noise.

It shifts accountability from people to systems. “We didn’t hit the number” leads to blame. “Our method produced this result — here’s what we learned and here’s what we’re changing” leads to improvement.

Applying the Question

“By what method?” belongs at the beginning of every significant initiative — not as an obstacle, but as an accelerant. It’s appropriate to ask when:

• A team commits to an outcome without a clear approach
• A leader sets a target without explaining how the system will change
• A retrospective surfaces recurring problems without a plan to address root causes
• An organization adopts a framework without connecting it to the actual work

The goal isn’t to demand perfection upfront. Methods evolve. The discipline is in articulating a method (a testable hypothesis about how you’ll achieve the result) and then learning from what happens.

Resources

• Outcomes Over Outputs — Knowing what you’re trying to achieve makes “by what method?” a sharper question.
• Continuous Everything — Methods improve through continuous inspection and adaptation, not one-time design.

Activities

• Gemba Walks — A structured practice for leaders to observe work as it actually happens, not as it’s reported. The most direct way to apply “by what method?” in the field.
• Retrospectives — The team-level practice for inspecting and adapting the method itself.