diff --git a/doc/customization/issue_and_merge_request_template.md b/doc/customization/issue_and_merge_request_template.md
index 5804f5193e5855b294d13d3f90da827c66ce009e..8cbd91bb282d6caa48f16af9d2f7ecb823419227 100644
--- a/doc/customization/issue_and_merge_request_template.md
+++ b/doc/customization/issue_and_merge_request_template.md
@@ -5,6 +5,22 @@ EE 6.9. Templates for issues were [introduced][ee-28] in GitLab EE 8.1._
 
 ---
 
+## Overview
+
+Templates provide standardized text for issues and merge requests (MRs).
+
+## Use-cases
+
+- Add a template to be used in every issue for a specific project,
+giving instructions and guidelines, requiring for information specific to that subject.
+For example, if you have a project for tracking new blog posts, you can require the
+title, outlines, author name, author social media information, etc.
+- Following the previous example, you can make a template for every MR submitted
+with a new blog post, requiring information about the post date, frontmatter data,
+images guidelines, link to the related issue, reviewer name, etc.
+
+## Description
+
 We all know that a properly submitted issue is more likely to be addressed in
 a timely manner by the developers of a project.