Driving UX Success Through Cross-Functional Collaboration
I have extensive experience working collaboratively with cross-functional departments, in an Agile environment, to successfully influence teams and create innovative products. I build trust with stakeholders by delivering quick wins, fostering transparent communication and consistent outcomes that align with their needs. I excel at identifying areas for improvement to team processes and collaboratively enact enhancements. I champion a highly collaborative design process and am trusted by cross-disciplinary teams to talk through both scope and technical challenges and negotiate thoughtful outcomes.

The Challenge:
Design is often brought in midway through a project, when the problem to be solved has been defined, and even the approach to solving the problem has been set. This puts designers in a reactive state, unable to participate in setting project goals and vision, unable to shape the approach. This is a missed opportunity to collaborate more deeply and tap into the specialized UXD/UXR skillset of the design team. The best collaboration between product and design happens with early involvement, shared ownership, structured communication, and mutual respect. These are some best practices for cross-functional teams to work together more effectively, resulting in products that are both user-centric and aligned with business goals.

Collaboration Principles
  1. Use communication channels, such as Slack, to create clear and open lines of communication. Avoid silos. If the product team works in isolation, they might focus too much on business goals at the expense of user needs. If the design team is too isolated, they might create experiences that aren't feasible given technical or business constraints. Breaking down these silos ensures that the product remains user-centered without losing sight of the business objectives.
  2. Use analytics and user feedback to inform design and product decisions, ensuring that the end product is both functional and user-friendly. Decisions should be driven by evidence rather than opinions. Features should be prioritized based on user and business impact. User research offers objective insights that can mediate differences in opinions.
  3. Use tools like Figma, Miro, Google Docs, and Jira, to allow teams to contribute to design and product documentation, track progress, and provide real-time feedback.
  4. Align on MVP, focusing on delivering essential features first, then iterating to add improvements based on user feedback. Leverage the design system to create consistency and reduce the back-and-forth on small design decisions.
  5. Use an iterative approach where designs are tested, feedback is gathered, and improvements are made in collaboration. This allows for continuous feedback and improvements, and ensures that design considerations are integrated into product development cycles. Design also needs to maintain flexibility to iterate on the product as user feedback comes in and business needs evolve.
  6. Clearly define the roles and responsibilities of the team to avoid overlap and ensure that everyone knows who is accountable for what. Create a sense of shared ownership over the product, where all parties feel responsible for the success of the final product.
  7. Encourage skill sharing sessions where designers can learn about product management strategies and vice versa, cultivating a deeper understanding of each other’s roles.
  8. Encourage team members to appreciate the challenges and goals of the other team. This builds respect and a collaborative spirit.
  9. Cultivate a culture where open and respectful communication is the norm, enabling teams to share ideas and concerns without friction. Promote a team mindset where all team members feel valued and empowered to contribute to solutions.

Cross-Functional Collaboration
Like what you see?
How exciting, let's collaborate!