- Typical systems: ERP with production planning, Bills of materials and costing, Quality management
- Common goal: Planning from sales orders to purchasing and production
- Compliance focus: Product quality and safety standards of the markets you sell in
- Measured by: On-time delivery, Yield and scrap, Equipment effectiveness
What manufacturing companies need
- ERP with production planning
- Bills of materials and costing
- Quality management
- Maintenance management
- Supplier portal
Typical ui/ux and product design projects in manufacturing
- Planning from sales orders to purchasing and production
- Batch and lot traceability
- Shop-floor data for real cost and efficiency
What we deliver
- User research and interviews
- Journey maps and information architecture
- Wireframes and clickable prototypes
- Visual design and a design system
- Accessibility review
- Usability testing
- Developer hand-off and design QA
Compliance and data considerations
- Product quality and safety standards of the markets you sell in
- Records for audits and recalls
- Export and customs data on each product
Systems it connects to
- Machines and sensors
- Warehouse and logistics
- Accounting
- Supplier systems
How we measure success
- On-time delivery
- Yield and scrap
- Equipment effectiveness
- Inventory days
Questions to settle before building
- Is planning done from sales orders, forecasts or both?
- What must be traced: batch, lot, serial number or supplier?
- Which machines produce data that is worth capturing?
Common mistakes in manufacturing projects
- Configuring an ERP around the org chart instead of the shop-floor flow
- Costing from estimates because actual times are not captured
- Leaving maintenance and quality outside the system
A sensible first phase
Start small and prove value: research the users and the task; then define the flows. In manufacturing, a good first release is one that delivers this outcome: planning from sales orders to purchasing and production. Later phases add the rest.
How the project runs
- 1Research the users and the task
- 2Define the flows
- 3Prototype and test
- 4Refine and design the visuals
- 5Hand off to developers
- 6Review the live product
What affects the cost
- Number of screens and user types
- Depth of research
- Design system scope
- Platforms
- Testing rounds
Frequently asked questions
Why does manufacturing need a specialist approach to ui/ux and product design?
Because its systems and rules differ: product quality and safety standards of the markets you sell in, and it relies on machines and sensors and warehouse and logistics.
What measures show that ui/ux and product design worked in manufacturing?
On-time delivery, Yield and scrap, Equipment effectiveness, Inventory days. We agree the measures before the work starts.
Do you design before building?
Yes. Testing a prototype is far cheaper than changing finished software.
Are the examples on this page general?
Yes. They describe typical needs of the industry. Your project is scoped after a review, and the laws named here change, so we confirm the current rules for your country before building.
Keep exploring
Last reviewed November 2026. General guidance, not legal, tax or financial advice. Laws, fees and thresholds change; we confirm the current position with the authority or a licensed professional before you act. Fees are quoted in writing after a short review of your case.