6 Keys to a Successful Product Development Partnership

The rhythm of product development has evolved. Here are six tips for getting what you expect from your product development service provider.

We’ve all been there or had nightmares about being there. It’s time for the unveiling of your product development team’s work. They’re practically glowing. They lift the metaphorical curtain and…it’s not at all what you were expecting.

The rhythm of product development has evolved, and success today relies on active partnerships with clearly defined goals. A partnership is no longer just handing off a set of requirements and picking up the results. Engineers and industrial designers work together in a collaborative partnership that involves an ongoing exchange of ideas coming from both sides.

Here are six tips for maximizing the probability that you will get what you expect from your product development service provider. Whether you’re focused on execution-oriented projects or a research-focused initiative, success for all parties is grounded in making sure everyone is on the same page at the start.

1.) Create Clear Requirements

Seems simple, right? You’d be surprised how rarely a product development partner starts with clarity around expressed (and implied) expectations. Whenever you engage with a product development consulting firm, clearly defined goals are crucial—even when the project is open-ended and research-oriented. Regardless of the type of project, it’s essential to establish parameters for expectations. Both you and your partner must understand those goals at the start to avoid confusion and conflict later.

Too often, I’ve seen product development experts called into meetings with prospective clients where the product development requirements are loosely defined. An experienced product development partner will encourage those clients to complete a brief and inexpensive “discovery” phase to gather baseline requirements. With those requirements in hand, clients are in a better position to seek competitive proposals and can be confident they are getting apples-to-apples responses for even comparison.

Investing upfront in the development of a comprehensive requirements document that defines project interim and exit characteristics is always money well spent. It will greatly reduce the probability of misalignment and dissatisfaction at the end.

2.) Check Qualifications

Product development projects require diverse skills to execute. Understanding which skills are key to your particular product and which you lack can help you choose the right partner. Perhaps your internal core competencies are in backend infrastructure, analytics, and mobile app development. If that’s the case, look for a partner who doesn’t duplicate those skills but has expertise and experience in microprocessors, energy management, RF or wired communications, sensing technology, mechanical design, and hardware industrial design.

Also look for partners who have all of the skills you want in-house. They will be more accountable and better able to execute the vision than a firm that assembles a team from several subcontractors. Those cobbled together teams often have problems “herding cats” because partners possess conflicting cultures and budgetary expectations.

Make sure your product development partner has sufficient bandwidth to handle a project of your scope and complexity. And find out who specifically will be the key team members assigned to your program. Watch out for the bait and switch in which you meet several individuals you expect to be on the team only to later find out the assigned team members are not the people you expected (nor of the expected caliber).

3.) Clarify Deliverables

Nearly as dangerous as sketchy requirements are loosely defined deliverables. Having a common understanding of deliverables is not just a measure to satisfy procurement teams. It is necessary to understand how your partner will demonstrate results.

Lack of agreement on deliverables from the outset of the relationship can be a big cause of dissatisfaction for both buyers and providers. It opens the door to debates over the quality and quantity of the deliverables.

Identifying quality standards for documents also is important to aligning your needs with the mission of your product development partner. This can be as simple as providing sample documents or, if available, formal internal or industrial/commercial standards.

Comments (0)

Please log in or to post comments.
  • Oldest First
  • Newest First
Loading Comments...