You are not your team: the mistake most new managers make

The biggest mistake most new managers make is assuming their team experiences work the way they do. Your preferences for how to get information, make decisions, and handle stress feel like common sense because they’re yours. They aren’t your team’s, and leading as if they were quietly breaks things.

I know because I did it. Here’s what happened, what I learned, and what you can do this week to avoid the same mistake.

What happened when I became a manager with no management experience?

I’m a serial entrepreneur and a full-stack developer. I’m comfortable building things. So when I became VP of Operations and Product at a small marketing and software firm and was asked to rebuild its team, I treated it like any other build. Find the right parts. Put them together. Ship.

I had never managed anyone. I didn’t know that mattered as much as it did.

I hired résumés, not people. If the experience lined up and the skills matched the job post, I made the offer. I didn’t ask how someone liked to work, how they handled pressure, or what kind of team they did their best work on.

The hires didn’t last. Clients left. Everyone was stressed. The strange part is that the business side was growing. I was good at the operations and the product. I was failing at people.

Why did I assume everyone worked like me?

I’m a neurodivergent introvert. I didn’t know that at the time.

What I did know was how work felt to me: how I took in information, how I thought things through, how I recharged. I assumed that was just how work is. So I managed the way that made sense to me, and I didn’t stop to ask whether it made sense to anyone else.

I wasn’t being careless. I was being normal. Your own experience is the only one you get to see from the inside, so it’s easy to treat it as the default. Most new managers do exactly this. They were promoted for being good at the work, and they lead the way they would want to be led.

The problem is that “the way I’d want to be led” is a sample size of one.

What do designers know that managers don’t?

Every designer knows you are not your user. Most managers never learn: you are not your team.

In product design, “you are not your user” is one of the first lessons. Designers learn that their own taste and habits are a trap. What feels obvious to the person who built the product is often confusing to the person using it. So designers watch, ask, test, and adjust. They design for real people, not for themselves. (If that idea is new to you, our glossary entry on design thinking is a short primer.)

Management needs the same discipline. Your team is made of people who take in information differently, make decisions at different speeds, collaborate in different ways, and react to stress in ways that might look nothing like yours. If you design the work around yourself, you’ll get a team that works great for exactly one person: you.

I didn’t learn this from a book. I learned it by watching someone else do it right. Short-staffed, and not out of any brilliance on my part, I put Billy, now my co-founder, in charge of the people side of digital marketing. She treated the team like a design problem, and the same roles that had failed under my hiring started to work. That story is the heart of our guide, your team is a design problem.

What does projecting onto your team look like day to day?

It rarely looks like a big mistake. It looks like a hundred small defaults. Here are some common ones:

None of the left column is wrong. It’s just one way of working, and it’s probably yours.

The tricky part is that projection feels like having standards. “Everyone should speak up in meetings” sounds like a reasonable expectation. It’s also a work-style preference dressed up as a rule.

How do you notice when you’re doing it?

You won’t catch it by trying harder to be fair. You catch it by watching for patterns. A few signs that you’ve designed the work around yourself:

• The same friction keeps coming back with the same people. If you keep clashing with one person in the same way, that’s a mismatch, not a coincidence.
• Your feedback doesn’t land. You said it clearly, by your standards. They heard something different, or nothing at all.
• Your favorite meetings are everyone else’s least favorite. Look at who talks and who goes quiet.
• You describe someone as “difficult” and can’t say exactly what they do. That word often means “works differently than I do.”
• Only some people seem to thrive. If the people who thrive are the people who are most like you, that’s worth noticing.

When you see one of these, get curious before you get frustrated. Ask yourself: is this a performance problem, or a design problem?

How do you stop projecting onto your team?

Here’s what I’d tell myself on day one.

1. Learn your own work style first

You can’t separate your preferences from “how work is” until you can name them. How do you like to get information? How do you make decisions? What do you need when things get stressful? Write it down. Seeing it on paper makes it much easier to notice when you’re treating it like a rule.

2. Ask each person how they work best

This sounds too simple. It works. In your next one-on-one, ask:

• How do you like to get new information: written, in conversation, or both?
• Do you prefer to decide quickly, or take time to think?
• How do you like to work with others on a project?
• What does a stressful week look like for you, and what helps?
• How do you like to get feedback?

Write the answers down and actually use them. A work-style assessment can give everyone a shared language for these conversations, but the asking matters more than the tool.

3. Offer more than one way in

You don’t need a custom process for every person. You need a few options. Send the agenda before the meeting. Let people add ideas in writing afterward. Give a heads-up before big changes instead of announcing them live. Small changes like these let different people do their best work without anyone needing special treatment.

4. Treat friction as information

When you clash with someone, map the difference instead of judging it. If you decide fast and they decide slowly, that isn’t a flaw on either side. Put together, it can be a better decision-making system: you push toward action, they catch what you’d miss. That idea has its own post: how to turn opposite work styles into balance.

5. Adjust how you communicate, not who people are

The goal isn’t to change your team into people who work like you. It isn’t to change yourself into someone you’re not, either. It’s to translate. Give the detail-lover the detail. Give the big-picture person the headline first. Our glossary entry on communication styles at work covers the basics.

6. Check your hiring too

Projection doesn’t stop at managing. It shapes who you hire. I hired people whose résumés looked like a fit, and I never asked how they’d fit with the team. Hire people, not résumés. I wrote more about that in what to look for beyond the interview.

What changed once I stopped assuming?

Watching Billy rebuild the team taught me that the people I’d struggled with were never the problem. I saw it again when I applied the same approach on the sales-driven side of the business. An employee leadership wanted to fire was promoted to manager within a year.

The “bad employees” I’d been warned about on day one weren’t bad. They were being managed in a way that didn’t fit them. Almost every people problem is a management problem.

That’s a hard sentence to read when you’re the manager. It’s also hopeful. If the problem is how the team is being managed, you can change it. You don’t need to replace your people. You need to understand them.

Where do you go from here?

Start small. Learn your own style. Ask your team the five questions above. Watch for patterns of friction, and treat them as design problems instead of personality flaws. That’s the core of people-first management, and you don’t need a title or a training program to begin.

We’re building Woosah Teams to make this easier: a short work-style assessment for each person, and a manager view that shows your whole team on one page, so you can see where styles overlap, where they clash, and how to lead each person the way they work best. You can read more about how it works or what it’s being built to do for managers.

But you can start today, without any tool at all. Just remember: you are not your team.