Table 2 Guidelines for cluster labels

1

Short and elegant; simpler is better.

2

Easier for users to remember.

3

No redundancies (e.g., labeling with “…the implementation process” which is redundant in mentioning implementation because all these are for implementation; and redundant also because implementation is a process).

4

Not too short; enough description to evoke the general purpose/intent/theme underlying the cluster of techniques that are included.

5

Short enough to make it clear to users that they must look at the individual techniques within the cluster/package to know/understand the activities. A fully descriptive title may lead users to believe the label says it all.

6

Begin with a verb.

7

Command structure (definition: A type of sentence that gives advice or instructions or that expresses a request or command.). Not that these are requests/commands but they are certainly words of action-oriented advice.

8

Use layperson terms to the extent possible.