Summarize team themes from an anonymous survey

작성자: AILesson9 분 소요테스트::ChatGPT검토일: 2026-08-28

빠른 답변

Aggregate ratings and comments into privacy-safe themes with denominators, variation, counterevidence, and limits. 제공할 내용: Survey data and codebook, Privacy and reporting rules, Analysis and decision needs. 예상 결과: A privacy-checked theme table, rating summary, cautious interpretation, action questions, and disclosure audit.

맥락 추가

텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.

Survey data and codebookPrivacy and reporting rulesAnalysis and decision needs

프롬프트

채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다

Analyze the anonymous team survey using the supplied codebook, privacy rules, and decision needs.

Survey data:
[survey]

Privacy rules:
[privacy]

Analysis needs:
[analysis]

Audit eligibility, response rate, item denominators, scale direction, missingness, duplicates, period comparability, and any weights before analysis. Do not infer who wrote a response or combine details that could re-identify someone. Suppress cuts and themes below the stated thresholds; paraphrase rather than quote when required. Report rating distributions and denominators, not only averages. Code a response into a theme only when text supports it; show theme count, denominator, definition, evidence paraphrase, counterevidence or variation, confidence, and privacy action. Separate respondent perceptions, observed survey patterns, hypotheses, and confirmed organizational facts. Do not diagnose people, infer motives, rank individuals, claim representativeness or causality, or treat silence as satisfaction. Produce a privacy-safe summary, theme table, data limitations, questions for discussion, proportionate action options, and a final disclosure-risk audit.

Playground에서 사용해 보기

기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.

입력에서 결과까지

적용 예시

구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요

실제 입력

Survey data and codebook: Quarterly pulse, open 1–7 August. Eligible 42; 28 complete responses and 2 partial responses. Anonymous response IDs A01–A30. Scale 1 strongly disagree to 5 strongly agree. Q1 ‘I understand this quarter’s priorities’: 28 valid, counts 1:2, 2:5, 3:8, 4:10, 5:3. Q2 ‘I can raise workload concerns safely’: 27 valid, counts 1:4, 2:7, 3:6, 4:8, 5:2. Comments, 18 respondents: 9 independently describe priorities changing after weekly planning; 5 of those ask for one written source. Four say changes are understandable during the migration. Seven describe meeting-free focus blocks being interrupted; three say customer incidents justified interruptions. Five mention helpful peer reviews. Two comments describe a specific rare role and event; one alleges manager retaliation without dates or evidence. No demographic fields. Prior quarter had 34 eligible and 26 complete, but Q2 wording was ‘My manager listens to workload concerns,’ so it is not directly comparable.
Privacy and reporting rules: Leadership report. Do not publish verbatim comments. Minimum reported theme count 4; no subgroup cuts. Do not combine rare role, event, location, tenure, or reporting line. Preserve only aggregated analysis; raw comments stay with People Analytics. Allegations or safety concerns go privately to People Lead, not into a public theme detail. Never try to identify a respondent. Mention count alone does not prove prevalence among nonrespondents.
Analysis and decision needs: Summarize current distributions, response coverage, and comment themes; no employee ranking or causal claims. A theme is material at 5 or more independent comments, but safety issues escalate regardless of count. Leadership must decide whether to create one written priority log and protect focus blocks. Show count among comment respondents and total eligible where useful. Compare response rate with prior quarter, but do not compare Q2 scores because wording changed.

예시 출력

Privacy-safe pulse summary

Coverage: 28/42 eligible employees completed the survey (66.7%), versus 26/34 (76.5%) previously, a decline of 9.8 percentage points. Two partial responses are retained only in item-specific denominators. Nonresponse reasons are unknown, so results describe respondents rather than the whole team.

Ratings: priority understanding has 28 valid responses—7 unfavorable, 8 neutral, 13 favorable; mean 3.25/5. Safe workload voice has 27 valid—11 unfavorable, 6 neutral, 10 favorable; mean 2.89/5. The prior Q2 is not comparable because its subject and wording differ.

Theme	Evidence	Variation or counterevidence	Confidence and privacy action
Priority changes after planning	9/18 comment respondents; 5 request one written source	4 say migration-related change is understandable	high confidence the perception exists; no quotes or subgroup detail
Focus blocks interrupted	7/18	3 describe customer incidents as justified interruptions	moderate; distinguish avoidable and incident-driven cases before action
Peer review helps	5/18	no counterexample supplied	moderate; do not infer effect size
Rare-role event	suppressed, count 2	not reportable	route no identifying detail

The retaliation allegation is not expanded in this report because detail could increase disclosure risk and the claim is unverified. People Analytics should route it privately to the People Lead under the existing escalation rule; this is not a finding about a manager.

Decision questions: Would a dated, owner-controlled priority log reduce ambiguity without slowing urgent migration changes? What qualifies as an interruption to a focus block, and which customer incidents override it? How will leadership test whether a change helps—such as fewer priority-clarification requests next pulse?

Proportionate options: pilot one priority log and define its update owner; classify focus-block interruptions for four weeks before changing policy; preserve peer review while measuring workload. Final disclosure audit: no quotes, subgroups, rare-role details, identities, or combined attributes; counts meet the threshold except explicitly suppressed material.

효과가 있는 이유

1
Minimum counts and disclosure review protect anonymity that thematic detail can otherwise erode
2
Denominators and counterevidence keep a memorable comment from becoming a team-wide conclusion

결과 확인

Could any theme, subgroup, paraphrase, or detail combination reveal a respondent?
Does every metric and theme show its eligible denominator, missingness, and evidence threshold?
Are perceptions and hypotheses kept separate from confirmed causes or organizational facts?

안심하고 사용하세요

자주 묻는 질문

이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변

What should I prepare before using “Summarize team themes from an anonymous survey”?

For “Summarize team themes from an anonymous survey,” prepare Survey data and codebook, Privacy and reporting rules, and Analysis and decision needs. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Summarize team themes from an anonymous survey” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A privacy-checked theme table, rating summary, cautious interpretation, action questions, and disclosure audit—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Summarize team themes from an anonymous survey”?

The published test record for “Summarize team themes from an anonymous survey” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

더 많은 탐색 방법