Problems

thought 47

As an engineer, you learn to solve problems. Depending on the type of engineer you are, you’ll be given the task of taking a problem your client has and coming up with a solution.

Sometimes we can get fooled into thinking that our job as problem solvers is to just create the solution someone else has thought up. After all, they are the creative one right?

In technology, the engineer usually has a larger breadth and depth of knowledge that he can call on than the client. It’s his/her responsibility to take charge and root out what the client really needs not what he/she thinks they want.

Many programmers have gotten into trouble by not vetting their client long enough. If you build something for a client and it isn’t what they really needed, they will most likely come back to you, pointing fingers.

I recently started conversations with a client that is in the same boat. They came to me with a problem and what they think the solution is. Many times the client is right in identifying the problem but needs help with the type of technology available to solve their problem.

In this case, we realized that the solution was to explore more, even though they have been currently developing our their prototype. I’ve found that if your client is willing to explore further with you, they are typically someone that will be ok to work with, but this isn’t the case every time.

So remember, if you are presented with a problem and a solution paired together, take a step back and ask yourself “is this really the right solution to this problem?”

stay tuned.
Sterling