Skip to Content
JUST IN: 2027 Internal Comms Trends Report icon

Internal Communication

Project management for internal communicators (because you’re already doing it)

Project management for internal communicators (because you’re already doing it)

If you’ve ever been three days from launch, coordinating edits still rolling in from your leadership team, legal asking for one more review, letting a designer know there’s a few more copy tweaks before it’s final, and someone casually Slacking, “Could we add a video?” — congratulations! You’re doing project management. 🙃

As a project manager, I’ve spent a lot of my career watching internal communicators do exactly what I do: manage timelines, stakeholders, approvals, dependencies, deliverables, and approximately 47 Slack threads at any given moment – they just don’t always call it project management.

And here’s the thing: most internal communicators were never actually taught how to project-manage. It might not be in the job description, but it is absolutely in the job.

So, what actually counts as a project?

Scott Berkun, author of Making Things Happen: Mastering Project Management, has a wonderfully simple take: “Everything is a project.”

Project management is about how the work gets done — timelines, owners, approvals, deliverables.

When you try to manage all of this from memory (or Slack, or email, oh my 😬), things get messy fast. Deadlines slip, requests multiply, approvals arrive approximately four minutes before send time. And somehow, a “quick email” has eaten your entire week.

Here’s the rule of thumb I use with internal comms teams: if the work has a defined beginning and end, multiple deliverables or steps, and more than one stakeholder, you probably have a project on your hands.

Think: campaigns, launches, recurring newsletters, benefits enrollment, town halls or employee events, change management communications, intranet migrations, org change rollouts (need I go on?). 

Here’s my case: internal comms work is project work. 

And then there’s my personal favorite: the quick email.

Someone asks for a quick email, then leadership needs to review it, HR has edits, someone decides managers need talking points. Oh! And could we add an FAQ?

Three weeks later, you’re managing six deliverables and nobody ever stopped to say, “Hey, I think this is a bigger project.” So once you realize you have a project on your hands, what do you actually do with it?

Good news: you don’t need to PMP-ify your entire life. A few simple project management habits will get you surprisingly far. 

So let’s make the project management part of your job a whole lot easier. As a career project manager, here’s my advice on how to manage a project, without being a “project manager.” 

1. Use a framework you can actually remember

You do not need to become a certified project manager. You need a framework simple enough to remember while six people are asking you for six different things.

That’s my bar.

Try: Scope → Plan → Execute → Launch → Measure → Debrief

Scope: What are we actually doing?

Before you build a beautiful color-coded spreadsheet, or open a project in your project management tool (Asana is my favorite! There’s even a free version), get clear on the basics. I love to open up the conversation by just saying, “let’s get everything out of our brains.” 

  • What are we trying to accomplish? 
  • Who is it for? 
  • If we go big, medium, or small, what does this look like?
  • What are we creating? (Maybe also, what are we not creating?)
  • Who needs to be involved? 
  • When does it need to be done?

This is your best chance to catch all those sneaky little extras before they become, “Oh, can we add this in?”

My rule of thumb: if you’re wondering about something, someone else probably is too. Ask the “silly” question. Nine times out of ten, it isn’t silly.

AI tip: Paste the original request (yes, even the chaotic Slack message) into Claude or ChatGPT and ask, “What questions should I ask before I scope this?” It’s a great way to catch the sneaky extras before they catch you.

Plan: How are we getting there?

Now work backward from the deadline.

Map the big milestones, owners, dependencies, and approval time (this one especially deserves approximately 14 underlines). 

  • If legal usually takes three days, don’t give them three hours.
  • If your CEO historically reviews copy the night before it goes out, plan around the CEO you actually have, not the beautifully punctual imaginary CEO living in your project plan.

Buffers are what keep one late approval from turning Wednesday afternoon into a five-alarm fire. Build for your reality!

Execute: Do the work. 

This is the messy middle: drafting, designing, reviewing, revising, and herding approvals toward the finish line. Your plan stops being a document you made and starts being the thing you manage from.

A few habits that keep the work moving:

  • Keep one source of truth. Status, owners, and the latest version live in one place (your project tool or comms calendar), not in someone’s DMs.
  • Do a quick weekly check-in. Fifteen minutes (or an async Slack thread) to answer: what’s done, what’s stuck, and what’s next?
  • Flag risks early. If an approval is running late, say so now, not the day before launch.
  • Use designated project channels in Slack to keep communication about the project contextualized and clear. 
  • Create Claude or ChatGPT bots that scan for updates and post status updates regularly throughout the week to help keep the project team on track. 
  • Let AI take the first pass. Use Cici in Workshop to spin up a first draft, ask Claude or ChatGPT to turn a long brief into a manager FAQ, and let Asana AI summarize where things stand for your weekly update.

