))
Ep9 - Developing products as a platform - Key Tech POV
Manage episode 325185525 series 3326488
Content provided by A.Mckenzie and Key Tech. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by A.Mckenzie and Key Tech or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
You don’t know where test data will lead, but you can follow it if you plan ahead
A few weeks ago Andy and Jake Cowperthwaite spoke with Steve Schaefer, CEO of CoolTech, about designing your device as a platform. Steve’s company was able to use their temperature management platform to develop two devices, for two distinct applications.
They were able to achieve this by designing enough flexibility into the initial design, which is what Andy and Jake discuss in depth this time around.
Need to know:
- Design the device as a platform with flexibility to facilitate future changes
- Let the end user tell you what the ideal architecture should be
- The more data logging, the better
- Four critical areas to allowroom for improvements: software, electronics,, mechanical modules, and service access
The nitty-gritty:
When thinking about flexibility, there are four core elements to keep in mind.
Flexibility in Software Design
Plan for software upgrades and how you will deliver them. Plan to log as much data as possible, because you never know what data you will need.
Flexibility in Electrical Design
Ensure your power supply can support new features. Include hooks on circuit boards for future sensors and actuators.
Flexibility in Mechanical Design
Focus on modularity, so you can change parts of the hardware without impacting the entire device.
Flexibility in Serviceability
Focus on easy access to internal components, and make disassembly and reassembly as easy as possible.
While you can’t plan for everything, doing preformative testing early, and letting your prospective end users tell you what the ideal product architecture and use case should be. This way, once you get into a trial, the development changes are very technical in nature, rather than being due to the device not being easy to use.
For a great example of how to do this, take a listen to our interview with Steve Schaefer.
HELPFUL LINKS:
42 episodes
Share
