Key concepts

The platform revolves around the repeatable cycle Ask → See → Discuss → Verify. Below are the basic words that appear in the documentation and interface. This is not a technical dictionary, but a map of objects the team works with.

Diagnostics

Survey — a study through which the organization collects participant feedback. It contains categories and questions: a participant selects a score, can leave a comment, and the AI facilitator helps clarify a short or emotional response. Learn more in the What is a Survey article.

Measurement — one run of a survey over time. While a measurement is open, the link accepts responses. When it’s closed, it stores the results of that round. The next measurement doesn't erase the previous one; it places a new result alongside it so the team can check for changes.

Score or point — the numerical result of a survey. The platform calculates it at the organization, team, and participant levels, as well as by categories. Comparing it with the previous measurement shows the direction: improved, worsened, or with no noticeable change.

From analysis to action

Topic — an analysis thread that links a question, answers, results, a growth point, and a recommendation. Usually, you don’t need to manage topics manually: they help the platform understand where the same meaning repeats, even when people phrase it differently.

Growth point — a working record of a recurring diagnostic signal. It’s not an accusation or a tracker task, but a focused area of tension that the team can address openly: discuss, add ideas, assign a responsible person, and check the effect in the next measurement. Learn more in the Growth points section.

Idea — a suggestion for a growth point. It can be added by a participant, and some ideas may emerge from answer analysis. Ideas let the team go beyond stating the tension and collect action options. Learn more in the Ideas article.

Recommendation — an action tip from the knowledge base. It’s matched to the growth point’s topic and helps choose a practice to try, discuss, and then verify with a new round of the cycle. Learn more in the Recommendations article.

People and visibility

Organization — a space where surveys, teams, participants, growth points, and privacy settings live. When creating an organization, you choose the anonymity mode: in anonymous mode, participants act under pseudonyms; in open mode, under their real names.

Participant — a person in the organization. They take surveys, see personal results, join growth point discussions, and can suggest ideas. The personal result is separate from management analytics: it helps the participant but is never a control tool.

Team — a group of participants within the organization. Results can be viewed by team if enough responses are gathered for safe aggregate display.

Role determines what actions you can take: who can configure the organization, manage surveys, summarize results, or only participate. A role does not override privacy rules: nobody sees raw answers.

Privacy

Participants’ answers are never displayed as a list of raw remarks. Only anonymized answers and aggregates are surfaced, and only when enough responses exist. This protects honest feedback from being traced back to the author.

The discussion works differently: growth points, ideas, and comments are visible to the team even in an anonymous organization. The platform hides the authorship of the original feedback but doesn’t conceal the collaborative work on solutions. Learn more in the FAQ.