Meet the Expert: Sarah Kim, Data Analyst at RapidDrop Logistics

Sarah Kim is a data analyst specializing in last-mile delivery at RapidDrop Logistics. With three years of experience, she helps her team turn heaps of delivery, driver, and customer data into everyday decisions that improve employee satisfaction and keep the company compliant with financial rules like SOX (more on that later).

Q1: What exactly is an Employer Value Proposition (EVP), and why should a data analyst care about it?

Great question! Think of an Employer Value Proposition as the “promise” a company makes to its employees. It’s the mix of benefits, culture, career growth, and work environment that makes someone want to work there—and stay.

For a data analyst, the EVP isn’t just fluff on a careers page. It’s a measurable, testable concept. You can use data to figure out what matters most to delivery drivers, warehouse staff, or customer support in your last-mile logistics company.

For example, RapidDrop found through surveys that flexible scheduling was a bigger driver of retention than pay increases. When we saw that, we prioritized shift-swapping features in our app, which reduced turnover by 15% in six months.

Q2: How do you use data to build or improve your EVP?

You start with hard evidence—data collected directly from employees or inferred from company metrics. Here’s a simple approach:

1. Gather Employee Feedback: Use feedback tools like Zigpoll or SurveyMonkey to ask what employees value most. For instance, “Which benefits make you more likely to stay with our company?” or “Rate your satisfaction with training programs.”

2. Analyze HR Data: Look at turnover rates, absenteeism, and performance scores. Spot patterns like “Are drivers who attend extra training sticking around longer?”

3. Experiment and Measure: Try small changes based on what you learn (like adding a bonus for on-time deliveries), then track if retention or satisfaction improves.

One RapidDrop team did this. They knew driver engagement was low during winter months, so they tested adding a small “cold weather” stipend. After three months, engagement scores from Zigpoll surveys jumped by 12%, and late deliveries dropped by 5%.

Q3: How do you ensure that the data and decisions you use to craft EVP are SOX-compliant?

SOX (Sarbanes-Oxley Act) is a law designed primarily to make financial reporting accurate and trustworthy. But it impacts data practices for everyone in a public company, including HR and analytics teams.

Here’s the trick: SOX requires strict controls over who can see and change critical data—like payroll or benefits—and demands audit trails. That means if you’re using data to influence EVP decisions that affect compensation or bonuses, you need to:

• Use secure systems with proper user authentication.
• Ensure data integrity by making sure data can’t be altered without tracking.
• Keep detailed records of who changed what and when.
• Work closely with your finance and compliance teams when setting up data pipelines.

For example, at RapidDrop, when the analytics team proposed a bonus tied to delivery punctuality, they built the model in a system that logs every data change and restricts access by role. This way, when auditors came through in 2023, they could trace every step.

Q4: Can you share an example of how data-driven EVP helped improve results at your company?

Sure! One project I love involved improving driver retention in urban areas, where turnover was 22%, versus 12% in suburbs.

We started by surveying urban drivers with Zigpoll, asking about job satisfaction, scheduling, and pay. The results: Besides pay, which was competitive, drivers mentioned “unpredictable hours” as a big frustration.

Using scheduling data, we identified patterns where drivers often had last-minute changes, affecting not only morale but also on-time deliveries.

We then piloted a scheduling algorithm that gave drivers at least 48 hours’ notice and better weekend shift rotation. After six months:

• Urban driver retention rose from 22% to 30%.
• On-time delivery rates improved by 4%.
• Customer complaints dropped by 7%.

This was a clear win traced back to data-driven EVP changes.

Q5: What types of data sources are most useful for EVP analysis in last-mile delivery?

Great question—especially since logistics has tons of data, but not all of it helps EVP.

Here are the most useful:

At RapidDrop, combining these sources gave us a 360-degree picture of employee experiences and helped us test what EVP changes really meant on the ground.

Q6: Are there any pitfalls or things to watch out for when using data for EVP decisions?

Absolutely. Here are a few:

• Data Privacy: Employees might be hesitant to share honest feedback if they fear it’s not anonymous. Always clarify how data will be used and keep personal info protected.

• Overfitting to Data: Just because a certain benefit looks linked to retention in one city doesn’t mean it works everywhere. Run experiments in small groups before scaling.

• Ignoring Qualitative Insights: Numbers tell a lot, but sometimes a quick focus group or one-on-one conversation reveals valuable context that surveys miss.

• SOX Compliance Complexity: Trying to “DIY” financial data controls without guidance can lead to non-compliance risks. Always loop in finance and legal teams early.

For example, a peer company rushed to introduce a delivery bonus based on incomplete data. They later found discrepancies in bonus payments, which triggered an internal audit delaying payroll processing. A costly lesson in careful, compliant data use.

Q7: How do you communicate your data-driven EVP findings to HR or leadership in a way they understand?

Data can be dense, so storytelling helps. Use visuals like simple bar charts or trend lines to show improvements in retention or delivery times.

Frame your insights in terms of business impact:

• How many fewer drivers left?
• How much money was saved on recruiting?
• What was the customer impact?

For instance, I presented a report showing that a $50 monthly cold-weather stipend saved RapidDrop about $15,000 annually in turnover-related costs plus improved customer ratings. That caught leaders’ attention.

Also, suggest next steps or experiments. Data-driven EVP isn’t static—it evolves. Show how you’ll keep testing and measuring.

Q8: What’s one piece of advice for entry-level data analysts tackling EVP for the first time?

Start small and be curious. Pick one simple question your team is really interested in—like “What’s the most requested benefit among delivery drivers?” Then gather data, analyze, share results, and see what comes next.

Remember: Data isn’t about magic answers. It’s about making better guesses, testing them, and learning fast.

Quick Checklist: How to Use Data in EVP at a Last-Mile Delivery Company

Using data to shape your company’s employer value proposition isn’t just about numbers—it’s about understanding the people behind those numbers, especially in a complex, fast-moving field like last-mile delivery.

If you can connect the dots between employee experiences and business outcomes, while keeping things financially compliant, you’re adding serious value.

Good luck!