I have to admit, I’ve really pined to write this eBook for quite some time. You see, as I’ve written blog posts, whitepapers, eBooks, developed and analyzed surveys and had discussions with users and software providers, there’s always been a connected network between them in my mind. It’s just that the scope has always been very large. Too often it’s been too big for a single eBook, blog post or discussion. So finally, after clearing my schedule, I dedicated over a month of my time to write this, The Engineering Manager’s Survival Guide. In it, there’s a flow from the trends shaping engineering to the initiatives engineering managers can pursue and ultimately to the technologies that enable those efforts. For a sneak peek, here’s a short excerpt. This one comes from the section on the inherently volatile nature of engineering work.
Designing new products often involves the development of new systems, hardware and many other things. Anything that is new in that development effort will likely have issues at some point. The key question is this: when are they caught and subsequently fixed?
Analysis, testing, qualification, certification and other efforts are made to catch any issues as early as possible. However, despite all those efforts, some of those issues will proceed unchecked past design release. Later in the development process, those issues turn into full-blown problems. No matter whether they are caught in sourcing, production or even after delivery or launch, problems return to engineering as fire drills in the form of design rework.
This eBook weighs in at nearly forty pages. To download the full eBook, simply follow this link.
