What we must learn from Steve Jobs is that there is another path besides following the leader, (and that customer focus groups only produce the results that marketing wonks are looking for). The other lesson is to not be enslaved to fear, which is very obvious in the business plan and offerings from quite a few organizations. The third lesson is that a product should not go on sale until the design is completed. His style of creating a new product instead of a copy with a few more features is what made Apple what it is today. There is a whole lot that we can learn from him, but these are the lessons that I see as first.
I'd say that jobs did two things. He was a visionary, as so many have noted. The second thing might not be so obvious. He finished things. There are a lot of companies that produce products with essentially the same feature set. So often though, while the Apple product speaks and truly understands the user's language, the other products are essentially speaking phonetically without the real understanding of how all of those features go together.
From a distance the products may not look different, but up close, personal and in use, that extra time and thought taken makes all the difference in the world.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.