By: Audrey Denise B. Cachuela
A project lead who used to run a small two-person team gets asked to manage a team of twelve. It felt like a win at first. Three months in, it feels like drowning. Meetings get shorter, memory gets stretched thinner, and the manager starts wondering if they’re not cut out for the job. What actually happened is simpler: the informal habits that worked for two people stopped working at a larger scale, and nobody flagged it in advance.
Brian Watkins, founder and president of BTOM Consultants, sees this constantly with frontline and middle managers. They take on a team, but nobody gives them more training, time, or support to go with it. Calendars fill up, attention splits too many ways, and the informal routines that kept a project team aligned start falling apart before most managers notice.
Management Habits That Work Small Often Break Big
With small teams, informal management just works. Someone has a question; they ask it in the hallway. A performance dip gets noticed fast. Feedback happens over coffee. Everybody has a rough sense of what everyone else is doing without anyone tracking it. That ease is deceptive. It’s easy for a manager to think the team runs well because they’re good at this, when really the team is just small enough that almost nothing can hide.
Add more people and a new title, and the whole thing changes. Information stops traveling the way it used to. Small confusions sit there longer than they should. Decisions take an extra day or two to reach whoever’s waiting on them. And attention starts pooling around whoever’s loudest, whoever’s on the flashy project, whoever needs help right this second, while everyone else just waits their turn.
That’s a problem for the quiet, capable people on the team. They don’t create emergencies, so they don’t get attention. New hires can be struggling and say nothing for weeks. Small misunderstandings sit there silently until they turn into a missed deadline, a tense exchange between coworkers, or a performance conversation that catches the manager off guard. On top of that, a new manager is also learning what their own bosses expect, and trying to prove that confidence was warranted.
The data backs this up. Manager engagement worldwide dropped from 27% in 2024 to 22% in 2025, while individual contributor engagement barely moved. That gap tracks with managers getting squeezed between changing executive priorities and employees who expect more from them than they used to (Source: Gallup, 2026).
The usual fix people reach for is tighter control of time. Trim the meetings. Block the calendar. Squeeze more out of the hour. That misses what’s actually breaking. A bigger team needs a deliberate way to spread clarity, attention, feedback, and accountability. Equal time for everyone isn’t realistic once headcount climbs, and chasing it is a losing game. What holds up is a system that gives each person roughly what they need, not an identical slice of the manager’s day, since a bigger team has a lot less room for error than a small one.
Effective Team Management Starts With Role Clarity
This is where most of it starts. You can’t hold someone accountable for a target that was never clearly defined. “Take ownership” and “communicate more” sound like direction, but they don’t say what to actually do differently. Real clarity spells out the result expected, how much autonomy the person has, the deadline that matters, and the point where they need to loop the manager back in.
It gets more important once responsibilities start overlapping, which happens often when companies merge teams or cut a layer of management. Someone inherits work that used to belong to a different role, and if nobody resets expectations, three people end up assuming three different things about who owns what. Then it gets duplicated, delayed, or quietly dropped.
Brian Watkins built something called the Great Manager Operating System around this idea. It runs on repeatable behavior: define expectations, run one-on-ones that actually accomplish something, notice what each person needs to grow, catch performance problems before they spread. The underlying point is that a repeatable system holds up a lot better than habits, good and bad, that only live in someone’s head.
That matters even more for managers who got the job because they were good individual contributors, which is most of them. A 2023 study of more than 4,500 UK workers and managers found that 82% of people stepping into management received no formal training at all (Source: Chartered Management Institute, 2023). Being good at the technical side of a job gets someone promoted. It doesn’t teach them how to build clarity for a dozen people watching them for cues.
Why One-on-One Meetings Need an Actual Purpose
Role clarity sets the destination. One-on-ones are how a manager actually gets to know the individual, how they work, when they’re struggling, and what they need. Unfortunately, they’re usually the first thing to slip once workloads pile up. One gets pushed a week. Another gets cut to fifteen minutes. A third turns into a Slack message and never gets rescheduled. None of that feels like a big deal in the moment, but add it up over a quarter, and the message is clear: these conversations only happen when nothing louder is competing for the calendar.
The bar is higher than just holding the meeting. Plenty of one-on-ones are just status updates that an email could’ve handled. A one-on-one that’s actually doing its job surfaces something the manager wouldn’t have found out otherwise.
The good ones cover current priorities, catch obstacles before they turn into blockers, open up feedback in both directions, and check in on where the person wants to go. What that looks like changes person to person. A new hire probably needs more frequent guidance and reassurance, while someone five years in probably needs more autonomy, a sounding board for hard calls, and an honest conversation about where their career is headed.
Equitable support means adjusting time and attention to each person’s real differences in experience, confidence, workload, and ambition. A manager who keeps a reliable cadence and actually adjusts the content person by person gets a lot more out of that time than one running the same fifteen minutes with everyone.
That cadence does more than develop people, too. It catches problems while they’re still small. A missed deadline can mean ownership was never clear. A shift in someone’s tone often signals something unresolved under the surface. And repeated requests for sign-off on things someone should be deciding themselves usually point to confusion about how much authority they actually have.
Skip the cadence, and managers usually find out about these things only after the consequences show up, and by then the fix is messier and a lot more emotionally loaded than it needed to be. There’s a quieter benefit too. Employees stop having to decide whether something’s worth interrupting the manager over, because there’s already a place on the calendar to bring it up.
Feedback Loses Its Value the Longer It Waits
Catching something early is only half of it. What happens next matters just as much, and that comes down almost entirely to timing. Feedback that only shows up in a quarterly or annual review has already lost its value. If someone hears about a recurring problem for the first time in a quarterly review, that is a sign the manager failed.
Feedback given close to the moment ties a specific behavior to its effect, which makes it easier to understand and act on. It also keeps things anchored to the work instead of feeling personal. Positive feedback needs that same precision. “Good job” feels nice for about five seconds, but it doesn’t say which behavior to repeat. Spelling out what worked turns a one-time win into something someone can rely on again.
A manager also needs a way to check whether the feedback landed, without hovering. That just means a defined follow-up point: the employee knows what improvement looks like, when it’ll come up again, and what support exists in the meantime. Done right, this builds accountability without tipping into micromanagement, since the manager stays connected to the outcome while the employee still owns how they get there.
Your Attention Is Teaching the Team What Matters
Managers teach priorities through their behavior, often without meaning to. If the loudest problem always wins the most attention, the team learns urgency beats planning. If a strong performer only hears from the manager when there’s more work to hand off, doing well starts to feel like a punishment. If hard conversations keep getting pushed to next week, the team quietly learns that standards are optional until something forces the issue.
Brian puts it bluntly: “Calm is contagious, and so is panic.” That matters more as a team grows. A manager’s visible frustration used to reach one or two people. Now it shapes how an entire group reads uncertainty. People get hesitant, or defensive, or lean too hard on approval, and a lot of that is just them reacting to the manager’s mood rather than the actual level of risk in front of them.
Staying calm means separating urgency from anxiety. That means naming the issue, saying what’s actually known and acknowledging what isn’t known, assigning ownership, and setting the next decision point. That gives a team something to act on instead of something to sit and worry about.
This is genuinely harder now than it used to be. Among more than 31,000 workers surveyed across 31 countries, 53% of leaders said productivity needs to go up, and 80% said they lack the time or energy to keep up with what’s already being asked of them (Source: Microsoft, 2025). Nobody can make that pressure disappear, but a manager can control whether it steers how they talk to people.
How to Manage a Larger Team Without Micromanaging Anyone
Start with an honest audit. Feedback that only happens when a manager notices something in passing is too fragile to survive growth. Priorities that live mostly in conversation send three people out of the same meeting with three different memories of what got decided. A one-on-one that disappears the second things get busy costs the team its only dependable connection point.
Writing the system down is what actually makes it stick. A one-page expectations doc per person, updated whenever the role shifts even a little, prevents more duplicated or dropped work than any single conversation ever will. The same logic applies to the calendar. A recurring one-on-one invite survives a busy week in a way that a meeting booked fresh every Monday just doesn’t.
It’s worth checking where coaching time actually goes each month. Pull up the calendar and be honest about it. Does it default to whoever escalates the fastest, or to whoever actually needs it most? Attention shaped by real judgment beats a perfectly even split, which nobody’s going to hit anyway.
Last, trade constant availability for clear access. People need to know which decisions are theirs to make alone, which questions can wait for the next scheduled check-in, and which situations need to go straight to the manager. That clarity cuts down on interruptions and gives people more confidence to move without asking permission for every little thing.
This compounds over time. Fewer emergencies show up. People stop guessing what they’re actually allowed to decide. And the manager stops carrying the whole operation around in their head.
Anyone stepping into a bigger team needs a system like this before informal habits turn into a string of performance problems nobody saw coming. Brian Watkins and BTOM Consultants work with frontline and middle managers on exactly this kind of transition, helping them build habits sturdy enough to handle growth instead of buckling under it. If you want to see more of how that works in practice, BTOM Consultants is a good place to start.
