✓ Machine Certified10/10?

How do you coach a rep who avoids logging activities because they think it's a waste of time

📖 2,635 words🗓️ Published Jul 2, 2026

Direct Answer

You coach a rep who avoids logging activities not by forcing compliance but by connecting the data to their paycheck and showing them the hidden cost of their resistance. The core issue is almost never laziness — it's a belief gap: they genuinely think logging adds no value because they've never seen it work for them. Your job is to run a two-week experiment: have them log everything perfectly for 10 days, then pull a report that reveals the real conversion rates (calls-to-meetings, meetings-to-pipeline) that their gut was wrong about. When they see that their "busy" week actually had a low connect rate or that their best deals came from a specific activity pattern they ignored, the logging becomes a tool for winning, not a chore. The key is to stop arguing about "why logging matters" and instead let the data prove it — and to make the logging process itself fast and painless so the friction disappears. This guide is for sales managers, team leads, and enablement pros who are tired of nagging and ready to build a data-driven culture without the drama.

CRO SYNDICATE

Why This Happens — Diagnose the Resistance

Before you coach, you must understand the root cause of the resistance. Most reps who skip logging fall into one of these camps: the "I remember everything" rep (overconfident in their memory), the "it's busywork" rep (sees logging as admin, not strategy), the "I hate the CRM" rep (frustrated by a clunky tool), or the "I'm too fast-paced" rep (prioritizes speed over discipline). Each requires a different coaching approach. The first step is to have an honest, non-judgmental conversation: *"Walk me through your thought process when you skip logging. What's the real reason?"* Listen for the belief, not the excuse. Often, the rep has never been shown what the data can do for them — they've only been told to do it for the manager's report. Until you shift that frame, no amount of nagging will work.

The Two-Week Experiment — Prove the Value

This is your most powerful tool. Tell the rep: *"I'm not asking you to believe me. I'm asking you to try this for 10 working days. Log every single activity — calls, emails, meetings, follow-ups — with the outcome. Then we'll look at the data together. If it doesn't show you something useful, we'll drop it."* The key is to make the experiment low-friction: use a simple spreadsheet, a voice-to-text tool, or a CRM shortcut. After 10 days, run a report that shows conversion rates (e.g., "You made 50 calls, got 10 meetings, closed 2 deals — that's a 4% call-to-close rate"). Then ask: *"Before this experiment, what did you think your conversion rate was?"* The gap between their perception and reality is the moment of truth. Most reps discover they were wrong — and suddenly, logging becomes a competitive advantage because it reveals which activities actually work. This experiment has turned more skeptics into believers than any lecture ever could.

Make It Painless — Reduce Friction to Zero

If the CRM is clunky, your rep is right to resist. Spend your energy removing the friction instead of fighting the behavior. Options include: voice-to-text logging (dictate "called Smith, left voicemail" into a notes app), email-to-CRM integration (auto-log sent emails), batch logging (set a 5-minute timer at the end of the day), or a simple paper tracker that gets entered weekly. The goal is to make logging take under 15 seconds per activity. If it takes longer, the rep will skip it. Also, automate what you can: many CRMs now auto-log calls from phone systems, calendar meetings, and email sequences. The less manual work, the more compliance. Remember: your job is to design the system so the right behavior is the easiest behavior. Don't blame the rep for a bad tool.

Connect It to Their Paycheck — The Compensation Link

The most persuasive argument for logging is money. Show the rep how activity data directly impacts their commission. For example: *"If you log 10 more calls per week and your conversion rate holds, that's more meetings per month — which historically leads to more deals."* Then make logging a requirement for payout in a way that feels fair, not punitive. Some teams tie a small portion of commission to data quality (e.g., "You must log at least 80% of activities to qualify for the monthly bonus"). Others use gamification: a leaderboard of logging accuracy with a small prize. The key is to align the incentive — not to punish non-compliance but to reward the behavior that leads to better coaching and better results. When the rep sees that logging directly helps their own pipeline forecasting and manager support, it becomes a tool for earning, not a chore.

The Coaching Conversation — Ask, Don't Tell

