Hot Debrief Tool
A digital tool for fast, structured debriefs following events in high-pressure defense and emergency environments.
A digital tool for fast, structured debriefs following events in high-pressure defense and emergency environments.
Project Type
Project Type
Conceptual project
Responsibilities
Responsibilities
Research, UX Design, UI Design
Tools
Tools
Figma
The Problem
Teams often delay debriefing until emotions have cooled and critical details have faded from memory. This timing gap results in shallow insights and missed opportunities for immediate learning and operational improvement.
Project Goal
Create a focused and minimal environment that enables effective hot debriefing, even in moments when attention is low and mental overload is high.
User Understanding
In this project, my user understanding approach was to define the key roles involved and outline the practical difficulties they encounter right after an event.
By identifying their pain points and needs, I structured the user flow and key features to directly address those real-world challenges.
User Pain Points
"I need my people to talk, but I also need them to process. Most of them aren't really present yet."
Lt. Or Ben-Ari – Team Leader
Struggles to get meaningful input when the team is still emotionally reactive
Feels pressure to debrief quickly, but lacks the tools to balance emotional readiness with operational timelines
"My head's still in the mission. I don't have the words yet, but I know what happened."
Sgt. Alon Levi – Squad Sergeant
Feels mentally and emotionally saturated right after the action
Often lacks the time to process events before the debrief starts
User Needs
Team Leader
Needs structured facilitation tools that work even when the team is emotionally reactive and may not be fully present
Squad Member
Needs simple, guided prompts to express observations without requiring complex analysis
Main User Flow
After exploring different reflection models, the main flow was shaped around one clear purpose: capturing operational insight in the immediate aftermath of an event.
The flow guides users through a lightweight, structured process that minimizes cognitive effort, helping them process and communicate what happened.
Mark Key Moments
Answer Guided Prompts
Review & Add Notes
Submit Summary
Key Features
Two Entry Points, Two Mindsets
The Situation: After intense events, users come in with different mental states. Some need to reconstruct what happened, others are ready to speak.
Design Approach: The tool offers two distinct flows, Timeline-first for memory mapping, Prompt-first for direct reflection.
Minimal Prompts, Maximum Precision
The Situation: Users are emotionally reactive and cognitively overloaded. Open-ended questions can overwhelm.
Design Approach: Each step asks a single, tightly scoped question. Prompts are clear, closed, and built to elicit operational insights. Responses are formatted in bullet points, making it easy to focus on key takeaways with minimal effort.
Flexible Summary, Actionable Output
The Situation: After input is collected, users need clarity and control over
what happens next.
Design Approach: A structured summary is auto-generated. Users can edit, add tags, and choose to either save the reflection privately or forward it to a team lead. This supports both private processing and operational use, empowering the user to decide what stays personal and what becomes part of team learning.
Design Thinking
This project challenged me to design not around tasks, but around mental readiness. The users weren't just operating under pressure. They were processing reality as it unfolded or even before they could.
As a designer, I focused on creating a mental environment, not just a digital space. That meant stripping away aesthetic noise, reducing interactions to micro-decisions, and building logic that flexes with emotional availability.
Each UX choice from flow options to question phrasing was a response to a user state, not just a role. Instead of designing one system for one user type, I built a lightweight adaptive structure that responds to different coping modes.
Hot Debrief Tool
A digital tool for fast, structured debriefs following events in high-pressure defense and emergency environments.
A digital tool for fast, structured debriefs following events in high-pressure defense and emergency environments.
Project Type
Project Type
Conceptual project
Responsibilities
Responsibilities
Research, UX Design, UI Design
Tools
Tools
Figma
The Problem
Teams often delay debriefing until emotions have cooled and critical details have faded from memory. This timing gap results in shallow insights and missed opportunities for immediate learning and operational improvement.
Project Goal
Create a focused and minimal environment that enables effective hot debriefing, even in moments when attention is low and mental overload is high.
User Understanding
In this project, my user understanding approach was to define the key roles involved and outline the practical difficulties they encounter right after an event.
By identifying their pain points and needs, I structured the user flow and key features to directly address those real-world challenges.
User Pain Points
"I need my people to talk, but I also need them to process. Most of them aren't really present yet."
Lt. Or Ben-Ari – Team Leader
Struggles to get meaningful input when the team is still emotionally reactive
Feels pressure to debrief quickly, but lacks the tools to balance emotional readiness with operational timelines
"My head's still in the mission. I don't have the words yet, but I know what happened."
Sgt. Alon Levi – Squad Sergeant
Feels mentally and emotionally saturated right after the action
Often lacks the time to process events before the debrief starts
User Needs
Team Leader
Needs structured facilitation tools that work even when the team is emotionally reactive and may not be fully present
Squad Member
Needs simple, guided prompts to express observations without requiring complex analysis
Main User Flow
After exploring different reflection models, the main flow was shaped around one clear purpose: capturing operational insight in the immediate aftermath of an event.
The flow guides users through a lightweight, structured process that minimizes cognitive effort, helping them process and communicate what happened.
Mark Key Moments
Answer Guided Prompts
Review & Add Notes
Submit Summary
Key Features
Two Entry Points, Two Mindsets
The Situation: After intense events, users come in with different mental states. Some need to reconstruct what happened, others are ready to speak.
Design Approach: The tool offers two distinct flows, Timeline-first for memory mapping, Prompt-first for direct reflection.
Minimal Prompts, Maximum Precision
The Situation: Users are emotionally reactive and cognitively overloaded. Open-ended questions can overwhelm.
Design Approach: Each step asks a single, tightly scoped question. Prompts are clear, closed, and built to elicit operational insights. Responses are formatted in bullet points, making it easy to focus on key takeaways with minimal effort.
Flexible Summary, Actionable Output
The Situation: After input is collected, users need clarity and control over
what happens next.
Design Approach: A structured summary is auto-generated. Users can edit, add tags, and choose to either save the reflection privately or forward it to a team lead. This supports both private processing and operational use, empowering the user to decide what stays personal and what becomes part of team learning.
Design Thinking
This project challenged me to design not around tasks, but around mental readiness. The users weren't just operating under pressure. They were processing reality as it unfolded or even before they could.
As a designer, I focused on creating a mental environment, not just a digital space. That meant stripping away aesthetic noise, reducing interactions to micro-decisions, and building logic that flexes with emotional availability.
Each UX choice from flow options to question phrasing was a response to a user state, not just a role. Instead of designing one system for one user type, I built a lightweight adaptive structure that responds to different coping modes.
Hot Debrief Tool
A digital tool for fast, structured debriefs following events in high-pressure defense and emergency environments.
A digital tool for fast, structured debriefs following events in high-pressure defense and emergency environments.
Project Type
Project Type
Conceptual project
Responsibilities
Responsibilities
Research, UX Design, UI Design
Tools
Tools
Figma
The Problem
Teams often delay debriefing until emotions have cooled and critical details have faded from memory. This timing gap results in shallow insights and missed opportunities for immediate learning and operational improvement.
Project Goal
Create a focused and minimal environment that enables effective hot debriefing, even in moments when attention is low and mental overload is high.
User Understanding
In this project, my user understanding approach was to define the key roles involved and outline the practical difficulties they encounter right after an event.
By identifying their pain points and needs, I structured the user flow and key features to directly address those real-world challenges.
User Pain Points
"I need my people to talk, but I also need them to process. Most of them aren't really present yet."
Lt. Or Ben-Ari – Team Leader
Struggles to get meaningful input when the team is still emotionally reactive
Feels pressure to debrief quickly, but lacks the tools to balance emotional readiness with operational timelines
"My head's still in the mission. I don't have the words yet, but I know what happened."
Sgt. Alon Levi – Squad Sergeant
Feels mentally and emotionally saturated right after the action
Often lacks the time to process events before the debrief starts
User Needs
Team Leader
Needs structured facilitation tools that work even when the team is emotionally reactive and may not be fully present
Squad Member
Needs simple, guided prompts to express observations without requiring complex analysis
Main User Flow
After exploring different reflection models, the main flow was shaped around one clear purpose: capturing operational insight in the immediate aftermath of an event.
The flow guides users through a lightweight, structured process that minimizes cognitive effort, helping them process and communicate what happened.
Mark Key Moments
Answer Guided Prompts
Review & Add Notes
Submit Summary
Key Features
Two Entry Points, Two Mindsets
The Situation: After intense events, users come in with different mental states. Some need to reconstruct what happened, others are ready to speak.
Design Approach: The tool offers two distinct flows, Timeline-first for memory mapping, Prompt-first for direct reflection.
Minimal Prompts, Maximum Precision
The Situation: Users are emotionally reactive and cognitively overloaded. Open-ended questions can overwhelm.
Design Approach: Each step asks a single, tightly scoped question. Prompts are clear, closed, and built to elicit operational insights. Responses are formatted in bullet points, making it easy to focus on key takeaways with minimal effort.
Flexible Summary, Actionable Output
The Situation: After input is collected, users need clarity and control over
what happens next.
Design Approach: A structured summary is auto-generated. Users can edit, add tags, and choose to either save the reflection privately or forward it to a team lead. This supports both private processing and operational use, empowering the user to decide what stays personal and what becomes part of team learning.
Design Thinking
This project challenged me to design not around tasks, but around mental readiness. The users weren't just operating under pressure. They were processing reality as it unfolded or even before they could.
As a designer, I focused on creating a mental environment, not just a digital space. That meant stripping away aesthetic noise, reducing interactions to micro-decisions, and building logic that flexes with emotional availability.
Each UX choice from flow options to question phrasing was a response to a user state, not just a role. Instead of designing one system for one user type, I built a lightweight adaptive structure that responds to different coping modes.