Platform access level: Org Admins and Managers. Arist enables Diagnostic for your organization before it appears in the sidebar.
After concluding interview collection, open Results to review conclusions, generate recommended actions, and prepare a report.
Important: Updating the analysis removes the current interventions and report. Generate interventions again before creating a report from the updated conclusions.
To gather more input first, follow Collecting Diagnostic Interviews to reopen collection.
1. Review the conclusions and supporting evidence
Open Diagnostic and select your concluded project.
Open Results.
Select a conclusion to review its explanation and supporting evidence.
The detail panel can include:
What we found: An explanation of the conclusion.
Category: Gap, strength, or theme.
Impact: High impact, Medium impact, or Low impact. Not every conclusion shows an impact label.
Raised by: How many people raised the conclusion.
Proof: Supporting sources and quotes. Quotes are attributed by role or, when fewer than three participants share a role, a general label. An English translation appears beneath quotes in another language.
Except for conclusions in the Strength category, impact is shown as Low impact when fewer than three participants raise a conclusion. In a project with more than one role, it also stays Low impact when only one role raises it. This is why small projects can show mostly Low impact conclusions.
Use the campaign filters to focus on a particular group.
Once the project has at least three sources across interviews and uploaded organizational data, the Executive summary card shows the summary. The Results header shows the number of people and sources of organizational data included in the analysis, for example Based on 302 people and 3 documents.
Each conclusion shows the number and percentage of people who raised it, with a likely range for that percentage. Hover over the header count to see the explanation. The 95% range accounts for sampling variation, but not for who chose to take part.
With fewer than three sources, the summary displays Not enough sources yet. This is not an error. Treat the conclusions as hypotheses to validate, then reopen interviews to collect more input. When you conclude collection again, Arist updates the analysis.
Discuss conclusions in the project chat
Select conclusions to include them in the project chat. The selection bar shows the conclusions included in your next chat message. Remove conclusions individually or select Clear.
Use the chat to ask about the evidence or request changes, such as combining conclusions, removing a conclusion, or changing its impact.
If a request would replace existing conclusions, select Confirm to proceed or Cancel to keep them.
Changes to conclusions affect the generated outputs:
Wording only: The evidence, impact, group, and interventions stay unchanged. Generate a new report to include the revised wording.
Other changes: The current interventions and report are removed. Generate interventions again before generating another report.
Download an individual conclusion
Open a conclusion and use its download menu to export it as a PDF, Word, or Markdown file. While a file is being generated, the selected format displays Preparing… and the other formats remain unavailable.
2. Explore conclusions by campaign
Use a campaign filter or ask the project chat about a campaign, such as, “What are the top themes among managers?”
Campaign breakdowns can include participant totals, call statuses, and topics raised by the group. They remain available when names are not collected because the campaign comes from the link or phone number used to join the interview.
Interviews excluded from analysis are also excluded from campaign and conclusion totals.
3. Generate recommended actions
Once the conclusions are ready, select Generate interventions or ask the project chat to create them.
Each intervention recommends an action and identifies the conclusions it addresses. Interventions may be classified as Live only, Process change, or Talent. A Talent recommendation can appear when the project supports a hiring, promotion, or staffing decision and the evidence supports it.
Open the interventions from the project chat and use the download menu to export them as a PDF, Word, or Markdown file. While a file is being generated, the other formats remain unavailable.
4. Generate and review your report
Report generation becomes available after you generate interventions. Until then, the report card displays Unlocks after interventions.
Choose which conclusions to include and how to present them in the Generate report dialog.
Choose the conclusions to include
Select Generate report.
Under Conclusions to include, clear any conclusions you want to omit and star the conclusions the report should emphasize. Include at least two conclusions.
For guidance on choosing what to emphasize, see Best Practices for Running a Diagnostic.
Select the report type
Under What the report should be, choose the format that fits your purpose:
Report type | What it includes |
Full report | Executive summary, methodology, conclusions, evidence, and recommendations |
Conclusions readout | Conclusions and supporting evidence without recommendations |
One-pager | Cover, executive summary, conclusions at a glance, and next steps |
Choose the layout and audience
Choose Document or Slides under How it presents. The default is Slides.
In Who it is written for, describe the intended readers in up to 280 characters. This changes how the conclusions are explained, not the conclusions themselves. Select Generate report when your choices are ready.
Arist can also tailor the audience and tone used across your organization’s reports. Contact your Arist Customer Success contact to discuss the guidance for your organization.
When a project focuses on capabilities, its reports can also include a matrix comparing current and needed capabilities across roles.
Check the generated report
Review the report and its supporting evidence before sharing it.
When available, the cover includes your Purpose, Key decision, and Stakes from the project setup.
In the report and its PDF, a conclusion can show a signal label beside its impact label. The signal describes the strength of supporting evidence; impact describes the consequence.
Strong signal: Strong supporting evidence.
Emerging signal: Moderate or developing supporting evidence.
Early signal: Preliminary supporting evidence.
Not enough data: The conclusion remains a hypothesis that needs more evidence.
After the executive summary, What you asked connects your original questions to the conclusions that answer them. Each answered question includes a short explanation and the supporting conclusion numbers. Questions without supporting evidence read Not enough evidence yet.
This section is available for projects whose plans were generated after the update and only when the report includes every conclusion. Reports for older plans do not gain it automatically. What we didn't expect lists conclusions outside your original questions when there are any.
Quotes from uploaded organizational data are credited to the source document.
The report’s evidence check marks some passages Not confirmed by the evidence. Review them against their sources before relying on them. The label appears only when you view the report in Arist; the exported PDF prints these passages as written, without the label.
Recommendations in the report can show an Owner, Sponsor, Timebox, and Measure. These details are marked Proposed until you confirm them through the project chat. Generate a new report to remove the mark.
A phased action plan can organize recommendations into immediate actions, subsequent work, and longer-term structural changes.
A generated report closes with a Final takeaway, after the recommendations when the report includes them. It draws together two to four themes to explain what the conclusions add up to.
Check the results for each role
A report can show a full page for each role, including its participant count, a conclusion, Why it matters, a supporting quote, and up to three Top capability needs. With your organization’s competency model, the strip reads Top competency needs. These needs reflect what participants raised; they are not proficiency scores.
Roles with fewer than three participants do not receive a page, and a project with only one role has no role section. When a report includes only some conclusions, the role pages omit the needs strip. Ask the project chat to switch between role rows and full pages, then generate the revised report.
Check who contributed
On projects where a campaign was added after launch, the methodology section of a Full report can list campaigns with their interview counts and opening dates. It also identifies campaigns added after launch.
Groups with only one or two interviews are combined under Other groups.
Regenerate or download the report
When regenerating a report, its conclusions, stars, report type, and audience carry over. The layout returns to Slides, so reselect Document when needed.
Select Export report from the report card or Download PDF from the open report. Reports cannot be downloaded as Word or Markdown files.
Version history lists previous reports with the newest first. Downloadable versions include their date, time, and conclusion and intervention counts. Failed versions are marked, and older files may no longer be available.
Use your organization’s competency model
Give the project chat a list of 2 to 20 competencies using your organization’s names and preferred order. When at least two roles each have three or more interviews, the report can include a heat map with one row for each competency, in your order. It keeps every competency in your list, even when no conclusion maps to it.
The heat map notes that its rows follow your organization’s competency model.
For a project about the capabilities people need, the project chat asks for your competency model during setup. If none is saved, it asks again once interventions are ready, when at least two roles each have three or more interviews. You can also provide a competency model for other types of projects.
5. Export interview transcripts
In Results, scroll to Individual interviews.
Select Export all transcripts to download the workbook.
The workbook contains:
An interview summary, including exclusions from analysis, each interview’s Status, and an Outcome reason when one was recorded.
Full transcripts.
Structured answers.
A response summary.
Information about the export.
Participants who take the interview in a browser can submit one written addition through Anything we missed? after their call, while interviews are still open. The addition is included in the analysis and identified as written after the call in transcripts, transcript exports, and generated reports.
In the same table, use Search interviews & quotes to find participant names or quote text.
The export control is unavailable when there are no interviews or another export is running. To download one transcript, open the interview and use its download control after the transcript loads.
Check your team and download access
Your active team must own the Diagnostic to export all transcripts, including when you are an Org Admin. Selecting the organization’s root team does not provide access to another team’s exports.
If transcript downloads are disabled for your organization, the bulk and individual download controls are hidden. Report downloads remain available.
Anonymous exports leave the name, email, and phone fields blank, but spoken answers may still contain identifying information. Review transcripts before sharing them and limit access to the appropriate audience. See New User Onboarding for Running a Diagnostic for your organization’s responsibilities.
6. Use the results to plan what happens next
Revise the interview plan
To change the questions or audiences before collecting more input, reopen the plan. To collect more interviews with the existing plan, follow Collecting Diagnostic Interviews.
The Reopen plan button appears in the Interview plan panel until the first report is generated, and not while conclusions or interventions are generating.
Open Interview plan in Results.
Select Reopen plan and review the confirmation.
Confirm to return the project to Draft with an unapproved plan.
Review and approve the revised plan before launching interviews again. See Setting Up a Diagnostic for the setup and launch steps.
Agree on actions and share an appropriate summary
Review the conclusions, evidence, and recommended actions with relevant stakeholders. Agree on what can begin immediately and what requires more preparation.
Participants do not automatically receive the conclusions or report. Plan how to share an appropriate summary and communicate progress.
See Best Practices for Running a Diagnostic for guidance on agreeing on actions, assigning responsibility, and closing the feedback loop.
Related articles
Note: Need help at any point? Reach out to your Arist Customer Success contact, or email [email protected].























