What I learned this week … came from a presentation given by Jim Heppelmann and Brian Shepherd of PTC and this week’s PTCUser conference. The presentation gave a view into some of the interesting things that PTC is working on in their solution set, and a peek into their vision for the future of PLM systems. More accurately, what Jim and Brian said the future for their Product Development System as opposed to “PLM,” which is an important differentiation for them.
PLM
One-to-One: Sopheon Hypes up its Customer Needs Management Capabilities
I had a chance to talk with… the team at Sopheon about their recent product enhancement in the customer needs management (CNM) space. Through an OEM agreement with German based idea management vendor, Hype Software, the product portfolio management company has announced Idea Lab, an idea discovery, management, collaboration and analytic offering – areas that were partially addressed by their existing idea management offering. With Sopheon’s existing portfolio management and product planning/roadmapping strengths, these additional capabilities at the very front end of innovation give it a strong offering in the customer needs management space.
What I Learned: Mechatronic Product Development and the Talking Refrigerator
What I learned this week … came from the keynote and press conference at IBM’s Rational Software Conference (RSC2009). IBM is talking about how to help companies develop and manage today’s smarter products. What was surprising to me is that the conference is focused on developing software – not physical products – but that a lot of the conversations focused on manufacturers and product development. Are we finally getting to the point where ALM (application lifecycle management) and PLM (product lifecycle management) can be discussed in the same sentence?
What I learned: The Front End of Innovation is Disconnected from PLM
What I learned this week… came from The Front End of Innovation event in Boston. One thing that stuck in my mind from the event, based on conversations with end users and from presentations, is the lack of connection between the front end of innovation and the rest of the product lifecycle. Customers seem content…
What I Learned: Socially Developed Engineering and Product Documentation?
What I learned this week … came from two recent conversations with manufacturers about their use of social computing to support product innovation, product development, and engineering. I am exploring how companies are using these technologies to improve design and product development collaboration, but also trying to uncover ways they are going beyond collaboration on a specific product or design. Two of my recent conversations touched on the use of wikis and blogs to present information. To be more accurate, these manufacturers are using wikis and blogs to both collect and communicate engineering and product knowledge. Pretty interesting stuff, I think.
What I Learned: Innovation at 27,000 feet on Mount Everest?
What I learned this week . . . came from The Front End of Innovation event in Boston. At day one of the event, Author Jim Collins (Good to Great, Built to Last, Why the Mighty Fall) gave a rousing presentation of findings from his latest research. According to his research, the reason mighty companies fail is not because of lack of innovation. In fact the ones that succeed in the harshest conditions, at “27,000 feet on Mount Everest,” are not necessarily ones who bring a lot of new products to market; it’s the companies that are disciplined in their innovation approach, and have the right people working on the right projects.
- « Previous Page
- 1
- …
- 72
- 73
- 74
- 75
- 76
- 77
- Next Page »