10 minutes
Time expectations without assumptions A relational sense of time is a documented pattern across this cluster, and knowing it can keep you from reading a late start as disrespect. It cannot tell you why any one person is late. The useful move is to agree on expectations explicitly.
What you’ll be able to do Agree time expectations explicitly with a colleague or partner, using the cluster's documented time orientation to avoid misreading a late start as disrespect, without assuming that it explains any individual. Compare the responses to this question and explain your choice: What is the most accurate and useful way to handle this? Document a next step for Time expectations without assumptions: Before your next joint deadline with a colleague or partner, agree on the start time and the reason it matters together, out loud, rather than assuming what time means to them. A pattern can inform you; it cannot explain a person Across the Sub-Saharan Africa cluster, cross-cultural research describes time as relational and present-centered: gatherings begin when the people are ready, and the conversation in front of you matters more than the clock. For someone whose default is clock-driven, knowing this pattern exists is useful for one reason. It can stop you from reading a late start as a statement about how much you, or the meeting, matter.
That is where the pattern's usefulness ends. It cannot tell you why Kwame, or anyone else, joined at 10:20. He may hold a relational sense of time. He may also have been on another call, waiting for a bus, handling a family matter, or simply have had the wrong time in his calendar. Plenty of people connected to this cluster keep exact time by habit, training, or preference. Deciding that his culture explains his timing, and adjusting around him without saying so, is a stereotype even when it is meant generously. It also leaves him without the one thing that would actually help: a clear, shared expectation.
The reliable move works with everyone. Separate the clock time from the real constraint, name that constraint plainly, ask what start time works, and agree on it together, including what each of you will do if one of you runs behind. You learn what time means to a specific person by agreeing on it with them, not by guessing from where they are from.
Agreeing expectations explicitly Say the real constraint: a hard external deadline, a room booked for a fixed hour, a colleague who has to leave at a set time
Ask what start time genuinely works, rather than announcing one and assuming it means the same thing to both of you
Confirm the agreement out loud or in writing, including what each of you will do if one of you is running behind
Have the same conversation with everyone; do not tighten expectations for one person, or loosen them, because of their background
Agree the expectation; do not assign the reason What you can change You control whether you guess at the reason for a late start or agree on the expectation directly. Only one of those gives the other person a real say.
What to watch for Do not label anyone's relationship to time from their background, whether the label is "disrespectful" or "that is just their culture," and do not let a real deadline go unspoken because you assumed a clock time would carry it.
Your next step In your next scheduling conversation, name the constraint, ask what start time works, and confirm it together.
Time without assumptions What is the one thing the cluster pattern can do for you?
It can stop you from reading a late start as a personal slight. It cannot tell you why a specific person was late.
Is "that is just how time works in their culture" a safe assumption?
No. It is a stereotype, even when kindly meant. It labels a person with a pattern they may not hold and leaves the expectation unspoken.
What works with everyone?
Name the real constraint, ask what start time works, and agree on it together, including what to do if someone runs behind.
Carry this forward A polychronic, relational approach to time is documented across this cluster: people and the moment take priority over the clock. Knowing this can stop you from reading a late start as a personal slight.
The pattern does not explain any individual. A colleague may start late because of a relational sense of time, a caregiving obligation, a bus route, or a calendar mix-up, and the only way to know is to ask. Treating culture as the explanation is a stereotype, even when it is meant kindly.
Agreeing expectations explicitly works with everyone: name the real constraint, ask what start time works, and confirm the agreement together, rather than assuming either punctuality or lateness from where someone is from.
A scenario decision about a partner's late start to a planning call, and a knowledge check on agreeing time expectations without assuming any individual's relationship to time.
Before your next joint deadline with a colleague or partner, agree on the start time and the reason it matters together, out loud, rather than assuming what time means to them.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Next lesson Carry this into practice Explore the limits of the Sub-Saharan Africa cluster framework; compare it with real context and individual experience before drawing conclusions.
Return to the experience: What did you notice or try, whose perspective informed it, and what would you keep or adjust?
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.
