Started explaining the problem to Claude before actually asking for anything — small change, made a real difference

A developer shares a new habit that significantly improved their interaction with Claude: explaining the problem in plain language before making any specific request. This approach often helps the user identify the core issue themselves while typing. When Claude does respond, the subsequent, more specific requests lead to noticeably better answers, as Claude doesn't have to guess the user's actual needs. This small change has made a real difference in their daily workflow.

Unlike typical prompt engineering advice, this report focuses on a pre-prompting habit that helps users clarify their own thoughts before engaging Claude.