Managing Power Gaps as an Element of Pair Programming Skill: A Grounded Theory
This paper uses Grounded Theory to demonstrate that pair programming sessions can fail despite high mutual understanding due to "Power Gaps" arising from knowledge disparities and hierarchical behavior, and proposes that practitioners can improve outcomes by recognizing these gaps and applying "Equalizing Behavior."
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine two people trying to solve a puzzle together. They are sitting side-by-side, looking at the same screen, and trying to build a piece of software. This is Pair Programming.
Usually, when two people work well together, they have a "super-connection." They know what the other is thinking before they even say it. The researchers call this "Togetherness."
But here is the weird thing the paper discovered: Sometimes, a pair looks like they are getting along great. They are smiling, laughing, and nodding. They have high "Togetherness." Yet, the work is going terribly. The code is bad, the mood is tense, and one person is secretly checking out.
Why? Because of a hidden invisible wall called a Power Gap.
Here is the story of how that wall gets built, how it breaks the team, and how to tear it down.
1. The Starting Point: The Knowledge Gap
Imagine one person is an expert chef (let's call them Chef) and the other is a beginner who has only ever boiled water (let's call them Helper).
They are trying to make a complex soufflé. The Chef knows the recipe; the Helper doesn't. This difference in knowledge is a Knowledge Gap.
- Normal: The Chef explains things gently. The Helper asks questions. They learn together.
- The Problem: If the Chef starts acting like a boss, the Helper stops asking questions.
2. The Trap: Hierarchical Behavior
The Chef starts acting superior. Maybe they sigh loudly when the Helper makes a small mistake, or they grab the keyboard and start typing without asking, or they say, "Well, obviously, you should do it this way."
The researchers call this Hierarchical Behavior. It's like the Chef saying, "I am the Captain, and you are the Cabin Boy." Even if the Chef thinks they are just being "efficient," the Helper feels small and judged.
3. The Invisible Wall: The Power Gap
Because of the Chef's bossy behavior, the Helper starts feeling like they don't have a real say in the process. They feel like they are just watching the Chef work.
This feeling is the Power Gap.
- The Chef feels dominant (they have the power).
- The Helper feels subordinate (they have no power).
Even though they are sitting next to each other, they are no longer a team. One is driving the car; the other is just a passenger holding their breath.
4. The Crash: Two Bad Reactions
When the Helper feels this Power Gap, they usually react in one of two bad ways:
A. The "Defensive" Reaction (The Silent Treatment)
The Helper stops talking. They stop suggesting ideas. They might nod and say "Sure," but they aren't really listening. They are putting up a wall.
- Analogy: Imagine the Helper is a dog that got scolded. They stop wagging their tail and just sit in the corner, waiting for the storm to pass. They aren't helping; they are just surviving.
B. The "Disengaging" Reaction (The Ghost)
The Helper stops trying to learn. They stop asking questions because they are afraid of looking stupid. They let the Chef do everything.
- Analogy: The Helper is like a passenger in a car who closes their eyes and puts on noise-canceling headphones. They aren't helping steer. They are just hoping to get to the destination without getting yelled at.
The Result: The Chef keeps driving, but they are driving blind because they aren't getting feedback. The Helper learns nothing. The code gets messy. The "Togetherness" is a fake mask.
5. The Solution: The "Equalizer"
The paper says there is a way to fix this. It's called Equalizing Behavior. This is a skill that either person can use to break the Power Gap.
If you are the Chef (The "Senior"):
- Stop bossing. Instead of grabbing the keyboard, ask, "What do you think?"
- Make it safe. If the Helper makes a mistake, laugh it off. Say, "I made that mistake too last week!"
- The "Meta-Chat": If you see the Helper getting quiet, say, "Hey, I feel like I'm doing too much talking. Do you want to take the wheel?"
If you are the Helper (The "Junior"):
- Speak up. Instead of staying silent, say, "I'm feeling a bit lost here. Can we slow down?"
- Don't hide. Admit you don't know something. "I don't know how this works yet, but I want to learn."
The Magic: When the Chef does this, the Power Gap shrinks. The Helper feels safe again. The "Togetherness" becomes real, not fake. They start solving the puzzle together again.
The Big Picture
The researchers studied hundreds of hours of programmers working together. They found that Pair Programming isn't just about coding skills. It's about emotional skills.
- Bad Pairing: One person acts like a boss, the other acts like a scared kid. The work suffers.
- Good Pairing: Both people act like partners. They notice when the "Power Gap" is getting too big, and they use "Equalizing Behavior" to fix it immediately.
The Takeaway for Everyone:
Whether you are a boss, a teacher, or a teammate, if you notice someone pulling away or getting quiet, don't assume they are lazy or stupid. They might just feel like they have no power.
The secret to success isn't being the smartest person in the room; it's being the person who makes sure everyone in the room feels like they have a voice. That is the true skill of working together.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.