Sunday, February 01, 2009
Enterprise Architecture: Best Practices in Asking Questions...
There is a right and wrong way to ask questions...
When you ask a question, you are asking people to do you a favor. People have no reason to help you. I wonder if I had asked Craig Randall in a nicer way why DFS is designed the way it is or James Robertson why he believes Smalltalk as a great language is on the decline, I would have gotten different responses.
The hardest demographic to ask questions is of the crowd that reads into vs simply reading as you are also required to think about how others may interpret (or get it twisted). This is a skill that enterprise architects need to master in order to truly understand the strategic intent of the business.
Sometimes questions on the surface appear dumb and it is our job to peel back the onion. It may sound something like: what is the difference between X and Y. Sometimes your mind may immediately jump to substituting X for ass and Y for a hole in the ground, but that would rob you and others from truly allowing insight to emerge.
Of course, I don't follow my own advice. When I was starting to learn Java after getting frustrated when coming from an MS-centric MFC point of view, "Microsoft does better than Java" or "Java is bad because it can't do ". Every time I did this, I was flooded with solutions... unless I was right. The same behavior patterns occur in the blogosphere in that if I post something inaccurate, I will get flooded but if I share accurate opinions on blog entries on Indian Outsourcing, SOA, BPM, ECM or whatever other topic, no one ever responds.
My preferred approach can certainly be considered hostile and to beg the question of whether it is necessary, to which I can soundly say No. Of course this would also require acknowledgement that my approach is efficient which should be another goal of enterprise architecture...
| | View blog reactionsWhen you ask a question, you are asking people to do you a favor. People have no reason to help you. I wonder if I had asked Craig Randall in a nicer way why DFS is designed the way it is or James Robertson why he believes Smalltalk as a great language is on the decline, I would have gotten different responses.
The hardest demographic to ask questions is of the crowd that reads into vs simply reading as you are also required to think about how others may interpret (or get it twisted). This is a skill that enterprise architects need to master in order to truly understand the strategic intent of the business.
Sometimes questions on the surface appear dumb and it is our job to peel back the onion. It may sound something like: what is the difference between X and Y. Sometimes your mind may immediately jump to substituting X for ass and Y for a hole in the ground, but that would rob you and others from truly allowing insight to emerge.
Of course, I don't follow my own advice. When I was starting to learn Java after getting frustrated when coming from an MS-centric MFC point of view, "Microsoft does
My preferred approach can certainly be considered hostile and to beg the question of whether it is necessary, to which I can soundly say No. Of course this would also require acknowledgement that my approach is efficient which should be another goal of enterprise architecture...
