10 minutes
Confirming capacity with everyone "Simpatía" — warm, pleasant, agreeable conduct — is a population-level pattern worth keeping in mind, not a prediction about any one colleague. The habit that protects the work is the same with everyone: ask about capacity, confirm the specifics, and put them in writing.
What you’ll be able to do Ask about capacity and confirm a commitment in writing with any colleague or partner, and check your own assumptions before explaining a missed deadline by someone's culture. Compare the responses to this question and explain your choice: What is the most accurate way to understand what happened? Document a next step for Confirming capacity with everyone: In your next request to anyone, follow the yes with one capacity question, confirm the date, and send a short written recap before you treat it as a commitment. Warmth is not the same as a plan "Simpatía" describes a broad preference, documented across the Latin America cluster, for pleasant, harmonious social exchange and for avoiding a blunt no. Research suggests one possibility worth keeping in mind: a warm "yes" can express goodwill about the relationship without settling the question of capacity. That is a reason to ask a better question. It is not a fact about the specific colleague in front of you, and it is never the reason any particular person said yes.
The habit that protects the work is the same no matter who you are talking with. A willingness question ("can you do this?") invites a yes from almost anyone. A capacity question ("what else is your team carrying this week, and does Friday still work?") invites real information. Confirm the date, then send a short written recap that names what will be delivered, by when, and by whom. This is ordinary project hygiene, and it never singles anyone out.
When a deadline is missed anyway, resist explaining it by someone's background, even sympathetically. Competing requests, an unclear ask, a date heard as a target, and a handoff that never happened are all more common than any cultural explanation, and they apply to everyone. Ask the person what happened. In this scenario, Camila told you: her team was already behind. That is the answer to work with.
Good confirmation habits, for any request Ask a capacity question, not only a willingness question: what else is on their plate, and does the date still hold?
Restate the specific deliverable and date, and get a direct confirmation
Send a short written recap naming what, when, and who
Agree on how either of you will flag a problem before the date arrives
When something slips, ask the person what happened before you decide why
Ask the capacity question, then recap in writing What you can change You control what you ask and whether the request ends with a written recap. A capacity question and a two-line recap belong in every request you make, not only requests to colleagues from a particular background.
What to watch for Do not treat a pleasant tone as confirmation of a plan, and do not explain a missed deadline by someone's culture — or their character — before you have asked them what happened.
Your next step Before your next deadline request to anyone, ask one specific capacity question, confirm the date, and send a short written recap.
Same exchange, three readings Character reading Culture reading Checked reading
"She said yes and then missed the deadline. She over-promised and should have been straight with me." This decides Camila's character before you have the facts.
"She said yes because that is how people from her background keep things pleasant. I can't rely on a yes from her." This sounds more understanding, but it still decides her motive for her and treats a population-level pattern as a fact about one person.
"I asked whether she was willing, never what her team was carrying, and I sent nothing in writing. She told me her team was already behind. I'll ask about capacity and send a recap next time, with everyone."
Checking assumptions What does "simpatía" describe?
A documented cluster-level preference for pleasant, harmonious exchange and avoiding a blunt no. A broad pattern to keep in mind, never a statement about why a specific person said yes.
What do you ask instead of "can you do this?"
A capacity question — what else is on their plate, and does the date still hold — followed by a confirmed date and a short written recap. With everyone.
A deadline was missed. What comes first?
Ask the person what happened. Ordinary reasons such as competing requests or an unclear ask are far more common than any cultural explanation, and they apply to anyone.
Try a situation You ask Camila, a program partner, whether her team can turn around a data request by Friday. She smiles warmly and says, "Of course, no problem at all!" You do not ask what else her team is carrying, and you do not send a follow-up note. Friday passes with no data. When you follow up, she is apologetic and explains that her team was already behind on two other requests when you asked.
What is the most accurate way to understand what happened? Camila was not honest with you; she should have said no if she could not deliver.
Camila said yes because people from her background agree to keep things pleasant, so a warm yes from her cannot be relied on.
You asked about willingness, never about capacity, and nothing was confirmed in writing. Check your own assumptions, ask Camila what a workable timeline looks like now, and make capacity questions and written recaps your standard practice with everyone.
Consider your choice Try another response Carry this forward Asking a capacity question ("what else is on your plate, and does Friday still work?") and sending a short written recap is ordinary project hygiene you apply with everyone, not a precaution for colleagues from a particular background.
Cross-cultural research describes "simpatía," a broad preference for pleasant, harmonious exchange, across the Latin America cluster. It is one possibility to keep in mind: a warm yes can express goodwill without settling capacity. It is not a diagnosis of why a specific person said yes.
When a deadline is missed, ordinary reasons — competing requests, an unclear ask, a date heard as a target — are far more common than any cultural explanation, and they apply to everyone. Ask the person what happened; their answer is the reliable one.
Explaining a colleague's behavior by their culture, even kindly, treats a population-level tendency as a fact about them. It damages trust as surely as calling a missed deadline dishonesty.
A scenario decision about a partner's warm agreement and a missed deadline, and a knowledge check on checking your own assumptions before attributing behavior to culture.
In your next request to anyone, follow the yes with one capacity question, confirm the date, and send a short written recap before you treat it as a commitment.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Next lesson Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
