Summary of "Exploring Solution Engineering Best Practices"
Main ideas & lessons (solution engineering best practices)
1) Discovery: focus on pain and gain, not a full process
- Discovery should not be “walk through the entire process.”
- Instead, concentrate on:
- Pain they want reduced
- Gains they want added
- Ask for key objectives (often “three things”), then:
- Translate them into additional value they may not have requested.
- Bring ideas that reflect thought leadership (automation, reporting, mobile, etc.).
- Don’t ask the customer to design the solution—customers know their problems best; the SE figures out the solution.
2) Presentations/demos: earn attention first, then deliver value immediately
- The “one thing” for success is ensuring audience attention right now.
- Assume the audience is stressed and easily distracted; if they aren’t paying attention, nothing lands.
- Focus on the intersection of:
- What you can show (your capabilities)
- What matters to them (their priorities)
- What is “cool” in a way that’s relevant (not random feature lists)
3) Demo style: avoid “pointing” / feature-listing; “paint” a future outcome
- “Pointing style” = “Here you can see… and over there…”
- Called out as a non-engaging “harbor cruise.”
- Instead, use a painting style demo:
- Explain how you will change their future.
- Show the story of how the solution works in a way that excites and convinces.
4) Remove unnecessary detail (“uncanny valley” for demos)
- Adding more realism/detail doesn’t automatically improve quality.
- Risk: detail creep can make the presentation worse by increasing confusion or distracting the audience.
- A strong demo strips away unnecessary junk.
- Presenting everything can signal insecurity and create more “knits” (things the audience can criticize).
5) Make demos defensible: assume a “hostile audience”
- Treat the audience like they will pick at details.
- Prepare so every displayed element has value.
- This reduces the number of objections (“nits”) they can raise.
6) “So what?” test for every demo component
For each element in your presentation, be able to answer:
- So what?
- What value is lost if it’s removed?
- Which part of your story/value prop breaks?
- Why is it there?
- Who cares?
- Who in the audience cares about it?
- How does it impact the value proposition?
7) Order & pacing: give the value prop up front
- Don’t “save the best for last” like a murder mystery.
- Exec attention spans are short—lead with the goodness early.
- For executives, use “razzle-dazzle”:
- Give the demo twice:
- Fast preview (2 minutes), no questions
- Then the full slow version
- Provide a “table of contents” feel by mapping what tabs/areas will be covered.
- Give the demo twice:
8) Delivery: be likable; don’t turn into a scripted monotone lecture
- “Brother-in-law demo” philosophy:
- Be personable and conversational, not uptight.
- High energy isn’t the same as engagement; engaging delivery can be calm/slow if compelling.
- Don’t repeatedly ask “Any questions?”—it breaks flow and can cause attention to drop.
- If the audience disengages, stop presenting and re-engage via conversation.
- Script vs ad hoc:
- The goal is an engaging, effective presentation—not perfect reading.
- Some people need a script (especially early); others work from outlines/keywords.
- Watch out: scripted demos can break if strategy/pivot happens mid-way.
9) Demos/dry runs: treat them as “necessary evil” with controlled input
- Dry runs are common for important deals and needed because:
- Leadership needs to see it’s solid
- It prevents a “train wreck” that triggers questions later
- Advice:
- You control the driver.
- Let the requesting leader “check boxes” and provide a limited set of changes.
- Don’t let others run the whole dry run—unpredictable changes reduce effectiveness.
10) SE success metrics: tie impact to revenue and pipeline influence
- Measure success by influence on money:
- Revenue / pipeline movement tied to your efforts.
- Some SE orgs track:
- Hard KPIs (demos, calls, discoveries)
- Soft KPIs (sales team advocacy/praise)
11) New SE confidence & impostor syndrome
- Impostor syndrome is normal.
- Confidence can’t be guaranteed before you’re skilled; it grows with reps/quarters.
- Test whether you can communicate:
- Can you tell a story to friends and hold their attention?
- If not, the role may be a poor fit (or you may need a different path/approach).
12) What makes a great SE partnership: make the sales team love you
- Core SE purpose (as stated):
- Help make deals bigger and close faster**
- Don’t confuse the role with enablement, onboarding, or support alone.
- Trust-building operational behaviors:
- Don’t over-qualify in a way that delays sales help.
- Work like a service: get in, support, and be reliable.
- Your “brand” is what people say about you when you’re not in the room.
13) Remote demos/webinars: changed expectations, not core mechanics
- Pandemic increased comfort with webcams and virtual participation.
- Mechanics remain similar: you still must manage attention and engagement.
- Remote can be advantageous for scale and convenience.
14) Tools & tactics: mind maps and visible artifacts for engagement
- Use a mind map during discovery to keep screens visually active and interactive.
- Helps maintain engagement and improves recall/clarity.
- Call on participants by name:
- Visual anchors help re-engage anyone who tuned out.
- Take notes visibly with the customer and provide an artifact at the end.
Methodologies / processes presented (detailed bullets)
A) Process-based vs pain/gain discovery (recommended approach)
- Conduct discovery by:
- Asking for the customer’s key objectives (e.g., 3 things).
- Identifying:
- Pain they want reduced
- Gains they want increased
- Avoid covering the entire end-to-end process.
- Focus the solution narrative where pain/gain concentrates.
- After objectives are captured:
- Propose solutions that address those objectives.
- Add capability they didn’t explicitly request (automation, reporting, mobile, etc.).
- Treat thoughtfulness as differentiation.
B) Demo “acceptance checklist” using “So what? / Who cares?”
For every element you plan to show:
- So what?
- If removed, what part of the value proposition/story breaks?
- Why is it there (justify it)?
- Who cares?
- Which stakeholder cares about it?
- How does it affect their success/decision?
C) Executive demo structure (“demo twice”)
- First pass:
- Give the “same demo” quickly (~2 minutes)
- No questions during this preview
- Act like it’s a “table of contents”
- Second pass:
- Repeat with full, slow pacing
- Allow it to land with more depth
D) Dry run execution (controlled participation)
- Plan the dry run as a check:
- Invite leadership who requested it
- Ask them specifically where they want input (what must be “right”)
- SE controls:
- Don’t hand over the driver
- Prevent uncontrolled changes from weakening effectiveness
Speakers / sources featured
Speakers
- Dave Nava — host; Lead Solution Engineering Salesforce; “Military Trailblazer” office hours host
- Iman McGurry (said as “Iman Mclaren” in subtitles; likely the same person) — co-host; distinguished Solution Engineer at Salesforce; presenter
Other individuals mentioned (not interviewed as speakers)
- Mark Benioff (Salesforce CEO) — mentioned
- Brett — mentioned (as part of an interaction)
- Elio — mentioned as someone asking/participating (appears to be another participant, not a main presenter)
- Eman / Aman / Annie / Lindsay / David / Catherine / Carrie / Michelle / Priscilla / Marina / Ira / Elio — mentioned by name as participants asking questions/comments (no separate main-source speaking time beyond Q&A comments)
Category
Educational
Share this summary
Is the summary off?
If you think the summary is inaccurate, you can reprocess it with the latest model.
Preparing reprocess...