When you sit down with the rep, use Socratic questioning to let them discover the value themselves. Try these openers:

*"If you could know exactly which activities produce the most pipeline for you, would that be useful?"*
*"What's the cost of not logging — what are you missing out on?"*
*"How would your week change if you could see your own conversion rates in real time?"*
*"What's the one thing that would make logging feel worth it to you?"*

Let them talk. Often, the rep will admit they don't trust the data or they don't know how to use it. That's your opening to teach. Show them a pipeline review where you use logged data to spot a pattern (e.g., "You're great at opening calls but weak at closing — let's drill that"). When they see you using their data to make them better, not to micromanage, the resistance drops. The conversation should end with a shared agreement: *"Let's try this for two weeks, and we'll check back. If it doesn't help, we'll adjust."*

CRO SYNDICATE

Build a Data-Driven Culture — The Team Level

One resistant rep can infect a team. To prevent this, normalize logging as a team habit. Start every weekly meeting with a data share: "Here's what we logged this week and what it tells us about our pipeline." Celebrate reps who log accurately, not just those who log a lot. Create a "data hero" award each month. Also, lead by example: log your own coaching activities and share what you learn. When the team sees that logging leads to better coaching, faster deals, and fewer surprises, it becomes a cultural norm. The goal is to shift from "logging for the manager" to "logging for the team's success." This takes time, but it's the only sustainable fix.

The Hidden Cost of Not Logging: A Manager's Diagnostic Framework

Before you can coach the behavior, you need to understand why this particular rep resists logging. Most managers jump straight to "you need to log more" without diagnosing the root cause. Use this simple framework in your next 1:1:

The Three Resistance Types (and how to spot them):

The "I'm Too Busy" Rep – They genuinely believe logging takes too long. Watch for complaints about "admin work" and "red tape." Solution: Time them. Sit with them for 30 minutes and have them log everything they do. If it truly takes more than 2-3 minutes per activity, the issue is your CRM setup, not their attitude. Fix the process first.

The "It Doesn't Help Me Close" Rep – They've never seen logging pay off. They're results-oriented and need proof. Solution: Run a "logging audit" on their past 30 days. Pull their actual activity data (even if incomplete) and compare it to their pipeline. Show them the correlation between logged activities and closed deals. When they see that every deal they won had multiple logged touchpoints before the close, the lightbulb goes on.

The "I Don't Trust Management With My Data" Rep – They fear logging will be used against them. They worry about micromanagement or being penalized for low activity. Solution: Build a "no-punishment zone" for 30 days. Tell them: "I won't look at your logs for anything except helping you win. If you log 100 calls and get 0 meetings, we'll work on your script together. No judgment, just coaching." Trust is rebuilt through safety.

The Diagnostic Conversation Script:

"Help me understand your thinking. When you skip logging a call or email, what's going through your mind? Is it that it takes too long, that it doesn't help you, or that you're worried about what I'll do with the data? Be honest — I'm not here to punish you, I'm here to help you work smarter."

Listen without interrupting. The answer will tell you exactly which path to take. Most reps will admit the real reason within 30 seconds if they feel safe.

The "Logging as a Superpower" Reframe: From Chore to Competitive Advantage

The most effective coaching move is to change the metaphor. Stop calling it "logging" or "data entry." Start calling it "intelligence gathering" or "pattern recognition." The rep who logs well doesn't just satisfy management — they build a personal playbook that makes them unbeatable.

The Three Superpowers of Complete Logging:

Pattern Recognition – When you log every call, email, and meeting, you can spot your own winning patterns. Do you close more deals when you send a follow-up within 2 hours? Do you get more meetings when you call between 10-11am? Without logs, you're guessing. With logs, you're a scientist running experiments on your own success.

Pipeline Forecasting – The rep who logs accurately can predict their own commission check. They know: "If I make 50 calls today, I'll get 5 meetings this week, which will generate pipeline." That's not micromanagement — that's personal financial planning. Show them how to build their own forecast spreadsheet using their logged data. When they see the direct line between activities and income, logging becomes a money-making tool.

