How can you use Quality Assurance communication to persuade others?

Data based factual rational representation helps drive focus on issue than specific ref. Agree to disagree & push for remediation or future mitigation as objective. Audience to relate to a positive future rather than a post-mortem effort on action already taken brings positivity in proposals. Insist on participation, invite ideas to mitigate concerns in future. Accept we evolve and learn from mistakes and drive is for a better today than yesterday. As much as possible explain the situation with eg. to something one can easily relate. Always keep and state the Included reasonable buffer in the projected numbers. Need not be diplomatic but need to be fair. Avoid representations that can lead to contradictory interpretations or understanding.

Additionally, it helps to know your audience as individuals. Knowing and understanding individual communication methods (i.e. do they communicate better through email/written form, or do they prefer face-to-face interactions) can assist you in your QA communications

As a quality manager, we conducted, management review meetings periodically. These meetings typically involve Top management, leaders and managers discussing various aspects of the company's performance, goals, quality policy and objectives, and strategies, which is a crucial part of internal communication and decision-making. And QA data from all departments, not limited to Corrective actions, customer satisfaction, KPIs etc were used.

Communication is the backbone of video game QA. To avoid conflicts, addressing issues with good manners and straightforward communication is crucial. In this fast-paced industry, effective communication is essential to prevent working in isolation and ensure a smooth workflow. When dealing with varying views on quality standards, I strive to find a middle ground through open and clear communication. Sometimes, it becomes necessary to talk to programmers and convey the importance of certain aspects from a QA perspective. It's all about bridging the gap between different perspectives. Simple, direct communication is the cornerstone of successful QA in the ever-evolving world of game development.

In video game QA, I leverage effective communication as a persuasive tool by maintaining transparency. Whether dealing with design changes in the fast-paced environment or advocating for critical bug resolutions, clear and straightforward communication is paramount. During my tenure at EA, I ensured swift communication and issue prioritization in weekly updates using tools like Jira. Adapting my communication style to fit the urgency of issues, from showstoppers demanding immediate attention to minor bugs with a reasonable four-week timeframe, proves effective in conveying QA perspectives. This approach fosters a collaborative and proactive environment, ensuring the team is aligned toward delivering a high-quality gaming experience.

We may not always be providing them with this information that we need. A careful understanding of the program may show that they already have all you need. For some, it's easier for them to provide you with their own information that is tied to their work and the company objectives. As organizations matured, they soon realize that they were forcing data or things that do not correspond with the function, and information that would not be the best measure of actual process activities.

I've found giving examples and showing proof of how something is to be done helps the person to see that what I'm saying or recommending is accurate per our protocol.

I usually receive periodic quality reports and KPI. This is a good way of getting feedback and knowing process owners, and analyzing reports, and collective look at data, and suggesting timely solutions, and Corrective actions and improvements. These process are done before former management reviews meetings.

Here, we have used internal and external audits including certification audits to verify implementation of promises and commitments. This also happened at the management reviews meetings. Where applicable forms, documents and digital means are usually revised to keep track and capture and implement changes to the quality management systems.

When I review a case, if it is a more involved one will do a two week follow up and tell the person if they don't understand what was asked to let me know. This way we can go over it and help them to have a clearer understanding.

The delivery of critique can either make you or break you. Keeping it on the up and up rather than tearing the person down keeps the working relationship positive. Helps their development and in turn helps the company get stronger.

It depends on your audience, right? If you are talking with more technical colleges, try to use simple terms that will ommit any ambiguity. You can demonstrate or showcase your point of view. Be open-minded and mindful when receiving feedback. If talking with less technical peers, think about Feynman's technique. Think about how you can simplify your information and present it to the college. Understand the scope of the information that needs to be presented. Explain how your QA approach can provide benefit and help to them. In the end, it's always great to listen to your colleagues. By being an active listener you are halfway done!