What Entrepreneurs Can Learn from Queen Bees and Wannabes
Priya ran a twelve-person startup out of a converted warehouse, and for months she told herself the team was flat and friendly, that titles barely mattered here. Then she noticed that decisions about vendors, conferences, even lunch plans, seemed to route through the same two people first. Nobody had assigned them that authority. When a new hire suggested a different project tool in a meeting, three people glanced at those two before anyone responded, and the idea quietly died. Priya had assumed conflict would look like raised voices or a formal complaint. Instead it looked like silence, an idea disappearing without a vote or an explanation. She started noticing who got asked for input before a plan was announced, and who found out only after it was already decided.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
The org chart nobody wrote down
Every young company develops a shadow hierarchy long before anyone gets a title. Certain people become the ones others check with before speaking up, and their opinions carry weight regardless of the formal reporting line. This isn't dysfunction by itself; groups organize this way quickly under pressure. The mistake is assuming that because a company is small and casual, no such structure exists, and missing that one person's approval has quietly become a precondition for anyone else's idea to survive.
A founder assumes an open-door policy is enough and never asks who actually gets consulted before decisions reach her, so the same two voices keep shaping the roadmap while others disengage.
Once a month, ask each team member privately who they'd loop in before proposing an idea, and see if the same names keep surfacing.
Cliques aren't just about who's rude
When friction shows up between employees, the automatic story is that one person is difficult. But status conflict in a small team often comes from scarce resources like credit or access to the founder's time, not individual character. Two capable people can end up in quiet rivalry not because either is unkind, but because the company's structure has made it feel like only one of them can be seen as indispensable. Treating every conflict as a personality problem misses the group dynamic driving it.
A founder pulls two feuding employees aside, tells each to "just be professional," and never checks whether the credit structure is quietly pitting them against each other.
Before mediating a conflict, map out what each person might be competing for that has nothing to do with liking each other.
What happens after someone tells you the truth
When an employee finally tells a founder that the culture feels exclusionary, the founder's very next response decides whether that employee, or anyone who hears about it, ever raises a concern again. Brushing it off, or publicly fixing it without asking what the employee wants, both tend to close that channel. Asking genuine questions first, and treating the report as useful information, keeps people willing to speak before small friction becomes a resignation.
A founder hears a complaint about exclusion, restructures the team in a public all-hands to "fix" it, and never realizes the employee only wanted to be noticed, not spotlighted.
When someone raises a concern, ask what outcome they're hoping for before deciding what to do about it.
Building judgment, not dependency
The deeper goal isn't a founder who personally resolves every team tension, it's employees who develop their own confidence to navigate disagreement, push back on a dominant voice, or ask for what they need without waiting for rescue. A founder who always smooths things over may feel responsible, but she is also training her team to bring her every friction rather than building the muscle to handle smaller ones themselves.
Recognizing the informal hierarchy and naming exclusion honestly can pull a founder toward fixing everything herself, undercutting employees' own judgment. Protecting a struggling employee by restructuring the team can also confirm, to everyone watching, that speaking up gets you rescued rather than heard. There's real tension between noticing structure early enough to prevent harm and resisting the urge to manage every relationship on the team's behalf.
Name one thing, honestly
When someone on your team raises a conflict, do you ask more questions than you give answers?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
When someone raises a concern, ask what outcome they're hoping for before deciding what to do about it.