You can customize the survey in many ways. Some of the options you can modify in the Advanced Editor as part of the free package. You can request our assistance for advanced customization or if you need additional features.

Self service customization options

Title of survey

By default the survey title is “Invitation for assessing ” + the organization name, however this can be modified.

Default

Custom survey title

Advanced Editor

  • To modify the survey title please add the “inviteTitle” field with your custom title on the “mapData” level.

JSON

{
  "mapData": {
    "model": "ROM",
    "language": "en",
    "inviteTitle": "This is a custom title",
    "devLines": {},
    "valueDefs": []
  }
}

Hide map on survey

By default the system shows the map without results right under the survey title and above the questions. When the map is visible surveyees can see the different developmental lines and their consciousness level values we are going to ask them about. In case you want surveyees to not know anything about the map before filling out the survey you can hide it.

Default

Map hidden

Advanced Editor

  • To hide the map on the survey page please add the “inviteShowMap” field with “no” value on the “mapData” level.

JSON

{
  "mapData": {
    "model": "ROM",
    "language": "en",
    "inviteShowMap": "no",
    "devLines": {},
    "valueDefs": []
  }
}

Survey description

You can tell your personal message to the surveyees to help them better understand the context of the survey.

Default

Custom survey description

Advanced Editor

  • To add description to the survey please add the “description” field with the text that you’d like to show on the “mapData” level.
  • It can contain HTML markup as well.

JSON

{
  "mapData": {
    "model": "ROM",
    "language": "en",
    "description": "This is a custom description. It can contain <b>HTML</b> <i>markup</i> as well.",
    "devLines": {},
    "valueDefs": []
  }
}

Surveyee name

By default the platform gives the option for the surveyee to provide his or her name. In case they don’t provide the name the platform records the result with the name “Anonymous”. If you do not want to collect the name you can disable this feature.

Default

Surveyee name entry field hidden

Advanced Editor

  • To hide the surveyee name field please add the “hideParticipantName” field with “yes” value on the “mapData” level.

JSON

{
  "mapData": {
    "model": "ROM",
    "language": "en",
    "hideParticipantName": "yes",
    "devLines": {},
    "valueDefs": []
  }
}

Assessment title

By default the platform calls the survey “Assessment” however you can override that name.

Default

“Assessment” title customised

Advanced Editor

  • To change the word “Assessment” add the “assessmentTitle” field on the “mapData” level and add the text you’d like to show.

JSON

{
  "mapData": {
    "model": "ROM",
    "language": "en",
    "assessmentTitle": "Reflexion",
     "devLines": {},
    "valueDefs": []
  }
}

Custom questions and answers

By default the platform displays the name of the developmental line and the text from the map for each consciousness levels. You can customize that by providing your question and answers.

Default

Questions and answers customised

Advanced Editor

  • To specify the custom question please add the “description” field on the developmental line level.
  • To specify the custom answers please add “oneLineName” fields on the consciousness levels, eg. red, amber, etc.

JSON

"6b2q4AzWkZVkvwgzIbhB": {
    "name": "DECISION\nMAKING",
    "description": "Who and how are decisions made in your organization?",
    "levels": {
        "red": {
            "name": "boss\ndecides",
            "oneLineName": "Our boss makes the decisions"
        },
        "amber": {
            "name": "leaders\n(not transparent)",
            "oneLineName": "Decisions are made by our leaders, however it is not always clear for us why."
        },
        "orange": {
            "name": "goals and\nstrategy",
            "oneLineName": "Decisions are made according to the global strategies and the team goals"
        },
        "green": {
            "name": "values",
            "oneLineName": "Decisions are made in a distributed way taking into consideration the culture and values of the organization."
        },
        "teal": {
            "name": "evolutionary\npurpose",
            "oneLineName": "Decisions are made in a distributed way taking into consideration the evolutionary purpose of the organization."
        }
    }
}

Description per developmental line

You can add additional text above the developmental line question to help the surveyee to understand the context better.

Default

Custom description per developmental line

Advanced Editor

  • To add per developmental line description please add the “beforeDescription” field on the developmental level.
  • It can contain HTML markup as well.

JSON

"6b2q4AzWkZVkvwgzIbhB": {
    "name": "PERSONNEL\nDEVELOPMENT",
    "beforeDescription": "This is a description shown before the question of the \"Personnal development\" developmental line. It can contain <b>HTML</b> <i>markups</i> as well.",
    "levels": {}
    }
}

Question order

By default the platform shows the questions in clockwise order:

  • Quandrant 0 – Right upper quadrant
  • Quandrant 1 – Right lower quadrant
  • Quandrant 2 – Left lower quadrant
  • Quandrant 3 – Left upper quadrant

