Help a Security Champion Build an Internal Case

A security practitioner might see a difficult problem long before they have authority to start an evaluation. Their manager, architect, procurement partner, and risk leader often approach the subject from different directions. An SDR earns trust by helping a practitioner prepare for an internal discussion before asking for a larger meeting. The aim is an honest next conversation, not a speech written for a buyer.

Begin with the practitioner’s own description. Ask what work creates friction, who feels the effect, and what recent event made the concern urgent enough to discuss. Do not translate a concern into a product claim. If alert review consumes attention during busy periods, record alert review as their concern. Ask what a better working day would look like. Their answer gives the practitioner language for an internal discussion without placing a sales promise in their mouth.

Ask who will question the project. A security manager might care about team time and priority. An architect might need specific information about proposed data movement. Procurement might ask about timing or process. A risk leader might need a review path. Ask which person needs context first and what question they are likely to raise. This helps the practitioner decide whether their first step is a short note, an informal conversation, or a scheduled discovery call.

In a fictional practice situation, Sam works as a detection engineer at an ecommerce company. Sam tells Rowan, an SDR, “Our team spends too much time sorting similar alerts during busy periods.” Rowan asks who needs to hear about this concern before an evaluation begins. Sam says their manager, Lee, will ask whether a new workflow deserves time from the team. Morgan, an architect, needs context about any proposed data movement.

Rowan does not answer technical questions from memory. Instead, Rowan asks what Lee already knows and whether Morgan has named a technical concern. Sam says Lee knows about the review burden but has not seen examples from a recent week. Morgan has not joined a conversation. Rowan and Sam choose a small preparation step. Sam will collect two fictional practice examples of repeated review work, with no customer details. Rowan will prepare a plain language agenda for Sam’s discussion with Lee.

Keep an internal note narrow. Write the observed problem, affected team, question for discussion, and open items. Tie each statement to words the practitioner gave you. Avoid phrases such as “will solve” or “will reduce” unless an approved source supports the statement and the buyer has confirmed relevance. A useful note helps a champion start an honest conversation. A promotional page rarely serves this purpose.

For Sam, Rowan writes: “Sam’s team reports repeated review work during high alert periods. Sam wants to discuss whether a focused evaluation deserves time. Lee might want examples of current review steps and a sense of time involved. Morgan has not yet shared a technical question.” The note leaves room for Lee and Morgan to add their own concerns. No promise appears in the wording.

Ask the practitioner how they prefer to introduce a colleague. Some people want a short written recap before speaking with a manager. Others prefer a thirty minute discovery conversation. Respect their internal rhythm. If Sam says, “I cannot bring Lee in yet,” ask, “What would Lee need to see before joining?” The answer might be a clearer problem statement, a short agenda, or an example of current work. You now have a next action without pressing Sam into an early meeting.

Suppose Sam asks Rowan, “Will this fit our current architecture?” Rowan should not offer a confident answer. Rowan asks which part of the architecture Morgan wants to examine first and offers a discussion with a prepared specialist. A useful reply sounds like this: “I want Morgan’s specific question before we arrange technical review. Which information path or system connection matters most for their first look?” This response moves work forward and makes uncertainty visible.

Prepare stakeholders before discovery. Ask Sam for the meeting goal, attendee names, known concerns, and one decision each person needs after the call. Send an agenda in ordinary language. Lee’s part might cover current review work and desired priority. Morgan’s part might cover the first technical question Morgan wants examined. Avoid a long feature tour. A focused conversation gives the champion material for their next internal step.

During a fictional discovery call, Lee says, “I need to know whether this deserves time from my team.” Rowan asks Sam to describe one recent review sequence. Sam explains an analyst reviewed several related alerts, then asked a teammate for context. Rowan asks Lee what would help with an initial priority decision. Lee asks for a clearer picture of the review sequence and names the teams needed for further discussion. Rowan records Lee’s request without changing the request into a promise.

After the call, Rowan sends Sam and Lee a recap. The note identifies the example needing clarification, stakeholder questions, and a proposed technical discussion after Morgan shares an initial question. Sam owns the practice example. Rowan owns the agenda. Morgan owns technical questions for specialist review. Lee owns the internal priority decision. Each person has a named next action, so Sam does not need to carry the entire evaluation alone.

A champion often worries about appearing to sell for an outside vendor. Help them frame an internal introduction as a question rather than a conclusion. Sam might tell Lee, “I found a possible avenue for reviewing repeated alert work. Would you be open to a short discussion about whether evaluation deserves time?” Lee retains room to assess priority. Sam does not need to defend claims Rowan never made.

Do not overfill the champion’s note. A page of claims creates more work for Sam and draws attention away from the original concern. Give Sam a short problem statement, a few open questions, and a clear purpose for the next discussion. When new evidence appears, label who supplied the evidence and whether an approved owner needs review. Source labels matter when a note reaches people absent from the first call.

Rowan then asks Morgan for one initial technical question before proposing a specialist call. Morgan asks what information needs review during a possible evaluation. Rowan records Morgan’s wording and schedules no technical session yet. Sam sends Lee the short note, one practice example, and a request for a fifteen minute conversation on Wednesday. The request has one purpose: decide whether further discovery deserves time from Lee’s team.

Practice this fictional situation with a colleague. One person plays Sam and says they are interested but cannot introduce Lee yet. The SDR has seven minutes to learn Sam’s concern, identify Lee’s likely question, and agree on one preparation step. The SDR avoids claims about results or technical fit. Then switch roles. Read the recap aloud and remove every sentence neither person heard from Sam.

For your next champion conversation, ask who needs context first and what question would earn their attention. Write a four sentence note using only the practitioner’s words. Leave technical material marked for review. Send the practitioner an agenda draft, then ask them to choose one example they will bring to their discussion with their manager.