From abc6394a753e11e800224ec53ca0f75e9cfa956f Mon Sep 17 00:00:00 2001
From: Dimitrie Hoekstra <dimitrie@gitlab.com>
Date: Thu, 17 Jan 2019 13:45:48 +0000
Subject: Update issue template with user journey, persona label additions, and
 clarification between success metrics and acceptance criteria

---
 .gitlab/issue_templates/Feature proposal.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to '.gitlab')

diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md
index a6f06998ef3..4d4d3bfda15 100644
--- a/.gitlab/issue_templates/Feature proposal.md	
+++ b/.gitlab/issue_templates/Feature proposal.md	
@@ -4,7 +4,7 @@
 
 ### Target audience
 
-<!--- For whom are we doing this? Include either a persona from https://design.gitlab.com/getting-started/personas or define a specific company role. e.a. "Release Manager" or "Security Analyst" -->
+<!--- For whom are we doing this? Include either a persona from https://design.gitlab.com/getting-started/personas or define a specific company role. e.a. "Release Manager" or "Security Analyst". Use the persona labels as well https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A -->
 
 ### Further details
 
@@ -12,11 +12,11 @@
 
 ### Proposal
 
-<!--- How are we going to solve the problem? -->
+<!--- How are we going to solve the problem? Try to include the user journey! -->
 
 ### What does success look like, and how can we measure that?
 
-<!--- If no way to measure success, link to an issue that will implement a way to measure this -->
+<!--- Define both the success metrics and acceptance criteria. Note thet success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this -->
 
 ### Links / references
 
-- 
cgit v1.2.3