Within the quadrant between the developmental lines the “quadrantOrder” field specifies the order just like on the map. You can override this with your custom order.

Note: Only those developmental lines will be displayed on the survey form that are directly referenced. Due to this it is possible to hide some developmental lines if that is necessary.

Default

Custom question order

Advanced Editor

  • To set the question order please add the “questionOrder” field on the “mapData” level and set its type to array.
  • Add an entry for each question that you want to show on the survey.
  • The entries in the array must reference a valid developmental line’s unique key. You can find these in the “devLines” section as shown on the image.

Note: You can learn more about “quadrant” and “quadrantOrder” in the … article. TODO

JSON

{
  "mapData": {
    "model": "ROM",
    "language": "en",
    "questionOrder": [
      "YmENKXQXdqdnOvkW9oYX",
      "Cj50bKV8jVbfytK3qVDn",
      "R7htnxFVZY6WtYN4BX8u",
      "wAEiz9imdeTYlvhr9cGq",
      "XT1OpDooLkSvc2qat5gD",
      "wMjRNoYB1ed0eTE7RgL5",
      "6b2q4AzWkZVkvwgzIbhB",
      "pbhjuyn5VmbwkeQdP1YC",
      "0GAiblvhKJKkUDPcfW91",
      "iFXFpn5nfdJVCaeZeV9V",
      "...copy the keys as you need the order to be...",
    ],
    "devLines": {},
    "valueDefs": []
  }
}

Availability of  “inBetween” option in answers

By default the system provides the possibility to choose the “In between” options:

  1. Red
  2. In between – meaning between red and amber
  3. Amber
  4. In between – meaning between amber and orange
  5. Orange
  6. In between – meaning between orange and green
  7. Green
  8. In between – meaning between green and Teal
  9. Teal

However the “In between” option can be disabled and in this case only direct conscious level values can be chosen.

Default

“In between” disabled

Advanced Editor

  • To disable the “inBetween” answer options please add the “inBetween” field with “no” value on the “mapData” level.

JSON

{
  "mapData": {
    "model": "ROM",
    "language": "en",
    "inBetween": "no",
    "devLines": {},
    "valueDefs": []
  }
}

Answer randomization

By default the system shows the answers in order of red to teal. However you can change this to random order.

Note: This feature needs to be used together with answer numbering hiding and in between options disabled otherwise the answers do not make sense.

Default

“In between” disabled and “Randomize” enabled

Advanced Editor

  • To enable the answer randomization feature please add the “randomize” field with “yes” value on the “mapData” level.

JSON

{
  "mapData": {
    "model": "ROM",
    "language": "en",
    "inBetween": "no",
    "randomize": "yes",
    "devLines": {},
    "valueDefs": []
  }
}

Hide answer numbering

