Read time: 8 minutes

Welcome to Tactical Memo, my newsletter where I share clear lessons and simple systems for project managers, operators, and team leaders navigating the AI era. Each issue tackles one real workplace challenge and hands you a ready-to-use solution.

If you want practical guidance you can use at work this week, you are in the right place.

👉 Why Read This Edition: I am going to show you how to run a team that does not report to you, and why the people who figure this out are the ones who actually get promoted.

APRIL LINEUP

April is a big month over here.

We have an incredible line up for free lightning lessons, paid workshops, and extended cohorts.

Free Live Events

• Mon, Apr 20 at 11:00 AM — Become the Project Manager Everyone Wants to Work With

• Fri, Apr 24 at 11:00 AM — The 4-Phase AI Framework Every Project Manager Needs

Courses (4 weeks, Apr 13 – May 10)

• AI-Powered Project Management — Build the skills to apply AI to your real projects starting this week.

• Project Management That Actually Works — Build the project management skills that actually drive outcomes.

1-Day Course (May 13)

Before 4/3: use code SPARK → get a 50% discount. Limited to 30 Seats.

• Become Irreplaceable: Build the Edge AI Can't Copy - When AI Gives Everyone the Same Tools, Execution Sense Is What's Left

THE PROBLEM

Here is an unpopular opinion. The org chart is a crutch. And the people who lean on it the hardest are usually the weakest leaders in the building.

You got handed a cross-functional project. Maybe a product launch. Maybe some initiative your VP dropped on your desk between meetings and forgot about by lunch. Now you need output from engineers, marketers, and finance people who have their own bosses, their own deadlines, and zero obligation to care about your project.

You have no authority over any of them. You cannot write their reviews. You cannot promote them. You cannot fire them. And when the project misses its deadline, nobody is going to blame the engineer who ghosted your Slack messages. They are going to blame you.

Most people respond to this situation in one of two ways, and both are pathetic.

The first type sends polite emails. They schedule "alignment" meetings. They follow up with "just circling back" messages that everyone ignores. They wait. They hope. They eventually do the work themselves at 11pm because waiting on someone else felt worse than doing it alone. That is not leadership. That is volunteering to be a doormat.

The second type runs to their manager. They CC leadership on every email. They try to borrow someone else's authority to force people into action. This works once. After that, nobody picks up when they call. They become the person everyone avoids on Slack.

Both types share the same problem. They think leadership is a position. It is not. Leadership is a behavior. And the sooner you accept that, the sooner you stop being the person chasing people and start being the person people come to.

THE SOLUTION: THE INFLUENCE WITHOUT AUTHORITY FRAMEWORK

I spent years running consulting teams and cross-functional projects where I had zero direct reports. Tiger teams. Recovery teams. Teams built to fix something that was already on fire. The framework was always the same.

Part 1: Earn the right before you ask for anything

Here is what most people get wrong. They walk into the first meeting, introduce themselves as the project lead, and immediately start assigning work. Then they wonder why nobody delivers.

You have not earned anything yet. The title on the project charter is meaningless. The only question anyone on that team is asking about you is: "Why should I care about this person's project when I have my own work to do?"

You answer that question with preparation. Before your first meeting, learn what each person's actual priorities are. Find out what their manager is pushing them on this quarter. Understand what their version of winning looks like. Not your version. Theirs.

Then do something for them before you ask for anything. Share context they did not have. Flag a risk headed their way. Give them a head start on something their boss is going to ask them for next week. I have seen this single move, one act of giving value before requesting it, change the entire dynamic of a project within 48 hours.

The best leaders I have worked under all had the same trait. They made the people around them measurably better. Not in an inspirational poster way. In a "you saved me two hours this week" way. The person who walks into a cross-functional team and makes everyone else's job 10% easier has more influence than any VP who sends a "please prioritize this" email.

Part 2: Kill the ambiguity

Ambiguity is where cross-functional projects go to die. When people do not know exactly what is expected, by when, and why it matters, they do the rational thing. They work on what their actual boss is measuring them on. Your project drops to the bottom of the list.

Most project leads try to fix this with more meetings. More status updates. More Slack channels. That is treating symptoms. The disease is unclear expectations.

Here is how you fix it.

Define a win that a human being would care about. "We ship this feature by March 15 so the sales team can demo it at the conference" is a win. "Complete sprint tasks on time" is a Jira metric. Nobody stays late for a Jira metric.

Make every commitment public. In your first working session, go around the room and have each person say out loud what they are going to deliver and by when. Not in a side DM. Not in an email thread. In front of everyone. Public commitment changes behavior in a way that private agreements never will. There is research on this. Robert Cialdini documented it decades ago. When people commit in front of peers, follow-through rates go up dramatically.

Build one source of truth and keep it updated. One doc. One tracker. If someone has to message you to find out what is going on, you have already failed. The system should answer that question without you being in the room.

Run 15-minute check-ins every week. Three questions only. What did you finish. What is stuck. What do you need from someone else here. That is it. If your check-in takes longer than 15 minutes, you are having a meeting, not running a check-in.

Part 3: Be candid, not political

This is where I break from the conventional advice. Most leadership content tells you to be diplomatic. To manage up. To navigate. I think that is a recipe for mediocrity.

When someone on your team misses a deadline, go talk to them directly. Not in a meeting. Not in an email. Walk over, pick up the phone, or get on a video call. Ask what happened. Then shut up and listen.

Nine times out of ten, there is a real reason. They got pulled onto a fire drill. Their manager changed their priorities. They did not understand the ask. All of those are fixable in a five-minute conversation.

Here is what you do not do. You do not CC their boss. You do not flag it in a status report to make yourself look responsible. You do not use the miss as leverage. That is cowardice dressed up as accountability.

Handle it directly. Help them course-correct. Move on.

But here is the key part. If you have the direct conversation and the person still does not deliver, you escalate immediately. Not after a third chance. Not after another "gentle reminder." You go to their manager, explain the situation clearly, and ask for a solution. Directness is a gift. Letting someone quietly fail while you absorb the consequences is not kindness. It is cowardice in the other direction.

The best cross-functional leaders I have worked with had a simple pattern. They were incredibly generous with their time, their context, and their patience on the first conversation. And they were ruthlessly direct on the second one. People respected them for it because everyone knew exactly where they stood.

THE REAL TEST

Here is the question that separates the real leaders from the people who are just managing a spreadsheet with names on it.

If this project ended tomorrow and a new one started next month, would the people on your team volunteer to work with you again?

Not because they have to. Because they want to.

The people who build reputations inside organizations are not the ones with the biggest titles. In every company I have worked with, the most influential people were individual contributors and mid-level managers who could walk into any room and get people to follow them. They had earned it by being prepared, being direct, and treating every person on the team like an adult who deserved honesty.

You do not need a reporting line. You do not need a corner office. You need the discipline to show up prepared, the guts to be direct when something is off, and enough self-awareness to give credit to the people who actually did the work.

Pick one person on your cross-functional team this week. Learn what they are being measured on. Do something that helps them hit their number before you ask them for anything. Then watch how fast the dynamic changes.

That is influence. And it is worth more than any title you will ever hold.

If this helped you, send it to someone who could use it this week.

Until next time,
Justin

✍️ From the Desk of Justin Bateh, PhD
Simple tactics. Real results. No fluff.