| Course | MT262 Leading Global Teams |
|---|---|
| Unit | Unit 6 |
| Paper type | Seminar reflection |
| Length | About 800 words, 5 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | BS in Business Administration |
| Updated | October 2026 |
Free sample paper for MT262 Unit 6
Culture, Then Clocks, Then Configuration: A Unit 6 Seminar Reflection on What Makes Dispersed Teams Hard
[Student Name]
Purdue University Global
MT262: Leading Global Teams
Unit 6 Seminar Reflection
[Instructor Name]
[Date]
The writer's team, the classmates' teams and every detail are composite and illustrative; classmates are described by their experience rather than by name; the sources cited are real.
My Answer Going In
My starting belief was that cultural difference is the main obstacle for global teams. My evidence was my own team: eleven people spread over Arizona, Portugal, Vietnam and New Zealand, building booking software for tour operators. When things go wrong between our offices, it often feels like a clash of styles, of how directly people disagree or how they read a request from headquarters. So when the instructor asked what makes dispersed teams hard, I said culture, and several classmates nodded.
Three Stories
The instructor then asked three classmates to describe teams they had worked on, without naming the people involved.
The first had managed a marketing team split between Honolulu and Boston. Everyone was American, most had similar backgrounds, and the team still fell apart within a year. Boston's afternoon was Honolulu's morning, so the two halves had only a few working hours in common, and decisions made in Boston's late afternoon landed in Honolulu as surprises. Meetings were always at the start of Honolulu's day and the end of Boston's, and both halves felt they were working on the other's schedule.
The second had worked in a university research lab in Houston with members from six countries, all in one building. Language and working styles differed widely. But the lab worked well, she said, because people could knock on a door, eat lunch together and fix misunderstandings in a minute.
The third had been the only remote member of a data team in Denver. Everyone else sat in one office. He missed hallway decisions, was often left out of quick calls and felt, in his words, like a guest on his own team. He had it hardest of the three, and no cultural difference was involved at all. Polzer et al. (2006) found that when dispersed teams form co-located subgroups, the boundary between sites can split the team, and a single isolated member sits on the wrong side of every such boundary.
The Framework That Organized Them
The instructor introduced O'Leary and Cummings (2007), who separate geographic dispersion in teams into three dimensions. Spatial dispersion is the physical distance between members. Temporal dispersion is how few working hours they share. Configurational dispersion is how members are arranged across sites: how many sites, how many people at each and whether anyone is isolated.
The three stories lined up neatly. The Honolulu and Boston team had low cultural difference but high temporal dispersion. The Houston lab had high cultural difference but almost no dispersion of any kind. The Denver analyst's team had low temporal dispersion, since everyone shared the same day, but extreme configurational dispersion: one person alone against a co-located majority. The difficulty in each case followed dispersion, not culture.
The team with the most cultures had the fewest problems, because it shared a hallway.
What Changed
My view narrowed rather than reversed. Culture still matters, and the Houston lab's members said language differences cost them time. But in all three stories, the main source of difficulty was how the team was spread out, and that is also true of my own team when I look again. Our hardest pair, Lisbon and Auckland, shares no working hours at all. Our office in Ho Chi Minh City has only two people, which makes it the closest thing we have to the Denver analyst's position. And most of the incidents I had filed under culture this term, such as the "EOD Monday" message, turned out to be about clocks.
In the account of Hinds and Bailey (2003), being apart breeds friction by itself, because messages arrive late and stripped of context, and teams then blame the friction on personalities or national styles. I had been doing exactly that. It is an easy mistake, because cultural explanations feel insightful and clock problems feel trivial, but the trivial ones caused most of our incidents.
Turning the Dimensions on My Own Team
Applied to my team, the three dimensions suggest three priorities. Temporal: use the pairs that share hours and design written handoffs for those that do not. Configurational: watch the two-person Ho Chi Minh City office for the isolation the Denver analyst described, and make sure its members are not left out of decisions made in larger offices' hallways. Spatial: accept that without a travel budget we will not meet, and build trust in other ways. Culture comes fourth, and the questions it raises are best asked person by person.
References
Hinds, P. J., & Bailey, D. E. (2003). Out of sight, out of sync: Understanding conflict in distributed teams. Organization Science, 14(6), 615-632. https://doi.org/10.1287/orsc.14.6.615.24872
O'Leary, M. B., & Cummings, J. N. (2007). The spatial, temporal, and configurational characteristics of geographic dispersion in teams. MIS Quarterly, 31(3), 433-452. https://doi.org/10.2307/25148802
Polzer, J. T., Crisp, C. B., Jarvenpaa, S. L., & Kim, J. W. (2006). Extending the faultline model to geographically dispersed teams: How colocated subgroups can impair group functioning. Academy of Management Journal, 49(4), 679-692. https://doi.org/10.5465/amj.2006.22083024
MT262 Unit 6 instructions, in plain terms
In Unit 6 the class lays its dispersed teams side by side; the written piece records your opening view, what the side-by-side comparison revealed and what it implies for a team you know. Summarize classmates' cases by experience rather than name. Use a model such as O'Leary and Cummings's three kinds of dispersion to line up the cases, then point it at your own team and say which dimension matters most there. A narrowed view is as acceptable as a reversed one, if you explain what remains of the original. Two pages in your own voice is enough, with at least two APA 7 sources; students writing the alternative assignment follow the same outline.
How the MT 262 Unit 6 example is put together
The reflection opens with the writer's starting belief and the four-office team behind it. Three classmates' stories follow, each summarized by what happened, under a margin note on describing classmates by experience. Polzer and colleagues explain why the lone remote analyst struggled most. The O'Leary and Cummings framework then lines the stories up, high temporal dispersion in Honolulu and Boston, almost none in Houston and extreme configurational dispersion in Denver, with the highlighted line about the team that shared a hallway. A section on what changed applies the comparison to the writer's own Lisbon and Auckland pair and two-person Vietnam office, citing Hinds and Bailey. Ranked priorities for the writer's team close it under a final note.
MT262 Unit 6 rubric: what earns full points
Seminar reflections in MT 262 earn their marks for an honest starting position, accurate summaries of the cases discussed, correct use of a dispersion framework and a meaningful application to the writer's own team. Instructors reward comparisons that hold one factor steady, such as culture, to show the effect of another, such as time zones. Applying each dimension accurately, with the classmates' cases as evidence, shows understanding. A view that narrows rather than reverses is fine when the reflection explains what still holds. Concrete priorities for the writer's team show the lesson traveled. The voice is first person, references still follow APA, and classmates' privacy should be respected throughout.
MT262 Unit 6 help: mistakes that cost points
A common weakness is retelling each classmate's story at length without comparing them. Another is applying the framework only to the classmates' teams and never to the writer's own. Some reflections swap one single explanation for another, from culture to time zones, without allowing that both matter. Others name classmates or describe them in identifying detail. Keep each case to its main features, and check that each dimension is applied to every case, not just the one it fits best. Share the cases your seminar discussed and your own team's setup, and a writer can organize the comparison and draft the turn back to your team.
Get an MT262 Unit 6 example written to your instructions
Jot down the classmates' experiences your seminar discussed, described by role or setting, and your own starting view. Missed the live session? Then send the written-alternative questions you answered. With the Unit 6 prompt and rubric, the first reflection is free, returned in 24-48h, and shows how your position moved. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More MT262 papers and BS in Business Administration samples
- MT262 Unit 1: Discussion Board Post
- MT262 Unit 2: Cultural Framework Application
- MT262 Unit 3: Communication Failure Analysis
- MT262 Unit 4: Time Zone Working Plan
- MT262 Unit 5: Asynchronous Process Design
- MT262 Unit 7: Trust Building Plan
- MT262 Unit 8: Virtual Conflict Case
- MT262 Unit 9: Team Working Agreement
- MT262 Unit 10: Global Team Leadership Plan
- MT260 Unit 6: Seminar Reflection
- MT247 Unit 6: Seminar Reflection
- MT246 Unit 6: Seminar Reflection
- MT245 Unit 6: Seminar Reflection
MT262 Unit 6 questions, answered
What if classmates' experiences did not change my view?
Explain which account came closest to challenging it and why your position survived. A view tested and kept, with reasons given, earns credit comparable to a changed mind. What reads poorly is a reflection that never engages with the others' experience. Showing the comparison, whatever it concluded, is what the unit rewards.
Which frameworks suit comparing classmates' teams?
Research on dispersion, such as O'Leary and Cummings's spatial, temporal and configurational dimensions, suits comparison because it gives each team a position. Gibson and Gibbs's work on the dimensions of virtuality is another option. Cultural frameworks help where difference is part of a story. Choose one that lets you place several teams on the same terms.
Can I include my own team as one of the cases?
Yes, and many reflections do, usually as the starting point or as the case the writer reconsiders at the end. Describe it by role and location rather than by colleagues' names. Give classmates' accounts equal attention, though, since the seminar is about comparing experience, and a reflection centered only on your own team can miss the point of the session.
Where can I find a free MT262 Unit 6 sample paper?
You can read the complete MT262 Unit 6 seminar reflection here. It compares three classmates' dispersed teams with O'Leary and Cummings's dimensions and narrows the writer's view that culture is the main obstacle.
Why did the lone remote analyst have it hardest in the MT262 Unit 6 sample?
Everyone else shared one office, so decisions happened in hallways and quick calls he could not join. That is configurational dispersion, being isolated against a co-located majority, and no cultural difference was involved.