The design decisions behind andthen — what evidence drove the choices, and why this approach produces better lessons than the traditional after-action review.
andthen isn't a survey tool. It's a structured observation capture system built around the specific behavioral and organizational dynamics of emergency response teams. Every design decision is grounded in research on how people give feedback under fatigue, how organizations convert observations into change, and why the traditional AAR process fails to close the loop.
Emergency management has a documented "lessons identified vs. lessons learned" crisis. Organizations capture observations, write reports, and file them — but the same problems recur across incidents. The terminology has become a cliché: "lessons identified" means the organization found the problem. "Lessons learned" means something changed because of it. IFRC 2019
The gap is structural. Most organizations have no mechanism to track whether an observation moved from identification to implementation. When a contributor submits feedback, they receive no signal that anything changed. This erodes participation: why observe, when nothing happens?
The feedback loop must close. andthen shows contributors exactly what happened to their observations — acknowledged, implemented mid-operation, deferred to the AAR, or declined with a stated reason. This is the primary driver of sustained participation.
Traditional AARs ask people to recall events days or weeks later, via email surveys with low completion rates. andthen is designed for the demobilization window: the period immediately after operational stand-down while personnel are still assembled.
This window has three critical properties:
While practitioner consensus strongly supports demobilization-window collection, a peer-reviewed controlled study measuring demobilization-window vs. delayed collection in emergency management contexts has not been independently verified in this project. The design decision is supported by organizational behavior literature on episodic memory decay and group recall, but the specific emergency management application remains a practitioner-validated rather than fully peer-reviewed claim.
andthen uses the Stop / Continue / Start framework, a structured feedback methodology that forces specificity by anchoring observations to concrete behaviors and decisions.
This structure produces qualitatively different inputs than open-ended surveys. It forces the contributor to think in operational terms — specific moments, specific behaviors — rather than general impressions. Emerald 2017
A 42% quality improvement figure for Stop/Continue/Start vs. open-ended review appears in secondary literature but the original source has not been independently verified by this project. Treat this as directionally supported, not precisely established.
andthen collects no names. Observations are anonymous by default, with optional function/role/location context that contributors choose to provide.
The anonymity-first design addresses a well-documented problem in organizational feedback: people self-censor when observations might be attributed to them, particularly in hierarchical emergency response structures where criticism of decisions can have career consequences. APA 2003
The framing of optional context is deliberate: "Adding context helps us fix the right thing in the right place." It positions context as a tool for routing, not attribution. This produces higher-quality labeled observations without the chilling effect of mandatory identification.
The 40–60% improvement in honest response rates from anonymous vs. named surveys appears across organizational behavior literature but the specific University of Michigan study cited in secondary sources was not independently verified. Direction is well-supported; magnitude is uncertain.
The difference between an andthen collection event and a dead email survey is the facilitation checkpoint. andthen is designed to be used during an explicit demobilization moment when the Incident Commander or demob leader gives the signal: "Before we scatter — two minutes. Phones out."
Completion rates collapse without active facilitation. Email-based post-event surveys routinely achieve under 20% completion. Synchronous mobile-first collection during a facilitated demob checkpoint approaches full participation — because the window is defined, the expectation is set, and friction is minimal. DMPHP
andthen doesn't solve the facilitation problem. That's an organizational and cultural question. It eliminates the friction barrier so that two minutes of real facilitation produces the full data set.
Designed for fatigue. Three questions, 400 characters each, optional context. Submittable with one hand on a phone.
QR code → mobile browser → form. Nothing to download, no account, no onboarding. Friction removed.
Participants see live counts: how many observations submitted, how many implemented mid-operation.
Every observation moves through a defined lifecycle: received → acknowledged → implemented/deferred/declined → AAR → CIP.
andthen treats each observation as a unit that moves through a defined state machine. This is the mechanism that closes the feedback loop:
Observation submitted. No facilitator action yet.
A facilitator has seen and reviewed the observation. The contributor's input has been read.
The observation was actioned during the event. The problem was fixed, the approach was adopted, or the gap was addressed before the event ended.
The observation requires more time, resources, or organizational decision-making. It is carried forward to the After-Action Review for structured follow-up.
The observation won't be actioned, with a stated reason. Transparency here is critical — declining without explanation destroys trust and future participation.
Post-event: the observation produced a concrete change in policy, training, equipment, or procedure. "Applied" means the change was made. "Learned" means it was incorporated into organizational knowledge.
When multiple agencies participate in a response, the reciprocity dynamic matters. Participants from Agency B are unlikely to submit feedback unless they believe it will be seen and acted on — and unless they see that Agency A contributed too.
The metrics counter on the submission form ("732 observations collected, 6 implemented mid-operation so far") addresses this directly. It signals that the system is active, that others are using it, and that observations have already produced results. This is the social proof mechanism that sustains multi-agency participation. Eval 2019