Understanding Someone Else's POV

Abstract

Problem: Why does trying to understand someone else's point of view so often get you into trouble, and why does it matter for game development?

Approach: Tim Cain shares personal stories and professional experiences illustrating the friction that comes from genuinely trying to understand other perspectives β€” and connects this skill directly to game industry work.

Findings: Understanding β‰  agreeing. People routinely conflate explanation with endorsement, and curiosity with attack. Yet the ability to inhabit other perspectives is essential for team leadership, brainstorming, and writing compelling characters.

Key insight: If you can only think from your own point of view, you'll be a poor team member, a weak brainstormer, and a one-note narrative designer β€” understanding others' POV is a core professional skill, not just a nice personality trait.

Source: https://www.youtube.com/watch?v=26zFDKHLD_8

The Core Problem: Understanding vs. Agreeing

Tim Cain enjoys asking people why they feel the way they do β€” why they love or hate a game, a movie, or even a political candidate. He's not trying to argue or judge. He genuinely wants to understand the reasoning that led someone to their conclusion.

The biggest problem he encounters: people frequently think you're attacking their point of view just because you ask them questions. He understands why β€” some people do use questions as weapons ("Really? You think that's a good reason?") β€” but that's not what he's doing.

Explaining Is Not Justifying

Tim recounts a comment section discussion about gambling mechanics and microtransactions. He was explaining why the industry uses them β€” the answer being money. Someone immediately accused him of justifying the practice. His response: "No, I'm explaining why they do it. I don't like it. I don't do it in any of my games. But I understand why they do it."

He finds the "don't talk about a thing because that makes it real" mentality genuinely incomprehensible β€” the idea that merely discussing something constitutes endorsement of it.

Personal Examples of Misunderstood Intent

Getting Names Wrong

Tim openly acknowledges he's terrible with names β€” people's names, product names, song names. He's done it his whole life; it's not a new development. But people jump to assumptions: people of color have thought he was being racist, women have thought he was being sexist, and colleagues have gotten genuinely upset that he can't remember their names after 30 years.

Pronoun Struggles

He's tried multiple approaches to pronoun use in game manuals β€” "he or she" (awkward), alternating genders per paragraph (some people don't like it), singular "they" (confuses him when there's a plural noun nearby, plus a strict grammar teacher drilled it out of him). He references a YouTuber called Language Jones who made a video arguing that no matter what you do with pronouns, you're upsetting some group of people. Tim loves that perspective β€” it illustrates the impossibility of universal correctness.

Religion and Assumptions

Tim describes himself as secular and notes that people immediately assume this means he's anti-religious. He's not β€” he took a comparative religion class in college out of genuine curiosity. He sees religion the same way he sees college, music concerts, or therapy: great for some people, not for others, and he's curious about why.

The Famous Writer Controversy

Without naming names, Tim describes trying to understand a famous writer's arguments about trans people and bathrooms. By merely trying to understand where her argument came from, multiple people he knew well accused him of supporting her position. He was simply trying to understand why people on both sides were so upset β€” and concluded that individual private bathrooms (common in Europe and Australia) would solve the whole issue.

Why This Matters for Game Development

Tim identifies three concrete reasons this skill matters for anyone entering the game industry:

Managing and Working in Teams

If you become a lead, you'll manage many different people who don't all work or think the same way. Even without a leadership role, you must work in teams and make accommodations. If you can't consider how other people approach issues, you'll be terrible at collaboration. "If everything has to be your way or the highway, you're going to be out on the highway very quickly."

Brainstorming and Evaluating Ideas

People often pitch ideas that sound wrong at first. But if you listen, ask questions, and try to understand their approach, you sometimes discover a genuinely novel solution that bypasses problems you'd been stuck on. You only get there by trying to understand what someone else is actually saying rather than dismissing it immediately.

Writing Convincing Characters

For narrative designers especially: if you want to write a compelling villain, you need to understand why someone would do terrible things β€” even though you personally wouldn't. Characters who disagree with your worldview need to feel genuine, with real motivations. If you can only write characters who feel the way you do, "you're going to be a very one-note narrative designer." Tim observes that audiences have grown frustrated with games where characters aligned with the writer's views are deep and well-crafted, while opposing characters are shallow and unconvincing.

The Bottom Line

Understanding someone else's point of view doesn't mean agreeing with it, defending it, or supporting it. It's a skill β€” one that makes you better at working with others, generating ideas, and creating authentic characters. Tim's advice: ask questions, stay curious, and don't be afraid to explore perspectives that aren't your own.

References