There are product companies, and then there is Gembah.
Gembah operates a product development marketplace that connects entrepreneurs, e-commerce companies and small-to-midsize businesses with experts at every stage of the product development process. Design plays a key role, helping to bring ideas to life for everything from technology to pet products and fitness equipment.
It only makes sense then that the company places a major emphasis on its own product development process. Cross-team collaboration is a major element of the process, with design, product and engineering working closely to develop a cohesive interpretation of a client’s vision along with a strategy for execution.
Of course, strong relationships between teams don’t just happen. They’re built. Bridget Sandoval, head of product and UX, shared her methods for strengthening ties between Gembah’s design, product and engineering teams.
How do you collaborate with product and engineering on a daily basis? Why is that collaboration necessary?
We utilize collaboration tools like Jira, Git or Slack to track progress, assign tasks and manage workloads. These tools can help streamline communication and keep everyone informed of progress and changes.
Collaborate early and often, explain the ‘why’ behind UX decisions and be open to feedback.”
How do you advance the needs of UX design while also respecting the priorities and considerations of product and engineering?
As a first step, it’s important for all parties to understand each other’s needs and priorities. Product and engineering teams may be focused on functionality and technical requirements, while UX design teams are focused on user needs and experience. By understanding each other’s needs, teams can work toward a shared goal.
What tips would you share with fellow UX design leaders to strengthen their collaborative relationship with product and engineering teams?
The product development process should be iterative, with regular feedback and testing. This allows for UX design to make incremental changes and improvements based on user feedback while also addressing technical considerations. To achieve this, I recommend collaborating early and often, explaining the “why” behind UX decisions and being open to feedback.
