Record details by using “As per our conversation”

This article is based on information from the article Do you send “As Per Our Conversation” emails? Published by SSW Enterprise Software Development a company I used to work for.

Have you ever been to a meeting where various tasks or actions were verbally agreed upon, only to be forgotten about in a few hours? Or have specific details or tasks not been recorded, and there is no written communication about tasks or deliverables that have been agreed upon in the meeting?

This standard encourages people to record official conversations containing tasks or information that could impact a project or topic. The key takeaway is to record the conversation and share it with all attendees and relevant stakeholders so they are kept in the loop and have the opportunity to correct information if required.

Recording an official conversation is a reference point, reducing the risk of misunderstandings or miscommunication. It also adds a layer of professionalism and formality, demonstrating attention to detail and a commitment to clear, consistent communication.

Lastly, this standard helps maintain a documented conversation trail, which can be invaluable for future reference.

Let’s look at a good example of how this standard is applied to a situation. Matt, a web designer, presented a series of web design options over a Teams call. All the stakeholders liked Option B but also wanted a few changes, which were discussed in our meeting. The senior stakeholder in the meeting decided to send an “As per our conversation” email to document the meeting and clearly outline the changes we would like to see in the main design.

✅ Good Examples

Hi Matt,

As per our Team’s conversation with Mary and Luke, I am very happy with the designs you’ve presented to us. Option B is what we like the best. But I would like a few minor changes.

Purple is my favourite colour, so please use light purple for titles. I see Google Maps on many similar websites, so I would like to see this somewhere on the page. The only other negative I see with the design is the lack of a link to the Contact Us page.


Email: Good example of “As per our conversation”

When we look at the email, the author clearly outlines where we had the conversation and the stakeholders involved in it.

Matt now understands what we want to see revised in this design. All relevant stakeholders have been CC’d so they know what changes will be made in the next iteration and can chime in if any recorded detail is inaccurate.

In our next standard, on using numbered lists for tasks, we will examine how to make actionable tasks easy to identify. I look forward to seeing you in the next Flex video.