"Communication is the key to success." At some stage in our lives we were taught that there is no such thing as a dumb question. If its one thing that I've learned in my plight to seek understanding on given topics it's that repeating the same sentence over and over again will not lead to a clearer understanding of an agenda item. In order to grasp a firmer understanding of a common goal, the end product should be clearly communicated in order to be visualized. Some may agree that when working backwards from the projected outcome it could be the more effective method of moving forward. When working with others this may require a tiny bit of patience but when that wears thin it can be a disaster.
Truthfully, picking apart a reason why someone may be seeking clarification is unwarranted and unnecessary, especially in the professional realm. If an individual is reaching out to say, I don't understand or is "x" what you are looking for then a positive way to handle it is to try to understand what the other person is looking to accomplish rather than a dismissal. Admittedly there are those cases where there is freedom to figure out a project on your own and allow for great creativity to get the job done, however in the instance where there is a specific task with a specific end goal, let's be very clear. This is where the trouble stems in consistently repeating the same thing over again- it is a waste of time. Chances are, if the first communication wasn't successful --- saying it again isn't going to do the trick. When I've been put into this position, I try to come up with different ways to communicate the projected outcome or potential obstacles and I suppose I am guilty of wanting the same. I have to say that I admire those who work in technical positions where even though each project is unique, the result is the same...such as creating a website. The challenge stems from what the website is to offer in terms of graphics and backgrounds, design layouts and formats--the languages used to create the script, whether it should be run with Java or Flash, is it W3C compliant --does it fit the format of web 2.0? Overall, the end product is to create a website--and if you meet the needs of your client then all is well at the end of the day. This is not to say that this work is any less difficult because it seems like it can be pretty tricky but ultimately the project was given because the creator is capable of achieving this end goal. I find that its the small projects that are tedious and time consuming and the catalyst of all frustrations, similar to a paper-cut which hurts more than a scrape as an example. Granted, if the person you are communicating with is your boss, then requesting advice on how to do your job is probably not a good idea --but when working with a colleague I'd say, that's open room for a discussion because working as a team effectively means working together. This also holds true to friendships, relationships and family communications because your team is the circle you keep in your life.
"Communication is the key to success." At some stage in our lives we were taught that there is no such thing as a dumb question. If its one thing that I've learned in my plight to seek understanding on given topics it's that repeating the same sentence over and over again will not lead to a clearer understanding of an agenda item. In order to grasp a firmer understanding of a common goal, the end product should be clearly communicated in order to be visualized. Some may agree that when working backwards from the projected outcome it could be the more effective method of moving forward. When working with others this may require a tiny bit of patience but when that wears thin it can be a disaster. 
Truthfully, picking apart a reason why someone may be seeking clarification is unwarranted and unnecessary, especially in the professional realm. If an individual is reaching out to say, I don't understand or is "x" what you are looking for then a positive way to handle it is to try to understand what the other person is looking to accomplish rather than a dismissal. Admittedly there are those cases where there is freedom to figure out a project on your own and allow for great creativity to get the job done, however in the instance where there is a specific task with a specific end goal, let's be very clear. This is where the trouble stems in consistently repeating the same thing over again- it is a waste of time. Chances are, if the first communication wasn't successful --- saying it again isn't going to do the trick. When I've been put into this position, I try to come up with different ways to communicate the projected outcome or potential obstacles and I suppose I am guilty of wanting the same. I have to say that I admire those who work in technical positions where even though each project is unique, the result is the same...such as creating a website. The challenge stems from what the website is to offer in terms of graphics and backgrounds, design layouts and formats--the languages used to create the script, whether it should be run with Java or Flash, is it W3C compliant --does it fit the format of web 2.0? Overall, the end product is to create a website--and if you meet the needs of your client then all is well at the end of the day. This is not to say that this work is any less difficult because it seems like it can be pretty tricky but ultimately the project was given because the creator is capable of achieving this end goal. I find that its the small projects that are tedious and time consuming and the catalyst of all frustrations, similar to a paper-cut which hurts more than a scrape as an example. Granted, if the person you are communicating with is your boss, then requesting advice on how to do your job is probably not a good idea --but when working with a colleague I'd say, that's open room for a discussion because working as a team effectively means working together. This also holds true to friendships, relationships and family communications because your team is the circle you keep in your life.
No comments:
Post a Comment