Coaching Leverage – The rep who logs everything can walk into any 1:1 and say: "Here's exactly what I did, here's what worked, here's what didn't, and here's what I need help with." That's power. That's the difference between a rep who gets vague advice and a rep who gets specific, actionable coaching. Logging turns you from a passenger to a pilot.

The Reframe Exercise:

In your next team meeting, ask everyone to share one insight they discovered *only because they logged their activities*. Examples:

"I learned I close better when I send a video instead of an email"
"I realized I get more meetings when I call on Tuesdays"
"I found out my best deals come from referrals, not cold calls"

When the resistant rep hears their peers getting real value from logging, the argument shifts from "why should I?" to "how do I get that too?"

The "Logging in 90 Seconds" System: Removing All Friction

The biggest practical barrier is time. If logging takes 5+ minutes per activity, no amount of coaching will stick. You must make it faster than the alternative. Here's a system you can implement in one afternoon:

The 90-Second Rule: Every activity must be loggable in 90 seconds or less. If it takes longer, the system is broken. Fix the system, not the rep.

Three Friction-Removal Tactics:

Keyboard Shortcuts and Templates – Set up CRM shortcuts for common activities. A "cold call" log should auto-populate with today's date, your name, and a default outcome dropdown. The rep should only need to: click "new call," select the contact, choose "left voicemail" or "spoke," and hit save. Total time: 15 seconds.

Voice-to-Text Logging – For reps who hate typing, enable voice-to-text in your CRM. They can dictate: "Called John Smith, left voicemail about the proposal, follow up Thursday." That's 10 seconds of talking vs. 2 minutes of typing.

Batch Logging at Set Times – Instead of logging after every activity, create two "logging sprints" per day: 10 minutes at 11am and 10 minutes at 4pm. The rep jots down everything from the previous block on a sticky note, then enters it all at once. This reduces context-switching and makes logging feel like a single task rather than 20 interruptions.

The "Logging Buddy" Accountability Trick:

Pair the resistant rep with a high-logging peer for one week. They check in twice a day: "Did you log your morning calls?" "What's your afternoon plan?" The peer pressure and social proof often work better than any manager directive. Plus, the high-logging rep can share their own shortcuts and tricks.

The One-Week Challenge:

Tell the rep: "Try this for 5 days. Log everything perfectly. At the end of the week, we'll pull your report together. If you don't see at least one actionable insight that helps you sell more, I'll buy you lunch and we'll never talk about logging again." The bet is low-risk for them, and the data almost always proves the point. Reps who take this challenge almost never go back to spotty logging — because they've seen the proof in their own numbers.

FAQ

What if the rep still refuses after the experiment? Then it's a will gap, not a belief gap. Move to a formal performance conversation: logging is a job requirement, and consistent refusal is grounds for a PIP. But give them one more chance to choose.

How long should the experiment last? 10 working days is the sweet spot — long enough to gather meaningful data, short enough to feel like a test. Any less and the sample is too small; any more and they'll resist.

What if the CRM is genuinely terrible? Then fix the CRM first. No amount of coaching can overcome a tool that takes 5 minutes per log. Advocate for a better system or create a workaround (e.g., a simple Google Form that auto-populates).

Should I tie logging to compensation? Yes, but lightly. A small bonus for data accuracy (e.g., 5% of monthly variable) works better than a penalty. Make it a reward for good data, not a punishment for bad.

How do I handle a top-performing rep who doesn't log? This is the hardest case. Use the experiment approach, but also ask: *"If you're already winning, what could logging help you win even more?"* Top performers often have blind spots that data can reveal. Frame it as a growth tool, not a compliance check.

What's the biggest mistake managers make here? Nagging. Repeatedly asking "Did you log?" creates a parent-child dynamic that breeds resentment. Instead, focus on showing the value and removing the friction. The rep will come around when they see it helps them.

Sources

Sales Management Association
Harvard Business Review — Sales Coaching and Performance
Salesforce CRM Best Practices Guides
HubSpot Sales Blog — Activity Logging
LinkedIn Sales Solutions — Data-Driven Selling
The Challenger Sale — Corporate Executive Board
Gartner Sales Enablement Research
Sandler Training — Sales Coaching Techniques

