.jpg)
Choosing a product design partner often starts with a straightforward question: can this team do the work? Capability matters, but it doesn’t tell you much about what working together will look like once development gets complicated. Evaluating a product design partner also means understanding how the firm works through open questions and how well its process fits your internal team.
Looking beyond the capabilities page can give you a much better sense of what the working relationship may look like once the project gets underway.
Get Clear on Why You Need Outside Support
Before comparing firms, get specific about the gap you’re trying to fill. Your internal engineers may have the right expertise but lack the bandwidth to give a project consistent attention. In other cases, the product may require experience outside the team’s usual scope.
You don’t need every requirement finalized before starting these conversations. In our experience, product development often exposes assumptions about users, use cases, or technical requirements that haven’t received enough attention yet.
Pay attention to how a prospective partner responds to those unknowns. A productive early conversation should help clarify what the team already knows and identify areas that need further investigation before everyone commits to a direction.
Look Past the Finished Products in a Portfolio
A portfolio can show the types of products a firm has worked on, but the finished product doesn’t tell you how the team contributed.
Ask about the work behind relevant projects. Did the firm develop the industrial design, handle mechanical engineering, or support prototype development? How closely did its team work with the client’s engineers?
The answers provide useful context when you’re evaluating experience. A firm doesn’t necessarily need a portfolio filled with products that look like yours. Relevant problem-solving experience may tell you much more about how the team could contribute.
This becomes especially important with complex electromechanical products. Mechanical design decisions can affect electronics packaging, while industrial design needs to stay grounded in the product’s internal architecture. Look for a team that can explain how it coordinates those decisions as the product develops.
Pay Attention to the Questions the Firm Asks
One of the easiest ways to evaluate a potential partner is to listen to the questions coming from the other side of the table.
A firm may ask about the product’s development history or the requirements your team has already identified. Strong early discussions can also surface assumptions that haven’t made their way into a formal specification.
We place a lot of value on developing requirements rather than assuming they arrive fully formed. Questions about users or use cases can expose gaps that affect later engineering decisions. Finding those gaps gives the development team something concrete to investigate.
A proposal still needs enough definition to establish useful boundaries around the work. At the same time, physical product development involves discovery. The firm’s process should have room for new information to influence what happens next.
Questions Worth Asking a Potential Partner
You can learn a lot about a firm’s working style by asking a few direct questions:
- How do you develop scope when some requirements still need investigation?
- What happens when testing changes the direction of the work?
- Who will work directly with our internal team?
- How do you coordinate work that requires outside specialists?
- How do you determine what a prototype needs to answer?
Listen to how the team explains its reasoning. The conversation should give you a clearer picture of how the firm works when a project doesn’t follow the original plan exactly.
Look at How the Team Communicates During Development
Product development brings a steady stream of decisions. Some affect technical performance, while others influence the schedule or work that comes later.
That makes communication worth evaluating before an engagement begins. Ask who will serve as your primary contact and how the firm typically shares progress. It also helps to understand how the team raises issues that could change the scope or budget.
Your internal team shouldn’t have to chase down the reasoning behind a major engineering decision. At the same time, an outside firm shouldn’t require your engineers to manage every detail of its work.
The right balance depends on your organization. What matters is knowing how that balance will work before the project is underway.
Consider How the Firm Fits Your Existing Team
Outside product development support can take different forms. Some internal teams need extra engineering capacity within a process they already manage. Others want a partner to take responsibility for a larger portion of development.
When reviewing product design services, consider how those services will fit the way your team already operates. Find out where responsibilities will sit and how decisions will move between teams. You should come away with a reasonable picture of who handles what without creating unnecessary layers of coordination.
Ownership matters here, too. Your team still brings the product knowledge, business context, and internal priorities that guide development. An outside partner should work with that knowledge rather than create distance between your team and the product.
Understand How the Firm Uses Prototypes
Prototyping can reveal a lot about a product design firm’s development philosophy.
We view prototypes as tools for answering questions. Depending on the stage of development, a prototype might help investigate function or user interaction. Another may help the team evaluate packaging or determine whether a design change produced the intended result.
That’s different from treating an early prototype as evidence that a product is ready for manufacturing.
Manufacturing considerations become more prominent after the primary prototype cycles have validated the core direction. Engineering and DFM work can focus more closely on manufacturability and cost at that point. Later prototypes may help verify that those changes haven’t compromised the product’s core function or usability.
When speaking with a potential partner, ask what it expects to learn from a prototype and how those findings affect the next development decision. The answer can tell you much more than the prototype itself.
Find Out How the Team Handles Unknowns
Physical product development rarely follows a perfectly predictable path. Testing can expose an assumption that doesn’t hold up. A technical decision may create a constraint somewhere else in the product.
That uncertainty doesn’t mean a project lacks direction. It means the development process needs a way to respond when new information changes what the team knows.
When evaluating your product design partner, listen to how the firm talks about those moments. Can the team separate what it knows from what still needs investigation? Does it explain how new findings may affect the work?
A detailed proposal can provide useful structure, but detail alone doesn’t remove uncertainty. The better question is how the team will work with you when development provides an answer nobody had at the beginning.
Look for a Working Relationship That Keeps You Involved
Bringing in outside product development support shouldn’t mean handing over the product and waiting for a finished result. Your team knows the product’s history and understands the business considerations surrounding it. That context remains valuable throughout development.
A productive relationship keeps those perspectives connected to the engineering work without asking your internal team to direct every task.
The right product design partner should make it easier for your team to understand the decisions ahead and participate where its input carries the most value. If you’re considering outside support for a new product or the next stage of an existing one, SGW Designworks can help you talk through the open questions and determine what kind of engineering support makes sense for the work ahead.