Your job here isn’t to do everything yourself. It’s to keep the work visible, so nothing surprises anyone on launch day.

Launch: Ship it!

This is the send, launch, rollout, event, migration, or whatever you’ve been working on.

At this point, you’re making sure everyone knows what’s happening, who owns what, and where the latest version lives. (And no, final_FINAL_v7_USETHISONE.docx does not count as a project management system.)

This is also when things inevitably get a little spicy. Someone finds a typo an hour before go-live, a stakeholder asks for “one tiny edit,” or classically, the platform chooses today to have feelings.

So decide a few things before launch day: 

  • Who has the final sign-off? 
  • Who’s the point person if something breaks? 
  • What actually warrants delaying the launch? 
  • We love to use the language “fast follow” for anything that we’d suggest still editing or fixing, but doesn’t stop the launch from happening. 

One person coordinating those calls, even for a few hours, can save you from five people editing five versions in five different places.

Measure: Did it work?

Decide what success looks like before you launch.

Maybe it’s opens and clicks, town hall attendance, benefits enrollment, employee sentiment, intranet adoption, or simply fewer confused questions afterward (clarity is a great metric in comms!).

You probably don’t need a 17-metric dashboard, just pick the two or three things that will actually tell you whether the communication did its job and pay attention to those.

AI tip: If your success metric includes open-ended feedback (survey comments, pulse checks, “any questions?” replies), paste it into Claude or ChatGPT and ask for the top themes. Hours of reading becomes a five-minute summary you can actually share with leadership.

Debrief: What are we stealing for next time?

This is the part everyone skips because the project is finally over and we would all very much like to move on with our lives.

Do it anyway! I promise.

What worked? What got weird? Where did things stall? What should you repeat next time? And what should Future You never have to experience again?

I love a simple start, stop, continue:

  • What should we start doing?
  • What should we stop doing?
  • What should we continue doing?

And because humans are endlessly imaginative when it comes to adding new things, I actually like to start with stop. What can we stop doing to get some time back before we decide what shiny new thing we’re going to add?

Even ten minutes of reflection can make the next project noticeably easier.

For us, we create a “retro” task in Asana 30 days post-launch and have an easy template for the project owner to fill out and share with the team. We cap the “data digging” at 1hour so retroing actually feels approachable and not like a whole project in and of itself.

AI tip: Turn on an AI notetaker (Zoom AI Companion, Gemini in Google Meet, or whatever your team already uses) during the debrief. Then ask it to sort the conversation into start, stop, and continue so Future You has a tidy record without anyone taking notes.

2. Make it work for the team you actually have

“But I’m a team of one.” Great! This still works.

Project management doesn’t require a project management team. If you’re a solo internal communicator, think of this framework as your POS (your personal operating system, obviously 😉).

You don’t need more meetings, twelve new processes, or to spend Friday afternoon lovingly maintaining a Gantt chart no one else will ever open.

You need fewer things living exclusively inside your brain.

David Allen put it perfectly in Getting Things Done: “Your mind is for having ideas, not holding them.”

So get the work out of your head.

Scope it and make the plan, then manage the plan from there. We all know what happens to the best-laid plans, right? That’s okay! A plan that changes isn’t a failed plan. It’s a plan doing its job. The point is that when things shift, you can see what moved and who needs to know.

And if you’re a team of one, AI might be the closest thing you’ll get to a project coordinator. A few ways I lean on it:

  • Get a starting plan in minutes. Paste the request into Claude or ChatGPT and ask for a scope, milestones, and a timeline worked backward from your launch date. It won’t be perfect, but editing a solid draft beats staring at a blank page.
  • Hand off the busywork to Asana’s AI agents. Asana’s AI Teammates can break a brief into tasks, triage incoming requests, flag what’s slipping, and draft status updates, so you’re not chasing every update yourself.
  • Build the comms faster with Cici. Workshop’s AI agent can take a single prompt and build a ready-to-review email, so more of your time goes to strategy and stakeholders (and less to wrestling with formatting).

Think of it as extra hands, not an extra brain. You still own the judgment calls. AI just helps you get the work out of your head faster.

And if you’re on a small team, the exact same framework becomes shared vocabulary. Instead of one person holding every piece, everyone can see who owns what, where the handoffs happen, and when someone else needs to jump in.

Same framework. More people holding the pieces.

Intention — not headcount — is what makes it project management.

3. Choose tools your team will actually use

I regret to inform you that there is no magical project management tool that will fix a messy process.

(I know. Rude.)

A spreadsheet can work. A shared doc can work. Asana, Monday, ClickUp, Notion — all great.

