Have you come across those heated email exchanges between customer stakeholders (manager, architect, tech lead, senior engineer etc) and stakeholders from your team including developers, tech lead, managers or architect? If you have worked in IT services company whose primary business is to work on development, support and migration of one or more applications in different technologies, instances like these are more likely to appear.
If you want to act as an equal partner and contribute to maximum in overall growth of your customer’s business, you are surely expected to contribute much more than just do what is asked to be done. In that regard, you may be expected to contribute during design discussions, code review discussions, general planning meeting etc. If you do not contribute, you are bound to have customers rightfully complain on “lack of initiatives”. And, if you contribute but not in polite manner, there is high chances of bad reputation which is not going to serve any purpose. Thus, what to do?
Disagree Politely 🙂
Let’s try and see what are those phrases/statements, scenarios that would have your customer stakeholder get offended and respond sharply:
Lets try and understand some of the ways in which you would want to disagree in a polite manner:
When building a regression model or performing regression analysis to predict a target variable, understanding…
If you've built a "Naive" RAG pipeline, you've probably hit a wall. You've indexed your…
If you're starting with large language models, you must have heard of RAG (Retrieval-Augmented Generation).…
If you've spent any time with Python, you've likely heard the term "Pythonic." It refers…
Large language models (LLMs) have fundamentally transformed our digital landscape, powering everything from chatbots and…
As Large Language Models (LLMs) evolve into autonomous agents, understanding agentic workflow design patterns has…