By default the system adds numbers in front of the answers according to their values on the map, however this can be disabled.

    Default

    “Answer numbering” hidden, “In between” disabled and “Randomize” enabled

    Advanced Editor

    • To disable the answer numbering feature please add the “inviteShowNumber” field with “no” value on the “mapData” level.

    JSON

    {
      "mapData": {
        "model": "ROM",
        "language": "en",
        "inBetween": "no",
        "randomize": "yes",
    "inviteShowNumbers": "no", "devLines": {}, "valueDefs": [] } }

    Additional questions

    By default only the developmental line questions are included in the survey. However you can add custom questions if needed.

    Note: You must finalize all additional questions before people start filling out the survey, because later editing might result in corrupted data.

    Parameters of additional questions:

    • There are two types of questions:
      • Drop down – Select one from choices
      • Free text
    • You can set whether an additional question is mandatory to fill out or not.
    • The additional questions can be placed either before or after the map questions and their order can be set.

    Example 1: Mandatory dropdown question before the developmental line questions

    Without customization

    Added dropdown question

    Example 2: Optional free text question after the developmental line questions

    Without customization

    Added free text question

    Example 3: Result of the collected information

    The answers to the additional questions can be seen in the Additional Answers section and the dropDown style answers show up in the particpant table as well. 

    Advanced Editor

    • To add additional questions please add the “additionalQuestions” field on the “mapData” level and set its type to object.
    • Add a new entry to “additionalQuestions” object with a 20 characters long unique key for each question that you want to add to the survey. The key consists of alphanumeric characters.
    • Each question must have the following attributes:
      • Question type
        • Add “type” attribute with “dropDown” value for a selector or “text” value for free text answer
      • Question
        • Add “question” attribute with the text of the question that you’d like to ask
      • Placement
        • Add “placement” attribute with “before” value if you want your question to show up before the developmental line questions or with “after” value if you want your question to show up after the developmental line questions.
      • Order
        • Add “order” attribute with a numerical value to set the order of the questions.
        • Before and after orders are handled separately.
      • Mandatory
        • Add “mandatory” attribute with “yes” value if you want to make sure that surveyees fill out that question.
    • The “dropDown” type questions have more required attributes:
      • Options
        • Add “options” attribute and set its type to array
        • Add entries to the array that are going to be the options the surveyee can choose from
      • Group Name
        • Add “groupName” attribute to set the column header in the result table.

    JSON

    {
      "mapData": {
        "model": "ROM",
        "language": "en",
        "additionalQuestions": {
          "jSW5AivCdwDI4QMoGSxL": {
            "type": "dropDown",
            "question": "Which department do you work at?",
            "groupName": "Department",
            "options": [
              "Finance",
              "IT",
              "Management"
            ],
            "placement": "before",
            "order": 0,
            "mandatory": "yes",
          },
          "Fx5ulwVMnQmrRUS2bRLu": {
            "type": "text",
            "question": "Do you have any other comment?",
            "placement": "after",
            "order": 0,
            "mandatory": "no"
          }
        },
        "devLines": {},
        "valueDefs": []
      }
    }
    

    Additional questions – Title and description

    • You can specify a title and description for the before and fter additional questions

    Advanced Editor

    • To add title for the before questions please add “additionalQuestionsBeforeTitle” field on the mapData level and set the text you want to show.
    • To Add description after the title please add “additionalQuestionsBeforeDescription” field on the mapData level and set the you want to show. This can include html elements as well.
    • To add title for the after questions please add “additionalQuestionsAfterTitle” field on the mapData level and set the text you want to show.
    • To Add description after the title please add “additionalQuestionsAfterDescription” field on the mapData level and set the you want to show. This can include html elements as well.

    Conditional questions

    • Additional questions can have conditions that define whether a question is visible or not.

    Example 1: Text field is only visible when “Finance” is selected in drop down  

    Without condition

    With condition

    Advanced Editor

    Conditions consist of

    • Logical expressions
      • “_and” – logical AND of values
      • “_or” – logical OR of values
      • “_not” – negating the value
    • Referencing a question and check its value(s)
      • “_eq” – Form value is equal to a certain value
      • “_in” – Form value is within a list of certain values

    Example 1 – reference1 AND reference2

    "conditions": {
      "_and": {
        "reference1": { "_eq": "referenceValue1" },
        "reference2": { "_eq": "referenceValue2" }
      }
    }

    Example 2 – (reference1 OR reference2) AND reference3

    "conditions": {
      "_and": {
        "_or": {
          "reference1": { "_eq": "referenceValue1" },
          "reference2": { "_eq": "referenceValue2" },
        },
        "reference3": { "_eq": "referenceValue3" }
      }
    }

    Example 3 – reference1 AND (NOT reference2)

    "conditions": {
      "_and": {
        "reference1": { "_eq": "referenceValue1" },
        "_not": {
          "reference2": { "_eq": "referenceValue2" },
        }
      }
    }

    JSON

    {
      "mapData": {
        "model": "ROM",
        "language": "en",
        "additionalQuestions": {
          "Fx5ulwVMnQmrRUS2bRLu": {
            "type": "dropDown",
            "question": "Which department do you work at?",
            "groupName": "Department",
            "options": [
              "Finance",
              "IT",
              "Management"
            ],
            "placement": "before",
            "order": 0,
            "mandatory": "yes",
          },
          "jSW5AivCdwDI4QMoGSxL": {
            "type": "text",
            "question": "Do you have any other comment?",
            "placement": "before",
            "order": 1,
            "mandatory": "no"
            "conditions": {
              "Fx5ulwVMnQmrRUS2bRLu": {
                "_eq": "Finance"
              }
            }
          }
        },
        "devLines": {},
        "valueDefs": []
      }
    }
    

    Customization available from the Teal Compass team

    Custom language on survey

    The platform’s main language is English, however for the seamless survey experience the survey part has been translated to several languages.

    The questions and answers come from the map itself so those are available in as many languages as many community translation we have. The additional text, error messages, buttons, etc… are only suppoorted in the following langues:

    • English
    • German
    • Hungarian
    • Polish
    • Russian
    • Italian
    • Dutch

    If you need the platform to support the survey in a different language please contact us and we can add it for a nominal fee.

    Additional features

    Our main focus is on the development of Teal Compass, the successor of Atlas Platform, however we maintain Atlas Platform as well. In case you need additional features please contact us.