diff --git a/_posts/2020-07-13-how-to-deliver-a-difficult-message.markdown b/_posts/2020-07-13-how-to-deliver-a-difficult-message.markdown
index 601309278..951ee4e20 100644
--- a/_posts/2020-07-13-how-to-deliver-a-difficult-message.markdown
+++ b/_posts/2020-07-13-how-to-deliver-a-difficult-message.markdown
@@ -11,6 +11,7 @@ tags:
 - stakeholder
 author: fhubin
 layout: default_post
+summary: In this article, I would share some thoughts about how to approach something we all dread and why it is important to be transparent in an appropriately sensitive way.
 ---
 
 In a client-supplier relationship, communication is of paramount importance. And good communication requires transparency. A supplier in charge of a doomed project telling their client that all is going well would not be doing a very good job. Similarly, a client whose budget has been cut telling a supplier that all is well would also not be delivering the right message.
diff --git a/lintPosts.js b/lintPosts.js
index bbf4f2e9b..faeb86597 100644
--- a/lintPosts.js
+++ b/lintPosts.js
@@ -93,7 +93,11 @@ const lintPosts = () => {
         const postDate = new Date(postDateString);
         if (postDate > new Date("2018-03-26")) {
           // Note _prose.yml specifies 130 characters are needed, so if you change this please also change the instructions
-          if (!summary || summary.length < 130) {
+          if(!summary) {
+              console.error("The post " + path + " does not have a summary.")
+              fail = true;
+          }
+          else if (summary.length < 130) {
             console.warn(
               "Post summary length is " + summary.length + ". Recommended minimum length for the summary is 130 characters."
             );