This is my experience leading cross-team initiatives, I just want to share what I learned from it
When you lead a big initiative, it’s usually cross-team. You’ll need other teams’ help, and you’ll be dealing with product scope and domain knowledge you’re not familiar with, yet you still have to lead them. At first it will feel scary, but with a good plan and preparation, it gets much less scary.
First things first, clarify the requirements with your product manager. What’s the big idea, what’s the story, and what value will the initiative bring? That gives you a clear picture of its purpose and what you need to prepare.
Once the requirements are clear, the next step is to ask your colleagues on the other team about their scope and how their system works at a high level, not in detail.
For example, if your project involves a payment gateway or financing flow you don’t know, ask the team at least enough to understand the general flow:
Don’t ask for too much detail. You won’t master it in a short time anyway, so once the requirements and constraints are clear, that’s enough.
A big initiative usually has a lot to prepare: tasks you do yourself, tasks your peers handle, and tasks other teams take on to support it. To keep them on track, create a task tracker. A spreadsheet or a simple note works. It keeps you focused and gives you an eagle view of the project.
Many tasks won’t be in your hands, but it’s still your job to make sure they get done. The tracker doesn’t have to be perfect at first. It just has to be useful for tracking the project.
Next step: draft the RFC document
A Request for Comments (RFC) document makes the discussion clearer. List the topics you want to discuss and include a high-level design of how it will be done. It helps your team understand the general flow, it also tells other teams what the project is about, so they know why they need to help.
Don’t wait for them to give the solution, offer them a few options you think could fit the project. These days AI can propose a solution for almost anything, but its proposal won’t always match the other team’s concerns because you don’t know the other team’s scope. Giving options is a good way to start the discussion.
The solution you propose isn’t always good for the other team. Only the service owner knows their concerns, their issues, and how they handle situations in their team. AI doesn’t always suggest something that fits those issues either, so you still need to clarify with them.
You propose a solution to make your own service run smoothly, but you don’t know their problems yet. So the right approach is to listen to their feedback, understand what would happen if they implemented your proposal, and try to find a solution for each gap.
Sometimes the meeting goes well: they give feedback, you listen, and they listen to you. Other times it doesn’t, and they reject all your proposed solutions without giving any feedback. At that point, you have to remember that your initiative isn’t their big story. They have their own. It’s not their job to solve the problem. It’s yours.
So listen to their concerns, try to see things from their side, and ask politely how they’d handle it and how they want the system to work. Then write another RFC to prepare for the next meeting. If this keeps looping, remember you’re not working alone. Escalate to your manager and ask for help.
Still, aim for a decision both sides agree on. A one-sided decision is a bad move.
A cross-team initiative runs for a long time, and people forget about it if you go quiet. So keep your product manager, your manager, and the other teams involved up to date on progress.
Write each update from your task tracker. Keep it short and use the same format every time:
Send it on a regular schedule (for example, weekly), not only when there’s a problem. The other teams will see the initiative moving, and they’ll know what’s coming for them before it becomes urgent. Bad news that comes early can still be handled. Bad news that comes at the end can’t.
A big initiative takes a lot of energy. A tracker helps you monitor the project, and an RFC gives other teams more clarity, but you still need clarity until everything is clear. You’ll depend on other teams for help, so don’t push them to accept your approach. Instead, get them to agree on the decision made in the meeting. Disagreements can be resolved through RFCs, listening, and escalation.