Problem and outcome framing

Problem framing gives the recipient a reason to recognize the email before you ask for a reply. Start with a situation they can inspect, connect it to a business consequence, and leave room for them to correct your read. Frame a narrow problem that can earn a conversation and a seat at the table for a broader solution.¹ The email should first earn agreement on the problem, then permission to explain the outcome. Put the problem in the second paragraph, after the opening, so the message has a clear center.²

Start from the objective

Start with an objective the recipient can recognize without knowing your offer. The problem explains what may be blocking it.

Tie the recipient's objective to a problem you think they might have.³ Before writing, find what they have already invested in and committed resources to.⁴ Use those details to choose a problem that fits their situation. If the objective is unclear, ask what they are trying to accomplish and what may be getting in the way.

Name the gap

Make it easy for the recipient to confirm your read, correct it, or dismiss it. Treat the problem sentence as a working assumption that earns a response.

State the assumption plainly: "Here's what I'm assuming your problems are.".⁵ Problem agreement means the recipient agrees there is a problem you can solve.⁶

Use four checks in the draft.⁷ Ask what standard, target, or requirement should have been met.⁸ State what was observed or measured.⁹ Show how large or frequent the difference was.¹⁰ Name where and when it occurred.¹¹ Define the gap before trying to explain it.¹²

If the issue may be unfamiliar, discuss a similar customer's problem so the recipient can recognize that you may be able to help.¹³ Keep the story close to the problem you want them to inspect. Move on when they confirm the situation or give you a better version of it.

Connect the problem to business outcome

A process issue earns a reply when the recipient can see what it affects beyond the workflow. Make that connection before explaining your offer.

Attach a business problem to the process problem.¹⁴ Ask:

"Why does that problem matter to the greater business?".¹⁵

Build your hypothesis around how the specific problem might contribute to a larger objective.¹⁶ Trace its effect into other parts of the business so the issue has a wider context.¹⁷ If you cannot make that connection, keep working on the problem frame before adding product language.

Draw out the outcome

A problem tells the recipient what needs attention. The outcome tells you whether solving it would change something that matters to them.

Use these questions:

"Okay, well, assuming we could solve that for you, what would that look like for you?".¹⁸

"What are the business outcomes you are looking to accomplish by solving this problem?".¹⁹

"So why is this important to you?".²⁰

If the answer stays vague, establish the current state in quantifiable terms before you claim value.²¹ Listen for the result they want and the reason they care about it. When they explain a motivation or want, turn it into a problem you can examine in the next exchange.

Put the solution after recognition

Give the offer space after the recipient can see the problem and its consequence. Keep the solution sentence narrow enough to fit the frame you have established.

Use this pattern: "You're struggling with X and with Y, which is leading to Z. My company solves it by ABC."²² Once the problem and consequence are clear, say in one sentence that you can help.²³

Before sending, separate the problem framings you can solve from the ones you cannot. That practice trains you to connect each problem to a capability you can explain.²⁴ Use the language internal to the buying team and include the trigger words they use.²⁵

When the recipient replies, map the problem to how your offer can help so the next explanation fits their situation.²⁶ If the problem does not match what you can solve, keep the frame accurate and leave the offer out.

When they reply

Use the response to tighten your frame before expanding the pitch. The reply should give you better language for the problem, its effect, or the outcome.

When the recipient explains a motivation or want, turn it into a problem.²⁷ Once the problem is clear, align the pain to value.²⁸ Ask about the part that remains unclear, then use the answer to shape the next message. A reply that corrects your assumption gives you language the recipient recognizes.

What not to do

Keep these checks beside the draft while you decide whether the problem is ready to send.

• Avoid sending an assumed problem, proposed solution, and email link as though the recipient recognizes the problem. You do not know whether they do.²⁹
• Continue the exchange only when you have both the recipient's problem context and your solution context. Missing context gives them room to fill gaps inaccurately.³⁰
• Define the gap before explaining the cause, assigning blame, or prescribing a solution.³¹
• Avoid generic business problem language that could apply to any customer.³²
• Cover business priorities and problems before bringing product language into the message.³³