A young business analyst walked out of the meeting room wearing an expression of guilt and regret, it was evident that the skype meeting with the client did not go well, he sat on his desk and contemplated for a while then packed his laptop took his office bag and barged out.
Seemingly just barging out of the office did not help at all, the thoughts kept coming back, the client’s disappointment was roaring in his ears, questions raised in his stressed mind, questions that threw him in a deep mess of professional existentialism.
What alarmed him the most were the approaching deadlines; this was a mere module of the enterprise application that will be concluded in a month and needless to say a month from now a lot more will be at stake when he will be giving the demo. As he contemplated further a question kept subjecting itself to him, he mumbled to himself what went wrong? All the functionality worked just fine, then why wasn’t the client satisfied? Why couldn’t he convince the client that what the developers had done was the absolute best they could do for the project?
The answers to these questions were beyond his understanding business analysis, later that night as he was surfing through his cupboard struggling to find his phone charger he stumbled upon the solution to the problem that haunted his day, a book on SQL and database development.
Something triggered and Analyst read through the basic and advanced concepts of Database and SQL religiously every day, the concepts came easily to him given to his technical background, he got so comfortable with Database development that he started writing APIs for the development team.
He could feel a sense of confidence in his professional self as the date of the final client meeting came close, finally the day arrived and as soon as the call connected the client in his usual style bombarded the Analyst with questions, unlike the previous time the Analyst remained calm this time and rather than dodging the client he started explaining the architecture of the project and not only the architecture but database flow of the project. He literally stepped into the architect’s shoes perhaps this was what was needed the last time.
The Analyst confidently surfed through the files that contained the most complex of the codes and through his acute knowledge he started making valid arguments as to how the project is in the absolute best condition and how the team has met the client’s requirements on deadline.
As the meeting ended the young analyst walked out the meeting room in the same fashion carrying his new shining laptop with the sigh of relief and a smile on his face, he practically delivered what his project manager expected him to.