An industrial design studio can help turn an early product idea into a clear, useful physical form. But a polished concept is only one part of bringing a product to market. If your project also needs electronics, prototypes, supplier coordination, or manufacturing preparation, you need to understand whether the studio covers those steps or hands them to others. This guide shows how to assess the difference and choose a team that fits the work ahead.
Talk with Jackson Hedden about your product
What does an industrial design studio do?
An industrial design studio develops the form, function, and physical experience of products. The work may begin with research into users and context, then move through sketches, form studies, models, and a more resolved design. The exact scope differs from one studio to another, so the label alone does not tell you what a team will deliver.
For a consumer product, industrial design decisions can include its overall shape, size, grip, controls, material direction, visual character, and how a person understands its use. These choices are connected. A change to the enclosure may affect internal space. A control that looks simple on a sketch may be hard to reach or assemble. A surface finish can change how a product feels and how it must be made.
That is why it helps to ask what happens after a concept is selected. Some studios focus on early exploration and visual definition. Others can carry the selected direction through detailed design, physical testing, electronic integration, and manufacturing preparation. A client may need either model, but should know where the studio's responsibility ends before work begins.
Jackson Hedden is an industrial design firm that combines product design with mechanical and electrical capabilities, prototyping, and manufacturing support. Explore its product design services to see how those activities can fit within a product program. The practical question is not which label sounds broader. It is whether the proposed scope covers the risks and decisions your specific product still has to resolve.
When is a studio-only scope enough?
A focused studio engagement can be a good fit when your primary need is to explore and define a product's physical direction. That might mean comparing several form concepts, improving the ergonomics of an existing object, or creating a coherent design language across a product family. It can also work when your company already has in-house technical and production resources ready to take over.
Before choosing a limited scope, confirm that the next team can use its outputs. Ask what format and level of detail the studio will provide. Will you receive sketches and renderings, dimensioned models, a CAD package, material recommendations, or a documented rationale for the selected direction? Do not assume that attractive images are equivalent to information another team can build from.
A studio-only scope is less likely to be sufficient if basic product questions remain unanswered. For example, a portable device may need space for a battery, sensors, a charging interface, and a secure enclosure. A wearable product may need to balance comfort, attachment, cleaning, and component placement. If these issues are not considered while the form is being shaped, later changes can force a redesign.
Write down the decisions your internal team can own, too. If you already have a product lead, electronics specialists, a manufacturing partner, and a clear transfer process, a specialist design studio may slot into the plan cleanly. If those roles are not in place, a narrow brief can leave you coordinating several separate providers while trying to make decisions across design, function, and production.
When does a product need a full-service partner?
A broader product development partner is useful when important decisions cross disciplines and no single internal team is coordinating them. The work may include industrial design, mechanical layout, electronic design, prototype builds, supplier conversations, and preparation for production. Integrating these activities can make it easier to test whether the product direction is workable before details become expensive to change.
Consider a connected home device. The enclosure must make room for the electronics, provide access to buttons and charging, and suit the intended environment. The internal layout influences the exterior form. A prototype can reveal whether the controls are understandable and whether the parts fit as expected. Manufacturing input can then inform how the design should be divided into components and assembled.
In that kind of program, the value of one coordinated team is not that every decision becomes simple. It is that design intent and technical constraints can be discussed together, with clear owners and review points. You still need to define who approves choices, who supplies components, and what evidence is needed before moving to the next phase.Check the proposed team's actual scope rather than relying on the phrase “full service.” Ask whether the team will make the product, coordinate with external factories, or prepare files and recommendations for your chosen supplier. These are different responsibilities. Jackson Hedden's manufacturing and sourcing overview and prototyping services can help you understand the kinds of work to discuss. Confirm the exact deliverables for your project directly.
How should you define the project before comparing teams?
Start with the product and its current state, not with a list of studio services. A short project brief should explain who will use the product, what job it should do, what exists today, and what must be learned before a production decision. State which elements are fixed and which are open to change. This gives each prospective partner the same starting point.
Product and user: Describe the intended user, setting, and primary task. Note relevant conditions such as one-handed use, portability, frequent cleaning, or use by people with different levels of dexterity.
Starting materials: Share sketches, existing CAD, prototypes, research, electronics, supplier information, and prior test results. Separate verified facts from assumptions.
Known constraints: Identify target dimensions, interfaces, materials, budget boundaries, timing needs, and existing components when these are established. Mark estimates as estimates rather than promises.
Open questions: List the uncertainties that could change the concept, such as preferred interaction, internal packaging, attachment method, or how a part will be assembled.
Decision owners: Name the roles that will give feedback and approve major choices. Explain how quickly the team can respond and how conflicting input will be resolved.
Next milestone: Define what you need to decide at the end of the engagement. A concept review, a tested prototype, and a supplier-ready design package are different endpoints.
Keep the first brief focused. A long wish list can conceal the question the team needs to answer first. For instance, if you do not know whether customers prefer a handheld or countertop format, detailed surface refinement may be premature. A useful kickoff identifies that uncertainty and makes a plan to test it before committing to a final direction.
If you need help clarifying which decisions belong in the first phase, the product design consultation is one route to discuss project fit. Bring the current brief, known constraints, and the questions your team cannot yet answer.
Which deliverables reveal the real scope?
Deliverables should match the decisions you need to make and the next person who will use the work. Ask a prospective studio to describe each output in plain terms, including its level of detail, file format, review point, and limitations. A list of deliverable names is not enough if no one can explain what the files allow you to do next.
Early exploration
Early work may include research synthesis, sketches, form alternatives, rough mockups, and a record of the criteria used to compare directions. These outputs help a team discuss different possibilities without mistaking an early idea for a finished product. Ask how feedback will be gathered and how the team will narrow options.
Design definition
Later design outputs may include refined geometry, dimensions, interface details, material and finish direction, and visualizations of the selected concept. Ask whether the geometry is intended for discussion, further development, or production preparation. Also ask how changes are tracked so your team can distinguish current files from superseded versions.
Prototype and production preparation
A prototype plan should say what the build is meant to learn. It might test size and grip, component fit, a control interaction, assembly order, or the appearance of a material. No single prototype proves every aspect of a product. Make sure the build method and fidelity suit the question, and agree on what will be recorded after testing.
For manufacturing preparation, clarify whether the package includes part models, drawings, material specifications, assembly information, and supplier-facing communication, or only selected items. Ask what is excluded and who will check the design against the chosen supplier's processes. The manufacturing support page offers another starting point for a scope conversation; your statement of work should define project-specific responsibilities.
How can you assess a studio's work samples?
Look beyond the final render. A finished image can show a product's appearance, but not how a team got there or whether the design was carried into a usable next stage. Ask for a project example with enough context to understand the problem, the decisions made, and the form of the result. If confidential details cannot be shared, a team should still be able to explain its process at an appropriate level.
Look for the starting problem. What user, use context, or product constraint shaped the work?
Trace the decisions. How did the team compare concepts, test assumptions, and choose a direction?
Check the level of resolution. Did the example stop at concept visualization, or proceed to physical prototypes and manufacturing preparation?
Notice the trade-offs. Can the team explain what was simplified or changed and why?
Ask what the client contributed. Understand which capabilities came from the studio and which came from the client's staff or other suppliers.
Relevant examples do not need to look exactly like your product. A consumer accessory, a connected device, and a medical product can have different constraints while sharing useful questions about physical interaction, packaging, and use. What matters is whether the team can describe how its method adapts to your project's risks rather than forcing every brief into the same template.
Jackson Hedden's portfolio includes work such as INMO, Saalt, and the RelieVRx case study. Use portfolio examples as prompts for questions about scope, collaboration, and deliverables. Do not assume that another project's exact process or outcome will apply to yours.
What questions should you ask before signing?
A productive selection conversation should make the working relationship concrete. Ask who will lead the day-to-day work and who will make key decisions. Clarify how often you will review progress, how feedback will be captured, and what happens when new information changes the scope. These details have a direct effect on whether the work can move through decisions without confusion.
What phases do you recommend for this brief, and what decision does each phase support?
Which tasks will your team perform directly, and which require my staff, a supplier, or another specialist?
What will we receive at each milestone, and what level of completeness should we expect?
How will you involve us in user feedback, prototype review, and design selection?
How will revisions, new requirements, and delays in client decisions affect the plan?
Who owns and maintains the working files, and how will the selected supplier receive the information?
What assumptions could make the proposed scope change?
Good answers are specific without pretending that every unknown is already resolved. A team should be able to explain its reasoning, identify dependencies, and distinguish a confirmed commitment from an estimate. If a proposal promises an outcome but does not state what work, inputs, or approvals that outcome depends on, ask for the assumptions in writing.
Look at fit in both directions. A studio may have strong work but not cover the phase you need. A broad partner may offer capabilities that your established internal team already provides. Your goal is to buy the right combination of work, not the largest possible scope. A clear division of responsibility can be more useful than paying two teams to make the same decisions.
How do you make the final choice?
Compare the proposals against a short set of project-specific criteria. A simple written scorecard can help keep the discussion grounded. Rate each team on scope fit, relevant experience, clarity of deliverables, collaboration model, and how well its plan addresses your main uncertainty. Add notes explaining each rating instead of relying on a total score alone.
Then check the gaps. If one proposal covers concept development but not the handoff, decide who will complete that work. If another includes prototype builds, ask what those builds are intended to test and what decisions follow. If electronics or a supplier are involved, identify where their input enters the process. A lower price or broader service list is not a meaningful comparison unless the work and assumptions are comparable.
For example, compare two proposals for a rechargeable handheld product. One may cover user research, form exploration, and a refined appearance model. Another may also include internal layout discussions, an electronic prototype, and a review of how the enclosure could be assembled. Neither scope is automatically better. If your team already owns the electronics and has a supplier ready to review the design, the first scope may cover the missing need. If those decisions are still open, the second proposal may provide more relevant coordination. In either case, make sure the proposal states what is being tested, who supplies the inputs, and what decisions are reserved for your team.
Finally, agree on a first milestone that limits avoidable commitment while producing useful learning. That milestone could be research and concept framing, a set of evaluated forms, or a prototype aimed at a clearly stated question. Decide in advance what evidence will justify continuing, revising, or stopping. This makes the relationship a sequence of informed choices rather than a single leap from idea to finished product.For additional context on the industrial design profession, the Industrial Designers Society of America is a professional association and a useful place to explore the field. Your own selection should still be based on the needs, people, and product decisions in your brief.
When you are ready to outline a product or compare possible scopes, contact Jackson Hedden to discuss your project.
Frequently asked questions
Is an industrial design studio the same as a product development partner?
Not necessarily. An industrial design studio may concentrate on product form, usability, and design definition. A product development partner may also coordinate activities such as electronic design, prototype builds, and manufacturing preparation. Ask each team to list its responsibilities and handoff points rather than relying on its title.
Can a small company work with a studio if it has no internal product team?
Yes, but the company should identify who will make decisions and whether it needs help beyond design exploration. Without internal owners for technical questions, prototypes, and supplier communication, a narrow studio scope may leave important work unassigned. Discuss the complete path to the next milestone before starting.
What should I send a studio before an introductory conversation?
Share a concise description of the product, intended user, current stage, known constraints, and biggest unanswered questions. Include existing sketches, models, or test information if available. Make clear which details are confirmed and which are assumptions so the discussion can focus on what must be learned.
Do I need a prototype before choosing an industrial design studio?
No. A prototype can help explain an idea, but sketches, reference objects, and a clear account of the use case can also provide a strong starting point. If you already have a prototype, describe what it demonstrates and what it does not. The team can then recommend what should be explored or tested next.
How can I tell whether a design is ready for a manufacturer?
Ask the team to define what “ready” means for the product and supplier involved. Confirm which files, dimensions, materials, assembly details, and supplier reviews are included. A design package should have a stated purpose and known limitations; do not assume that a concept model or presentation rendering is sufficient for production.
The right industrial design studio is the one whose scope matches the decisions your product still needs, and whose handoffs leave the next phase clear. Define those needs before comparing proposals, then choose a team that can explain how its work will help you make each decision.
