Symptom / stage drift
The same stage means different things.
Ask managers what evidence moves an opportunity forward. If answers differ, a stage definition may be more useful than another dropdown.
Field notes / sales operations
Sales ops: before you add another pipeline field.
When stage reports disagree and records go stale, a new field can look like the answer. First, find out whether the real issue is a missing definition, an unclear owner, or a CRM that needs to adapt.
Explore the CRM workflow
Investigation board
Illustrative sequence
ANotice the frictionWhere does data break?
BAgree on the ruleWhat should happen?
CAssign the ownerWho keeps it current?
A working discussion, not a software interface.
01 / Diagnose
Read the record before changing the system.
A CRM is a shared record of relationships, opportunities, and activity. Its reports depend on people recording the same events in comparable ways. Look for the decision behind the inconsistency before prescribing a customization.
Symptom / missing context
Handoffs rely on side conversations.
Trace a recent handoff. Identify which detail the next person needed, where it was recorded, and whether anyone was responsible for updating it.
Symptom / noisy reports
Fields are filled, but not trusted.
Compare a few records with the underlying conversations. A required field is less useful if its choices do not match the way the team works.
Workshop prompt
Bring sales operations and two people who update opportunities into the same review. Pick three recent records and mark each point where someone had to guess what a field or stage meant.
02 / Map the workflow
Customize the decision, not just the screen.
Use a real opportunity journey to evaluate CRM software. For each step, define the information needed, who enters it, and what the next person does with it. Then test whether the system can support that agreement.
Start with a useful record.
Decide which account and contact details are needed for a first follow-up. Evaluate custom fields and duplicate controls against those needs, including how someone corrects a mistaken match.
Put evidence behind stages.
Write entry and exit criteria for each pipeline stage. Ask whether configurable stages and validation rules can reflect those criteria without blocking legitimate exceptions.
Make ownership visible.
Agree who updates the next step and who reviews aging opportunities. Evaluate whether views, reports, and activity records make that responsibility clear to each role.
The maintenance test: Every custom field, rule, or stage needs a purpose and an owner. Ask how it will be documented, tested when the process changes, and retired if nobody uses it. If the cost of keeping it accurate outweighs the decision it supports, simplify first.
03 / Responsibility map
Permissions should follow the work.
Access is not simply a hierarchy. Map what each role must see, change, and review, then evaluate how a CRM handles those distinctions. The examples below are starting points for discussion, not a universal access policy.
Opportunity owner
Typical responsibilityKeep the next step and opportunity details current.
Question to testCan owners update their work without changing shared definitions?
Sales manager
Typical responsibilityReview pipeline evidence and coach on stalled deals.
Question to testCan managers see the records they oversee and correct ownership when needed?
Sales operations
Typical responsibilityMaintain definitions, reporting conventions, and approved changes.
Question to testCan configuration changes be limited to designated owners and reviewed before rollout?
Group exercise: Take one disputed edit and ask who should be able to make it, who needs to see it, and who resolves exceptions. Use that answer to test the permission model, rather than granting broad access by default.
04 / Quality review
Four questions for the next configuration review.
Use these prompts with the people who enter data and the people who depend on it. A short review of existing records can reveal more than a long wish list of fields.
- Is the definition usable?
Ask two users to classify the same opportunity. Discuss any difference before adding a rule.
- Does the field change a decision?
Name the report, handoff, or action that depends on it. If there is none, consider whether it belongs.
- Can errors be found and corrected?
Evaluate duplicate handling, bulk correction, and the visibility of stale or incomplete records.
- Who owns the upkeep?
Record who approves changes, updates guidance, and checks whether the configuration still reflects the sales process.
Take it to the table