
GITNUXSOFTWARE ADVICE
Mental Health PsychologyTop 10 Best Empathy Software of 2026
Top 10 empathy software ranked for team use cases, with feature notes and tradeoffs, including Kairos, Dovetail, and Miro.
How we ranked these tools
Gitnux editors write the brief first: the topic, the inclusion rules, and the frame for what belongs.
Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Kairos is the best fit when contact centers need reviewed emotion insights across calls and chats, whereas Miro works better for teams running collaborative workshops that turn empathy maps and customer journeys into living artifacts.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Kairos
Consent-aware emotion analysis outputs structured review artifacts for analyst interpretation, not just dashboards.
Best for: Fits when contact centers need reviewed emotion insights across calls and chats.
Dovetail
Editor pickEvidence-linked insight cards that keep themes tied to source notes across collaborative projects.
Best for: Fits when research teams need traceable empathy insights across recurring studies and stakeholder review.
Miro
Editor pickFrames and board organization let teams nest empathy maps, evidence, and action notes in one navigable workspace.
Best for: Fits when teams need collaborative empathy artifacts that evolve through workshops and iterative reviews.
Comparison Table
Kairos
API-firstEmotion AI APIs for detecting facial expressions and inferring affective states.
Consent-aware emotion analysis outputs structured review artifacts for analyst interpretation, not just dashboards.
Kairos focuses on emotion and affect extraction from real interaction artifacts, including speech inputs that require transcription and alignment before analysis. Outputs are structured for downstream use in tagging, thematic review, and conversation-level reporting that supports qualitative research and journey mapping inputs. The API surface supports event-driven ingestion, letting teams push conversations into analysis pipelines and pull back structured results for orchestration.
A key tradeoff is that high-quality emotion outcomes depend on clean inputs and consistent labeling so teams can compare signals across channels and time. Kairos fits best when empathy analysis needs to be reviewed by analysts rather than used as an automated decision trigger, such as routing escalations after agent-call emotion shifts are detected.
- +Emotion scoring works across text and speech workflows
- +API-based ingestion and result retrieval supports automation
- +Human-in-the-loop review keeps emotional signals interpretable
- +Consent-aware handling supports sensitive customer interaction data
- –Best results require consistent data prep and labeling
- –Emotion outputs need analyst review to avoid over-interpretation
- –Some integrations require engineering effort for stable pipelines
- –Conversation mapping workflows can take time to tune for each channel
Customer experience analysts
Tag emotion spikes across support calls
Fewer manual labeling hours
Contact center ops teams
Route cases after emotional escalation
More consistent escalation decisions
Show 2 more scenarios
Product research teams
Feed empathy insights into journey maps
Sharper empathy-backed journey revisions
Structured outcomes are mapped back to key journey moments for qualitative synthesis.
Data and automation engineers
Integrate emotion analysis with internal systems
Higher throughput across workflows
API ingestion and result pulls support event-driven enrichment of CRM and ticket metadata.
Best for: Fits when contact centers need reviewed emotion insights across calls and chats.
Dovetail
API-firstDovetail organizes user research, customer feedback, insights, and evidence for empathy-led product decisions.
Evidence-linked insight cards that keep themes tied to source notes across collaborative projects.
Dovetail is a strong fit for research teams that need traceability from raw notes to themes, because findings stay anchored to the source items inside a shared workspace. It supports tagging, theme building, and collaborative synthesis so cross-functional partners can review the rationale without hunting across separate docs. Integration depth matters because Dovetail connects research artifacts with other tools used for documentation and feedback collection. The standout workflow is converting conversation and interview notes into reusable evidence and structured insights for ongoing empathy work.
A tradeoff is that Dovetail works best when research teams adopt its project structure and keep their tagging conventions consistent, because inconsistent taxonomy creates duplicated or fragmented themes. It fits situations where multiple stakeholders run recurring research cycles and need human-in-the-loop review before insights inform product decisions. It is less efficient for one-off analyses that never require ongoing repository hygiene or evidence linking.
- +Evidence-linked themes connect synthesis back to specific interview notes
- +Tags and collaborative workspaces reduce context switching across studies
- +API and integrations support automation of recurring research workflows
- +Workspace permissions support controlled collaboration across functions
- –Theme quality depends on consistent tagging conventions across the team
- –Bulk reorganization can be time-consuming when taxonomy changes late
- –Advanced automation requires engineering effort for reliable orchestration
Product research teams
Synthesize interviews into reusable empathy themes
Faster alignment on key needs
Customer insights managers
Maintain continuity across research cycles
Less rework across cycles
Show 2 more scenarios
UX and content strategists
Build journey narratives from findings
Stronger narrative with evidence
Anchor journey mapping inputs to specific excerpts and synthesis outputs shared with partners.
Data and platform teams
Automate tagging and reporting
Consistent reporting cadence
Use API and integrations to pipeline research artifacts into standardized tagging and insight exports.
Best for: Fits when research teams need traceable empathy insights across recurring studies and stakeholder review.
Miro
enterpriseMiro provides collaborative whiteboards with templates for empathy maps, personas, and customer journeys.
Frames and board organization let teams nest empathy maps, evidence, and action notes in one navigable workspace.
Miro provides practical collaboration mechanics for qualitative empathy work, including sticky-note style collection, digital whiteboarding for customer journey and empathy maps, and annotation via comments on parts of the canvas. Template libraries and reusable frame layouts help keep artifacts consistent across workshops and iterative follow-ups. The board model supports linking supporting assets such as images, diagrams, and documents so findings stay clustered with the map or persona.
A tradeoff appears when empathy workflows require deep automation for text or emotion inference inside the board, since Miro focuses on collaboration rather than built-in emotion recognition or conversational analytics. Miro fits best for human-in-the-loop synthesis where interview notes, tagging decisions, and action ownership are reviewed together during workshops and refinement cycles.
- +Real-time board collaboration keeps empathy mapping and workshop notes co-located
- +Frames and templates standardize journey map and persona artifact structure
- +Comment threads and region-level context reduce lost decisions during review
- +Permissions and board sharing support governance for shared empathy workspaces
- –Limited native analysis for empathy signals from text or audio
- –Long-running boards can become hard to navigate without consistent structure
- –Automation depends on integrations rather than deep in-board workflow engines
- –Template reuse still requires manual upkeep for cross-team standardization
Product and UX teams
Run empathy mapping workshops for design decisions
Shared insights drive next design steps
Customer research teams
Synthesize interview findings into journey maps
Consistent themes across sessions
Show 1 more scenario
Customer success operations
Coordinate cross-team journey and action ownership
Clear accountability for improvements
Shared boards keep action items, stakeholder perspectives, and supporting materials in one workspace.
Best for: Fits when teams need collaborative empathy artifacts that evolve through workshops and iterative reviews.
Mural
enterpriseVisual collaboration workspace for empathy maps and design thinking.
Empathy mapping and journey mapping templates that tie qualitative notes directly to personas and touchpoints within shared boards.
Mural pairs a collaborative visual workspace with empathy-mapping and journey-mapping templates that fit workshops and cross-functional alignment. The core workflow centers on structured boards, sticky-note capture, and facilitation flows that keep qualitative findings tied to specific touchpoints and personas.
- +Empathy mapping and journey mapping templates reduce setup time for workshops
- +Structured board elements keep notes aligned to personas and touchpoints
- +SSO and workspace administration support controlled access for stakeholder-heavy teams
- +App integrations and embed options widen how artifacts appear in other tools
- –Empathy AI or sentiment automation is not a native center of gravity
- –Governance and scale require disciplined board labeling and template usage
- –Automation for tagging and taxonomy management is limited without external workflows
- –Large maps can slow interaction when many collaborators add content
Best for: Fits when teams need workshop-grade empathy and journey artifacts that stay editable for ongoing planning.
UserTesting
enterpriseUserTesting provides recorded human feedback and research workflows for understanding customer behavior.
Study panels with scripted tasks produce comparable session data that teams can tag and synthesize quickly.
UserTesting recruits real people through its study panels and turns their sessions into structured feedback for product decisions. The core workflow pairs scripted tasks with session recordings, transcripts, and tagging so teams can find themes across usability and concept tests.
- +Panel-sourced sessions speed study turnaround without recruiting pipelines
- +Task scripts produce comparable sessions for usability and concept testing
- +Transcripts and tagging make qualitative synthesis faster than manual review
- +Exports support sharing research artifacts beyond the research team
- –More automation is needed for high-volume studies than templated tagging offers
- –Engineering-oriented API automation for downstream systems is limited
Best for: Fits when teams need recurring, moderated-style usability and concept feedback with fast participant sourcing.
Dscout
vertical specialistDscout supports qualitative research through mobile missions, video diaries, and participant feedback.
Timed diary-style prompts that generate reviewable, evidence-backed participant clips across days.
Dscout runs remote research studies that combine moderated interview sessions with tasks captured on participants’ devices. Its core workflow centers on recruiting through pre-built panels, study launch and scheduling, and collecting structured responses alongside video and screen-based evidence.
- +Study builder supports timed prompts for multi-day participant check-ins
- +Video and screen artifacts are organized per participant and per task
- +Theming and tagging make cross-interview synthesis faster than manual notes
- +Panel-based recruiting reduces setup time for recurring research studies
- –Qualitative coding depth is limited compared with dedicated research ops systems
- –Requires research workflow discipline to keep tags and themes consistent
- –API access is not a primary integration path for custom research tooling
- –Governance controls for sensitive data are less granular than enterprise platforms
Best for: Fits when product teams need remote, evidence-based empathy research with light coding and fast synthesis.
Hume AI
API-firstAPI platform for empathic voice AI that detects vocal intonation and prosody in real time.
Project-based workflow configuration that turns emotion model outputs into auditable, review-gated tagging for qualitative and CX analyses.
Hume AI focuses on emotion AI pipelines for text, voice, and multimodal inputs, with model outputs designed for downstream analysis and human review. The product routes emotion signals into configurable tagging and workflow steps that support qualitative research themes and conversation analysis. Admin controls center on project isolation, access management, and review workflows that keep human-in-the-loop in the loop for sensitive judgments.
- +Emotion detection across text and speech for consistent empathy signals
- +Human-in-the-loop review steps for governance of sensitive interpretations
- +Configurable tagging and workflow hooks for research and CX pipelines
- +API-first integration for building custom conversation analytics
- –Higher setup effort than generic sentiment tagging tools
- –Emotion outputs need careful calibration for low-resource languages
Best for: Fits when teams need emotion signals from calls or transcripts and want automated tagging with human review control.
Affectiva
enterpriseComputer-vision emotion and affect analytics for empathy-adjacent customer and research workflows.
Real-time or batch facial affect inference from video, producing structured emotion signals for review and tagging workflows.
Affectiva applies emotion recognition and affective computing to build empathy-oriented analytics from real user behavior. The core capability centers on analyzing facial expressions in video streams to infer affective states for qualitative research and customer feedback analysis.
- +Facial expression inference turns interview and test footage into structured affect signals
- +Affective outputs support clustering for thematic review and emotion-driven tagging
- +Human-in-the-loop review fits qualitative research workflows that need traceability
- +Extensible inference outputs support downstream analytics and custom reporting
- –Video ingestion and labeling workflows add overhead versus text-only emotion tools
- –Governance for biometric-derived signals requires tight consent and data handling discipline
- –Calibration and context handling can limit accuracy across lighting and demographics
- –Automation surface depends on integration choices rather than built-in journey mapping
Best for: Fits when teams need affective signals from video studies to guide customer feedback analysis and research coding.
Symbl.ai
API-firstConversation intelligence API providing real-time emotion and intent detection in conversations.
Webhook event delivery paired with an analytics API so conversation insights can trigger human-in-the-loop review workflows.
Symbl.ai turns calls, meetings, and messages into structured conversational analytics with speakers, topics, and insights. It supports both speech-to-text and text analytics so teams can apply the same tagging and extraction workflow across voice and chat.
- +API-driven extraction of speaker turns, topics, and insights
- +Webhooks deliver near-real-time conversation events to downstream systems
- +Consistent analytics for text and speech inputs
- +Extensible tagging and export for qualitative review workflows
- –Higher setup effort to align consent, redaction, and retention across pipelines
- –Empathy mapping outputs still require manual interpretation for themes
Best for: Fits when contact centers or research teams need API automation for conversation tagging and insight exports.
Gong
enterpriseRevenue intelligence platform with conversation sentiment and emotion analysis for sales calls.
Clip-level review with workflow routing ties AI-tagged moments to structured coaching actions inside Gong.
Gong brings empathy-adjacent analytics into customer conversations by combining transcript capture with conversational tagging and review workflows. Teams use its AI to surface themes and moments in calls and meetings, then route clips into human-in-the-loop review for coaching and qualitative analysis. The value for empathy work comes from how Gong links tags to specific conversation segments, then supports follow-up review cycles with configurable permissions and audit visibility across workspaces.
- +Conversation-level tagging links insights to exact moments in transcripts
- +Review workflows support human-in-the-loop coaching and thematic validation
- +Admin controls enable workspace permissions and governance for reviewers
- +API access supports automation and exporting analysis outputs
- –Empathy mapping requires extra setup to translate conversation tags into personas
- –Automation and governance depth demand active configuration and taxonomy upkeep
- –Speech-to-text quality depends on microphone setup and call recording conditions
- –High-volume review can increase operational overhead for reviewers
Best for: Fits when call and meeting analytics must feed human-reviewed empathy and coaching loops for customer-facing teams.
Conclusion
After evaluating 10 empathy software, Kairos stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right Empathy Software
Empathy software helps teams convert qualitative signals into reviewable artifacts that stakeholders can interpret and act on. This guide compares Kairos, Dovetail, Miro, and Mural for empathy mapping and evidence-linked analysis workflows, then adds UserTesting, Dscout, Hume AI, Affectiva, Symbl.ai, and Gong for automation and conversation or biometric signal handling.
The selection criteria across the reviewed tools focus on integration depth, automation and API surface, and the admin and governance controls needed for consistent emotion or empathy tagging. Each tool review reflects how its workflow frames consent-aware outputs, evidence traceability, board-based artifact structure, or webhook and routing mechanics.
Empathy Software that turns emotion and qualitative signals into reviewable empathy artifacts
Empathy software captures customer emotions and qualitative research evidence and packages the results into artifacts teams can annotate, tag, and validate. Kairos emphasizes consent-aware emotion analysis outputs that arrive as structured review artifacts for analyst interpretation, while Dovetail emphasizes evidence-linked insight cards that keep themes tied to source notes across collaborative studies.
Many empathy workflows blend automation with human review. Hume AI and Gong support human-in-the-loop gating for emotion or conversation tagging, while Miro and Mural focus on shared workspace structure for empathy maps and journey artifacts that evolve through workshops.
Empathy Software capabilities that determine usable outputs
Empathy software must convert raw qualitative evidence into artifacts that teams can review, tag, and audit internally. The best tools attach interpretation steps to either source evidence, time-stamped moments, or analyst review gates so stakeholders can trust what they see.
The category splits into two operational patterns. Some products center on structured review artifacts like consent-aware emotion outputs or evidence-linked insight cards. Others center on workspace structure for empathy mapping and journey artifacts, or on automation surfaces like APIs and webhooks that push signals into human-in-the-loop workflows.
Consent-aware emotion outputs that arrive as structured analyst artifacts
Kairos produces consent-aware emotion analysis outputs as structured review artifacts designed for analyst interpretation across text and speech ingestion. Hume AI also turns emotion model outputs into auditable, review-gated tagging, but it uses a project-based configuration workflow that adds setup effort.
Evidence-linked synthesis that keeps themes connected to notes
Dovetail creates evidence-linked insight cards that keep themes tied to source notes across collaborative projects. This matters more than generic tagging because theme quality depends on consistent tagging conventions during collaborative studies.
Workshop-grade empathy maps and journey artifacts inside navigable boards
Miro supports frames and templates that let teams nest empathy maps, evidence, and action notes in one workspace for iterative reviews. Mural ties empathy mapping and journey mapping templates to shared boards with structured elements aligned to personas and touchpoints, but it does not treat empathy automation as a native center of gravity.
Automation interfaces that export empathy signals into downstream workflows
Symbl.ai pairs webhook event delivery with an analytics API so conversation insights can trigger human-in-the-loop review workflows. Kairos also supports API-based ingestion and result retrieval for automation, but its emphasis is structured emotion review artifacts rather than event streaming.
Human-in-the-loop gating and review workflows for sensitive interpretation
Gong routes AI-tagged moments into structured clip-level review workflows tied to coaching actions for customer-facing teams. Hume AI adds human-in-the-loop review steps to govern sensitive interpretations of emotion signals extracted from calls or transcripts.
Research operations formats that generate reviewable participant evidence
Dscout uses timed diary-style prompts that generate reviewable, evidence-backed participant clips organized by participant and task. UserTesting uses study panels with scripted tasks that produce comparable session data teams can tag and synthesize quickly.
Choosing Empathy Software by workflow control, not by feature checklists
The deciding factor is how teams want empathy signals to become reviewable artifacts. Some teams need consent-aware emotion outputs and analyst gating for interpretation. Other teams need evidence-linked cards or workshop-grade artifacts to keep synthesis traceable across recurring studies.
A second deciding factor is where automation should land. Some products emphasize APIs and webhooks for exporting signals into downstream systems. Other products emphasize collaborative board structure where humans create and maintain empathy maps over time.
Start with the artifact shape stakeholders must review
If stakeholders need structured emotion outputs created for analyst interpretation, Kairos fits contact-center and mixed text and speech workflows with API-based ingestion and result retrieval. If stakeholders need evidence-linked themes that stay connected to interview notes, Dovetail fits recurring research cycles with insight cards designed to preserve traceability.
Pick the workflow control model: gating, boards, or study panels
Choose Hume AI when human-in-the-loop review gates must sit directly in the tagging workflow so sensitive emotion interpretations are review-gated. Choose Miro or Mural when the primary work happens in workshops with nested empathy maps and journey artifacts that stay editable through iterative planning.
Route empathy signals through automation only when downstream systems require it
Choose Symbl.ai when near-real-time webhook delivery and an analytics API must trigger human-in-the-loop review workflows in other systems. Choose Kairos when automation must retrieve structured emotion results for analyst interpretation rather than just publish events.
Match the evidence collection format to how quickly studies need to run
Choose Dscout when timed diary-style prompts must generate participant clips across multiple days with evidence organized per participant and task. Choose UserTesting when study panels with scripted tasks must produce comparable sessions for fast tagging and synthesis.
Validate mapping and coaching integration requirements for contact-center and customer-facing loops
Choose Gong when conversation-level tagging must link exact transcript moments to clip-level review and routing into coaching actions. Choose Mural when the priority is structured empathy mapping and journey templates inside shared boards and automation for empathy signals is not the primary requirement.
Plan for governance tasks that affect theme accuracy and usability
If emotion outputs will be reused across teams, budget governance time for consistent data prep and labeling in Kairos and careful calibration in Hume AI for low-resource languages. If qualitative synthesis depends on consistent tagging conventions, plan process time for Dovetail theme quality and prepare for bulk reorganization when taxonomy changes late.
Who benefits from which Empathy Software workflow
Empathy software is most effective when the team’s working rhythm matches how outputs become reviewable artifacts. The tools below segment by whether the work is primarily analyst interpretation, workshop artifact creation, or research evidence collection with structured sessions.
The best fit also depends on whether empathy signals must move into other systems via APIs and webhooks or stay inside collaborative workspaces and study environments.
Contact centers and CX analytics teams
Kairos supports consent-aware emotion analysis across text and speech with API-based ingestion and result retrieval, which aligns with call and chat review cycles. Gong adds clip-level review routing that ties AI-tagged moments to coaching actions inside Gong workflows.
Qualitative research and insight teams running recurring studies
Dovetail keeps themes tied to evidence-linked source notes through collaborative projects, which reduces context switching during stakeholder review. UserTesting and Dscout support faster study turnaround by generating comparable panel sessions or timed diary clips that teams can tag and synthesize.
Product and design teams running workshop-based empathy mapping
Miro nests empathy maps, evidence, and action notes using frames and templates so artifacts stay co-located through collaborative reviews. Mural provides empathy mapping and journey mapping templates that tie notes to personas and touchpoints within shared boards for ongoing planning.
Teams that need emotion or conversation signals routed into downstream systems
Symbl.ai provides webhook event delivery and an analytics API so conversation insights can trigger human-in-the-loop review workflows in other tools. Kairos offers API ingestion and result retrieval when automation needs structured emotion review artifacts rather than just event publishing.
Governance-heavy organizations handling sensitive interpretations
Hume AI includes human-in-the-loop review steps designed to gate emotion tagging and support auditability for sensitive interpretations. Affectiva and Gong both introduce extra handling overhead for biometric-derived or moment-based interpretation, which requires consent and governance discipline.
Common failure modes when buying Empathy Software
Empathy software breaks most often when teams assume that tagging alone creates trustworthy insights. Traceability, review gating, and evidence-linking determine whether artifacts survive stakeholder scrutiny.
Another recurring failure mode is mismatch between automation intent and operational workflow. Tools that publish signals via APIs and webhooks still require governance steps and taxonomy consistency to remain usable at scale.
Choosing a board-first tool without planning for emotion or sentiment automation needs
Miro and Mural excel at collaborative empathy maps and journey artifacts, but Mural does not treat empathy AI or sentiment automation as a native center of gravity. For emotion signal tagging requirements, Kairos or Hume AI align better with structured emotion outputs and review gates.
Assuming emotion outputs are self-interpreting without analyst review
Kairos requires analyst review of emotion outputs to avoid over-interpretation and it needs consistent data prep and labeling. Hume AI adds a human-in-the-loop review step, which means governance and calibration still matter for low-resource languages.
Letting taxonomy and tagging conventions drift across teams
Dovetail theme quality depends on consistent tagging conventions and bulk reorganization can become time-consuming when taxonomy changes late. Gong also needs active configuration and taxonomy upkeep to translate conversation tags into personas for empathy mapping.
Overbuilding automation pipelines without designing consent, redaction, and retention workflows
Symbl.ai setup requires aligning consent, redaction, and retention across pipelines because webhook and analytics outputs feed automation. Affectiva adds overhead due to video ingestion and labeling and it requires tight consent and data handling discipline for biometric-derived signals.
How We Selected and Ranked These Tools
We evaluated Kairos, Dovetail, Miro, Mural, UserTesting, Dscout, Hume AI, Affectiva, Symbl.ai, and Gong against automation and API surface, evidence traceability for review artifacts, and governance fit for human-in-the-loop interpretation. Features drove 40% of the scoring because each tool’s standout workflow ties signals or evidence to reviewable outputs like consent-aware emotion artifacts, evidence-linked insight cards, or clip-level routing.
Ease and value each contributed 30% because setup effort varies sharply between projects configured for emotion tagging and board-based workshop structures. Kairos scored highest due to consent-aware emotion analysis outputs that arrive as structured review artifacts with API-based ingestion and result retrieval supporting analyst interpretation workflows.
Frequently Asked Questions About Empathy Software
How do Kairos and Symbl.ai convert customer interactions into actionable empathy signals?
Which tools are built for workshop-style empathy mapping versus research repositories?
How do Hume AI and Gong handle human-in-the-loop review for sensitive emotion judgments?
When do teams typically choose Affectiva over text-based emotion pipelines?
What breaks if an empathy workflow needs traceable evidence links back to source notes?
How do Mural and Dovetail differ in admin controls for collaboration governance?
Which tool supports API-driven ingestion and automation hooks for empathy analysis?
How does Dscout structure remote qualitative empathy research across participants?
Where do integrations fall short if a workflow requires video emotion signals end-to-end?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
- Mental Health PsychologyTop 10 Best Psychology Software of 2026
- Healthcare MedicineTop 10 Best Therapy Emr Software of 2026
- HR In IndustryTop 10 Best Employee Engagement Software of 2026
- Social Services WelfareTop 10 Best Social Services Software of 2026
- Technology Digital MediaTop 10 Best User Support Software of 2026
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Mental Health Psychology alternatives
See side-by-side comparisons of mental health psychology tools and pick the right one for your stack.
Compare mental health psychology tools→