Due to my conditions as Aspie, I noticed quite a few times, in working environments, that I have a big communication barrier when it comes to task assignments. Most of the time, I have to work on a project multiple times, as the assignment was meant differently as I understood it. The main problem here is that I'm failing to understand the scope. Or I'm not aware of solutions for problems I just encounter while work is in progress.
A classical (but technical) example that should demonstrate it quite well. I once was designing a visual analyzing tool in Qt. One of my written tasks read like:
Visualizing the main graph in a Qt frame.
So, my project had an additional Qt frame object to be added, as I was new to Qt, I looked up the capabilities of that specific Qt frame object, found that it is able to initialize as an OpenGL frame (what technically, as I know now, works differently as the Qt one). So I realized the whole feature with an OpenGL frame, loaded into the Qt frame. Afterwards my boss wasn't so happy, as he dig up the written assignment and told me, how I can come up with using an OpenGL frame, if we wrote down "in a Qt frame", probably this is the common sense I'm missing, as I can't understand how using an OpenGL frame as feature of the Qt frame, violates "Visualizing the main graph in a Qt frame."
Most of the time, I get the following advice: "But if you aren't sure, just ask!". But I was sure. I wasn't aware that the Qt frame had other means to solve this problem. I just found a way to solve my problem, that respects (supposedly) the requirements. So why should I go on searching for other means to solve it? And if doing so generally, how would I know, when I found the best solution and can stop looking for others?
So how can I make sure having understood a task correct, where I lack the experience to know what ways are available to solve the task and my boss thinks he is clear enough in his wording?