Understanding and Solving Problems

One of the things I really enjoy doing is figuring out how an end product is put together. For example, how an arcade machine contains buttons, switches, lights, mechanical devices, and whatever else, all inside its shell. Nobody really gets the chance to see inside the various things we use very often and understand how all its parts combine into the final product. In my trade, products often start out as a broad idea, then it turns into a simple block diagram of what functions it needs to do, followed by more block diagrams of how to carry out the functions, until we get to schematics and blueprints which cement the bare minimum of getting these functions working on their own. I try to follow these design principles when I tackle problems at work, so that I don't end up getting off track with my solution or try to solve a problem that's completely unrelated to the situation. First, take note of the obvious: "The machine isn't starting." Cool, now I can move down into what the machine requires to start: "Sensors must be cleared of obstructions, seat belts must be fastened, credit has to be loaded". Now I have a checklist I can quickly run through before I try taking anything apart or attempt the wrong repair. Usually that's how deep I need to go, but occasionally I can find myself surrounded by various components, deep inside a machine trying to solve a very specific problem. It's extremely frustrating at times, but I absolutely enjoy that rush of relief when I solve a problem I spent so much time on. It feels great to be "the guy" your coworkers rely on to solve issues, and I feel like I've chosen the right career path for myself!