Ilina Maharjan Managing people and projects at the same time is one of the toughest transitions in any career, and almost nobody trains you for it. Most people get promoted into team management because they were good individual contributors — good developers, designers, or analysts. Then suddenly they’re expected to run a project and manage the people building it, often without anyone explaining that these are two different jobs that constantly pull against each other. This post is about doing both at once without burning out or burning your team out.
1. Separate “project health” from “people health” — track both
It’s easy to only check in on the project: is the sprint on track, are tickets moving, is the timeline holding. But a project can look green on the board while a team member is quietly drowning, disengaged, or about to leave.
- Have 1:1s that aren’t just status updates — ask what’s actually hard right now, not just what’s done
- Watch for early signs of overload: someone who used to speak up in standup going quiet, work quality dipping, deadlines being hit but with visible strain
- Separate the question “is the project on track” from “is this person okay” — you need honest answers to both, and they don’t always move together
2. Your job is to absorb ambiguity, not pass it downward
When requirements are unclear or priorities shift, the instinct under pressure is to relay that uncertainty straight to the team: “not sure what we’re doing yet, stakeholders are still deciding.” That’s honest, but it also makes the team anxious and unable to plan their own work.
A better default: absorb the ambiguity yourself, do the work of narrowing it down, and hand the team something concrete — even if it’s “here’s what we know for sure, here’s what might change, here’s what to do in the meantime.” Protecting the team from raw uncertainty is part of the job, not a failure of transparency. This kind of ambiguity shows up constantly on complex builds — for a closer look at where it derails timelines, see our guide to project management for ecommerce sites.
3. Delegate the project work, not just the tasks
There’s a difference between assigning tickets and delegating ownership. If you’re still the only person who understands why a decision was made or what the priority order is, you haven’t actually delegated — you’ve just distributed labor while keeping all the thinking to yourself.
- Give people context, not just instructions — the “why” behind a task, not just the “what”
- Let team members make calls within their area, even ones you might have made slightly differently
- Resist the urge to route every decision back through you — it slows the project and stunts the team
4. Protect the team from thrash, even when you can’t stop it
Priorities will shift. Stakeholders will change their minds. Your job isn’t to prevent that — you often can’t — but to buffer how much of that volatility actually reaches the team as constant redirection.
- Batch changes where possible instead of relaying every shift in real time
- When priorities do change mid-sprint, explain the why briefly, then move on — don’t let the team dwell in uncertainty longer than necessary
- If thrash is happening constantly, that’s a signal to push back upstream, not just to keep absorbing it indefinitely
5. Recognize burnout before the deadline does
Deadlines have a way of making burnout invisible until it’s a resignation letter. The behavior to watch for isn’t complaining — it’s the opposite: someone who stops raising concerns, stops pushing back, and just quietly grinds through.
- Ask directly, not rhetorically: “how’s your workload actually feeling this week?”
- Notice when someone hasn’t taken time off in a while and proactively suggest it, rather than waiting for them to ask
- If the team is consistently working unsustainable hours to hit dates, that’s a planning failure to fix, not a resilience test to praise
6. Give credit outward, take responsibility inward
When the project goes well, make sure the team’s contributions are visible to whoever’s above you — individually, not just as “the team did great.” When something goes wrong, own the parts that were yours to own before looking for what the team could have done differently. This single habit does more for trust than almost anything else on this list.
The Bottom Line on Managing People and Projects
Managing people and projects at the same time never gets easy, but it gets more sustainable once you stop treating them as one job. Track people health and project health separately, absorb ambiguity instead of relaying it, delegate ownership, and watch for burnout before a deadline forces the issue. Do that consistently, and managing people and projects together becomes a skill you build on purpose, not a role you fall into by accident.
Related Questions
Why is it hard to manage people and projects at the same time?
It’s hard because managing people requires empathy, coaching, and handling individual needs, while managing projects requires tracking deadlines, scope, and deliverables — two very different skill sets that can pull attention in opposite directions.
Do most managers get trained before becoming team leads?
No. Many people are promoted into management because they were strong individual contributors, not because they received formal training in leading people or running projects.
What is the biggest mistake new managers make?
A common mistake is focusing entirely on project deadlines while neglecting the people side of the role, which can lead to burnout, low morale, and turnover on the team.
How can a manager avoid burning out their team?
Managers can avoid burning out their team by setting realistic deadlines, checking in regularly with individuals, distributing workload fairly, and being honest about project constraints instead of absorbing all the pressure themselves.
Is it possible to separate people management from project management?
In smaller teams the same person often does both, but as teams grow, some organizations split the roles, with a project manager handling timelines and a people manager focused on team development and wellbeing.