flowchart TD A[Rep avoids logging activities] --> B{What is the root belief?} B -- I remember everything --> C[Memory gap: run a recall test] B -- It's busywork --> D[Value gap: run the experiment] B -- Hate the CRM --> E[Tool gap: simplify or automate] B -- Too fast-paced --> F[Speed gap: reduce friction] C --> G[Show them what they forgot in one week] D --> H[Prove ROI with 10-day log] E --> I[Find a faster logging method] F --> J[Create a 15-second log ritual]

flowchart TD A[Rep resists logging] --> B[Run 10-day experiment] B --> C[Show conversion rate vs. perception] C --> D{Does the data change their mind?} D -- Yes --> E[Logging becomes a winning tool] D -- No --> F[Reduce friction: automate or simplify] F --> G{Is the tool the problem?} G -- Yes --> H[Switch to a faster method] G -- No --> I[Connect logging to compensation] I --> J[Reward compliance, not punish] J --> K[Build team culture of data use]

Related on PULSE

Explore more in the PULSE library.

Download:

![How do you coach a rep who avoids logging activities because they think it's a waste of time?](https://media.licdn.com/dms/image/v2/D5612AQFPbnKSvNRFhQ/article-cover_image-shrink_720_1280/article-cover_image-shrink_720_1280/0/1679608492283?e=2147483647&v=beta&t=N5eY3_YRHdJOrlJ70aym3W_scT09K6E3n_1uGZusjCQ)

## Direct Answer

You coach a rep who avoids logging activities not by forcing compliance but by **connecting the data to their paycheck** and **showing them the hidden cost of their resistance**. The core issue is almost never laziness — it's a **belief gap**: they genuinely think logging adds no value because they've never seen it work for them. Your job is to run a two-week experiment: have them log everything perfectly for 10 days, then pull a report that reveals the **real conversion rates** (calls-to-meetings, meetings-to-pipeline) that their gut was wrong about. When they see that their "busy" week actually had a **low connect rate** or that their best deals came from a specific activity pattern they ignored, the logging becomes a **tool for winning**, not a chore. The key is to stop arguing about "why logging matters" and instead let the data prove it — and to make the logging process itself **fast and painless** so the friction disappears. This guide is for sales managers, team leads, and enablement pros who are tired of nagging and ready to build a **data-driven culture** without the drama.

## Why This Happens — Diagnose the Resistance

![How do you coach a rep who avoids logging activities because they  — Why This Happens — Diagnose the Resistance](/assets/cro-cover-5.jpg)


Before you coach, you must understand the **root cause** of the resistance. Most reps who skip logging fall into one of these camps: **the "I remember everything" rep** (overconfident in their memory), **the "it's busywork" rep** (sees logging as admin, not strategy), **the "I hate the CRM" rep** (frustrated by a clunky tool), or **the "I'm too fast-paced" rep** (prioritizes speed over discipline). Each requires a different coaching approach. The first step is to have an honest, non-judgmental conversation: *"Walk me through your thought process when you skip logging. What's the real reason?"* Listen for the belief, not the excuse. Often, the rep has never been shown **what the data can do for them** — they've only been told to do it for the manager's report. Until you shift that frame, no amount of nagging will work.

```mermaid
flowchart TD
  A[Rep avoids logging activities] --> B{What is the<br/>root belief?}
  B -- I remember everything --> C[Memory gap:<br/>run a recall test]
  B -- It's busywork --> D[Value gap:<br/>run the experiment]
  B -- Hate the CRM --> E[Tool gap:<br/>simplify or automate]
  B -- Too fast-paced --> F[Speed gap:<br/>reduce friction]
  C --> G[Show them what they<br/>forgot in one week]
  D --> H[Prove ROI with<br/>10-day log]
  E --> I[Find a faster<br/>logging method]
  F --> J[Create a 15-second<br/>log ritual]
```

## The Two-Week Experiment — Prove the Value

![How do you coach a rep who avoids logging activities because they  — The Two-Week Experiment — Prove the Value](/assets/cro-cover-5.jpg)


This is your most powerful tool. Tell the rep: *"I'm not asking you to believe me. I'm asking you to try this for **10 working days**. Log every single activity — calls, emails, meetings, follow-ups — with the outcome. Then we'll look at the data together. If it doesn't show you something useful, we'll drop it."* The key is to make the experiment **low-friction**: use a simple spreadsheet, a voice-to-text tool, or a CRM shortcut. After 10 days, run a report that shows **conversion rates** (e.g., "You made 50 calls, got 10 meetings, closed 2 deals — that's a 4% call-to-close rate"). Then ask: *"Before this experiment, what did you think your conversion rate was?"* The gap between their **perception** and **reality** is the moment of truth. Most reps discover they were wrong — and suddenly, logging becomes a **competitive advantage** because it reveals which activities actually work. This experiment has turned more skeptics into believers than any lecture ever could.

## Make It Painless — Reduce Friction to Zero

![How do you coach a rep who avoids logging activities because they  — Make It Painless — Reduce Friction to Zero](/assets/cro-cover-5.jpg)


If the CRM is clunky, your rep is right to resist. Spend your energy **removing the friction** instead of fighting the behavior. Options include: **voice-to-text logging** (dictate "called Smith, left voicemail" into a notes app), **email-to-CRM integration** (auto-log sent emails), **batch logging** (set a 5-minute timer at the end of the day), or a **simple paper tracker** that gets entered weekly. The goal is to make logging take **under 15 seconds per activity**. If it takes longer, the rep will skip it. Also, **automate what you can**: many CRMs now auto-log calls from phone systems, calendar meetings, and email sequences. The less manual work, the more compliance. Remember: your job is to **design the system** so the right behavior is the easiest behavior. Don't blame the rep for a bad tool.

## Connect It to Their Paycheck — The Compensation Link

The most persuasive argument for logging is **money**. Show the rep how **activity data** directly impacts their **commission**. For example: *"If you log 10 more calls per week and your conversion rate holds, that's more meetings per month — which historically leads to more deals."* Then make logging a **requirement for payout** in a way that feels fair, not punitive. Some teams tie a small portion of commission to **data quality** (e.g., "You must log at least 80% of activities to qualify for the monthly bonus"). Others use **gamification**: a leaderboard of logging accuracy with a small prize. The key is to **align the incentive** — not to punish non-compliance but to reward the behavior that leads to better coaching and better results. When the rep sees that logging directly helps **their own pipeline forecasting** and **manager support**, it becomes a tool for earning, not a chore.

## The Coaching Conversation — Ask, Don't Tell

When you sit down with the rep, use **Socratic questioning** to let them discover the value themselves. Try these openers:

- *"If you could know exactly which activities produce the most pipeline for you, would that be useful?"*
- *"What's the cost of not logging — what are you missing out on?"*
- *"How would your week change if you could see your own conversion rates in real time?"*
- *"What's the one thing that would make logging feel worth it to you?"*

Let them talk. Often, the rep will admit they **don't trust the data** or they **don't know how to use it**. That's your opening to teach. Show them a **pipeline review** where you use logged data to spot a pattern (e.g., "You're great at opening calls but weak at closing — let's drill that"). When they see you using their data to **make them better**, not to **micromanage**, the resistance drops. The conversation should end with a **shared agreement**: *"Let's try this for two weeks, and we'll check back. If it doesn't help, we'll adjust."*

## Build a Data-Driven Culture — The Team Level

One resistant rep can infect a team. To prevent this, **normalize logging** as a team habit. Start every weekly meeting with a **data share**: "Here's what we logged this week and what it tells us about our pipeline." Celebrate reps who log accurately, not just those who log a lot. Create a **"data hero"** award each month. Also, **lead by example**: log your own coaching activities and share what you learn. When the team sees that logging leads to **better coaching**, **faster deals**, and **fewer surprises**, it becomes a cultural norm. The goal is to shift from "logging for the manager" to **"logging for the team's success."** This takes time, but it's the only sustainable fix.

```mermaid
flowchart TD
  A[Rep resists logging] --> B[Run 10-day experiment]
  B --> C[Show conversion rate<br/>vs. perception]
  C --> D{Does the data<br/>change their mind?}
  D -- Yes --> E[Logging becomes a<br/>winning tool]
  D -- No --> F[Reduce friction:<br/>automate or simplify]
  F --> G{Is the tool<br/>the problem?}
  G -- Yes --> H[Switch to a<br/>faster method]
  G -- No --> I[Connect logging to<br/>compensation]
  I --> J[Reward compliance,<br/>not punish]
  J --> K[Build team culture<br/>of data use]
```

## The Hidden Cost of Not Logging: A Manager's Diagnostic Framework

Before you can coach the behavior, you need to understand **why** this particular rep resists logging. Most managers jump straight to "you need to log more" without diagnosing the root cause. Use this simple framework in your next 1:1:

**The Three Resistance Types (and how to spot them):**

1. **The "I'm Too Busy" Rep** – They genuinely believe logging takes too long. Watch for complaints about "admin work" and "red tape." Solution: Time them. Sit with them for 30 minutes and have them log everything they do. If it truly takes more than 2-3 minutes per activity, the issue is your CRM setup, not their attitude. Fix the process first.

2. **The "It Doesn't Help Me Close" Rep** – They've never seen logging pay off. They're results-oriented and need proof. Solution: Run a "logging audit" on their past 30 days. Pull their actual activity data (even if incomplete) and compare it to their pipeline. Show them the correlation between logged activities and closed deals. When they see that every deal they won had multiple logged touchpoints before the close, the lightbulb goes on.

3. **The "I Don't Trust Management With My Data" Rep** – They fear logging will be used against them. They worry about micromanagement or being penalized for low activity. Solution: Build a "no-punishment zone" for 30 days. Tell them: "I won't look at your logs for anything except helping you win. If you log 100 calls and get 0 meetings, we'll work on your script together. No judgment, just coaching." Trust is rebuilt through safety.

**The Diagnostic Conversation Script:**

"Help me understand your thinking. When you skip logging a call or email, what's going through your mind? Is it that it takes too long, that it doesn't help you, or that you're worried about what I'll do with the data? Be honest — I'm not here to punish you, I'm here to help you work smarter."

Listen without interrupting. The answer will tell you exactly which path to take. Most reps will admit the real reason within 30 seconds if they feel safe.

## The "Logging as a Superpower" Reframe: From Chore to Competitive Advantage

The most effective coaching move is to **change the metaphor**. Stop calling it "logging" or "data entry." Start calling it **"intelligence gathering"** or **"pattern recognition."** The rep who logs well doesn't just satisfy management — they build a personal playbook that makes them unbeatable.

**The Three Superpowers of Complete Logging:**

1. **Pattern Recognition** – When you log every call, email, and meeting, you can spot your own winning patterns. Do you close more deals when you send a follow-up within 2 hours? Do you get more meetings when you call between 10-11am? Without logs, you're guessing. With logs, you're a scientist running experiments on your own success.

2. **Pipeline Forecasting** – The rep who logs accurately can predict their own commission check. They know: "If I make 50 calls today, I'll get 5 meetings this week, which will generate pipeline." That's not micromanagement — that's **personal financial planning**. Show them how to build their own forecast spreadsheet using their logged data. When they see the direct line between activities and income, logging becomes a money-making tool.

3. **Coaching Leverage** – The rep who logs everything can walk into any 1:1 and say: "Here's exactly what I did, here's what worked, here's what didn't, and here's what I need help with." That's power. That's the difference between a rep who gets vague advice and a rep who gets specific, actionable coaching. Logging turns you from a passenger to a pilot.

**The Reframe Exercise:**

In your next team meeting, ask everyone to share one insight they discovered *only because they logged their activities*. Examples:
- "I learned I close better when I send a video instead of an email"
- "I realized I get more meetings when I call on Tuesdays"
- "I found out my best deals come from referrals, not cold calls"

When the resistant rep hears their peers getting real value from logging, the argument shifts from "why should I?" to "how do I get that too?"

## The "Logging in 90 Seconds" System: Removing All Friction

The biggest practical barrier is time. If logging takes 5+ minutes per activity, no amount of coaching will stick. You must make it **faster than the alternative**. Here's a system you can implement in one afternoon:

**The 90-Second Rule:** Every activity must be loggable in 90 seconds or less. If it takes longer, the system is broken. Fix the system, not the rep.

**Three Friction-Removal Tactics:**

1. **Keyboard Shortcuts and Templates** – Set up CRM shortcuts for common activities. A "cold call" log should auto-populate with today's date, your name, and a default outcome dropdown. The rep should only need to: click "new call," select the contact, choose "left voicemail" or "spoke," and hit save. Total time: 15 seconds.

2. **Voice-to-Text Logging** – For reps who hate typing, enable voice-to-text in your CRM. They can dictate: "Called John Smith, left voicemail about the proposal, follow up Thursday." That's 10 seconds of talking vs. 2 minutes of typing.

3. **Batch Logging at Set Times** – Instead of logging after every activity, create two "logging sprints" per day: 10 minutes at 11am and 10 minutes at 4pm. The rep jots down everything from the previous block on a sticky note, then enters it all at once. This reduces context-switching and makes logging feel like a single task rather than 20 interruptions.

**The "Logging Buddy" Accountability Trick:**

Pair the resistant rep with a high-logging peer for one week. They check in twice a day: "Did you log your morning calls?" "What's your afternoon plan?" The peer pressure and social proof often work better than any manager directive. Plus, the high-logging rep can share their own shortcuts and tricks.

**The One-Week Challenge:**

Tell the rep: "Try this for 5 days. Log everything perfectly. At the end of the week, we'll pull your report together. If you don't see at least one actionable insight that helps you sell more, I'll buy you lunch and we'll never talk about logging again." The bet is low-risk for them, and the data almost always proves the point. Reps who take this challenge almost never go back to spotty logging — because they've seen the proof in their own numbers.

## FAQ

**What if the rep still refuses after the experiment?**
Then it's a **will gap**, not a belief gap. Move to a formal performance conversation: logging is a job requirement, and consistent refusal is grounds for a PIP. But give them one more chance to choose.

**How long should the experiment last?**
10 working days is the sweet spot — long enough to gather meaningful data, short enough to feel like a test. Any less and the sample is too small; any more and they'll resist.

**What if the CRM is genuinely terrible?**
Then fix the CRM first. No amount of coaching can overcome a tool that takes 5 minutes per log. Advocate for a better system or create a workaround (e.g., a simple Google Form that auto-populates).

**Should I tie logging to compensation?**
Yes, but lightly. A small bonus for data accuracy (e.g., 5% of monthly variable) works better than a penalty. Make it a **reward for good data**, not a punishment for bad.

**How do I handle a top-performing rep who doesn't log?**
This is the hardest case. Use the experiment approach, but also ask: *"If you're already winning, what could logging help you win even more?"* Top performers often have blind spots that data can reveal. Frame it as a **growth tool**, not a compliance check.

**What's the biggest mistake managers make here?**
Nagging. Repeatedly asking "Did you log?" creates a **parent-child dynamic** that breeds resentment. Instead, focus on **showing the value** and **removing the friction**. The rep will come around when they see it helps them.

## Sources

- Sales Management Association
- Harvard Business Review — Sales Coaching and Performance
- Salesforce CRM Best Practices Guides
- HubSpot Sales Blog — Activity Logging
- LinkedIn Sales Solutions — Data-Driven Selling
- The Challenger Sale — Corporate Executive Board
- Gartner Sales Enablement Research
- Sandler Training — Sales Coaching Techniques

## Related on PULSE

- Explore more in the PULSE library.

Was this helpful?

⌬ Apply this in PULSE

Gross Profit CalculatorModel margin per deal, per rep, per territory

Deep dive · related in the library