As you send a message to your colleague, you think: There has to be a better way to communicate clearly. 💭 Oftentimes, details get lost in translation, especially for remote teams.
If only there were a way to improve communication at work so you could request help without a long string of emails. Luckily, we have the perfect solution:
✨ The CARS Communication Framework ✨
At ProcessDriven, we use CARS to save time, avoid misunderstandings, and communicate our needs effectively.
If you want to learn how to improve communication skills in the workplace with the CARS approach, check out the video or read the post below!
Disclaimer: This post may include affiliate links that may compensate us. For details, review our terms.
How to Communicate With Co-workers: CARS Method
CARS is an acronym that stands for Context, Attempts, Request, and Stakes. These four categories are vital to include in your conversations to ensure you get your point across without a hundred back-and-forth exchanges. Don’t you just love a clean inbox? 📧
Whether you send an email or a voice note, this effective communication framework allows you to communicate clearly without any room for misinterpretation.
Communication at Work Examples (00:23)
Let’s explore two communication scenarios. The first example will highlight a simple exchange between two colleagues about a website update. 💻
A: “Do you think we should update our Careers page? It’s pretty outdated.”
B: “Yes, definitely.”
Two days later…
A: “The page still isn’t done? Okay… Stay calm.”
10 days later… The Careers page remains the same.
Within this brief discussion, it’s clear that B didn’t take action on A’s observation about the Careers page. However, it’s also evident that A didn’t clarify their request, the purpose of the update, or the deadline. 📅
Let’s compare this with another exchange featuring the CARS Communication Framework.
A: “Hey Bob. I reviewed the Careers page and noticed the Benefits section is outdated. I looked over the rest, and it’s fine. But the Benefits section isn’t right. I intended to edit it, but I realized I don’t have access, so I’m asking for your help since you’re in charge of the website.
A: “Do you know when you can fix this? Just so you know, we will hire a new role at the end of the month, and we’ll post the job listing in about two weeks. I’d like to make sure the page is good by then.”
B: “Good catch! Thanks for letting me know. I review that page every 90 days. My next check is in 11 days. That timing works well. I’ll make a note to review the Benefits section when I do this. Does that work for you?”
A: “Yes, that’s perfect. Thanks!”
B: “Great. I’m also adding you as a Follower on the task, so you will be updated when it’s complete.”
A: “Amazing!”
Notice how much information A provides to B. A mentions the specific section that requires a revamp, why they need support, and when to complete the task. 💬
As a result, A communicates clearly, and B understands what they must do next. This is a win-win situation for small teams. 🏆
The following section will break down the CARS framework, starting with context.
Context: Set the Scene (03:09)
Context is about providing all the necessary details so your team can help you in a given situation. You’ll also want to anticipate questions that would prevent them from completing a task.
Consider a simple question: “Can you send this invoice?” 👎
While it seems straightforward, it’s a vague request. If you received this task, you may wonder who to send the invoice to and for what amount.
When you offer additional context, you can save yourself and the other person’s time by conveying all the information from the very beginning.
Let’s add context to the original question: “Hey, I have an invoice I need to send to John Doe, Inc. It’s for $1,200 for our VIP Service. Can you send this invoice?” 👍
💡 Pro tip: When including context, focus on what’s relevant, not chronological. You don’t need to mention everything leading up to the request or apologize for interrupting your colleague’s work. Instead, share the factors required to complete the task.
Attempts: Share Your Role So Far (05:16)
Wondering how to communicate with co-workers so they get the message loud and clear? Be transparent about your attempts to complete a task or project. 💪
While context is about saving you and your colleague time from back-and-forth messages, attempts save your team member’s time by describing your previous efforts to ensure they don’t repeat them.
Let’s say you’re troubleshooting links on your website. You’ve cleared the site’s cache and edited the webpages. If those attempts didn’t resolve the issue, mention this information before reassigning the task to them.
Communicating these details allows your colleague to explore other options and find a resolution quickly. 🏃♀️
🧠 Keep in mind: If you’re delegating tasks to your boss or clients, your attempts should be exhaustive and demonstrate everything you’ve done.
Delegating a task to a subordinate? Let them attempt to resolve the task and share need-to-know instructions.
Phew! That’s a lot of information so far. If you feel overwhelmed by the CARS approach, consider defining your team’s roles and responsibilities!
When you clarify these factors, you can delegate areas of your business to your crew. This option lets you skip the context and attempts and jump right to assigning. No need to expand. 👋
Request: Be Specific (07:51)
How difficult can it be to ask for help? As it turns out, many people are too vague with their requests, causing many questions.
For example: “Can you make a presentation by Friday?” A common answer would either be “Yes” or “No.”
But then, you’re left with a series of questions.
💭 What kind of presentation?
💭 How long should the presentation be?
💭 What do you want to include in the presentation?
Like context, specificity adds another layer to the CARS framework, spelling out what you want the other party to do, say, and/or create for you. It’s also valuable to provide a deadline.
Wondering how to be more specific with your communication at work? Be careful with how you ask for help.
👉 Avoid asking questions starting with the word “can.” These yes/no questions focus more on capability versus completing a task.
👉 Clarify what you’re looking for. If you want to know someone’s thoughts on a matter, you’re likely searching for approval, decision, feedback, or insight on details you missed. Be clear and concise, as in the example below. 👇
“I don’t think we should do a two-day virtual event. Here’s why… I believe a better alternative is X. Which of these options should we consider?”
💡 ProcessDriven tip: It may be ideal to place the request first in the CARS framework for busy people. If you’re delegating to your boss, you can begin or end your communication with the request.
Stakes: Clarify the Outcome (10:52)
Stakes describes what will occur if a request is not fulfilled and why it’s important to complete it. We recommend communicating the positive and negative outcomes to your team. 💬
However, in some cases, the stakes may not be entirely clear, e.g., when rescheduling a team meeting. If you’re unsure about the stakes, dig deeper and ask why the request is important.
Can’t determine a meaningful stake? This sign reveals that the request may not be worth doing.
📝 Quick note: Are you struggling to inspire your team to take accountability? Consider pairing your stakes with a dollar value. 💸
For example, you can implement a team-wide rule that states the stakes must be worth $500 before handing it to the manager.
Including monetary value in your stakes lets your team put tasks through a mental filter before working independently or checking in with a peer. 🧠
Once you implement an accountability threshold, you can let your crew take the reins. Yes, mistakes will happen. When they do, it’s essential to:
✅ Log the issue and the decisions involved.
✅ Discuss the poor choices and how to improve.
✅ Celebrate the solutions.
We talk more about transformational work habits in this post!
Promote Better Communication at Work With CARS
And now for the real challenge: Can you apply this information?
The next time you email a request to a colleague, consider including the main CARS components: Context, Attempts, Request, and Stakes. 📢
Spell it out or create a bullet list under each category. Even if your team isn’t familiar with this effective communication framework, they will understand what you need.
While communication is essential, it’s only one piece to a well-oiled machine. The next element is a robust system with clear workflows and processes. If your business feels a little everywhere, stay calm and sign up for our signature program, ProcessDriven Foundations™. ✍
It’s a step-by-step program for building your team’s operating playbook, helping you organize your business, implement effective processes, and receive support from seasoned operators.
Let’s improve our communication at work and enjoy the process!
ProcessDriven helps small teams turn chaos into process. The ProcessDriven Approach™ combines software expertise with practical process-first strategies that have helped 2,020+ teams build a scalable foundation of business systems.
