On this week's episode of Inside Outside Innovation, Brian Ardinger, IO Founder, sat down with Katherine Radeka, author of the new book, High Velocity Innovation. They talk about innovation and Agile and specifically how it fits into the hardware space, why everyone needs to be involved in the innovation process, and then most importantly, how companies can better align their innovation efforts with their core business.
Interview Transcript (To read the entire interview transcript, go to http://insideoutside.io.)
Brian Ardinger: Inside Outside Innovation is the podcast that brings you the best and the brightest in the world of startups and innovation. I'm your host, Brian Ardinger, founder of InsideOutside.IO, a provider of research events and consulting services that help innovators and entrepreneurs build better products, launch new ideas, and compete in a world of change and disruption. Each week we'll give you a front row seat to the latest thinking tools, tactics, and trends in collaborative innovation. Let's get started. Welcome to another episode of Inside Outside Innovation. I'm your host Brian Ardinger, and as always, we have another amazing guest. Today we have Katherine Radeka. She is the executive director of the Rapid Learning Cycles Institute and author of the new book High Velocity Innovation: How to get your best ideas to market faster. Welcome to the show, Katherine.
Katherine Radeka: Thank you. Innovation Journey
Brian Ardinger: I'm excited to have you on to talk about your new book. You have a varied background. I want to talk a little bit about the differences between innovating in the real world versus in the software world. Why don't we give our audience a little bit of background about how you got involved in innovation?
Katherine Radeka: I was working for Hewlett Packard and their inkjet printer division, and I made the transition to working with the blended teams that it takes to put together a printer is a printer, is a blend of the hardware and the ink cartridges and the firmware and the software drivers. And so program manager in that space has to be familiar with all of those different disciplines. What I learned very early on was that hardware is hard. That the reason why we were always being told to fix things in software is that once they had released something to the manufacturing environment, it was very, very expensive thing to fix. That became a passion for me, was to figure out how do we deliver hardware more effectively? How do we eliminate the problems that tend to arise in late development? That tend to make hardware programs disappointing. Either late or if they can't be late, they might be down scope, so they're disappointing. Or they might cost too much. To try to figure out how we could make it so that a person that had a great idea for a new physical thing, a new tangible thing, could be just as successful with innovation as a person that has an idea for new software.
To read the entire interview transcript, go to http://insideoutside.io.
Premium
Plus
Comentarios