Every situation demands a communication that fits the scenario. In my case, I ran into a tricky situation of working with couple of users from Japan & Korea. One of our epics in that quarter was to ingest their data into our database. A constraint was that their team was brand new and we initially had some communication problems with them. After my initial engagement with them, I understood that they:
1. Lack a clarity on the data egress patterns from their sources.
2. Unaware of how to provide a customised or static dataset.
3. Unclear on how quick they want this data to be available to all the users.
This made our leaders nervous about delivering this data ingestion. So I took the below initiatives:
1. Approached data architects and proposed my solution to make sure I don't deviate from org's data ingestion standards and practices.
2. Approached our principal engineers to determine if this is a sustainable design and if it could be applied for similar requests in the future. After I got their approval, I created a generic framework so that I can apply this automation for other teams as well.
3. Conducted thorough testing in our QA environments, took the sing-offs from our users and data analysts.
This helped me communicate with different teams, leaders, users, my own teams, approach stake holders and all of these areas require a distinct communication style and patterns. So it was a good learning opportunity for me to sharpen my communication skills.