3 Easy Tips to deliver Projects Successfully (not only for Engineers)

3 Easy Tips to deliver Projects Successfully (not only for Engineers)

So what is the secret of delivering successful projects? I worked for multiple clients in multiple sectors, from offshore to packaging, and consumer products to high tech machines. There's 3 main lessons I've learned to make sure the project is completed satisfactory.

And surprisingly, they're not even related to engineering!


1. Communication is everything

You have to treat your client like your boss, because in effect he actually is. Before you venture on the project, have a kickoff meeting with all stakeholders necessary. This means the project leader, your main engineer(s), the client, the client's boss, your boss, and their main engineer(s). Here you take the wheel and go over the deliverables, timeline, milestones and associated budget. This way, everybody knows what they're getting, and when. If it's a project with certain risks involved, you definitely need to tell during the kickoff and highlight how they will or could be solved. 

During the project you need to update your client regularly on the progress, whether good or bad. A simple (online)meeting every week of 30-45 minutes should be sufficient to tell about budget, state of technical progress, work to do, and when the next milestone will be reached. It also provides the opportunity to ask questions from both sides and clear up any confusion.


2. The 'actual' engineering work is only a part of the project

As much as we engineers like to think the work speaks for itself, and everything can be made and designed, usually the project's success isn't solely dependent on it. Even with best technical solutions, most high-tech designs and most exotic material and manufacturing use, a 'perfect' design can still result in an unhappy (and not returning) client. The design can be too expensive to make, to assemble, can't be supplied by the preffered suppliers, is prone to (user) failure or even (dare I say) just ugly.

A myriad of non technical reasons can also result in an unhappy client. Over budget, too late, bad progress communication, unrealistic expectations (from both sides!), unclear objectives or maybe even just a bad working relationship. As an engineer you are also responsible for all these issues, and when you spot something going wrong you need to tell, even if it's not your direct responsibility.


3. Don't assume, ask and confirm

Every company works different and the same at the same time. A new project arises, something needs to be engineered and manufactured, and finally tested and applied. Doesn't matter if that something is a wind turbine, a sorting machine or a cleaning robot, they all go through the same basic steps. However, every company has a different way of work. Some have them nicely documented in onboarding programs, how-to's, faqsheets, etc., most companies don't. So before you open your design software, ask for templates, past example designs, preferred suppliers, preferred materials and thicknesses, how to deal with standard parts like fasteners, etc. etc. 

And you're not done there. During the project you will encounter various moments when things are unclear. Clarify them before continuing! Every minute spent on working on something that turns out to be not according to spec or template, takes 3 minutes to correct: 1 spotting the mistake, 1 finding out how it should've been done and 1 fixing it. Those 3 extra minutes drive up costs, cause delays, and (again) make for unhappy non returning clients.


So in the end, apply above 3 points to your projects, and you will see more projects delivered on time and within budget and more happy and returning clients as a result. Everybody wins.

So very true. Should be standard practice for any engineer.

To view or add a comment, sign in

More articles by Daniel Muusers

Others also viewed

Explore content categories