Stepping into a project already in motion is one of the most exciting challenges a project manager can face. Whether I am scaling up a team or onboarding as a new partner or subcontractor, diving into a moving initiative offers a unique opportunity: the power of a fresh perspective and a clear-eyed read of where the contract stands against its requirements.

When I look at a project with fresh eyes, I am not bogged down by the day-to-day history. I have a chance to step back, look at the big picture, and determine how best to support my new team moving forward.

When joining a new project, my advice for fellow project managers is to run a quick, supportive audit of three core areas to help baseline where the team is and map out how to cross the finish line together.

1. The Pulse: Communication and Trust

Every high-performing project relies on a strong foundation of trust and psychological safety, and on a project manager who is familiar with the contract itself. When joining a team mid-stream, my primary goals are to understand the team’s current rhythm and ensure everyone feels supported.

Once I’ve reviewed the basics (scope and contracting), I focus on the following:

• What phase is the team actually in? Look at Tuckman’s team stages (Forming, Storming, Norming, Performing). A project’s timeline and its team dynamics should grow together. When you find a long-standing project where the team is still navigating the friction of the Storming phase, it diagnoses the underlying organizational challenges and gives you a clear baseline for how to adapt your leadership style to the team’s current needs, and flags risks to get ahead of them.
• Reading the Room: Paying close attention to the micro-signals that reveal a team’s true culture. For instance, are meetings “cameras off” with only one or two voices dominating the room, or is there active, balanced collaboration? Look for ways to spark that engagement, while also creating a collaborative space outside of meetings in Slack or Teams where anyone can comfortably ask questions.
• Are we keeping our promises? Trust with the client and within the team isn’t built on grand gestures; it’s built by saying you’re going to do something and consistently following through. Knowing exactly what I can commit to, and what requires client or contracting officer sign-off, is part of that trust. 
• Is there a safe space to be heard? In meetings and retrospectives, is there room for people to share real insights and feelings? At the end of the day, people just want to feel heard and understood.

2. The Tools: Making Them Work For You

A highly organized project is a sustainable project. When analyzing how a team tracks and manages its daily work, I have found it important to ask one guiding question:

“If a new team member were onboarded to this project tomorrow, could they look at our workspace and easily pick up where you left off?” For our government projects, if an auditor or a new contracting officer’s representative (COR) looked at our workspace, could they see exactly what we owe the government, when it’s due, and how we are tracking against it?

If the answer is no, it’s usually just a sign that our digital tracking tools need a quick tune-up. Whether your team manages work in Jira, Asana, Monday.com, or even a shared spreadsheet, the goals are the same. For example, if you are looking at a tool like Jira, you can focus on three quick wins to maximize clarity:

• Curation: Streamlining the backlog so the team is only looking at what is actively relevant to our immediate goals.
• Alignment: Ensuring individual tasks are mapped to overarching Epics and contract requirements so everyone understands how their daily work impacts the bigger picture.
• Predictability: Making sure tickets have clear, realistic due dates or release fix versions so the team can manage their capacity without burning out.

3. The Flow: Protecting Time & Trimming the Fat

Finally, look at the overall project workflow to see where we can inject a little more efficiency. Being a supportive leader isn’t about adding more overhead; it’s about clearing the obstacles that slow brilliant people down. To identify these gaps, start by asking one simple question: Why? Why are we doing things this way? Is it aligned to our contractual commitments, and is it truly serving us?

• Optimizing Meetings: Are our synchronous meetings serving the team well, or can we protect focus time by converting alignment checks into quick, asynchronous updates? Look closely at your calendar hygiene: Do you have the right people in the room? Is the frequency aligned with your sprint goals? Are meetings too long or too short? Is the cadence aligned with deliverable due dates? Asking these questions helps optimize everyone’s time.
• Refining Processes: Look at workflows to ensure every step adds tangible value. Are updates and documentation being shared just for the sake of it, or are they genuinely helpful? If a process or a tracking requirement feels heavy, collaborate with the team to strip away the fluff and simplify it. Sometimes, the best way to optimize a workflow is to simplify it or eliminate it. By stripping away the noise, we make everyone’s day-to-day lives just a little bit easier.

The Takeaway

Stepping into a new project isn’t about rewriting the script. It’s about empowering the people who are already doing the work and knowing that, at the end of the day, everything rises and falls on trust.

Without trust, I have found that my teams cannot have open, honest communication. Without open communication, team members lose that safe space where they feel comfortable calling out risks, sharing feelings, or asking for help. And once that safety net disappears, everything else, from your Jira organization to your project timeline, inevitably breaks down.

By prioritizing trust, building a strong foundation, and cleaning up our project tools and systems, it’s about more than just managing a project; it’s about supporting the people behind it. And that is how successful projects get delivered.