The best tool is the one your team will actually use and keep updated.

Meet people where they are. Implementing a new process is hard enough without also convincing 14 stakeholders to fall deeply in love with your new software.

For internal comms teams, I’m a big fan of using your comms calendar as the project hub whenever possible.

You’re already looking there to see what’s going out and when. Add milestones, owners, approvals, and status, and suddenly you’ve got one source of truth instead of another tab you have to babysit.

Keep it simple when you have one project, a short timeline, and a handful of stakeholders.

Level up when you’re juggling recurring programs, overlapping campaigns, lots of dependencies, or multiple people doing the work.

And forget whether a “serious” project manager would approve of your setup.

The better question is: Can you tell what’s happening without digging through six Slack threads?

If yes, beautiful. Carry on.

And yes, AI counts as a tool now, too. It won’t fix a messy process either (still rude), but it’s fantastic at the tedious stuff that eats your week:

  • Slack AI can recap a long thread or a busy channel, so you can catch up without scrolling through all 47.
  • Gemini in Google Workspace can summarize a doc, pull action items out of meeting notes, or help you find the latest version (goodbye, final_FINAL_v7).
  • Claude or ChatGPT can turn a messy brain dump into a clean brief, a timeline, or a status update in about 30 seconds.

My rule: AI drafts, humans decide. Give everything a once-over before it goes to a stakeholder, and keep sensitive employee info in the tools your company has actually approved.

4. Treat stakeholder management like part of the project

You can build the prettiest project plan in human history and still watch the whole thing fall apart because someone didn’t approve the copy.

Internal comms sits in the middle of so many teams — HR, leadership, IT, legal, marketing, operations, managers, and on and on.

Every one of those teams has different priorities, timelines, and opinions.

So yes, project management is about tasks and timelines.

But a huge part of it is really people management.

A few things I’ve learned to watch for:

  • Set approval deadlines that are actual deadlines. Give a specific date and time, not “by the end of the week.” And decide ahead of time what happens if someone misses it.
  • Make ownership painfully clear. “Someone” is not an owner. A person’s name is an owner.
  • Follow up without convincing yourself you’re professionally nagging everyone. You’re keeping the project moving. That’s the job!
  • Plan for competing priorities. Sometimes three VPs will all believe their thing is the most urgent thing. Your project plan won’t magically solve that, but it will make the tradeoffs visible.
  • Learn to spot scope creep wearing a tiny hat. If a “small request” adds a deliverable, another reviewer, or three extra days, it’s not small anymore. It’s a scope conversation.
  • Get comfortable pushing back without making it weird. Clear constraints are kinder than silently saying yes and missing the deadline later.

5. Steal these templates (and this checklist)

Here’s what I’d keep handy:

And while we’re here, you can steal this mini kickoff checklist right now.

Before you start, can you answer these nine questions?

  • What are we trying to accomplish?
  • Who is this for?
  • What are we creating?
  • Who owns each piece?
  • Who needs to approve it?
  • When do we actually need those approvals?
  • What could hold us up?
  • How will we know it worked?
  • Where does the latest version of everything live?

If you can answer those nine questions, you have a pretty solid project plan.

No certification required. ✨

6. Watch for the places projects usually go sideways

Even with a framework, there are a few traps I see internal comms teams fall into again and again.

And I have a feeling at least one of these is going to feel extremely familiar.

Not building in approval time.
The launch date is not the deadline for the first executive review. Give yourself room for the inevitable second (and third) round.

Skipping the debrief.
Ten minutes now can save you hours next quarter. Write down what Future You needs to know while Current You still remembers it.

Project-managing through Slack DMs.
Slack is great for conversation. It is significantly less great as the only place your deadline, approval, final copy, and important stakeholder decision exist.

Over-planning the tiny stuff.
The answer to messy work isn’t always more process. Sometimes the two-sentence update really is just a two-sentence update.

Ship it!

The goal is enough structure to make the work easier — not so much structure that managing the project becomes its own project.

You’re probably closer than you think

You don’t need a PMP certification to get better at project management.

You probably don’t even need a new tool.

You need a repeatable way to get the work out of your head, make expectations visible, and give yourself a little breathing room when things inevitably change.

Start small.

Pick one upcoming project and try:

Scope → Plan → Execute → Launch → Measure → Debrief.

Use it once. Notice what made your life easier. Toss what didn’t. Then use the good stuff again.

That’s project management.


Keep reading

Link copied!

Join the Happy Monday Club!

Start your week inspired and energized with our practical newsletter about positive company culture! It features actionable articles and little surprises, sent every Monday morning.

Happy Monday Club