There Are Only Two Ways Work Gets Done. Salary Isn’t One.
Same Company, Different Teams: Two Ways Work Gets Done
Disclaimer: I use AI to proofread and help shape the final version of my articles. But every piece is reviewed and published by me. Not an automated newsletter.
I’ve been at Amazon for more than 60 months — almost five years. This is my sixth team.
Changing teams wasn’t always my decision. Only twice did I move intentionally. Every other time, it was a re-org or a business need. But I always liked working in different teams, and still do.
Six teams. Four different organizations within Amazon. Four completely different work styles.
This might help if you’re joining Amazon and trying to understand the team you landed on. Or if you’re a manager trying to build an environment where people actually thrive — not just deliver.
This piece goes one level deeper: same company, same pay band, same leadership principles — but the team culture can change everything.
When salary stops being the motivator
In FAANG, including Amazon, people are paid well. In most cases, salary alone doesn’t drive the work.
After five years across six teams, one pattern became impossible to ignore.
There are two ways to get work done.
1. Inspire internal motivation
The original idea: driven by autonomy (choosing the right path) and mastery (doing it well).
2. Apply external pressure
The opposite: driven by deadlines (meeting demands) and avoidance (not wanting to fail others, or not wanting to be seen failing).
I’ve lived in both. Not once. Many times. That’s how I arrived at what follows.
When pressure gets the job done — and poisons everything else
External pressure works. Things ship. Deadlines get met. Dashboards turn green eventually.
But not in the right way.
You accumulate complexity. Tech debt piles up. People stop caring about the craft and start caring about survival. The environment stops feeling human.
The main concern is bureaucracy.
Every decision needs a document and approval. Every mistake needs a narrative. Process replaces judgment. Velocity replaces quality.
A few other things I noticed in pressure-first teams:
Status theater. Weekly meetings become performance reviews in disguise. People learn to report progress, not discuss problems.
Documentation as armor. Design docs aren’t written to clarify thinking. They’re written so that if something breaks, someone else takes the blame.
Hero culture. Firefighting gets rewarded. Prevention gets ignored. The person who does the production fix at 2 AM gets praised. The person who fixed in BETA stays invisible.
Quantity over quality. The work is never “the right thing.” It is just “the delivered thing.” Shipping beats correctness. Closing tickets beats solving problems.
People come and go. There is no long-term tenure. Those who stay usually aren’t the strongest builders. They’re the best at playing the visibility game — always in the right meeting, always aligned with whoever holds the red pen, always quick to attach to a win and slow to own a mess.
Out of this, the end product as a person is angry and frustrated.
And here’s the part that stuck with me most:
I’m not in touch with anyone from those teams.
Not because we had a falling out. Life just moved on. When pressure is the glue, the relationships don’t survive the re-org.
The other side: slower, quieter, and built to last
The inspiring side can feel boring at first.
Nobody is yelling. Nobody is counting your hours. Nobody is treating every sprint like a referendum on your worth.
But it has long-term value.
Innovation comes out of it. Yes, pressure can force a breakthrough once in a while. But it doesn’t scale. You can’t scare your way to a second great product.
You like the people around you. You go above and beyond — not because someone is watching, but because the work and the people deserve it.
You find the right project and the right person to do it. That person does an amazing job and never need to re-do that again.
Deadlines still exist. But they’re used in the right amount — as guardrails, not weapons.
Motivating people is hard. You do it by helping someone find their motivation — the impact of the project on real people, the craft of doing it well, the trust of the team counting on them.
You show up on Monday morning with energy. You go home with more energy than you arrived with.
That environment creates a different kind of person. Not soft. Not naive. Grounded. Generous. Ambitious.
“People don’t leave bad jobs. They leave bad managers.”
— Common workplace truth, backed by decades of engagement research
The manager — and the culture they protect — is the difference.
What the research says about this
This isn’t just my experience. Psychologists have studied it for decades.
Edward Deci and Richard Ryan developed Self-Determination Theory, which distinguishes between autonomous motivation (you act because the work matters to you) and controlled motivation (you act because of pressure, rewards, or fear of judgment).
Their research — and a recent meta-analysis of workplace studies — consistently finds the same pattern: when people feel autonomy, competence, and relatedness, they perform better, stay longer, and report higher well-being. When those needs are blocked — when work is driven by compliance and fear — burnout, turnover, and disengagement follow.
Dan Pink popularized a simpler version of this in Drive: autonomy, mastery, and purpose beat carrots and sticks for knowledge work.
On the other side, Amy Edmondson’s research on psychological safety shows why inspiration scales and pressure doesn’t. Teams where people can ask questions, admit mistakes, and challenge ideas learn faster and perform better over time. Teams where people stay quiet to survive may hit a deadline — but they rarely build anything that lasts.
Pressure can produce a successful sprint. It rarely produces a career, service, product, — or a friendship — you’re proud of five years later.
“Control leads to compliance; autonomy leads to engagement.”
— Daniel Pink
How to spot which environment you’re in
Early signals matter. Within a few weeks, ask yourself:
Do people admit mistakes openly, or rewrite history in retros?
Is the best engineer the most respected person — or the most politically visible?
Are design discussions about the customer — or about who will get credit?
Would you recommend this team to a friend?
Same company. Same LP deck on the wall. Completely different operating system.
What to carry forward
Three lessons — for any team you might one day lead:
Pressure delivers. Inspiration compounds. One hits the date. The other builds people who stay, learn, and raise the bar around them.
Watch how work gets done, not just what gets shipped. Tech debt, turnover, and silence in meetings are data. Read them early.
If you lead, choose the environment on purpose. Autonomy and mastery aren’t perks. They’re how you get work that survives the next re-org.
“Culture eats strategy for breakfast.”
— Peter Drucker
I send out Master Mentee 🎓 articles with curiosity and a passion for growth. If you’re enjoying it, I’d be grateful if you shared it with a friend who’d appreciate it too.
Not subscribed yet? Join the growing mentee squad of curious minds.
✨ Get the next issue in your inbox:
💚 If this resonated, tap the 💚—it’s free for you, but it supports my work and helps Master Mentee reach more amazing people like you.