Pygmalion Effect
Pygmalion Effect
What is the Pygmalion effect?
- High expectations raise real performance
- The virtuous cycle: expectation → behavior → performance
- The opposite is a vicious cycle: the Golem effect
What the Pygmalion effect really changes on the job is not the team member but how the leader diagnoses performance. Instead of looking for the cause of low performance only in a person’s ability and attitude, the leader starts counting: what level of difficulty did I assign last quarter, how many times did I give feedback, and how many times did I put this person in front of a customer? Expectation is not a mindset. It is a management behavior that leaves traces, such as task allocation sheets, one-on-one records, and speaking time in meetings, which makes it a variable you can check and correct.
Rosenthal identified four channels through which expectations reach the other person: climate, the warmth conveyed through facial expression and tone; input, the amount of explanation and the difficulty of the tasks given; output, opportunities to show ability, such as speaking and presenting; and the specificity of feedback. Expectations leak out through these four channels first, well before anyone says 'I expect a lot from you.' The effect also depends on timing: it works strongly right after a new leader arrives, or in the early days of a new hire or transferred employee, when judgments about the person have not yet hardened, and it weakens noticeably in relationships where a reputation has been fixed for years. When expectations a person holds of themselves raise performance, it is called the Galatea effect; when low expectations lock in low performance, it is called the Golem effect.
The most common misconception is treating expectations as words of encouragement. If a leader keeps saying, "You can do it," but the work handed over is still data compilation and meeting minutes and access to information stays the same, team members hear lip service. What remains is not an expectation effect but the conclusion that this is a leader whose words and actions don’t match, and they stop trusting even genuine offers later.
Second, the total amount of expectation is limited. If a leader concentrates good assignments and time on a few top performers who are already doing well, the Golem effect automatically applies to everyone else. Raising difficulty without support is not expectation either. When hard work is handed over without coaching, authority, or time, only failures pile up. It comes back as "I had expectations, but I was disappointed," and damages the relationship even further.
Seungbin JeonAn instructor who draws on psychology expertise to support communication and leadership growth in organizations
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum ConsultingIt was established when psychologist Robert Rosenthal and school principal Lenore Jacobson showed, in a 1968 elementary school classroom experiment, that 'teachers’ expectations change students’ achievement.' The name comes from Pygmalion, the sculptor in Greek mythology who fell in love with a statue he had made and brought it to life.
Consider a hypothetical case: the quality assurance team at Company A, a tier-2 automotive parts supplier with 260 employees. Associate Kim, in their fourth year, had received bottom ratings two years in a row and had come to be seen on the team as 'someone who just takes dictation for reports.' Customer claim analysis was concentrated on two senior managers, and lead times kept growing. This is a record of how the newly appointed QA team lead changed expectations and the allocation of opportunities over six months.
- When the team lead pulled the work allocation sheet for the past three months, everything assigned to Associate Kim was support for full-lot inspections and data entry, with zero client-facing tasks. At the team meeting, the lead was the first to admit, "We were the ones who didn’t give them work."
- In the one-on-one, the team lead assigned the task and gave reasons: "That defect root-cause table you put together last time was the cleanest document I’ve seen this year. You’ll be the main owner of next quarter’s claim analysis for Client B."
- To avoid simply handing work off, the lead set a fixed 30-minute coaching session every Tuesday and opened up access to quality data and a seat in regular client meetings at the same time. For the first two months, the lead reviewed report drafts together with Associate Kim.
- At the client review in the third month, Associate Kim presented in person. The team lead said on the spot, "Associate Kim did this analysis from start to finish," giving explicit credit and putting the owner in front of the client.
- Six months later, Associate Kim’s claim-handling lead time fell from an average of 11 days to 6, repeat claims from the accounts Kim handled dropped from 9 to 3 per quarter, and the number of people on the team able to do claim analysis grew from 2 to 4.