In today's slow economy, with pressure to be first to market and with engineers wearing more hats beyond just “design engineer,” it seems as if that special “x factor” in a product or design is slipping away. Are we as innovative as we can be? Do we need to take a step back and look at where we want to go instead of running as fast as we can and then figure out later where we are? Sometimes, we think we are going somewhere fast and making great progress — until we look down and see we are running on a treadmill, wearing ourselves down and going nowhere.
I've had many pet peeves and struggles as an engineer. You've surely heard that famous bromide, “Time is money.” Well, that may be true, but I always say, “If you don’t take the time, then it will cost you a lot of money.”
Do you ever find yourselves creating multiple versions of a project schedule and spending days on the task, without knowing if the project you're working on will even function?
Are you asked to take cost out of a design before you even start designing?
I think today that engineers are forced to move so fast that they don’t have time to fully test or are forced to skip steps and cut corners. Meanwhile, management wonders why the product is failing, UL is not approving the design, or reworks are forced to be made just a week before production. Schedules end up delayed anyway, so why not consider this on the front end. Initially, the schedule forces the design — and the schedule slips anyway. Because the schedule demands a rushed process, designs end up costing more than they would have if realistic schedules were in place.
What about innovation? Can we be innovative if we have to somehow put more features on a product, but do it for less cost than a previous basic model? I think too much emphasis is placed on cost on the front end rather than creating an innovative product that the customers need, one that solves a problem. Can’t we try to reduce cost later, rather than cutting costs before a design starts?
Engineers used to be people that sit in a lab, creating schematics with a pencil, sniffing solder fumes, blowing up ICs, staying up all hours soldering massive amounts of 30AWG wire to their handmade boards. However, today it seems engineers are sitting at tables comparing supplier costs, negotiating, and trying to get an IC a penny under the competition. Don’t get me wrong, we have to have cost-effective, innovative designs so they can actually hit the market and be affordable to purchase. However, should engineers have to worry about whose op amp is cheaper, or should they focus on design and solving problems?
Should purchasing groups become more technical so they can negotiate better? Should purchasing understand what an engineer needs and take away the cost burden from engineers? In my past experience, I worked with purchasing teams that saw a PCB and knew that it cost a certain dollar amount, but had no idea what the cost number meant or what made it up. How can you negotiate if you don’t know the product and what you are negotiating?
I remember the days where I had to order parts for production before my first engineering samples were complete or we had even started testing. This may not have been a problem if R&D had already proved it out. Many companies don’t have R&D groups. Do R&D groups cut down on development cost?
I would like to hear some opinions on what the priority list in development should be. Out of quality, cost, delivery, development time, and innovation, is there a special balance or formula for the perfect development cycle? Let me know what you think.