The best way to share DISC reports is to make sharing voluntary, explain the purpose before anyone sees a result, and spend the group time on conversation rather than on reading scores aloud. A report is a starting point for understanding how each person tends to communicate. It works best when people choose what they share and when the team agrees how the results will be used.
This guide walks through how to prepare, who should see what, how to run the conversation, how individuals can share their own report respectfully, and how to keep the results useful after the first meeting.
TL;DR
- Decide who will see which results before anyone takes the assessment, and tell people plainly. Sharing should be encouraged, never forced.
- Send the assessment ahead of time, give at least a week to finish it, and ask a short reflection question so people arrive prepared.
- Use the group session to talk about tendencies and shared language, not to hand out labels.
- Follow up at 30, 60 and 90 days so the insight is applied to real meetings and real conflicts.
- Treat results as a snapshot of current behavior, and revisit them when roles change.
Table of Contents
- Why the way you share matters more than the report itself
- Decide your sharing model before the assessment
- Prepare the team: send it early and ask a reflection question
- Running the session: how to lead a constructive discussion
- When someone wants to share their own report
- Handling disagreements, privacy worries and labels
- Remember what a report can and cannot say
- Make it stick with 30, 60 and 90 day follow-ups
- Our perspective
- Get your team started
- Sharing in nonprofits and volunteer settings
- FAQ
- Sources
Why the way you share matters more than the report itself
A DISC report describes behavioral tendencies: how a person is likely to approach problems, people, pace and rules. On paper that is neutral information. In a team it becomes social information, and people react to it. Someone who sees a colleague's profile may feel understood, or may feel judged, depending on how it arrives.
A Washington Post work-advice column, republished by the Anchorage Daily News, makes the principle plain: participation and sharing of results should be encouraged but voluntary. It also points out that it is disconcerting when results are shared after employees were led to believe they would be private, and that employers should not use these tests to push people into specific slots. The better aim is to get people thinking about how their own edges fit with others.
That gives you the foundation for everything below. Privacy is a promise you make up front, and you keep it.
Decide your sharing model before the assessment
There are three common models. Pick one deliberately and communicate it in writing.
| Model | What people see | Best for |
|---|---|---|
| Private first | Each person sees only their own report, then chooses what to share | New teams, mixed trust levels, anyone worried about being judged |
| Group report | A combined view of the team's styles, without individual detail | Small teams that want a shared picture quickly |
| Open sharing | Everyone sees everyone's summary, by agreement | Close teams that have already built trust and want to go deeper |
For most small businesses and nonprofits, we suggest starting with private first and moving toward a group view once people have read their own reports and had a chance to ask questions. Nobody should discover afterward that a result they thought was private had been passed around.
Write down the answers to four questions and send them with the invitation:
- Who will see individual reports? (Only the participant, the participant and a facilitator, or the whole team?)
- Will a group summary be created, and who will see it?
- Is sharing in the session optional, and how can someone opt out without explanation?
- How will results be used? Be specific, and say what they will not be used for, such as hiring, firing or performance ratings.
Prepare the team: send it early and ask a reflection question
People engage more honestly when they are not rushed. Innovation Training's facilitator toolkit recommends sending the assessment in advance with at least one week to complete it. It also suggests a short pre-work reflection with two questions: what do you hope to gain from learning about yourself and your teammates, and what do you think your strengths and working style are before you see the results?
Those two questions do useful work. The first sets a purpose that belongs to the participant rather than to management. The second turns the report into a comparison: Did this match what I expected? People who guessed first tend to engage with the places where the report surprised them, which is where the learning usually is.
A simple preparation message might include:
- Why you are doing this (better communication, smoother handoffs, fewer misunderstandings)
- How long the assessment takes and the date to finish it
- The privacy answers from the section above
- The two reflection questions, to be answered for themselves and brought to the session
If you want a ready bank of prompts, our guide to team assessment questions offers 40 you can choose from.
Running the session: how to lead a constructive discussion
Whether you are a manager, a coach or an office administrator, your job as facilitator is to keep the room safe and the conversation practical. A 60 to 90 minute session is enough for most small teams. Our guide to DISC team reports for small teams covers how to read a group report quickly and structure that time, and our group debrief guide for facilitators goes further into the flow.
Open with ground rules
Start by repeating the privacy promise out loud. Then offer a few agreements:
- Everyone speaks for themselves. "I tend to..." rather than "You always..."
- No one is required to share their full report.
- No style is better than another. Each brings something the team needs.
- What is said in the room about someone's report stays in the room.
Start with the individual, then move to the team
Give people five or ten minutes to reread their own report quietly and underline two things: one that rings true and one that does not quite fit. Then invite pairs to share only what they choose. Moving from private reflection to pairs to the full group lowers the stakes at each step.
Use questions that point toward behavior
Good debrief questions focus on what people do and need, not who they are:
- When a project is under pressure, what do you need from teammates to do your best work?
- What is one way people sometimes misread you, and what would help?
- Where might our different paces or priorities create friction on a typical week?
- What is one thing a teammate could do that would make handoffs smoother for you?
For coaches who want scripted prompts and timing, our DISC debrief questions page lays out 45 to 90 minute formats. Our piece on DISC team roles can also help the group see how each style contributes, which shifts the tone from comparison to appreciation.
End with one commitment each
Close by asking everyone to name one small change they will try in the next two weeks, such as sending an agenda ahead of meetings, adding a quick check-in on feelings about a decision, or giving more detail up front. Write the commitments down. They become your first follow-up agenda.
When someone wants to share their own report
Not every sharing moment happens in a workshop. A team member may want to hand a colleague or manager their report. A few habits make that go well.
Share a summary, not a stack of pages. Point to the two or three lines that best describe how you like to work. Something like: "I tend to prefer written detail before a meeting, and I do my best thinking when I have time to prepare."
Say what you want from it. "I'm sharing this so we can plan our weekly check-ins in a way that works for both of us" gives the other person a purpose and a way to respond.
Invite their view. Ask whether they recognize themselves, and offer to read theirs if they want to share.
Do not share someone else's report. If you are a manager or administrator with access to results, the owner of the result decides who sees it, unless everyone agreed otherwise beforehand.
Keep it a conversation starter. Sharing a report is more helpful as an opening line than as a final word about who you are.
Handling disagreements, privacy worries and labels
Even well-run sessions raise concerns. Here is how we recommend responding.
"This doesn't sound like me." Take it seriously. Reports describe tendencies, and people adapt to their environment. Ask which parts fit and which do not, and treat the person as the authority on their own experience.
"I don't want to share." Thank them and move on without comment. Voluntary has to mean voluntary, or the whole exercise loses trust. People often join in later after seeing that nothing bad happened to others.
"She's just a high D." When you hear a label used as an excuse or a dismissal, redirect to behavior and need: "What would help in that situation?" The Forbes Coaches Council piece on how DISC is used recommends giving teams shared language rather than shared labels, and that is a good rule to repeat to the group.
Two people's styles clash. Frame it as a difference in what each person needs, not a flaw in either. Ask each to describe, in a sentence, what a good working day with the other looks like.
A manager uses results to place people. Address this early and directly. The report should help people understand how their strengths fit with others, and it should not be used to pin someone into a role.
Remember what a report can and cannot say
A DISC result is a snapshot. According to the same Forbes Coaches Council article, DISC describes tendencies under current conditions rather than a fixed personality, and a profile from three years ago may not describe someone who has since moved from individual contributor to director. Treating a result as permanent freezes people in place, while revisiting it at inflection points keeps it useful.
In practice that means:
- Retake the assessment when someone changes roles, joins a new team or takes on a leadership position.
- Describe results with phrases like "tends to" and "often prefers."
- Never use a report as the sole basis for a decision about a person.
Make it stick with 30, 60 and 90 day follow-ups
The same Forbes article argues that the value lives in the conversations after the report and even after the workshop. It recommends recurring touchpoints rather than a single debrief, with a 30, 60 and 90 day check-in on how someone applied an insight to a real meeting or conflict.
A light structure works well:
- Day 30: Ten minutes at a team meeting. Each person shares one moment where they used what they learned.
- Day 60: Pair up. Each pair talks about one recent misunderstanding and what they would do differently.
- Day 90: Review the commitments made at the session. Which stuck? What should change? Does anyone's role warrant a retake?
Follow-ups also give you a natural place to practice working through friction. If the team wants a practical grounding in handling disagreements, this resource on conflict resolution skills pairs well with the day 60 conversation.
Our perspective
We built DISC Assess for the leaders who do not have a human resources department or a certification budget: small business owners, ministry and nonprofit leaders, coaches, and office managers who simply want their people to understand one another better.
In our experience, report sharing is where the real value is won or lost. A report that stays in an inbox changes very little. A report that is shared with care, discussed with honesty and revisited over time can help a team grow in patience, clarity and appreciation for how differently each person was made.
That is why we pay attention to the practical pieces: instant reports, group management tools and an admin portal that lets a facilitator organize a team without technical skill. We also offer a faith-based version for communities that want to connect behavior with discipleship and growth. Our model integrates temperament and character, and we aim to keep pricing accessible so that a small team can begin without a major investment.
Share generously, but let each person decide how much. That is how trust grows.
Tres
Get your team started
If you are ready to put this into practice, an individual assessment with an instant report is $29, and our Classic DISC Assessment (Non-Faith Version) with Report or Christian DISC® Assessment (Faith Version) with Report is $49 each. For a team, the Group Admin Account is $299 and lets you manage participants and group resources in one place. Facilitators who run sessions regularly can look at the Extended Pro Membership (6 Months) at $894.
You can see every option on the DISC Assess home page, or go straight to the assessments store to choose the version that fits your team. Facilitators can review the membership options.
Sharing in nonprofits and volunteer settings
Nonprofits often have a mix of staff, board members and volunteers, which makes privacy conversations even more important. Volunteers in particular may not expect to be assessed, so make participation clearly optional and explain the benefit to them. Our guides on personality tools for nonprofit staff development and onboarding volunteers with one-page cheat sheets show how to keep the process short and respectful. Boards can begin small with a quick pilot and checklist, and leaders building a longer path can use our nonprofit leadership development assessments guide.
For coaches working one on one, DISC profiles in leadership development coaching explains how to bring a report into a coaching relationship so the client stays in charge of what is shared.
FAQ
Should everyone on the team see each other's DISC reports?
Not by default. Sharing should be encouraged but voluntary, and people should know before they take the assessment who will see their results. Many teams begin with private reports and a combined group view, then share more detail only by agreement.
How long should a team DISC debrief take?
For a small team, 60 to 90 minutes is usually enough to cover individual reflection, pair conversations and group discussion. Send the assessment at least a week ahead so people arrive having already read their results.
What if someone disagrees with their report?
Treat their view as valuable. Reports describe tendencies under current conditions, so ask which parts fit and which do not, and focus on how the person prefers to work. A result is a conversation starter, not a verdict.
Can a manager use DISC results to decide who gets which role?
We advise against it. Results are best used to help people understand how their strengths fit with others, not to force anyone into a slot. Say this to the team in advance so no one worries about how the information will be used.
How often should a team revisit DISC results?
Revisit them at natural inflection points such as new roles, new teammates or leadership changes, and hold brief check-ins at 30, 60 and 90 days after the first debrief to keep the language in use.
Sources
- Innovation Training: Team Assessment Workshop Toolkit for Facilitators
- Anchorage Daily News: Work Advice on employer-required personality tests
- Forbes Coaches Council: how DISC is used and misused