Strategy
Part of Sales enablement assets: owners, gates and expiry dates
4 things about sales enablement best practices worth your time
Four sales enablement practices worth adopting: a message test, a battlecard review, a win/loss interview, and a quarterly asset retirement.
What to take away
- Run a message test each quarterpick the three claims sellers repeat most, and check each one against a document a buyer could read.
- Give every battlecard a named owner, a review date, and a kill condition. A card nobody has opened in 90 days is a card nobody uses.
- Interview three won and three lost buyers per quarter. Ask what they read, who they asked, and what nearly stopped them.
- Retire one asset every quarter. Inventory that only grows hides the material sellers actually reach for.
- Keep the whole loop inside the sales enablement working file so the next review starts from evidence, not memory.
Practice 1: the message test
Pick the three claims sellers repeat most often in demos and first calls. For each claim, name the document a buyer could read that supports it.
Message test: keep or cut?
Does a buyer-readable document support the claim?
Keep the claim in the deck
Rewrite to evidence or pull it
If no such document exists, the claim is a positioning risk, not a message. Rewrite it down to what the evidence carries, or pull it from the deck.
Run this quarterly. Claims drift as the product ships and competitors move. A claim that was safe two quarters ago can be the one that stalls a deal now.
Practice 2: battlecard review with a kill condition
Every battlecard gets an owner, a review date, and a kill condition. The kill condition is the trigger for retiring the card: the competitor exits the segment, the comparison stops being true, or nobody has opened it in 90 days.
Battlecard review requirements
- Assign an owner
- Set a review date
- Define a kill condition
- Name a checkable source
- State question, source, date
Review the card against a named source. Competitor pricing pages, release notes, and public filings are checkable. Analyst summaries and rep anecdotes are not, and a card built on them drifts into speculation.
The GAO evaluation design guide sets out how to connect an evaluation question to the evidence that can answer it. Apply that discipline to the card: state the question, the source, and the date, and leave out the claims the source cannot support.
Practice 3: win/loss interviews
Interview three won and three lost buyers each quarter. Twenty minutes each is enough. Ask what they read before the first call, who else they asked, and what nearly stopped the deal.
Record the answers verbatim and tag them by stage. Patterns show up by the fifth or sixth interview: a proof point nobody can find, a handoff that drops, a competitor framing that lands.
Keep the interview notes in the same file as the message test. A claim that survives the test but fails in interviews is the most useful finding the program produces.
Practice 4: retire one asset a quarter
Asset inventories only grow. Decks, one-pagers, case studies and battlecards accumulate until sellers cannot find the current version.
Each quarter, retire one asset. Name what replaces it, or state that nothing does. Record the decision and the date.
Two source checks keep the retirement honest. The GOV.UK open standards guidance treats interoperability and reduced supplier dependence as design goals, which is the test for whether a tool or format can be replaced without rebuilding the library.
The NIST Privacy Framework starting guide describes a voluntary process for identifying risk, assigning owners, and recording responses. Neither clears a marketing use on its own.
Both are management aids, and their scope stays visible.
Worked example: one quarter on one product line
A team sells a scheduling tool into mid-market clinics. It runs all four practices on a single product line for one quarter.
| Practice | What the team did | What it found |
|---|---|---|
| Message test | Checked the three most repeated claims | One claim had no supporting document |
| Battlecard review | Reviewed two competitor cards against public pricing pages | One card cited a price the competitor had changed |
| Win/loss interviews | Six buyers, three won and three lost | Four named the same missing integration proof |
| Asset retirement | Retired one outdated one-pager | Nothing replaced it; sellers had stopped using it |
The findings cost nothing to produce and changed the next release set. The integration proof moved to the top of the deck. The unsupported claim came out. The stale price came off the card.
Treat the results as diagnostic. Expansion to other product lines depends on whether the loop reproduces with the people, rights, and budget already in place.
Common questions
Who owns these practices?
Name one owner for the loop and one owner per asset. The loop owner schedules the quarterly message test and the win/loss interviews. Asset owners hold the review dates and kill conditions. Without a named owner, every one of these practices quietly stops after the first cycle.
How do we know the program is working?
Watch whether sellers reach for the material without being asked, and whether the findings change the next release set. Downloads and page views measure distribution, not use. If a quarter passes with no claim changed, no card retired, and no interview finding acted on, the loop is producing reports rather than decisions.
What should we avoid?
Avoid battlecards built on rep anecdotes and analyst summaries with no checkable source. Avoid interviews run by the seller who owned the deal, because buyers soften the answer.
Avoid letting the inventory grow without a retirement rule.
The GAO data reliability guide ties data quality to its intended use and calls for a documented assessment, which is the standard to hold the interview notes and card sources to.
