2 answers
Kefuwe
Student
Virginia Beach, Virginia
6
Questions
Asked
472 views
In your opinion what does 'joining dots' mean in terms of finding client's IT problem ? Please give a full description
Intrested in knowing more about IT support #ITsupportguidence
Login to comment
2 answers
Subodh Prabhu
ASIC Verification Engineer
2
Answers
Toronto, Ontario, Canada
Updated
Subodh’s Answer
Joining dots can mean a lot of things but in terms of a technology problem, I relate it to finding the big picture and addressing it with a solution that would scale in future and address root of the problem.
Lets take an example, a client says this tool that you provided to us is very slow. Now one may just dive into the performance aspect by making the tool faster. The problem would be solved in the moment but it may popup in future or one may realize further down the road that it simply does not scale.
Thinking of big picture would entail realizing why the customer had to face this problem to start with. Were there key use cases that were not tested for performance, did the customer underestimate how often this tool would be used, or was the tool used in ways that were not optimized for performance or is the tool at a fundamental level reaching its performance limits. Looking at the big picture might help you realize not just what an expedient fix would look like but also move in a direction that will progressively attack the core problem and solve it for good.
For ex. let's say that in reality the issue was that tool requires an architectural change to support future performance use cases. A big picture solution would be to rethink platform/architecture choices and refactoring tool it so that it allows performance to scale.
On the other hand , if the issue was because customer did not anticipate ways in which tool would be used, a big picture solution may require more discussions/representation from customer on eliciting this feedback earlier in tool design cycle.
Lets take an example, a client says this tool that you provided to us is very slow. Now one may just dive into the performance aspect by making the tool faster. The problem would be solved in the moment but it may popup in future or one may realize further down the road that it simply does not scale.
Thinking of big picture would entail realizing why the customer had to face this problem to start with. Were there key use cases that were not tested for performance, did the customer underestimate how often this tool would be used, or was the tool used in ways that were not optimized for performance or is the tool at a fundamental level reaching its performance limits. Looking at the big picture might help you realize not just what an expedient fix would look like but also move in a direction that will progressively attack the core problem and solve it for good.
For ex. let's say that in reality the issue was that tool requires an architectural change to support future performance use cases. A big picture solution would be to rethink platform/architecture choices and refactoring tool it so that it allows performance to scale.
On the other hand , if the issue was because customer did not anticipate ways in which tool would be used, a big picture solution may require more discussions/representation from customer on eliciting this feedback earlier in tool design cycle.
Craig Allinson
65
Answers
Updated
Craig’s Answer
Simply being like a detective, looking at the evidence of the problem, what the client did, what steps and tools used, features selected, messages seen from client and in your diagnostics tools and then you can figure out what went wrong and options to take to fix