When you communicate with database users, you should use clear and consistent language that avoids ambiguity, jargon, or acronyms. If you need to use technical terms, explain them in simple words or provide examples. If you need to use acronyms, spell them out the first time you use them. If you need to refer to database objects, such as tables, columns, or indexes, use their full names or aliases. If you need to share code snippets, use the
tag and follow the database syntax and conventions.
###### Provide relevant and accurate information
When you communicate with database users, you should provide relevant and accurate information that answers their questions, solves their problems, or meets their expectations. Do not provide too much or too little information, as this may confuse or frustrate them. Do not provide outdated or incorrect information, as this may cause errors or inconsistencies. Do not provide vague or incomplete information, as this may leave them hanging or guessing. Instead, provide specific, current, and complete information that is verified and validated.
###### Use appropriate channels and tools
When you communicate with database users, you should use appropriate channels and tools that facilitate the exchange of information and feedback. Depending on the situation, you may use email, phone, chat, video call, or face-to-face meeting. You may also use documentation, reports, dashboards, screenshots, or diagrams. You should choose the channel and tool that best suits the purpose, urgency, and complexity of your communication. You should also follow the best practices and etiquette of each channel and tool.
###### Seek confirmation and feedback
When you communicate with database users, you should seek confirmation and feedback that ensure the understanding and satisfaction of both parties. You should ask them to confirm that they received, understood, and applied your information. You should also ask them for feedback on the quality, usefulness, and timeliness of your information. You should listen to their comments, suggestions, or complaints and respond accordingly. You should also thank them for their cooperation and appreciation.
###### Keep a record and follow up
When you communicate with database users, you should keep a record and follow up on your communication. You should document the details, outcomes, and actions of your communication in a log, ticket, or report. You should also follow up with them on the status, progress, or results of your communication. You should update them on any changes, issues, or improvements that affect your communication. You should also keep them informed on any future plans, expectations, or opportunities that relate to your communication.
######Here’s what else to consider
This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?