Introduction

Critical to the success of the service is the operational relationship between predefined service objectives, assessment questions mapped to the underlying target model and the actionable recommendations that are generated service, resolving the complex and intertwined relationship between these abstract and practical considerations and producing a solution that can yield actionable recommendations.

Prototype 1.1

Initial Concept: Assessment filtered by Objectives

sts-object-1-1.png

The initial concept for how Objectives would be utilised in relation to the recommendations is that they could be used as a filter to narrow down the number of questions that the assessment stage would ask the user, if the user did not select any objectives by the default the application would present every category and all the assessment questions.

  • Complex and undefined relationship between objectives and recommendations

“All these are important, any school would select them all”

Question format

Multiple question formats were tested with users

questions-free-text.png questions-multiple-choice.png questions-yes-no.png questions-rag.png

Prototype 1.2

Concept Revision 2: Limiting Objective selection before Assessment

“In that case I would select”

Enforcing a limit on the number of objectives either by placing a limit on how many can be selected per category or a limit on how many could be selected across all categories would serve to narrow the focus and require users to think carefully about the objectives they were about to select.

  • Does not resolve the complexity between objectives and recommendations
  • Limited flexibility for schools when working with objectives
  • Narrow focus may enable poor objective decision making

“How do I know what my objectives should be?”

Concept Revision 3: Assessment selection before Objectives

“I would do the assessment first, then define the objectives”

If a user opts to undertake the full Assessment and then use the findings to define what objectives they would set for the school, this would effectively make the selection of objectives redundant as it is likely the recommendations would be relative to multiple objectives.

  • Limited relationship to objectives

Q and A user journey

Text

sts-QandA-1-2.png

Prototype 1.3

Concept Revision 4: Recommendations filtered by Objective

sts-filer-objectives-duo.png

sts-filer-objectives copy.png

In this scenario users would undertake either the full assessment or complete it partially, as soon as a minimum number of questions (termed the “threshold”) have been answered recommendations would be generated and the user would then have the option to filter them by any of the objectives mapped to the underlying framework. The advantages of this approach are:

  • Reduction of user complexity by making the user experience more linear and removing interlocking (objective-assessment-objective) areas of functionality
  • Removal of the need for the school to proactively or retrospectively consider the definition of objectives before the assessment.
  • Availability of usable recommendations as soon as the limited number of mandatory assessment categories have been completed
  • Flexibility that gives schools the option to engage at anytime with objective management further enabling the school the option to concentrate on one specific objective at a time in a manageable non-limited way

Q and A user Journey

text...

sts-QandA-1-3.png

sts-question-1-3.png

Share this page