From 934f58b798245e5e00666d33f7f33817a05be2eb Mon Sep 17 00:00:00 2001 From: Wouter Horlings Date: Wed, 10 Feb 2021 16:38:37 +0100 Subject: [PATCH] Small tweak of evaluation --- content/case_experiment_problem_description.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/case_experiment_problem_description.tex b/content/case_experiment_problem_description.tex index 9a6e2f8..b2d9a40 100644 --- a/content/case_experiment_problem_description.tex +++ b/content/case_experiment_problem_description.tex @@ -19,4 +19,4 @@ However, it was not expected to be this minimal. Perhaps the most serious disadvantage is the absence of stakeholders. Normally, a good problem definition focusses on getting the stakeholders on the same line \autocite{shafaat_exploring_2015}. However, this case study does only have one stakeholder, the author, defeating the purpose getting everyone on the same line. -Creating a more elaborate problem description would not improve the following design process, but it does cost valuable time. +Creating a more elaborate problem description would not improve the evaluation of the design process, but it does cost valuable time.