Working with another agency on a client project can be both an enlightening and a challenging experience.
Here's some of the lessons we've learned from working on cross-agency projects:
Embrace Collaboration - Working on a project with two agencies, multiple disciplines and many team members can be difficult, and accounting for everyone’s different styles can make it even harder. Both agencies want the best for the client, but one team’s idea or suggestion can create more work for the other team and vice versa. Work together to find the best solutions and ensure both teams are comfortable with the amount of work on their plates.
Ask Questions - People don’t know what they don’t know, which is why it’s important to ask questions, even if they seem too abstract or too obvious. Prior to a formal planning meeting, take a pass at determining project requirements or creating user stories and jot down questions as they arise. Even if you think your questions may have been discussed already, ask them. It’s entirely possible the other agency hadn’t discussed or even thought of your question. Having an open, honest and direct discourse facilitates collaboration.
Schedule Check-ins - Pick a regular time to meet. Whether it’s weekly, bi-weekly or daily, set aside a reserved slot for all parties to come together either in person or remotely. Some check-ins may be short and or even seem unnecessary, but some will help sort out questions or roadblocks you’ve encountered since the last time you met. It’s guaranteed time when everyone is together and hearing the same things.
Be Flexible - Sometimes due to timelines, budget or resource constraints, we’re forced to change directions. It can be an adjustment doing things a different way than you’re used to, but embracing new techniques or methods can result in professional growth, both on an individual and a team level.
A successful cross-agency experience requires constant communication and careful planning, but it also requires both parties embrace a spirit of partnership. Great work only gets created when all team members feel safe sharing ideas and offering constructive criticism, so make sure you establish transparency, flexibility and congeniality from the get-go.