Author Archives: Art Inteligencia

About Art Inteligencia

Art Inteligencia is the lead futurist at Inteligencia Ltd. He is passionate about content creation and thinks about it as more science than art. Art travels the world at the speed of light, over mountains and under oceans. His favorite numbers are one and zero. Content Authenticity Statement: If it wasn't clear, any articles under Art's byline have been written by OpenAI Playground or Gemini using Braden Kelley and public content as inspiration.

What Is the Difference Between Change Management and Project Management?

Leave a reply

What Is the Difference Between Change Management and Project Management?

by Braden Kelley and Art Inteligencia

What Is the Difference Between Change Management and Project Management? (Short Answer)

Project management delivers an output — a system, process, product, or deliverable — on time, on scope, and on budget. Change management prepares, equips, and supports people so that output is adopted and the change objectives are met in behavior. A project can finish successfully while the change still fails. Many organizations treat change management as a subset of project management. The healthier frame is the reverse: every project changes something, so project delivery sits inside a larger change effort.

Finishing the build is not the same as achieving the change.

Below you’ll find a side-by-side comparison, why the relationship is often drawn backwards, how the two disciplines work together, and how to tell which one you are missing. For the definition of change management itself, see What Is Change Management?

How Do Change Management and Project Management Differ?

Project management Change management
Primary question Did we deliver the output? Did people adopt the new way and meet the objectives?
Focus Scope, schedule, cost, quality of the deliverable Readiness, sponsorship, enablement, adoption, reinforcement
“Done” Go-live, handover, or project close Named behaviors stick after the project team leaves
Success metrics Milestones, budget, defect rates, on-time delivery Behavior adoption, old-path retirement, confidence, outcomes
Typical owner Project or program manager Change lead, sponsor, and a durable BAU owner
Risk if missing Late, over budget, or incomplete deliverable Shelfware, workarounds, and a “successful” project that changes nothing

Both disciplines matter. Confusing them produces the most expensive kind of success: a green project that never becomes a new way of working.

Why Do Organizations Treat Change Management as a Subset of Project Management?

Because the project is visible. It has a charter, a budget, a go-live date, and a RAG status. Change work — readiness, practice, sponsorship with real levers, retiring the old path — looks softer on a dashboard, so it gets bolted on as a communications workstream inside the project plan.

That staffing pattern is backwards. Every project changes something for someone. The project is one means of producing a new state. Change management is the discipline of making sure people can live in that state and that the objectives are met. In the Architecting the Organization for Change framing I use in Charting Change, project management sits inside the change agenda — not the other way around.

If change is a line item under the project, adoption will be a line item after the celebration.

How Should Change Management and Project Management Work Together?

  1. Share the same objectives. Write success as behaviors and outcomes, not only as deliverables. The project plan and the change plan should both serve those objectives.
  2. Start change work before build peaks. Impact, readiness, and sponsorship cannot wait until UAT. By then the design of the work is already frozen.
  3. Name two finishes. Technical go-live is one finish. Adopted behavior with a BAU owner is another. Celebrate the second, not only the first.
  4. Fund enablement like delivery. Practice time, coaching, and the stop list for the old way need budget and calendar space — not leftover goodwill.
  5. Align metrics. Project health and change health should both be visible. A green cutover with rising workarounds is not a green change. For what to measure after go-live, see 6 Metrics That Prove Change Worked — Beyond Go-Live Day.

When tools become shelfware, the failure is usually in that handoff between delivery and adoption — the patterns in 12 Adoption Mistakes That Turn Good Tools Into Shelfware.

How Do You Know Which One You Are Missing?

  • Strong project, weak change: On-time go-live, training completions up, and people still on the spreadsheet. Sponsors clap; the old path stays open “just in case.”
  • Strong change intent, weak project: Clear case for change and engaged champions, but the deliverable slips, quality fails, or the tool never works for the median user.
  • Both present and aligned: Delivery dates and adoption behaviors are on the same scorecard. Someone owns the new way after the PMO leaves. The old way has a kill date.

Leaders who still treat go-live as transformation should also read 8 Change Myths Leaders Still Believe in 2026. For the method spine behind planning, leadership, management, maintenance, and portfolio, see 5 Steps of Human-Centered Change That Survive Reality.

Which Comes First — the Project or the Change?

Start with the change you need in people’s work. Then decide which projects, if any, are required to make that change possible. A project without a change objective is construction. A change without delivery discipline is a wish. You need both — with adoption as the finish line that leadership actually funds.

Manage the project so something ships. Manage the change so something sticks.

Ready to Take the Next Step?

When project plans and change plans fight for the same calendar, people lose. The fix is a shared visual approach so delivery and adoption show up on the same page — with sponsors who have real levers.

See the methodology. Explore Human-Centered Change™, my visual, collaborative approach to planning change so the people who must live it can see the whole effort and adopt the new way.

Get the toolkit. Read Charting Change, my practical guide to Human-Centered Change™, built around the Change Planning Canvas™ and 70+ visual tools for getting everyone on the same page.

Deliver the output. Design the adoption. Do not mistake one for the other.

FAQ: Change Management vs Project Management

What is the difference between change management and project management?

Project management delivers an output on time, scope, and budget. Change management prepares and supports people so that output is adopted and the change objectives are met in behavior. A project can succeed while the change still fails.

Is change management part of project management?

No. Many organizations staff it that way, but every project changes something for someone. Project delivery should sit inside a larger change effort aimed at adoption and outcomes, not the reverse.

Can a project succeed and the change still fail?

Yes. The deliverable can go live on time while people keep using the old path, workarounds rise, and no one in the business owns the new way after the project team leaves. That is a successful project and a failed change.

Do you need both change management and project management?

Yes, for any effort that asks people to work differently. Project management ships the output. Change management makes the output usable and durable in real work. Missing either one produces delay, shelfware, or both.

When does change management start relative to the project?

Change management should start when the change is defined — impact, readiness, sponsorship, and adoption design — not after go-live. Waiting until delivery is nearly finished freezes bad job design and turns change work into a late communications push.

Image credits: Pixabay

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Cursor to clean up the article, add images and create infographics.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

What is the Innovation Process — and What Are Its Stages?

Leave a reply

What is the Innovation Process — and What Are Its Stages?

by Braden Kelley and Art Inteligencia

What Is the Innovation Process? (Short Answer)

The innovation process is how an organization turns a human problem into a widely adopted solution. Six stages: (1) frame the problem from insight, (2) generate options, (3) choose what to pursue, (4) develop and test evidence, (5) design adoption into how work actually runs, and (6) scale what people use — then learn. Launch is not the finish line. Adoption is.

If your innovation process ends at launch, you built a project plan — not an innovation process.

Below you’ll find why most process diagrams stop too soon, what each stage is for, how this differs from stage-gate and design thinking, where the process usually breaks, and how to run it without bureaucracy. The point of the process is adopted value, not novelty — see What Is Innovation? A Clear Definition, With Examples.

Why Do Most Innovation Process Diagrams Stop Too Soon?

The diagram most teams inherit looks like this: idea, screen, develop, launch. It is tidy. It is also incomplete.

What’s usually missing is the customer’s job, evidence before a big commitment, fit with the operating model, a named owner who will run the new way after the project team leaves, and proof that people actually adopted it. A beautiful stage-gate with nobody accountable after go-live is a slideshow.

A process that cannot kill ideas, or cannot hand them to the people who must live with them, is not an innovation process.

What Are the Six Stages of the Innovation Process?

Stage Purpose Done when
1. Frame the problem from insight Name who has the job and what is failing The problem is specific enough to test
2. Generate options Create real alternatives, including recombination You have more than one decorated concept
3. Choose what to pursue Fund a few bets and stop the rest Kills and parks are explicit, not “still in the pipeline”
4. Develop and test evidence Learn whether behavior will change before you scale spend You have evidence about use, not only applause
5. Design adoption into the operating model Make the new way survivable in real work Jobs, incentives, handoffs, and an owner are in place
6. Scale what is used — and learn Expand where adoption and value hold Behavior moves, the old path shrinks, and learning feeds the next cycle

1. Frame the Problem from Insight

Purpose: Who has the job? What frustration or unmet need is real? Start from evidence, not a sponsor’s favorite idea.

Done when: The problem is specific enough that a test could prove you wrong.

Common skip: Jumping to a solution because someone important already picked one.

2. Generate Options

Purpose: Produce several ways to solve the framed problem, including recombination of things that already exist — not only “brand-new.”

Done when: You have genuine alternatives, not one concept and a brainstorm that rubber-stamps it.

Common skip: Treating ideation as the innovation.

3. Choose What to Pursue

Purpose: Apply criteria tied to strategy, customer value, and the organization’s capacity — including the courage to stop. Different types of bets deserve different patience; see What Are the Different Types of Innovation?.

Done when: A small set is funded and the rest are explicitly killed or parked.

Common skip: Everything stays “in the pipeline.”

4. Develop and Test Evidence

Purpose: Prototypes, pilots, and cheap tests that could falsify the bet before you scale spend.

Done when: You have evidence about behavior, not only applause in a demo.

Common skip: Building the full product “to see if it works.”

5. Design Adoption into the Operating Model

Purpose: Jobs, incentives, training, handoffs, the old path, and a named owner who will run this after the project team leaves.

Done when: The new way can survive contact with real work.

Common skip: “We’ll handle change later.” For the stages teams most often leap over between learning and scale, see 6 Stages Most Organizations Skip Between Insight and Scale.

6. Scale What Is Used — and Learn

Purpose: Expand only where adoption and value hold, and feed what you learned back into the next insight.

Done when: Behavior and outcomes move for the people you meant to serve, and the old path shrinks.

Common skip: Scaling a pilot because the deck was approved. For how to measure value beyond idea count, see 12 Metrics That Actually Measure Innovation Value.

How Is This Different From Stage-Gate or Design Thinking?

Approach What it’s strong at Where it often stops short
Stage-gate Go/kill discipline and investment control Product-centric; “launch” treated as done
Design thinking Empathy, problem framing, and prototyping Operating-model adoption and scale left for “later”
This process Human insight at the front; adoption and learning at the back; explicit kills in the middle Becomes bureaucracy if every stage grows a committee

A culture that cannot fund, forgive, and finish will stall any diagram — see How Do You Build a Culture of Innovation?

Use the methods. Don’t let the method replace the outcome.

Where Does the Innovation Process Usually Break?

  • The problem was never framed. A solution is looking for a sponsor.
  • The choice was never made. The pipeline is obese; nothing is stopped.
  • Evidence was skipped. The team builds first and learns late.
  • Adoption was unfunded. Launch day is the celebration and the end. That pattern is a form of innovation theater.
  • Scale has no owner. The pilot runs forever because nobody in the business owns the new way.

How Do You Run the Innovation Process Without Bureaucracy?

  1. One page per stage: the question, the evidence required, the decision, and the owner.
  2. Same stages, different speed: incremental bets and radical bets share the path, but not the same evidence bar or patience.
  3. Kill criteria before affection: write what would stop the work before you fall in love with the idea.
  4. Name the adoption owner early: before development spend gets large.
  5. A quarterly learning review: what you stopped, what you scaled, and what you still don’t know.

A good innovation process is short enough to use and strict enough to stop the wrong work.

Ready to Take the Next Step?

A clean six-stage process only works if your organization can actually run it. Barriers in strategy, evaluation, development, and psychology stall stages even when the diagram on the wall is perfect.

Find out where you stand. Take the free Innovation Maturity Assessment: 50 questions, about 10–15 minutes, scored against a five-level Innovation Maturity Model so you can see your biggest barriers and set a baseline to improve from.

Learn how to remove the barriers. Read Stoking Your Innovation Bonfire, my roadmap for identifying what’s blocking innovation in your organization and building a culture where it can flourish (while also highlighting a couple alternative innovation processes/approaches).

The process tells you the path. Your barriers tell you where that path is blocked.

FAQ: The Innovation Process

What are the stages of the innovation process?

Six stages: frame the problem from insight, generate options, choose what to pursue, develop and test evidence, design adoption into the operating model, and scale what people actually use — then learn. Launch is a milestone inside the process, not the end of it.

What is the innovation process in simple terms?

The innovation process is how an organization turns a real human problem into a solution people widely adopt because they value it more than what they used before. It includes choosing, testing, adopting, and scaling — not only coming up with ideas.

What is the difference between the innovation process and stage-gate?

Stage-gate is a go/kill discipline that often treats product launch as the finish. This innovation process keeps human insight at the front and operating-model adoption and learning at the back, with explicit decisions to stop work in the middle.

Why do innovation processes fail?

They fail when the problem was never framed, nothing is ever killed, evidence is skipped, adoption is unfunded, or scale has no owner in the business. A diagram cannot compensate for those gaps.

When is an innovation process finished?

An innovation process is finished for a given bet when the people it was meant to serve have adopted it, outcomes have moved, the old path has shrunk, and what was learned has been fed back into the next cycle — not on launch day.

Image credits: Cursor

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Google Gemini and M365 CoPilot to clean up the article, add images and create infographics.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

What is the Future of Work — and What Jobs Will Exist in 10 Years?

Leave a reply

What is the Future of Work — and What Jobs Will Exist in 10 Years?

by Braden Kelley and Art Inteligencia

What Is the Future of Work? (Short Answer)

The future of work is the ongoing redesign of how, where, and by whom work gets done as AI, automation, demographics, and changing expectations reshape jobs. It isn’t a fixed forecast; it’s a set of choices being made now. Over the next ten years, most jobs will change more than disappear, and new roles will grow around guiding AI, verifying what’s real, designing experiences, leading change, and caring for people.

The future of work isn’t something that happens to us. It’s something we design — or something that gets designed for us.

Most “future of work” content is either a trend list or a fear headline. Neither helps you decide anything. Below you’ll find the five forces reshaping work, the jobs likely to exist in ten years, the jobs that will change most, what work itself will look like, and how individuals and leaders can prepare.

What Forces Are Shaping the Future of Work?

Five forces are reshaping work at the same time, and they interact in ways no single trend report captures:

  1. AI and automation. AI is changing the tasks inside nearly every job — automating some, augmenting others, and creating new ones. It is also adding a new kind of coworker: AI agents that can take actions, not just answer questions.
  2. Demographics. Aging populations, growing caregiving responsibilities, longer working lives, and fewer young people entering the workforce in many countries are changing who works, for how long, and what they need to do it well.
  3. Changing expectations. Flexibility, meaning, wellbeing, and fairness now weigh more heavily in where people choose to work and how long they stay.
  4. Volatility and climate. Supply shocks, extreme weather, and the energy transition are disrupting existing work while creating entire new categories of it.
  5. New ways of organizing. Skills-based hiring, platform and project-based work, and teams made up of people and AI agents are changing how organizations are structured and how careers unfold.

None of these forces decides the outcome. They set the conditions. People still choose the design.

What Jobs Will Exist in 10 Years?

Nobody can publish an accurate list of job titles for ten years from now. But you can see which families of work are growing, because many of these roles already exist in early form today:

Role family Example roles Why it grows
Guiding and overseeing AI AI agent supervisor, AI operations lead, AI evaluator and trainer, AI governance lead Every AI system acting in the world needs humans who direct it, check it, and answer for it
Verifying what’s real Trust and safety specialist, content provenance analyst, synthetic-media investigator As fake content becomes cheap, proving what’s authentic becomes valuable
Designing human–AI work and experiences Workflow designer, conversation designer, experience designer Someone has to design how people and AI work together — and how it feels to customers and employees
Leading change and adoption Change and adoption lead, AI enablement coach, learning experience designer Technology moves faster than organizations can absorb it without help
Caring for people Care navigator, eldercare coordinator, wellbeing and mental-health roles Aging populations and human needs that technology can support but not replace
Building resilience and the energy transition Building retrofit and heat-pump technicians, grid and battery specialists, resilience planners Climate adaptation and new energy systems require skilled hands and planning
Maintaining physical-digital systems Robotics maintenance technician, smart-building technician, field-service specialist More machines in the physical world means more people who install, maintain, and repair them
Sense-making and foresight Foresight analyst, futurist, strategic insights lead Faster change raises the value of seeing it coming and making sense of it

If the last row interests you, I explain the role in detail in What Does a Futurist Do — and How Do You Become One?

Job titles will change faster than this list. The pattern is what lasts: work grows wherever humans add judgment, trust, care, or the ability to fix what breaks.

Which Jobs Will Change the Most?

Over the next decade, most jobs won’t disappear. They’ll transform. A few examples of how:

  • Customer service shifts from routine answers to resolving complex problems and building relationships.
  • Marketing and content shifts from producing drafts to judgment, taste, and strategy.
  • Software development shifts from writing code to designing systems and reviewing AI-generated code.
  • Finance and accounting shifts from processing transactions to advising decisions.
  • Healthcare could shift toward more time with patients and less on documentation — but only if the time saved is protected instead of filled with more volume.
  • Managers will coach humans and orchestrate AI agents, which requires new skills on both fronts.
  • Entry-level roles face the biggest redesign challenge. AI is absorbing the routine work beginners used to learn on, so organizations will have to deliberately rebuild the path from newcomer to expert.

If you want to assess your own role, start with the five-question self-check in Will AI Take My Job? An Honest, Human-Centered Answer. For why the entry-level challenge deserves more attention than job-loss percentages, see 8 Predictions Leaders Can Ignore — and 8 They Cannot Afford To.

What Will Work Itself Look Like?

Beyond which jobs exist, the experience of working is changing too — how, where, and when work happens:

  • Human–AI teams become the default. People will routinely work alongside AI agents, with humans accountable for the outcomes.
  • Skills count alongside degrees. Hiring and promotion will increasingly rely on demonstrated capability, not only credentials.
  • Learning happens in the flow of work. Continuous learning on real tasks replaces one-time training events.
  • Arrangements become more flexible and varied. There won’t be a single winner between office and remote work; the right answer will differ by the kind of work and the people doing it.
  • Careers get longer and have more chapters. Expect multiple roles, reskilling, and transitions across a working life rather than one ladder.
  • Work gets measured by outcomes and experience, not activity. What got done — and how it felt to customers and employees — matters more than hours logged.

For how human–agent teams might reshape organizations in different ways, see 5 Scenarios for Agentic Organizations — and What Leaders Must Own in Each.

How Do You Prepare for the Future of Work?

If you’re an individual, become fluent with AI on real tasks, not just in training. Move toward work built on judgment, relationships, and outcomes. Keep a deliberate learning path, especially if AI is absorbing the work you used to learn on. And think in career chapters rather than a single ladder. For the capabilities that grow in value as automation spreads, see 9 Skills That Age Well When Everything Else Automates.

If you’re a leader, fund job redesign alongside every technology investment. Decide where saved time goes before it quietly turns into more volume. Rebuild the apprenticeship path for entry-level roles. And give frontline workers a real voice in how AI changes their work. For the warning signs that you’re preparing for the wrong version of the future, see 8 Signals You’re Preparing for the Wrong Future of Work.

The difference comes down to two landings. In a soft landing, work is redesigned around people, and they succeed alongside AI. In a hard landing, headcount math and tool rollouts design work by default — and people absorb the cost.

Ten years from now, the future of work will simply be work. The question is whether we designed it on purpose.

Ready to Take the Next Step?

The future of work won’t arrive as a single forecast. It will be shaped by the signals you notice early and the choices you make about them — as an individual planning a career or as a leader redesigning how your organization works. That is why I created FutureHacking™, a strategic foresight methodology that helps individuals and teams become their own futurist.

FutureHacking™ gives you a simple four-step approach, supported by 20+ visual, collaborative tools:

  1. Pick the signals that matter — the shifts most likely to reshape the work you do or the workforce you lead.
  2. Map how those signals evolve — so you can tell a passing headline from a real change.
  3. Explore possible, probable, and preferable futures — instead of betting everything on a single prediction.
  4. Make your preferable future a reality — with a roadmap, guideposts, and actions you can start now.

Whether you’re charting your next career chapter or helping your leadership team design work around people instead of headcount math, FutureHacking™ helps you design the future of work on purpose.

Learn more about the FutureHacking™ methodology →

FAQ: The Future of Work

What is the future of work?

The future of work is the ongoing redesign of how, where, and by whom work gets done as AI, automation, demographics, changing expectations, and climate reshape jobs. It is not a fixed forecast but a set of design choices organizations and people are making now.

What jobs will be in demand in 10 years?

Demand is likely to grow in roles that guide and oversee AI, verify what is real, design human–AI work and experiences, lead change and adoption, care for people, build climate resilience and new energy systems, maintain physical-digital systems, and practice foresight. Specific titles will vary, but these role families are already emerging.

What jobs will disappear in the next 10 years?

Most jobs will change more than disappear. Roles made up mostly of routine, predictable screen work — such as high-volume drafting, basic data processing, and rules-based first-line support — face the most pressure, especially where demand doesn’t grow as the work gets cheaper.

What skills will matter most in the future of work?

The most durable skills include AI fluency on real tasks, problem framing, judgment under uncertainty, relationship-building, facilitation, care and empathy, the ability to repair what breaks, and learning how to learn as tools keep changing.

Will remote work continue in the future?

Yes, in varied forms. Neither the office nor remote work is likely to win outright; the right arrangement depends on the kind of work, the team, and the people doing it. Flexibility will remain a major factor in where people choose to work.

Image credits: Cursor

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Google Gemini and M365 CoPilot to clean up the article, add images and create infographics.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

FutureSignals™: How to Separate Real Trends From Noise Before Your Next Planning Cycle

Leave a reply

FutureSignals™: How to Separate Real Trends From Noise Before Your Next Planning Cycle

by Braden Kelley and Art Inteligencia

Ask any leadership team to name a trend shaping their industry, and you’ll get an answer within seconds. Ask them to explain why they believe it’s real, as opposed to something that just happened to come up in three meetings this month, and the room usually goes quiet. Most organizations aren’t short on trends. They’re short on a way to tell which of the dozens of things competing for the label “trend” actually deserve it.

Why this matters more than people think

Every strategic plan I’ve ever reviewed has been shaped, at least in part, by trends nobody rigorously tested. Not because the people building the plan were careless, but because there’s rarely a formal step in the process for testing a trend before acting on it. Something gets mentioned by a well-regarded analyst, or shows up in three unrelated conversations in the same month, and it quietly graduates from “thing I noticed” to “trend we’re planning around” without ever passing through anything that could reasonably be called scrutiny. Get that step wrong at the start of a planning cycle, and everything built on top of it inherits the mistake.

What actually separates a signal from noise

A genuine signal has a few characteristics that noise almost never does, and it’s worth being explicit about them rather than trusting instinct alone.

  1. It shows up from more than one independent direction. A single source, however credible, is a data point, not a trend. When you start seeing the same underlying shift from unrelated sources — a customer behavior pattern, an unrelated industry’s earnings call, a regulatory conversation, a technology adoption curve — that convergence is a much stronger indicator than any one source repeating itself loudly.

  2. It has a mechanism, not just a correlation. Noise often sounds like a trend because two things happened around the same time. A real signal comes with an explanation for why it’s happening — an incentive that changed, a cost curve that shifted, a constraint that got removed — not just a coincidence in timing that a confident narrator strung together after the fact.

  3. It’s sustained, not spiking. A lot of what gets treated as a trend is really just a spike — a burst of attention that fades within a quarter once the news cycle moves on. Real signals tend to persist and, more tellingly, tend to keep showing up even after the initial attention around them fades.

The traps that let noise through anyway

Even knowing these criteria, a few predictable biases let noise slip past them constantly. Recency bias — whatever you read most recently feels more significant than it actually is, purely because it’s fresh. Authority bias — a signal feels more credible because someone senior or well-known repeated it, regardless of whether they did any more rigorous evaluation than anyone else in the room. And the most dangerous one, confirmation bias — signals that happen to support what leadership already wants to believe about the future get waved through with far less scrutiny than signals that would require uncomfortable change. I’ve watched this last one derail more planning cycles than any of the others combined, because it’s the hardest one for a room to catch in itself.

Building a genuine filter, not just a gut check

The fix isn’t more research, exactly — it’s a consistent set of questions applied to every candidate signal before it earns a place in your planning conversation: Where else is this showing up, independently? What’s the actual mechanism driving it, and does that mechanism hold up under a second look? Has it persisted past its first burst of attention? And, the uncomfortable one worth asking every time — would we be this quick to believe it if it pointed toward a future we didn’t want?

This is exactly what FutureSignals™ is built to do

This filtering discipline is the first formal stage of FutureHacking™, and I built a specific component — FutureSignals™ — around exactly this problem: giving a team a structured, repeatable way to gather candidate signals and stress-test them against real criteria, before any of them get promoted into “trend we’re planning around” status. It’s the foundation the rest of the methodology builds on, because every later stage — the trends you map, the futures you build, the roadmap you eventually commit to — is only as good as the signals it started from.

Where to start

The free FutureHacking Signal Picker puts this exact discipline into practice, at no cost, before your next planning cycle — a genuinely useful way to arrive at your next strategy conversation with signals that have actually been tested, rather than whatever happened to come up most recently.

Something new I’m building

I’m also finishing a second tool — the FutureCanvas Picker — that carries a planning team through the full arc in one sitting: from signals, to the trends they suggest, to a genuine set of possible futures, narrowing to your most probable future, and mapping the path to your preferable one. It’s the closest thing I’ve built yet to running a complete FutureHacking™ session on your own.

I’m opening early access to a select group first — strategic planners, CSOs, and leaders actively running planning processes right now — because I want real feedback from people using it under real deadline pressure before it’s available more broadly. If that’s you, and you’d like to be considered for early access, reach out and let me know — I’ll be following up personally with the first few who get in.

Most planning cycles fail long before the strategy gets built. They fail at the moment someone mistakes a spike for a signal, and nobody in the room had a way to catch it.

Image Credits: Gemini

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Claude to clean up the article.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Remembrance, Resilience, and 911 Advances in Public Safety

1 Reply

Twenty-Five Years Later

Remembrance, Resilience, and 911 Advances in Public Safety

by Art Inteligencia

What Do We Owe the Lives Lost on September 11, 2001?

On this twenty-fifth anniversary of September 11, 2001, we begin where we must: with the people. Nearly three thousand lives were taken in New York, at the Pentagon, and in the fields of Pennsylvania — parents, children, first responders, coworkers, passengers, and neighbors. Grief does not expire on a calendar. For families and friends, love and absence still share the same quiet rooms.

We say their names because numbers alone cannot hold a human being. The National September 11 Memorial & Museum keeps those names in bronze and in living memory. What follows is offered in that spirit of remembrance — with humility, and with hope that a safer, more decent future is part of how we honor them.

This article pairs 911 public-safety and national-defense advances since 2001 with the names of those killed in the attacks (drawn from public memorial listings). Each entry ends with two to four names in parentheses — not as a footnote to technology, but as a dedication: progress in service of human life, remembered alongside human life.

If you are a family member or survivor reading today: thank you for your courage. May these pages feel like respect, not noise.

How Did a Wounded World Also Learn to Protect Life Better?

Out of horror, people still chose to build. First responders rewrote doctrine. Engineers strengthened stairwells and codes. Public servants built new agencies and warning systems. Clinicians carried battlefield lessons into civilian trauma bays. Communities practiced saying something when something felt wrong. None of that erases what was lost. It does affirm a human truth: we can refuse to let the last word belong to those who destroy.

The list below is not a claim that technology heals grief. It is a map of effort — imperfect, debated, sometimes overdue — aimed at preventing the next hard landing for civilians, responders, and service members. Soft landings for a free society require both vigilance and humanity.

911 Public-Safety and Defense Advances — Each Dedicated to the Fallen

Source for names: public 9/11 memorial victim listings (World Trade Center, Pentagon, and Flights 11, 77, 93, and 175). Innovations emphasize aviation security, first response, critical infrastructure protection, cybersecurity, trauma care, and community resilience since 2001. Some themes appear more than once as capabilities matured and spread — because real safety work is rarely a single invention; it is sustained commitment.

2,975 names are included across the 911 dedications below.

  1. Creation of the U.S. Department of Homeland Security to unify domestic security missions. (In remembrance: Gordon M. Aamoth, Jr., Edelmiro Abad, Marie Rose Abad, Andrew Anthony Abate)
  2. Transportation Security Administration (TSA) screening standards for commercial aviation. (In remembrance: Vincent Paul Abate, Laurence Christopher Abel, Alona Abraham, William F. Abrahamson)
  3. Federal Air Marshal Service expansion for in-flight security. (In remembrance: Richard Anthony Aceto, Heinrich Bernhard Ackermann, Paul Acquaviva, Christian Adams)
  4. Reinforced cockpit doors as a global commercial aviation standard. (In remembrance: Donald LaRoy Adams, Patrick Adams, Shannon Lewis Adams, Stephen George Adams)
  5. Secure Flight passenger pre-screening for watchlist matching. (In remembrance: Ignatius Udo Adanga, Christy A. Addamo, Terence Edward Adderley, Jr., Sophia B. Addo)
  6. Advanced Imaging Technology (AIT) at airport checkpoints. (In remembrance: Lee Adler, Daniel Thomas Afflitto, Emmanuel Akwasi Afuakwah, Alok Agarwal)
  7. Explosive Trace Detection (ETD) for carry-on and cargo screening. (In remembrance: Mukul Kumar Agarwala, Joseph Agnello, David Scott Agnes, Joao Alberto da Fonseca Aguiar, Jr.)
  8. Computed tomography (CT) scanners for checked-baggage explosives detection. (In remembrance: Brian G. Ahearn, Jeremiah Joseph Ahern, Joanne Marie Ahladiotis, Shabbir Ahmed)
  9. Behavioral Detection Officer programs supporting layered aviation security. (In remembrance: Terrance Andre Aiken, Godwin O. Ajala, Trudi M. Alagero, Andrew Alameno)
  10. Known Crewmember and identity-verification programs for aviation workers. (In remembrance: Margaret Ann Alario, Gary M. Albero, Jon Leslie Albert, Peter Craig Alderman)
  11. TSA PreCheck risk-based screening for trusted travelers. (In remembrance: Jacquelyn Delaine Aldridge-Frederick, David D. Alger, Ernest Alikakos, Edward L. Allegretto)
  12. Global Entry and trusted-traveler programs at ports of entry. (In remembrance: Eric Allen, Joseph Ryan Allen, Richard Dennis Allen, Richard L. Allen)
  13. Customs and Border Protection biometric entry/exit modernization. (In remembrance: Christopher E. Allingham, Anna S. W. Allison, Janet Marie Alonso, Anthony Alvarado)
  14. Container Security Initiative for overseas cargo risk screening. (In remembrance: Antonio Javier Alvarez, Victoria Alvarez-Brito, Telmo E. Alvear, Cesar Amoranto Alviar)
  15. Customs-Trade Partnership Against Terrorism (C-TPAT) supply-chain security. (In remembrance: Tariq Amanullah, Angelo Amaranto, James M. Amato, Joseph Amatuccio)
  16. National Targeting Center analytics for cargo and traveler risk. (In remembrance: Paul W. Ambrose, Christopher Charles Amoroso, Craig Scott Amundson, Kazuhiro Anai)
  17. Fusion centers linking federal, state, and local threat information. (In remembrance: Calixto Anaya, Jr., Joseph P. Anchundia, Kermit Charles Anderson, Yvette Constance Anderson)
  18. Nationwide Suspicious Activity Reporting (SAR) initiatives. (In remembrance: John Jack Andreacchio, Michael Rourke Andrews, Jean Ann Andrucki, Siew-Nya Ang)
  19. If You See Something, Say Something public vigilance campaigns. (In remembrance: Joseph Angelini, Sr., Joseph John Angelini, Jr., David Lawrence Angell, Mary Lynn Edwards Angell)
  20. National Incident Management System (NIMS) for multi-agency response. (In remembrance: Laura Angilletta, Doreen J. Angrisani, Lorraine Antigua, Seima David Aoyama)
  21. Incident Command System (ICS) standardization across first responders. (In remembrance: Peter Paul Apollo, Faustino Apostol, Jr., Frank Thomas Aquilino, Patrick Michael Aranyos)
  22. National Response Framework for coordinated disaster operations. (In remembrance: David Gregory Arce, Michael George Arczynski, Louis Arena, Barbara Jean Arestegui)
  23. FEMA modernization of disaster logistics and mutual aid. (In remembrance: Adam P. Arias, Michael J. Armstrong, Jack Charles Aron, Joshua Todd Aron)
  24. Urban Search and Rescue (US&R) task-force capability expansion. (In remembrance: Richard Avery Aronow, Myra Joy Aronson, Japhet Jesse Aryee, Carl Francis Asaro)
  25. Interoperable radio and FirstNet public-safety broadband for responders. (In remembrance: Michael A. Asciak, Michael Edward Asher, Janice Marie Ashley, Thomas J. Ashton)
  26. Next Generation 911 (NG911) for text, location, and multimedia emergency calls. (In remembrance: Manuel O. Asitimbay, Gregg A. Atlas, Gerald Thomas Atwood, James Audiffred)
  27. Wireless Emergency Alerts (WEA) for mobile public warning. (In remembrance: Louis F. Aversano, Jr., Ezra Aviles, Sandy Ayala, Arlene T. Babakitis)
  28. Integrated Public Alert and Warning System (IPAWS). (In remembrance: Eustace R. Bacchus, John J. Badagliacca, Jane Ellen Baeszler, Robert J. Baierwalter)
  29. Enhanced 911 location accuracy for mobile callers. (In remembrance: Andrew J. Bailey, Brett T. Bailey, Garnet Ace Bailey, Tatyana Bakalinskaya)
  30. Automatic Vehicle Location (AVL) for fire and EMS dispatch. (In remembrance: Michael S. Baksh, Sharon M. Balkcom, Michael Andrew Bane, Katherine Bantis)
  31. Computer-Aided Dispatch (CAD) modernization for emergency services. (In remembrance: Gerard Baptiste, Walter Baran, Gerard A. Barbara, Paul Vincent Barbaro)
  32. Body-worn cameras with evidence-management workflows for accountability. (In remembrance: James William Barbella, Victor Daniel Barbosa, Christine Johnna Barbuto, Colleen Ann Barkow)
  33. License plate reader analytics used under policy for investigations. (In remembrance: David Michael Barkway, Matthew Barnes, Melissa Rose Barnes, Sheila Patricia Barnes)
  34. ShotSpotter and acoustic gunshot detection networks in cities. (In remembrance: Evan Jay Baron, Renee Barrett-Arjune, Arthur Thaddeus Barry, Diane G. Barry)
  35. Crime-mapping and real-time crime center platforms for police. (In remembrance: Maurice Vincent Barry, Scott D. Bart, Carlton W. Bartels, Guy Barzvi)
  36. Portable X-ray and robotics for bomb squad render-safe operations. (In remembrance: Inna B. Basina, Alysia Christine Burton Basmajian, Kenneth William Basnicki, Steven Joseph Bates)
  37. Advanced bomb suits and disruptor tools for EOD teams. (In remembrance: Paul James Battaglia, W. David Bauer, Ivhan Luis Carpio Bautista, Marlyn Capito Bautista)
  38. Biometric identity systems for watchlisting and credentialing. (In remembrance: Mark Lawrence Bavis, Jasper Baxter, Lorraine G. Bay, Michele Beale)
  39. FBI Next Generation Identification (NGI) biometric services. (In remembrance: Todd M. Beamer, Paul Frederick Beatini, Jane S. Beatty, Alan Anthony Beaven)
  40. Terrorist Screening Center watchlist operational improvements. (In remembrance: Lawrence Ira Beck, Manette Marie Beckles, Carl John Bedigian, Michael Ernest Beekman)
  41. No-Fly List and Selectee List process refinements with redress pathways. (In remembrance: Maria A. Behr, Max J. Beilke, Yelena Belilovsky, Nina Patrice Bell)
  42. Visa security and Student and Exchange Visitor Program oversight upgrades. (In remembrance: Debbie S. Bellows, Stephen Elliot Belson, Paul M. Benedetti, Denise Lenore Benedetto)
  43. US-VISIT / biometric border systems evolution. (In remembrance: Bryan Craig Bennett, Eric L. Bennett, Oliver Bennett, Margaret L. Benson)
  44. REAL ID Act identity standards for state-issued credentials. (In remembrance: Dominick J. Berardi, James Patrick Berger, Steven Howard Berger, John P. Bergin)
  45. Chemical Facility Anti-Terrorism Standards (CFATS). (In remembrance: Alvin Bergsohn, Daniel David Bergstein, Graham Andrew Berkeley, Michael J. Berkeley)
  46. Protective Security Advisor programs for critical infrastructure. (In remembrance: Donna M. Bernaerts, David W. Bernard, William H. Bernstein, David M. Berray)
  47. National Infrastructure Protection Plan sector partnership model. (In remembrance: David Shelby Berry, Joseph John Berry, William Reed Bethke, Yeneneh Betru)
  48. Cybersecurity and Infrastructure Security Agency (CISA) establishment. (In remembrance: Timothy D. Betterly, Carolyn Mayer Beug, Edward Frank Beyea, Paul Michael Beyer)
  49. National Cybersecurity Protection System and Einstein intrusion detection. (In remembrance: Anil Tahilram Bharvaney, Bella J. Bhukhan, Shimmy D. Biegeleisen, Peter Alexander Bielfeld)
  50. Continuous Diagnostics and Mitigation (CDM) for federal networks. (In remembrance: William G. Biggart, Brian Eugene Bilcher, Mark Bingham, Carl Vincent Bini)
  51. Binding Operational Directives for federal cyber hygiene. (In remembrance: Gary Eugene Bird, Joshua David Birnbaum, George John Bishop, Kris Romeo Bishundat)
  52. Election infrastructure security designation and support. (In remembrance: Jeffrey Donald Bittner, Albert Balewa Blackman, Jr., Christopher Joseph Blackwell, Carrie Rosetta Blagburn)
  53. Industrial control system (ICS/SCADA) security guidance for utilities. (In remembrance: Susan Leigh Blair, Harry Blanding, Jr., Janice Lee Blaney, Craig Michael Blass)
  54. Maritime Transportation Security Act port and vessel security regimes. (In remembrance: Rita Blau, Richard Middleton Blood, Jr., Michael Andrew Boccardi, John Paul Bocchi)
  55. Transportation Worker Identification Credential (TWIC). (In remembrance: Michael L. Bocchino, Susan M. Bochino, Deora Frances Bodley, Bruce Douglas Boehm)
  56. Automatic Identification System (AIS) vessel tracking for maritime awareness. (In remembrance: Mary Catherine Murphy-Boffa, Nicholas Andrew Bogdan, Darren Christopher Bohan, Lawrence Francis Boisseau)
  57. Coast Guard Maritime Security Response Team capabilities. (In remembrance: Vincent M. Boland, Jr., Touri Hamzavi Bolourchi, Alan Bondarenko, Andre Bonheur, Jr.)
  58. Radiation portal monitors at seaports and border crossings. (In remembrance: Colin Arthur Bonnett, Frank J. Bonomo, Yvonne Lucia Bonomo, Sean Booker, Sr.)
  59. Nuclear detection architecture for illicit radiological materials. (In remembrance: Kelly Ann Booms, Canfield D. Boone, Mary Jane Booth, Sherry Ann Bordeaux)
  60. BioWatch environmental monitoring for biological threat agents. (In remembrance: Krystine Bordenabe, Jerry J. Borg, Martin Michael Boryczewski, Richard Edward Bosco)
  61. Strategic National Stockpile modernization for medical countermeasures. (In remembrance: Klaus Bothe, Carol Marie Bouchard, J. Howard Boulton, Francisco Eligio Bourdier)
  62. Cities Readiness Initiative for mass prophylaxis distribution. (In remembrance: Thomas Harold Bowden, Jr., Donna M. Bowen, Kimberly S. Bowers, Veronique Nicole Bowers)
  63. Hospital surge and trauma system planning after mass-casualty lessons. (In remembrance: Larry Bowman, Shawn Edward Bowman, Jr., Kevin L. Bowser, Gary R. Box)
  64. Tactical Combat Casualty Care (TCCC) principles adapted to civilian EMS. (In remembrance: Gennady Boyarsky, Pamela Boyce, Allen P. Boyle, Michael Boyle)
  65. Stop the Bleed public hemorrhage-control training and kits. (In remembrance: Alfred J. Braca, Sandra Conaty Brace, Kevin Hugh Bracken, Sandy Waugh Bradshaw)
  66. Tourniquet and hemostatic dressing standards for first responders. (In remembrance: David Brian Brady, Alexander Braginsky, Nicholas W. Brandemarti, Daniel Raymond Brandhorst)
  67. Improved structural collapse rescue tools and shoring techniques. (In remembrance: David Reed Gamboa Brandhorst, Michelle Renee Bratton, Patrice Braut, Lydia Estelle Bravo)
  68. Firefighter accountability and PASS device improvements. (In remembrance: Ronald Michael Breitweiser, Edward A. Brennan III, Frank H. Brennan, Michael E. Brennan)
  69. Self-contained breathing apparatus (SCBA) and thermal imaging advances. (In remembrance: Peter Brennan, Thomas More Brennan, Daniel J. Brethel, Gary Lee Bright)
  70. Building code updates for high-rise egress, stairwell, and fireproofing. (In remembrance: Jonathan Eric Briley, Mark A. Brisman, Paul Gary Bristow, Marion R. Britton)
  71. NYC Local Law high-rise safety reforms after WTC investigations. (In remembrance: Mark Francis Broderick, Herman Charles Broghammer, Keith A. Broomfield, Bernard C. Brown II)
  72. NIST World Trade Center investigation recommendations for structural safety. (In remembrance: Janice Juloise Brown, Lloyd Stanford Brown, Patrick John Brown, Bettina B. Browne-Radburn)
  73. Progressive collapse design awareness in tall-building engineering. (In remembrance: Mark Bruce, Richard George Bruehert, Andrew Brunn, Vincent Edward Brunton)
  74. Impact-resistant glazing and progressive façade safety research. (In remembrance: Ronald Bucca, Brandon J. Buchanan, Greg J. Buck, Dennis Buckley)
  75. Elevator recall and firefighter emergency operation refinements. (In remembrance: Nancy Clare Bueche, Patrick Joseph Buhse, John Edward Bulaga, Jr., Stephen Bruce Bunin)
  76. Refuge floors and phased evacuation planning in skyscraper design. (In remembrance: Christopher L. Burford, Matthew J. Burke, Thomas Daniel Burke, William Francis Burke, Jr.)
  77. Active shooter preparedness curricula for schools and workplaces. (In remembrance: Charles F. Burlingame III, Thomas E. Burnett, Jr., Donald J. Burns, Kathleen Anne Burns)
  78. Run-Hide-Fight and ALICE-informed civilian response education. (In remembrance: Keith James Burns, John Patrick Burnside, Irina Buslo, Milton G. Bustillo)
  79. School soft-target hardening: controlled entry and visitor management. (In remembrance: Thomas M. Butler, Patrick Dennis Byrne, Timothy G. Byrne, Daniel M. Caballero)
  80. Stadium and large-venue security screening architectures. (In remembrance: Jesus Neptali Cabezas, Lillian Caceres, Brian Joseph Cachia, Steven Dennis Cafiero, Jr.)
  81. Explosive detection canine program expansion. (In remembrance: Richard Michael Caggiano, Cecile Marella Caguicla, John Brett Cahill, Michael John Cahill)
  82. Homemade explosive (HME) recognition training for responders. (In remembrance: Scott Walter Cahill, Thomas Joseph Cahill, George C. Cain, Salvatore B. Calabro)
  83. Counter-IED route clearance and vehicle-borne IED defense methods. (In remembrance: Joseph M. Calandrillo, Philip V. Calcagno, Edward Calderon, Jose O. Calderon-Olmedo)
  84. MRAP and blast-resistant vehicle lessons applied to force protection. (In remembrance: Kenneth Marcus Caldwell, Dominick E. Calia, Felix Bobby Calixte, Francis Joseph Callahan)
  85. Improved body armor and trauma plate systems for troops and police. (In remembrance: Liam Callahan, Suzanne M. Calley, Gino Luigi Calvi, Roko Camaj)
  86. Night-vision and sensor fusion for base and border protection. (In remembrance: Michael F. Cammarata, David Otey Campbell, Geoffrey Thomas Campbell, Robert Arthur Campbell)
  87. Unmanned aerial systems for border and disaster situational awareness. (In remembrance: Sandra Patricia Campbell, Sean Thomas Canavan, John A. Candela, Vincent A. Cangelosi)
  88. Counter-UAS detection and mitigation for airports and critical sites. (In remembrance: Stephen J. Cangialosi, Lisa Bella Cannava, Brian Cannizzaro, Michael R. Canty)
  89. Persistent ISR and wide-area airborne surveillance concepts. (In remembrance: Louis Anthony Caporicci, Jonathan Neff Cappello, James Christopher Cappers, Richard Michael Caproni)
  90. Predator/Reaper-class remotely piloted aircraft for overwatch missions. (In remembrance: Jose Manuel Cardona, Dennis M. Carey, Sr., Edward Carlino, Michael Scott Carlo)
  91. Precision munitions reducing collateral damage in counterterror operations. (In remembrance: David G. Carlone, Rosemarie C. Carlson, Mark Stephen Carney, Joyce Ann Carpeneto)
  92. Special Operations joint task force integration models. (In remembrance: Jeremy Caz Carrington, Michael T. Carroll, Peter J. Carroll, James Joseph Carson, Jr.)
  93. Joint Terrorism Task Forces (JTTF) expansion nationwide. (In remembrance: Christoffer Mikael Carstanjen, Angelene C. Carter, James Marcel Cartier, Sharon Ann Carver)
  94. Terrorism Liaison Officer programs for local agencies. (In remembrance: Vivian Casalduc, John Francis Casazza, Paul Regan Cascio, Neilie Anne Heffernan Casey)
  95. Open-source intelligence (OSINT) tradecraft for threat monitoring. (In remembrance: William Joseph Cashman, Thomas Anthony Casoria, William Otto Caspar, Alejandro Castaño)
  96. Social media exploitation cells for investigative leads (with legal process). (In remembrance: Arcelia Castillo, Leonard M. Castrianno, Jose Ramon Castro, William E. Caswell)
  97. Financial intelligence and terrorist financing disruption (FinCEN/OFAC tools). (In remembrance: Richard G. Catarelli, Christopher Sean Caton, Robert John Caufield, Mary Teresa Caulfield)
  98. SWIFT and banking compliance analytics against illicit finance. (In remembrance: Judson Cavalier, Michael Joseph Cawley, Jason David Cayne, Juan Armando Ceballos)
  99. Charity and NGO abuse detection for terror finance prevention. (In remembrance: Marcia G. Cecil-Carter, Jason Michael Cefalu, Thomas Joseph Celic, Ana Mercedes Centeno)
  100. Passenger Name Record (PNR) analytics with privacy safeguards. (In remembrance: Joni Cesta, John J. Chada, Jeffrey Marc Chairnoff, Swarna Chalasani)
  101. API/PNR advance passenger information systems. (In remembrance: William A. Chalcoff, Eli Chalouh, Charles Lawrence Chan, Mandy Chang)
  102. INTERPOL Stolen and Lost Travel Documents database wider use. (In remembrance: Rosa Maria Chapa, Mark Lawrence Charette, David M. Charlebois, Gregorio Manuel Chavez)
  103. ePassports and RFID chip identity documents. (In remembrance: Pedro Francisco Checo, Douglas MacMillan Cherry, Stephen Patrick Cherry, Vernon Paul Cherry)
  104. Facial recognition for watchlist matching at controlled borders. (In remembrance: Nestor Julio Chevalier, Jr., Swede Joseph Chevalier, Alexander H. Chiang, Dorothy J. Chiarchiaro)
  105. Iris and multimodal biometrics for high-security identity proofing. (In remembrance: Luis Alfonso Chimbo, Robert Chin, Eddie Wing-Wai Ching, Nicholas Paul Chiofalo)
  106. Mobile driver’s license and digital ID pilots with security controls. (In remembrance: John G. Chipura, Peter A. Chirchirillo, Catherine Ellen Chirls, Kyung Hee Casey Cho)
  107. Cloud-based emergency operations center (EOC) collaboration platforms. (In remembrance: Abul K. Chowdhury, Mohammad Salahuddin Chowdhury, Kirsten Lail Christophe, Pamela Chu)
  108. WebEOC and common operating picture systems for incidents. (In remembrance: Steven Paul Chucknick, Wai Ching Chung, Christopher Ciafardini, Alex F. Ciccone)
  109. Drone-based damage assessment after disasters and attacks. (In remembrance: Frances Ann Cilente, Elaine Cillo, Patricia Ann Cimaroli Massari, Edna Cintron)
  110. Satellite rapid mapping for incident commanders. (In remembrance: Nestor Andre Cintron III, Robert D. Cirri, Sr., Juan Pablo Cisneros, Benjamin Keefe Clark)
  111. GIS-based critical infrastructure dependency mapping. (In remembrance: Eugene Clark, Gregory Alan Clark, Mannie Leroy Clark, Sara M. Clark)
  112. Resilient power microgrids for hospitals and emergency facilities. (In remembrance: Thomas R. Clark, Christopher Robert Clarke, Donna Marie Clarke, Michael J. Clarke)
  113. Backup communications: satellite phones and mesh radio for blackouts. (In remembrance: Suria Rachel Emma Clarke, Kevin Francis Cleary, James D. Cleere, Geoffrey W. Cloud)
  114. Hardened data centers and continuity-of-operations (COOP) planning. (In remembrance: Susan Marie Clyne, Steven Coakley, Jeffrey Alan Coale, Patricia A. Cody)
  115. Continuity of Government and Continuity of Operations playbooks. (In remembrance: Daniel Michael Coffey, Jason Matthew Coffey, Florence G. Cohen, Kevin S. Cohen)
  116. Private-sector information sharing (ISACs) for critical industries. (In remembrance: Anthony Joseph Coladonato, Mark Joseph Colaio, Stephen J. Colaio, Christopher Michael Colasanti)
  117. Aviation ISAC and sector cyber threat sharing. (In remembrance: Kevin Nathaniel Colbert, Michel P. Colbert, Keith E. Coleman, Scott Thomas Coleman)
  118. Financial Services ISAC threat intelligence distribution. (In remembrance: Tarel Coleman, Liam Joseph Colhoun, Robert D. Colin, Robert J. Coll)
  119. Health-ISAC coordination for hospital cybersecurity. (In remembrance: Jean Marie Collin, John Michael Collins, Michael L. Collins, Thomas Joseph Collins)
  120. Multi-factor authentication mandates for privileged government access. (In remembrance: Joseph Kent Collison, Jeffrey Dwayne Collman, Patricia Malia Colodner, Linda M. Colon)
  121. Zero-trust network architecture adoption in federal IT. (In remembrance: Sol E. Colon, Ronald Edward Comer, Jaime Concepcion, Albert Conde)
  122. Endpoint detection and response (EDR) at national scale. (In remembrance: Denease Conley, Susan P. Conlon, Margaret Mary Conner, Cynthia Marie Lise Connolly)
  123. Security orchestration, automation, and response (SOAR) platforms. (In remembrance: John E. Connolly, Jr., James Lee Connor, Jonathan M. Connors, Kevin Patrick Connors)
  124. Threat intelligence platforms (TIP) for analyst collaboration. (In remembrance: Kevin F. Conroy, Brenda E. Conway, Dennis Michael Cook, Helen D. Cook)
  125. Malware reverse-engineering labs for nation-state and terror-linked tools. (In remembrance: Jeffrey W. Coombs, John A. Cooper, Julian T. Cooper, Joseph John Coppo, Jr.)
  126. Ransomware response playbooks for cities and hospitals. (In remembrance: Gerard J. Coppola, Joseph Albert Corbett, John J. Corcoran III, Alejandro Cordero)
  127. Election security risk-limiting audits and paper-ballot resilience. (In remembrance: Robert Joseph Cordice, Ruben D. Correa, Danny A. Correa-Gutierrez, Georgine Rose Corrigan)
  128. Deepfake detection research for influence-operation defense. (In remembrance: James J. Corrigan, Ret., Carlos Cortés-Rodriguez, Kevin Michael Cosgrove, Dolores Marie Costa)
  129. Content provenance and watermarking research for media authenticity. (In remembrance: Digna Alexandra Costanza, Charles Gregory Costello, Jr., Michael S. Costello, Asia S. Cottom)
  130. Secure software development frameworks (e.g., SSDF) for vendors. (In remembrance: Conrod Kofi Cottoy, Sr., Martin John Coughlan, John G. Coughlin, Timothy J. Coughlin)
  131. Software bill of materials (SBOM) transparency for supply-chain risk. (In remembrance: James E. Cove, Andre Colin Cox, Frederick John Cox, James Raymond Coyle)
  132. Hardware root-of-trust and secure boot for critical devices. (In remembrance: Michele Coyle-Eulau, Christopher Seton Cramer, Eric A. Cranford, Denise Elizabeth Crant)
  133. 5G security frameworks for public-safety broadband. (In remembrance: James Leslie Crawford, Jr., Robert James Crawford, Tara Kathleen Creamer, Joanne Mary Cregan)
  134. Mission-critical push-to-talk over LTE/5G for responders. (In remembrance: Lucia Crifasi, John A. Crisci, Daniel Hal Crisman, Dennis A. Cross)
  135. Wearable physiological monitoring for firefighters in IDLH atmospheres. (In remembrance: Kevin R. Crotty, Thomas G. Crotty, John R. Crowe, Welles Remy Crowther)
  136. Exoskeleton research for stretcher and rubble-lift assistance. (In remembrance: Robert L. Cruikshank, John Robert Cruz, Grace Alegre Cua, Kenneth John Cubas)
  137. Robotic casualty extraction concepts for denied environments. (In remembrance: Francisco Cruz Cubero, Thelma Cuccinello, Richard Joseph Cudina, Neil James Cudmore)
  138. AI-assisted triage research for mass-casualty incidents. (In remembrance: Thomas Patrick Cullen III, Joan Cullinan, Joyce Rose Cummings, Brian Thomas Cummins)
  139. Portable ultrasound and point-of-care diagnostics in field medicine. (In remembrance: Michael Joseph Cunningham, Robert Curatolo, Laurence Damian Curia, Paul Dario Curioli)
  140. Blood product and freeze-dried plasma advances for trauma. (In remembrance: Patrick Joseph Currivan, Beverly L. Curry, Andrew Peter Charles Curry Green, Michael Sean Curtin)
  141. REBOA and advanced hemorrhage control in trauma centers. (In remembrance: Patricia Cushing, Gavin Cushny, Caleb Arron Dack, Carlos S. da Costa)
  142. Burn care and skin-substitute advances informed by mass-casualty planning. (In remembrance: Jason M. Dahl, Brian Paul Dale, John D’Allara, Vincent Gerard D’Amadeo)
  143. Behavioral health programs for first-responder PTSD and grief. (In remembrance: Thomas A. Damaskinos, Jack L. D’Ambrosi, Jr., Jeannine Damiani-Jones, Manuel João DaMota)
  144. Peer support and critical incident stress management modernization. (In remembrance: Patrick W. Danahy, Mary D’Antonio, Vincent G. Danz, Dwight Donald Darcy)
  145. Family assistance center models refined after large disasters. (In remembrance: Elizabeth Ann Darling, Annette Andrea Dataram, Edward A. D’Atri, Michael D. D’Auria)
  146. Victim identification via DNA kinship analysis at scale. (In remembrance: Lawrence Davidson, Michael Allen Davidson, Scott Matthew Davidson, Titus Davidson)
  147. Rapid DNA instruments for disaster victim identification. (In remembrance: Niurka Davila, Ada M. Davis, Clinton Davis, Sr., Wayne Terrial Davis)
  148. NamUs and missing-persons forensic databases. (In remembrance: Anthony Richard Dawson, Calvin Dawson, Edward James Day, William Thomas Dean)
  149. Mass fatality management planning for medical examiners. (In remembrance: Robert J. DeAngelis, Jr., Thomas Patrick DeAngelis, Dorothy Alma de Araujo, Ana Gloria Pocasangre Debarrera)
  150. Public-private emergency logistics (retail/pharmacy distribution partners). (In remembrance: Tara E. Debek, James D. Debeuneure, Anna M. DeBin, James V. DeBlase, Jr.)
  151. Cashless and remote banking continuity after infrastructure shocks. (In remembrance: Jayceryll Malabuyoc de Chavez, Paul DeCola, Gerald F. DeConto, Simon Marash Dedvukaj)
  152. Telemedicine surge capacity for displaced populations. (In remembrance: Jason Christopher DeFazio, David A. DeFeo, Jennifer De Jesus, Monique Effie DeJesus)
  153. Remote learning continuity frameworks after campus closures/attacks. (In remembrance: Nereida De Jesus, Emy De La Peña, Donald Arthur Delapenha, Azucena Maria de la Torre)
  154. Hardened classroom locks and reunification protocols for schools. (In remembrance: Vito Joseph DeLeo, Danielle Anne Delie, Andrea DellaBella, Joseph A. Della Pietra)
  155. Anonymous tip lines and See Something apps for campuses. (In remembrance: Palmina DelliGatti, Colleen Ann Deloughery, Joseph DeLuca, Manuel Del Valle, Jr.)
  156. Behavioral threat assessment teams in schools and workplaces. (In remembrance: Francis Albert De Martini, Anthony Demas, Martin N. DeMeo, Francis Deming)
  157. Workplace violence prevention standards and training. (In remembrance: Carol Keyes Demitz, Kevin Dennis, Thomas Francis Dennis, Sr., Jean C. DePalma)
  158. Hotel and hospitality security training after soft-target attacks. (In remembrance: Jose Nicolas De Pena, Robert John Deraney, Michael DeRienzo, David Paul DeRubbio)
  159. House of worship security grant and training programs. (In remembrance: Jemal Legesse DeSantis, Christian Louis DeSimone, Edward DeSimone III, Andrew J. Desperito)
  160. Nonprofit security grants for vulnerable community sites. (In remembrance: Michael Jude D’Esposito, Cindy Ann Deuel, Melanie Louise de Vere, Jerry DeVito)
  161. Transit security: random bag checks and K9 teams in metros. (In remembrance: Robert P. Devitt, Jr., Dennis Lawrence Devlin, Gerard P. Dewan, Sulemanali Kassamali Dhanani)
  162. Railcar and tunnel fire/life-safety modernization. (In remembrance: Michael Louis DiAgostino, Matthew Diaz, Nancy Diaz, Obdulio Ruiz Diaz)
  163. Bridge and tunnel surveillance with intrusion detection. (In remembrance: Michael A. Diaz-Piedra III, Judith Berquis Diaz-Sierra, Patricia Florence Di Chiaro, Rodney Dickens)
  164. Pipeline and energy corridor monitoring sensors. (In remembrance: Jerry D. Dickerson, Joseph Dermot Dickey, Jr., Lawrence Patrick Dickinson, Michael D. Diehl)
  165. Smart grid anomaly detection for physical-cyber threats. (In remembrance: John Difato, Vincent Francis DiFazio, Carl Anthony DiFranco, Donald Joseph DiFranco)
  166. Water utility contamination detection and response protocols. (In remembrance: Eddie A. Dillard, Debra Ann Di Martino, David DiMeglio, Stephen Patrick Dimino)
  167. Laboratory Response Network for biological threat confirmation. (In remembrance: William John Dimmling, Marisa Dinardo Schorpp, Christopher More Dincuff, Jeffrey Mark Dingle)
  168. CDC quarantine station modernization at ports of entry. (In remembrance: Rena Sam Dinnoo, Anthony Dionisio, George DiPasquale, Joseph Di Pilato)
  169. Passenger contact-tracing protocols refined after health emergencies. (In remembrance: Douglas Frank DiStefano, Donald Americo DiTullio, Ramzi A. Doany, Johnnie Doctor, Jr.)
  170. N95 and respirator stockpile management lessons. (In remembrance: John Joseph Doherty, Melissa Cándida Doi, Brendan Dolan, Robert E. Dolan, Jr.)
  171. PPE surge manufacturing partnerships for national emergencies. (In remembrance: Neil Matthew Dollard, James Domanico, Benilda Pascua Domingo, Alberto Dominguez)
  172. Military dual-use logistics for domestic disaster support (DSCA). (In remembrance: Carlos Dominguez, Jerome Mark Patrick Dominguez, Kevin W. Donnelly, Jacqueline Donovan)
  173. National Guard civil support team (WMD-CST) readiness. (In remembrance: William H. Donovan, Stephen Scott Dorf, Thomas Dowd, Kevin Christopher Dowdell)
  174. CERFP and HRF CBRN response force packages. (In remembrance: Mary Yolanda Dowling, Raymond Matthew Downey, Sr., Frank Joseph Doyle, Joseph Michael Doyle)
  175. Civil Support Team analytical laboratory systems. (In remembrance: Randall L. Drake, Patrick Joseph Driscoll, Stephen Patrick Driscoll, Charles A. Droz III)
  176. Portable mass spectrometers for chemical identification. (In remembrance: Mirna A. Duarte, Luke A. Dudek, Christopher Michael Duffy, Gerard J. Duffy)
  177. FTIR and Raman handheld identifiers for hazmat teams. (In remembrance: Michael Joseph Duffy, Thomas W. Duffy, Antoinette Duger, Jackie Sayegh Duggan)
  178. Level A/B hazmat suit and decontamination corridor improvements. (In remembrance: Sareve Dukat, Patrick Dunn, Felicia Gail Dunn-Jones, Christopher Joseph Dunne)
  179. Foam and clean-agent firefighting for aircraft rescue (ARFF). (In remembrance: Richard Anthony Dunstan, Patrick Thomas Dwyer, Joseph Anthony Eacobacci, John Bruce Eagleson)
  180. Airport rescue and firefighting vehicle modernization. (In remembrance: Edward T. Earhart, Robert Douglas Eaton, Dean Phillip Eberling, Margaret Ruth Echtermann)
  181. Runway status lights and airport surface surveillance (ASDE-X/ASSC). (In remembrance: Paul Robert Eckna, Constantine Economos, Barbara G. Edwards, Dennis Michael Edwards)
  182. ADS-B air traffic surveillance improving situational awareness. (In remembrance: Michael Hardy Edwards, Christine Egan, Lisa Erin Egan, Martin J. Egan, Jr.)
  183. Unruly passenger enforcement and cabin crew security training. (In remembrance: Michael Egan, Samantha Martin Egan, Carole Eggert, Lisa Caren Ehrlich)
  184. Secondary cockpit barriers beyond the flight deck door. (In remembrance: John Ernst Eichler, Eric Adam Eisenberg, Daphne Ferlinda Elder, Michael J. Elferis)
  185. Flight crew self-defense and security curriculum updates. (In remembrance: Mark Joseph Ellis, Valerie Silver Ellis, Albert Alfy William Elmarry, Robert R. Elseth)
  186. Airline cybersecurity programs protecting operational technology. (In remembrance: Edgar Hendricks Emery, Jr., Doris Suk-Yuen Eng, Christopher Epps, Ulf Ramm Ericson)
  187. Airport perimeter intrusion detection systems. (In remembrance: Erwin L. Erker, William John Erwin, Sarah Ali Escarcega, Jose Espinal)
  188. Credential Authentication Technology (CAT) at TSA checkpoints. (In remembrance: Fanny Espinoza, Billy Scoop Esposito, Bridget Ann Esposito, Francis Esposito)
  189. CT scanners for carry-on bags reducing bag checks while raising detection. (In remembrance: Michael A. Esposito, Ruben Esquilin, Jr., Sadie Ette, Barbara G. Etzold)
  190. Algorithmic anomaly detection for checked-baggage images. (In remembrance: Eric Brian Evans, Robert Edward Evans, Meredith Emily June Ewart, Catherine K. Fagan)
  191. Liquid explosives detection research after aviation plots. (In remembrance: Patricia Mary Fagan, Ivan Kyrillos Fairbanks-Barbosa, Keith George Fairben, Sandra Fajardo-Smith)
  192. Shoe scanning and footwear policy evolution based on threat intel. (In remembrance: Charles S. Falkenberg, Dana Falkenberg, Zoe Falkenberg, Jamie L. Fallon)
  193. Cargo screening mandates for passenger aircraft holds. (In remembrance: William F. Fallon, William Lawrence Fallon, Jr., Anthony J. Fallone, Jr., Dolores Brigitte Fanelli)
  194. Known Shipper / Certified Cargo Screening Programs. (In remembrance: Robert John Fangman, John Joseph Fanning, Kathleen Anne Faragher, Thomas James Farino)
  195. Air cargo advance electronic information requirements. (In remembrance: Nancy C. Doloszycki Farley, Paige Marie Farley-Hackel, Elizabeth Ann Farmer, Douglas Jon Farnum)
  196. General aviation security awareness and LASP programs. (In remembrance: John Gerard Farrell, John W. Farrell, Terrence Patrick Farrell, Joseph D. Farrelly)
  197. Flight school candidate screening enhancements. (In remembrance: Thomas Patrick Farrelly, Syed Abdul Fatha, Christopher Edward Faughnan, Wendy R. Faulkner)
  198. UAV registration and remote ID for airspace accountability. (In remembrance: Shannon Marie Fava, Bernard D. Favuzza, Robert Fazio, Jr., Ronald Carl Fazio, Sr.)
  199. Temporary Flight Restrictions (TFR) tooling for national special events. (In remembrance: William M. Feehan, Francis Jude Feely, Garth Erin Feeney, Sean Bernard Fegan)
  200. National Special Security Event (NSSE) planning playbooks. (In remembrance: Lee S. Fehling, Peter Adam Feidelberg, Alan D. Feinberg, Rosa Maria Feliciano)
  201. Secret Service magnetometer and K9 screening for protectees. (In remembrance: Edward P. Felt, Edward Thomas Fergus, Jr., George J. Ferguson III, J. Joseph Ferguson)
  202. White House and campus vehicle barrier (anti-ram) standards. (In remembrance: Henry Fernandez, Judy Hazel Santillan Fernandez, Julio Fernandez, Elisa Giselle Ferraina)
  203. Pop-up vehicle barriers for temporary event protection. (In remembrance: Anne Marie Sallerin Ferreira, Robert John Ferris, David Francis Ferrugio, Louis V. Fersini, Jr.)
  204. Blast-resistant trash receptacles in transit hubs. (In remembrance: Michael David Ferugio, Bradley James Fetchet, Jennifer Louise Fialko, Kristen Nicole Fiedel)
  205. Crime Prevention Through Environmental Design (CPTED) in public plazas. (In remembrance: Amelia V. Fields, Samuel Fields, Alexander Milan Filipov, Michael Bradley Finnegan)
  206. Hostile vehicle mitigation landscaping and bollard design guides. (In remembrance: Timothy J. Finnerty, Michael C. Fiore, Stephen J. Fiorelli, Paul M. Fiori)
  207. Glass fragment retention film for blast and storm protection. (In remembrance: John B. Fiorito, John R. Fischer, Andrew Fisher, Bennett Lawson Fisher)
  208. Safe rooms and shelter-in-place standards for tornadoes and attacks. (In remembrance: Gerald P. Fisher, John Roger Fisher, Thomas J. Fisher, Lucy A. Fishman)
  209. Earthquake early warning systems (ShakeAlert) as dual-use alerting. (In remembrance: Ryan D. Fitzgerald, Thomas James Fitzpatrick, Richard P. Fitzsimons, Salvatore Fiumefreddo)
  210. Multi-hazard early warning integrating weather, quake, and security. (In remembrance: Darlene E. Flagg, Wilson F. Flagg, Christina Donovan Flannery, Eileen Flecha)
  211. Crowdsourced damage reporting apps for emergency managers. (In remembrance: Andre G. Fletcher, Carl M. Flickinger, Matthew M. Flocco, John Joseph Florio)
  212. Social media listening for emergency public information officers. (In remembrance: Joseph Walkden Flounders, Carol Ann Flyzik, David Fodor, Michael N. Fodor)
  213. Verified official alert accounts to combat rumor during crises. (In remembrance: Stephen Mark Fogel, Thomas J. Foley, Jane C. Folger, David J. Fontana)
  214. Rumor control and crisis communications playbooks. (In remembrance: Chih Min Foo, Delrose E. Forbes Cheatham, Godwin Forde, Donald A. Foreman)
  215. Multilingual emergency messaging for diverse communities. (In remembrance: Christopher Hugh Forsythe, Claudia Alicia Foster, Noel John Foster, Sandra N. Foster)
  216. Accessibility: visual/ vibrating alert devices for deaf/hard-of-hearing. (In remembrance: Ana Fosteris, Robert Joseph Foti, Jeffrey Fox, Virginia Elizabeth Fox)
  217. ADA-aware evacuation chair and refuge area standards. (In remembrance: Pauline Francis, Virgin Lucy Francis, Gary Jay Frank, Morton H. Frank)
  218. Pet and service-animal evacuation planning in disasters. (In remembrance: Peter Christopher Frank, Colleen L. Fraser, Richard K. Fraser, Kevin J. Frawley)
  219. Family reunification systems after mass displacement. (In remembrance: Clyde Frazier, Jr., Lillian Inez Frederick, Andrew Fredericks, Tamitha Freeman)
  220. Red Cross Safe and Well / digital check-in platforms. (In remembrance: Brett Owen Freiman, Peter L. Freund, Arlene Eva Fried, Alan W. Friedlander)
  221. Volunteer and donated-goods management platforms for EOCs. (In remembrance: Andrew Keith Friedman, Paul J. Friedman, Gregg J. Froehner, Lisa Anne Frost)
  222. Spontaneous volunteer credentialing to reduce convergence chaos. (In remembrance: Peter Christian Fry, Clement A. Fumando, Steven Elliot Furman, Paul James Furmato)
  223. Private security officer training standards in high-risk venues. (In remembrance: Karleton Douglas Beye Fyfe, Fredric Neal Gabler, Richard Peter Gabriel, Richard S. Gabrielle)
  224. Hospital lockdown and active threat clinical protocols. (In remembrance: James Andrew Gadiel, Pamela Lee Gaff, Ervin Vincent Gailliard, Deanna Lynn Galante)
  225. Emergency department decontamination shower and isolation designs. (In remembrance: Grace Catherine Galante, Anthony Edward Gallagher, Daniel James Gallagher, John Patrick Gallagher)
  226. Burn center regional coordination networks. (In remembrance: Lourdes J. Galletti, Cono E. Gallo, Vincent Gallucci, Thomas E. Galvin)
  227. Pediatric mass-casualty triage tools (JumpSTART and successors). (In remembrance: Giovanna Galletta Gambale, Thomas Gambino, Jr., Giann F. Gamboa, Ronald L. Gamboa)
  228. START/SALT triage training modernization. (In remembrance: Peter James Ganci, Jr., Michael Gann, Charles William Garbarini, Andrew Sonny Garcia)
  229. Tactical EMS and TEMS integration with SWAT. (In remembrance: Cesar R. Garcia, David Garcia, Jorge Luis Morron Garcia, Juan Garcia)
  230. Rescue task force (warm zone care) models for active assailant events. (In remembrance: Marlyn Del Carmen Garcia, Christopher Samuel Gardner, Douglas Benjamin Gardner, Harvey Joseph Gardner III)
  231. Bleeding control kits in public buildings and schools. (In remembrance: Jeffrey Brian Gardner, Thomas A. Gardner, William Arthur Gardner, Frank Garfi)
  232. AED ubiquity and PAD (public access defibrillation) programs. (In remembrance: Rocco Nino Gargano, James M. Gartenberg, Matthew David Garvey, Bruce Gary)
  233. Hands-only CPR public education campaigns. (In remembrance: Boyd Alan Gatton, Donald Richard Gavagan, Jr., Peter Alan Gay, Terence D. Gazzani)
  234. PulsePoint and similar bystander CPR notification apps. (In remembrance: Gary Paul Geidel, Paul Hamilton Geier, Julie M. Geis, Peter Gerard Gelinas)
  235. Smart smoke and CO alarms with remote alerting. (In remembrance: Steven Paul Geller, Howard G. Gelling, Jr., Peter Victor Genco, Jr., Steven Gregory Genovese)
  236. IoT leak and intrusion sensors for critical facilities. (In remembrance: Alayne Gentul, Linda M. George, Edward F. Geraghty, Suzanne Geraty)
  237. Video analytics for unattended bag detection in transit. (In remembrance: Ralph Gerhardt, Robert Gerlich, Denis P. Germain, Marina Romanovna Gertsberg)
  238. Privacy-preserving video analytics research for public spaces. (In remembrance: Susan M. Getzendanner, Lawrence D. Getzfred, James G. Geyer, Cortez Ghee)
  239. Encrypted radios with over-the-air rekeying for police. (In remembrance: Joseph M. Giaccone, Vincent Francis Giammona, Debra Lynn Gibbon, James Andrew Giberson)
  240. P25 Phase II trunked radio systems for multi-agency talkgroups. (In remembrance: Brenda C. Gibson, Craig Neil Gibson, Ronnie E. Gies, Andrew Clive Gilbert)
  241. Cross-band and gateway devices for mutual aid interoperability. (In remembrance: Timothy Paul Gilbert, Paul Stuart Gilbey, Paul John Gill, Mark Y. Gilles)
  242. CAD-to-CAD data sharing across neighboring 911 centers. (In remembrance: Evan Hunter Gillette, Ronald Lawrence Gilligan, Rodney C. Gillis, Laura Gilly)
  243. NG911 geospatial routing to the correct public-safety answering point. (In remembrance: John F. Ginley, Donna Marie Giordano, Jeffrey John Giordano)
  244. What3Words and plus-code experiments for locating callers in parks. (In remembrance: John Giordano, Steven A. Giorgetti, Martin Giovinazzo)
  245. Vertical location (z-axis) for 911 calls in high-rises. (In remembrance: Kum-Kum Girolamo, Salvatore Gitto, Cynthia Giugliano)
  246. AML (Advanced Mobile Location) for Android/iOS emergency calls. (In remembrance: Mon Gjonbalaj, Dianne Gladstone, Keith Alexander Glascoe)
  247. Text-to-911 for callers who cannot speak safely. (In remembrance: Thomas Irwin Glasser, Edmund Glazer, Harry Glenn)
  248. Video-to-911 pilots for situational awareness at PSAPs. (In remembrance: Barry H. Glick, Jeremy Logan Glick, Steven Glick)
  249. AI call-taking assistance for faster triage (human-supervised). (In remembrance: John T. Gnazzo, William Robert Godshalk, Michael Gogliormella)
  250. Language line integration for non-English emergency callers. (In remembrance: Brian F. Goldberg, Jeffrey G. Goldflam, Michelle Goldstein)
  251. Mental health co-responder and crisis intervention team (CIT) models. (In remembrance: Monica Goldstein, Steven Ian Goldstein, Ronald F. Golinski)
  252. 988 Suicide & Crisis Lifeline as a national behavioral health pathway. (In remembrance: Andrew H. Golkin, Dennis James Gomes, Enrique Antonio Gomez)
  253. Police alternative response for non-violent mental health calls. (In remembrance: Jose Bienvenido Gomez, Manuel Gomez, Jr., Wilder Alfredo Gomez)
  254. De-escalation training curricula for patrol officers. (In remembrance: Jenine Nicole Gonzalez, Mauricio Gonzalez, Rosa J. Gonzalez)
  255. Less-lethal options modernization (ECWs, 40mm, etc.) with policy. (In remembrance: Lynn Catherine Goodchild, Calvin Joseph Gooding, Peter Morgan Goodrich)
  256. Officer wellness and suicide prevention programs. (In remembrance: Harry Goody, Kiran Kumar Reddy Gopu, Catherine C. Gorayeb)
  257. Peer support apps for first responders. (In remembrance: Lisa Fenn Gordenstein, Kerene Gordon, Sebastian Gorki)
  258. Chaplaincy and grief support for line-of-duty and terrorism loss. (In remembrance: Kieran Joseph Gorman, Thomas Edward Gorman, Michael Edward Gould)
  259. Memorial and family liaison best practices after mass violence. (In remembrance: O. Kristin Osterholm White Gould, Douglas Alan Gowell, Yuji Goya)
  260. Victim compensation fund administration lessons (VCF). (In remembrance: Jon Richard Grabowski, Christopher Michael Grady, Edwin J. Graf III)
  261. World Trade Center Health Program for responders and survivors. (In remembrance: David Martin Graifman, Gilbert Franco Granados, Lauren Catuzzi Grandcolas)
  262. Long-term monitoring for dust and toxin-related illness. (In remembrance: Elvira Granitto, Winston Arthur Grant, Christopher S. Gray)
  263. Cancer and aerodigestive care pathways for 9/11 responders. (In remembrance: Ian J. Gray, James Michael Gray, Tara McCloud Gray)
  264. Research cohorts studying PTSD after terrorism. (In remembrance: John M. Grazioso, Timothy George Grazioso, Derrick Auther Green)
  265. Resilience training for communities recovering from attacks. (In remembrance: Wade B. Green, Wanda Anita Green, Elaine Myra Greenberg)
  266. Countering violent extremism (CVE) community partnership models. (In remembrance: Donald Freeman Greene, Gayle R. Greene, James Arthur Greenleaf, Jr.)
  267. Off-ramps and intervention programs for radicalization concerns. (In remembrance: Eileen Marsha Greenstein, Elizabeth Martin Gregg, Denise Marie Gregory)
  268. Prison radicalization monitoring and rehabilitation research. (In remembrance: Donald H. Gregory, Florence Moran Gregory, Pedro Grehan)
  269. Online radicalization early-warning research (civil-liberties aware). (In remembrance: John Michael Griffin, Tawanna Sherry Griffin, Joan Donna Griffith)
  270. Public literacy on disinformation used by extremist groups. (In remembrance: Warren Grifka, Ramon B. Grijalvo, Joseph F. Grillo)
  271. Hate-crime reporting improvements and community liaison officers. (In remembrance: David Joseph Grimner, Francis Edward Grogan, Linda Gronlund)
  272. Synagogue, mosque, and church security assessment tools. (In remembrance: Kenneth George Grouzalis, Joseph Grzelak, Matthew James Grzymalski)
  273. Nonprofit Security Grant Program expansions. (In remembrance: Robert Joseph Gschaar, Liming Gu, Richard J. Guadagno)
  274. Soft-target security design guides from DHS/CISA. (In remembrance: Jose A. Guadalupe, Cindy Yan Zhu Guan, Geoffrey E. Guja)
  275. Hometown Security and community preparedness curricula. (In remembrance: Joseph P. Gullickson, Babita Girjamatie Guman, Douglas Brian Gurian)
  276. Ready.gov household preparedness modernization. (In remembrance: Janet Ruth Gustafson, Philip T. Guza, Barbara Guzzardo)
  277. Go-bags and family communication plans as civic resilience practice. (In remembrance: Peter Mark Gyulavary, Gary Robert Haag, Andrea Lyn Haberman)
  278. Business continuity planning (BCP) mainstreamed for SMEs. (In remembrance: Barbara Mary Habib, Philip Haentzler, Nezam A. Hafiz)
  279. Supply-chain mapping after single-point-of-failure shocks. (In remembrance: Karen Elizabeth Hagerty, Steven Michael Hagis, Mary Lou Hague)
  280. Just-in-case inventory strategies for critical medical supplies. (In remembrance: David Halderman, Maile Rachel Hale, Diane Hale-McKinzy)
  281. Additive manufacturing for emergency spare parts. (In remembrance: Richard B. Hall, Stanley R. Hall, Vaswald George Hall)
  282. 3D-printed tourniquet and medical device surge research. (In remembrance: Robert J. Halligan, Vincent Gerard Halloran, Carolyn B. Halmon)
  283. Autonomous underwater vehicles for port security inspection. (In remembrance: James Douglas Halvorson, Mohammad Salman Hamdani, Felicia Hamilton)
  284. Harbor sonar and diver detection systems. (In remembrance: Robert W. Hamilton, Carl Max Hammond, Jr., Frederic K. Han)
  285. Container scanning with high-energy X-ray and muon tomography research. (In remembrance: Christopher James Hanley, Sean S. Hanley, Valerie Joan Hanna)
  286. Rail hazmat tracking and positive train control (PTC) safety. (In remembrance: Thomas Paul Hannafin, Kevin James Hannaford, Sr., Michael Lawrence Hannan)
  287. Positive Train Control nationwide deployment for collision prevention. (In remembrance: Dana Rey Hannon, Christine Lee Hanson, Peter Burton Hanson)
  288. Highway weigh-in-motion and commercial vehicle safety screening. (In remembrance: Sue Kim Hanson, Vassilios G. Haramis, James A. Haran)
  289. Bridge anti-collision and pier protection systems. (In remembrance: Gerald Francis Hardacre, Jeffrey Pike Hardy, T.J. Hargrave)
  290. Tunnel ventilation and fire detection upgrades. (In remembrance: Daniel Edward Harlin, Frances Haros, Harvey L. Harrell)
  291. Smart CCTV with privacy governance for city operations centers. (In remembrance: Stephen G. Harrell, Melissa Harrington-Hughes, Aisha Ann Harris)
  292. Domain Awareness System-style multi-sensor urban security platforms. (In remembrance: Stewart D. Harris, John Patrick Hart, Eric Hartono)
  293. License-to-operate cyber hygiene requirements for contractors. (In remembrance: John Clinton Hartz, Emeric Harvey, Peter Paul Hashem)
  294. FedRAMP authorized cloud services for secure government workloads. (In remembrance: Thomas Theodore Haskell, Jr., Timothy Shawn Haskell, Joseph John Hasson III)
  295. IL4/IL5 cloud for controlled unclassified and higher workloads. (In remembrance: Leonard W. Hatton, Jr., Terence S. Hatton, Michael Helmut Haub)
  296. Secure mobile apps for first responders (RJIS, FirstNet apps). (In remembrance: Timothy Aaron Haviland, Donald G. Havlish, Jr., Anthony Maurice Hawkins)
  297. Offline-capable mapping for responders in denied networks. (In remembrance: Nobuhiro Hayatsu, James Edward Hayden, Robert Jay Hayes)
  298. Augmented reality wayfinding research for smoke-filled structures. (In remembrance: Philip T. Hayes, Ret., W. Ward Haynes, Scott Jordan Hazelcorn)
  299. Digital twins of critical facilities for exercise and response. (In remembrance: Michael K. Healey, Roberta B. Heber, Charles Francis Xavier Heeran)
  300. Tabletop exercise platforms and virtual reality training for EOCs. (In remembrance: John F. Heffernan, Michele M. Heidenberger, Sheila M.S. Hein)
  301. National Level Exercise and Vibrant Response-style drills. (In remembrance: H. Joseph Heller, Jr., JoAnn L. Heltibridle, Ronald John Hemenway)
  302. Red team / purple team exercises for physical-cyber blended threats. (In remembrance: Mark F. Hemschoot, Ronnie Lee Henderson, Brian Hennessey)
  303. Capture-the-flag and cyber ranges for defender skill building. (In remembrance: Edward R. Hennessy, Jr., Michelle Marie Henrique, Joseph Patrick Henry)
  304. Bug bounty programs for critical public-facing systems. (In remembrance: William L. Henry, Jr., Catherina Henry-Robinson, John Christopher Henwood)
  305. Coordinated vulnerability disclosure policies in government. (In remembrance: Robert Allan Hepburn, Mary Herencia, Lindsay C. Herkness III)
  306. Patch Tuesday discipline and emergency directive patching. (In remembrance: Harvey Robert Hermer, Norberto Hernandez, Raul Hernandez)
  307. Legacy system isolation strategies for unpatchable OT. (In remembrance: Gary Herold, Jeffrey Alan Hersch, Thomas J. Hetzel)
  308. Air-gapped backups and immutable storage against ransomware. (In remembrance: Leon Bernard Heyward MC Sundance, Brian Christopher Hickey, Enemencio Dario Hidalgo Cedeño)
  309. Incident response retainers for cities and hospitals. (In remembrance: Timothy Brian Higgins, Robert D. W. Higley II, Todd Russell Hill)
  310. Cyber insurance underwriting driving baseline controls. (In remembrance: Clara Victorine Hinds, Neal O. Hinds, Mark Hindy)
  311. Board-level cyber risk governance for critical operators. (In remembrance: Katsuyuki Hirai, Heather Malia Ho, Tara Yvette Hobbs)
  312. Third-party risk management for vendor access to sensitive systems. (In remembrance: Thomas Anderson Hobbs, James J. Hobin, Robert Wayne Hobson III)
  313. Privileged access workstations for administrators. (In remembrance: DaJuan Hodges, Ronald G. Hoerner, Patrick A. Hoey)
  314. Just-in-time admin access reducing standing privilege. (In remembrance: John A. Hofer, Marcia Hoffman, Stephen Gerard Hoffman)
  315. Secrets management replacing hardcoded credentials. (In remembrance: Frederick Joseph Hoffmann, Michele L. Hoffmann, Judith Florence Hofmiller)
  316. Code signing and artifact integrity for software updates. (In remembrance: Wallace Cole Hogan, Jr., Thomas Warren Hohlweck, Jr., Jonathan R. Hohmann)
  317. Secure over-the-air update frameworks for vehicles and IoT. (In remembrance: Cora Hidalgo Holland, John Holland, Joseph F. Holland)
  318. Automotive cybersecurity (ISO/SAE 21434) awareness for fleets. (In remembrance: Jimmie I. Holley, Elizabeth Holmes, Thomas P. Holohan)
  319. Connected vehicle V2X security research for collision avoidance. (In remembrance: Herbert Wilson Homer, LeRoy W. Homer, Jr., Bradley V. Hoorn)
  320. UAS traffic management (UTM) concepts for safe drone skies. (In remembrance: James P. Hopper, Montgomery McCullough Hord, Michael Joseph Horn)
  321. Detect-and-avoid systems for beyond-visual-line-of-sight drones. (In remembrance: Matthew Douglas Horning, Robert L. Horohoe, Jr., Michael Robert Horrocks)
  322. Wildfire and disaster drone mapping shared with firefighters. (In remembrance: Aaron Horwitz, Charles J. Houston, Uhuru G. Houston)
  323. AI wildfire spread models for evacuation timing. (In remembrance: Angela M. Houtz, George Gerard Howard, Brady Kay Howell)
  324. Flood sensors and community flood early warning networks. (In remembrance: Michael C. Howell, Steven Leon Howell, Jennifer L. Howley)
  325. Tsunami warning buoy and siren network modernization. (In remembrance: Milagros Hromada, Marian R. Hrycak, Stephen Huczko, Jr.)
  326. Volcano and ash-cloud aviation alerts protecting flights. (In remembrance: Kris Robert Hughes, Paul Rexford Hughes, Robert T. Hughes, Jr.)
  327. Space weather alerts protecting GPS and power grids. (In remembrance: Thomas F. Hughes, Jr., Timothy Robert Hughes, Susan Huie)
  328. GPS backup / eLoran and PNT resilience research. (In remembrance: Lamar Demetrius Hulse, John Nicholas Humber, Jr., William Christopher Hunt)
  329. Anti-jam and authenticated GNSS research for critical timing. (In remembrance: Kathleen Anne Hunt-Casey, Joseph Gerard Hunter, Peggie M. Hurt)
  330. Precision timing for financial and power systems resilience. (In remembrance: Robert R. Hussa, Stephen N. Hyland, Jr., Robert J. Hymel)
  331. Undersea cable protection awareness and diverse routing. (In remembrance: Thomas Edward Hynes, Walter G. Hynes, Joseph Anthony Ianelli)
  332. Satellite mega-constellations for resilient communications. (In remembrance: Zuhtu Ibis, Jonathan Lee Ielpi, Michael Patrick Iken)
  333. Starlink and commercial SATCOM for disaster connectivity. (In remembrance: Daniel Ilkanayev, Frederick J. Ill, Jr., Abraham Nethanel Ilowitz)
  334. High-altitude pseudo-satellites for temporary coverage. (In remembrance: Anthony P. Infante, Jr., Louis S. Inghilterra, Christopher Noble Ingrassia)
  335. Portable cell-on-wheels (COW) and COLTs for event/disaster coverage. (In remembrance: Paul Innella, Stephanie Veronica Irby, Douglas Jason Irgang)
  336. Public Wi-Fi captive portals with emergency information modes. (In remembrance: Kristin Irvine-Ryan, Todd Antione Isaac, Erik Hans Isbrandtsen)
  337. ATM and fuel station generator requirements in continuity plans. (In remembrance: Taizo Ishikawa, Waleed Joseph Iskandar, Aram Iskenderian, Jr.)
  338. Fuel prioritization frameworks for emergency fleets. (In remembrance: John F. Iskyan, Kazushige Ito, Aleksandr Valeryevich Ivantsov)
  339. Emergency fuel waivers and Jones Act flexibilities in crises. (In remembrance: Lacey Bernard Ivory, Virginia May Jablonski, Bryan C. Jack)
  340. Strategic Petroleum Reserve drawdown playbooks. (In remembrance: Brooke Alexandra Jackman, Aaron Jeremy Jacobs, Ariel Louis Jacobs)
  341. Food bank logistics surge models after disruptions. (In remembrance: Jason Kyle Jacobs, Michael G. Jacobs, Steven A. Jacobson)
  342. Cold-chain integrity sensors for vaccine and blood transport. (In remembrance: Steven D. Jacoby, Ricknauth Jaggernauth, Jake Denis Jagoda)
  343. Blood donation surge campaigns coordinated after mass violence. (In remembrance: Yudhvir S. Jain, Maria Jakubiak, Robert Adrien Jalbert)
  344. National blood shortage early warning dashboards. (In remembrance: Ernest James, Gricelda E. James, Mark Steven Jardim)
  345. Organ and tissue donation continuity during disasters. (In remembrance: Amy Nicole Jarret, Muhammadou Jawara, Francois Jean-Pierre)
  346. Mortuary surge and dignified remains management protocols. (In remembrance: Maxima Jean-Pierre, Paul Edward Jeffers, John Charles Jenkins)
  347. Cultural and religious sensitivity guides for mass fatality care. (In remembrance: Joseph Jenkins, Jr., Alan Keith Jensen, Prem Nath Jerath)
  348. Multifaith chaplain coordination in family assistance centers. (In remembrance: Farah Jeudy, Hweidar Jian, Eliezer Jimenez, Jr.)
  349. Translation of death notification best practices. (In remembrance: Luis Jimenez, Jr., Charles Gregory John, Nicholas John)
  350. Child tracing and unaccompanied minor protocols in evacuations. (In remembrance: Dennis M. Johnson, LaShawna Johnson, Scott Michael Johnson)
  351. Elderly and disability registry systems for evacuation assistance. (In remembrance: William R. Johnston, Allison Horstmann Jones, Arthur Joseph Jones III)
  352. Accessible transportation contracts for emergency evacuation. (In remembrance: Brian Leander Jones, Charles Edward Jones, Christopher D. Jones)
  353. Hotel sheltering agreements pre-negotiated by emergency managers. (In remembrance: Donald T. Jones II, Donald W. Jones, Judith Lawter Jones)
  354. Non-congregate sheltering lessons for dignity and infection control. (In remembrance: Linda Jones, Mary S. Jones, Andrew Brian Jordan, Sr.)
  355. Household pet sheltering standards alongside human shelters. (In remembrance: Robert Thomas Jordan, Albert Gunnis Joseph, Ingeborg Joseph)
  356. Livestock and agricultural emergency response plans. (In remembrance: Karl Henry Joseph, Stephen Joseph, Jane Eileen Josiah)
  357. Foreign animal disease surveillance protecting food security. (In remembrance: Anthony Jovic, Angel L. Juarbe, Jr., Karen Sue Juday)
  358. Agroterrorism awareness for extension agents and producers. (In remembrance: Ann C. Judge, Mychal F. Judge, Paul William Jurgens)
  359. Food Defense plans for processing plants (FDA/USDA). (In remembrance: Thomas Edward Jurgens, Shashikiran Lakshmikantha Kadaba, Gavkharoy Kamardinova)
  360. FDA Food Safety Modernization Act preventive controls. (In remembrance: Shari Kandell, Howard Lee Kane, Jennifer Lynn Kane)
  361. Intentional adulteration rule for food facilities. (In remembrance: Vincent D. Kane, Joon Koo Kang, Sheldon Robert Kanter)
  362. Pharmaceutical supply-chain serialization against diversion. (In remembrance: Deborah H. Kaplan, Robin Lynne Kaplan, Alvin Peter Kappelmann, Jr.)
  363. DSCSA tracing for prescription drugs. (In remembrance: Charles H. Karczewski, William A. Karnes, Douglas Gene Karpiloff)
  364. Cold-chain IoT for insulin and specialty meds in disasters. (In remembrance: Charles L. Kasper, Andrew K. Kates, John A. Katsimatides)
  365. Hospital generator and fuel testing compliance upgrades. (In remembrance: Robert Michael Kaulfers, Don Jerome Kauth, Jr., Hideya Kawauchi)
  366. HVAC filtration and airborne infection isolation room standards. (In remembrance: Edward T. Keane, Richard M. Keane, Lisa Yvonne Kearney-Griffin)
  367. Negative-pressure ambulance designs for contagious patients. (In remembrance: Karol Ann Keasler, Barbara A. Keating, Paul Hanlon Keating)
  368. EMS powered air-purifying respirator (PAPR) protocols. (In remembrance: Leo Russell Keene III, Brenda Kegler, Chandler Raymond Keller)
  369. Fire service cancer prevention (contaminant control) programs. (In remembrance: Joseph John Keller, Peter R. Kellerman, Joseph P. Kellett)
  370. Extractors and gear cleaning reducing firefighter carcinogen exposure. (In remembrance: Frederick H. Kelley III, James Joseph Kelly, Joseph A. Kelly)
  371. PFAS-aware firefighting foam transitions. (In remembrance: Maurice P. Kelly, Richard John Kelly, Jr., Thomas Michael Kelly)
  372. Green chemistry foam research for ARFF and structural firefighting. (In remembrance: Thomas Richard Kelly, Thomas W. Kelly, Timothy Colin Kelly)
  373. Electric vehicle fire response tactics for first responders. (In remembrance: William Hill Kelly, Jr., Robert Clinton Kennedy, Thomas J. Kennedy)
  374. Lithium-ion battery fire containment tools. (In remembrance: Yvonne E. Kennedy, John Richard Keohane, Ralph Francis Kershaw)
  375. High-rise lithium battery storage fire code updates. (In remembrance: Ronald T. Kerwin, Howard L. Kestenbaum, Douglas D. Ketcham)
  376. Energy storage system (ESS) fire safety standards. (In remembrance: Ruth Ellen Ketler, Boris Khalif, Norma Cruz Khan)
  377. Hydrogen facility response guides for emerging energy sites. (In remembrance: Sarah Khan, Taimour Firaz Khan, Rajesh Khandelwal)
  378. LNG terminal emergency planning zones. (In remembrance: SeiLai Khoo, Michael Vernon Kiefer, Satoshi Kikuchihara)
  379. Ammonia refrigeration leak response for food warehouses. (In remembrance: Andrew Jay-Hoon Kim, Lawrence Don Kim, Mary Jo Kimelman)
  380. Chlorine and chemical railcar response playbooks. (In remembrance: Heinrich Kimmig, Karen Ann Kincaid, Amy R. King)
  381. Emergency Response Guidebook (ERG) continuous updates. (In remembrance: Andrew M. King, Lucille Teresa King, Robert King, Jr.)
  382. WISER and CAMEO tools for hazmat decision support. (In remembrance: Lisa King-Johnson, Brian K. Kinney, Takashi Kinoshita)
  383. Plume modeling software for evacuation zone decisions. (In remembrance: Chris Michael Kirby, Howard Barry Kirschbaum, Glenn Davis Kirwin)
  384. Reverse 911 / community notification calling systems. (In remembrance: Helen Crossin Kittle, Richard Joseph Klares, Peter Anton Klein)
  385. Opt-in county alert apps alongside WEA. (In remembrance: Alan David Kleinberg, Karen Joyce Klitzman, Ronald Philip Kloepfer)
  386. Siren networks rehabilitated for outdoor warning. (In remembrance: Eugueni Kniazev, Andrew James Knox, Thomas Patrick Knox)
  387. Earthquake-resistant hospital and firehouse retrofit programs. (In remembrance: Rebecca Lee Koborie, Deborah A. Kobus, Gary Edward Koecheler)
  388. Seismic gas shutoff valves reducing post-quake fire risk. (In remembrance: Frank J. Koestner, Ryan Kohart, Vanessa Lynn Przybylo Kolpak)
  389. Fire-resistant building materials research for tall timber and steel. (In remembrance: Irina Kolpakova, Suzanne Rose Kondratenko, Abdoulaye Koné)
  390. Intumescent coatings and fireproofing inspection regimes. (In remembrance: Bon Seok Koo, Dorota Kopiczko, Scott Michael Kopytko)
  391. Post-fire structural assessment drones and LIDAR. (In remembrance: Bojan George Kostic, Danielle Kousoulis, David P. Kovalcin)
  392. Urban canyon communications research for radio coverage. (In remembrance: John J. Kren, William Edward Krukowski, Lyudmila Ksido)
  393. In-building cellular and ERRCS (emergency responder radio coverage). (In remembrance: Toshiya Kuge, Shekhar Kumar, Kenneth Bruce Kumpel)
  394. Bi-directional amplifiers for subterranean transit radio. (In remembrance: Frederick Kuo, Jr., Patricia A. Kuras, Nauka Kushitani)
  395. Tunnel leaky-feeder systems for firefighter communications. (In remembrance: Thomas Joseph Kuveikis, Victor Kwarkye, Raymond Kui Fai Kwok)
  396. Mayday and RIT (rapid intervention team) training standards. (In remembrance: Angela Reed Kyte, Andrew La Corte, Carol Ann La Plante)
  397. Firefighter escape systems and personal bailout kits. (In remembrance: Jeffrey G. La Touche, Kathryn L. LaBorie, Amarnauth Lachhman)
  398. Thermal imaging cameras as standard engine company tools. (In remembrance: Ganesh K. Ladkat, James Patrick Ladley, Joseph A. Lafalce)
  399. Electric and hybrid fire apparatus reducing station emissions. (In remembrance: Jeanette Louise Lafond-Menichino, David James LaForge, Michael Patrick LaForte)
  400. Ergonomic stretcher power-load systems reducing EMS injuries. (In remembrance: Alan Charles LaFrance, Juan Mendez Lafuente, Neil Kwong-Wah Lai)
  401. Mechanical CPR devices for high-rise and prolonged transport. (In remembrance: Vincent Anthony Laieta, William David Lake, Franco Lalama)
  402. ECMO surge planning for severe respiratory failure. (In remembrance: Chow Kwan Lam, Michael S. Lamana, Stephen LaMantia)
  403. Burn surge caches and regional burn bed coordination. (In remembrance: Amy Hope Lamonsoff, Robert T. Lane, Brendan Mark Lang)
  404. Telecritical care connecting rural hospitals to specialists. (In remembrance: Rosanne P. Lang, Vanessa Lang Langer, Mary Lou Langley)
  405. Drone delivery research for emergency AED/defibrillator access. (In remembrance: Peter J. Langone, Thomas Michael Langone, Michele Bernadette Lanza)
  406. Blood-carrying drone pilots for remote trauma scenes. (In remembrance: Ruth Sheila Lapin, Ingeborg A.D. Lariby, Robin Blair Larkey)
  407. Autonomous ambulance research with remote clinician oversight. (In remembrance: Judith Camilla Larocque, Christopher Randall Larrabee, Hamidou S. Larry)
  408. Connected ambulance telemetry to receiving trauma bays. (In remembrance: Scott Larsen, John Adam Larson, Natalie Janis Lasden)
  409. Trauma center verification and ACS COT standards spread. (In remembrance: Gary Edward Lasko, Nicholas Craig Lassman, Paul Laszczynski)
  410. Stop the Bleed in airports, stadiums, and houses of worship. (In remembrance: Charles A. Laurencin, Stephen James Lauria, Maria LaVache)
  411. Public access bleeding control stations next to AED cabinets. (In remembrance: Denis Francis Lavelle, Jeannine Mary LaVerde, Anna A. Laverty)
  412. Hemorrhage-control education in workplace OSHA-adjacent training. (In remembrance: Steven Lawn, Robert A. Lawrence, Jr., Nathaniel Lawson)
  413. Tactical combat lessons applied to civilian tourniquet doctrine. (In remembrance: David W. Laychak, Eugen Gabriel Lazar, James Patrick Leahy)
  414. Pediatric tourniquet sizing and training awareness. (In remembrance: Joseph Gerard Leavey, Neil J. Leavy, Robert G. LeBlanc)
  415. Obstetric hemorrhage kits for maternity units in disasters. (In remembrance: Leon Lebor, Kenneth Charles Ledee, Alan J. Lederman)
  416. Mass-casualty ambulance bus and MCI trailers. (In remembrance: Elena F. Ledesma, Alexis Leduc, Daniel John Lee)
  417. Field hospital deployable shelters for surge. (In remembrance: David S. Lee, Dong Chul Lee, Gary H. Lee)
  418. Federal medical stations for large incidents. (In remembrance: Hyun Joon Lee, Juanita Lee, Kathryn Blair Lee)
  419. DMAT and NDMS medical team deployment readiness. (In remembrance: Linda C. Lee, Lorraine Mary Greene Lee, Myoung Woo Lee)
  420. Veterinary Medical Assistance Teams for animal disaster needs. (In remembrance: Richard Y.C. Lee, Stuart Soo-Jin Lee, Yang Der Lee)
  421. Urban Search and Rescue canine search specialist programs. (In remembrance: Stephen Paul Lefkowitz, Adriana Legro, Edward Joseph Lehman)
  422. FEMA US&R specialty teams (hazmat, structures, medics). (In remembrance: Eric Lehrfeld, David R. Leistman, David Prudencio Lemagne)
  423. Technical rescue: trench, confined space, high-angle standardization. (In remembrance: Joseph Anthony Lenihan, John Joseph Lennon, Jr., John Robinson Lenoir)
  424. Swiftwater and flood rescue team proliferation. (In remembrance: Jorge Luis León, Sr., Matthew G. Leonard, Michael Lepore)
  425. Helicopter short-haul and hoist rescue capability growth. (In remembrance: Charles A. Lesperance, Jeff LeVeen, John Dennis Levi)
  426. Night-vision air ambulance operations expansion. (In remembrance: Alisha Caren Levin, Neil David Levin, Robert Levine)
  427. HEMS weather decision tools reducing aviation EMS accidents. (In remembrance: Robert Michael Levine, Shai Levinhar, Daniel M. Lewin)
  428. Wire-strike protection and helicopter safety kits. (In remembrance: Adam Jay Lewis, Jennifer Lewis, Kenneth E. Lewis)
  429. ADS-B In traffic displays for emergency aircraft. (In remembrance: Margaret Susan Lewis, Ye Wei Liang, Orasri Liangthanasarn)
  430. Public-safety aviation FLIR for missing persons and fire mapping. (In remembrance: Daniel F. Libretti, Ralph Michael Licciardi, Edward Lichtschein)
  431. Law enforcement sUAS programs with privacy policies. (In remembrance: Samantha L. Lightbourn-Allen, Steven Barry Lillianthal, Carlos R. Lillo)
  432. Evidence drones for crash and crime scene documentation. (In remembrance: Craig Damian Lilore, Arnold Arboleda Lim, Darya Lin)
  433. 3D laser scanning for investigative reconstruction. (In remembrance: Wei Rong Lin, Nickie L. Lindo, Thomas V. Linehan, Jr.)
  434. Rapid DNA for booking and investigative leads (policy-bound). (In remembrance: Robert Thomas Linnane, Alan Patrick Linton, Jr., Diane Theresa Lipari)
  435. Familial DNA searching with legal and ethical frameworks. (In remembrance: Kenneth P. Lira Arévalo, Francisco Alberto Liriano, Lorraine Lisi)
  436. Genetic genealogy for cold cases (distinct from terror response). (In remembrance: Paul Lisson, Vincent M. Litto, Ming-Hao Liu)
  437. Ballistics NIBIN network improvements. (In remembrance: Nancy Liz, Harold Lizcano, Martin Lizzul)
  438. National Integrated Ballistic Information Network hits. (In remembrance: George A. Llanes, Elizabeth C. Logler, Catherine Lisa Loguidice)
  439. ATF eTrace for firearm tracing speed. (In remembrance: Jérôme Robert Lohez, Michael William Lomax, Stephen V. Long)
  440. Explosive taggants and detection research. (In remembrance: Laura Maria Longing, Salvatore P. Lopes, Daniel Lopez)
  441. Peroxide-based explosive detectors after aviation plots. (In remembrance: George Lopez, Luis Manuel Lopez, Maclovio Lopez, Jr.)
  442. Millimeter-wave and terahertz imaging research for concealed threats. (In remembrance: Manuel L. Lopez, Joseph Lostrangio, Chet Dek Louie)
  443. Walkthrough explosives detectors in high-security lobbies. (In remembrance: Stuart Seid Louis, Joseph Lovero, Sara Elizabeth Low)
  444. Magnetic anomaly detection for weapons at soft targets. (In remembrance: Jenny Seu Kueng Low Wong, Michael W. Lowe, Garry W. Lozier)
  445. AI weapons detection on CCTV (human-reviewed alerts). (In remembrance: John P. Lozowsky, Charles Peter Lucania, Edward Hobbs Luckett II)
  446. School weapons detection systems with privacy tradeoff debates. (In remembrance: Mark Gavin Ludvigsen, Lee Charles Ludwig, Sean Thomas Lugano)
  447. Clear bag policies at stadiums reducing concealment risk. (In remembrance: Daniel Lugo, Marie Lukas, William Lum, Jr.)
  448. Magnetometer lanes at concerts and arenas. (In remembrance: Michael P. Lunden, Christopher E. Lunder, Anthony Luparello)
  449. Temporary vehicle checkpoints with LPR support. (In remembrance: Gary Frederick Lutnick, Linda Anne Luzzicone, Alexander Lygin)
  450. Mobile vehicle X-ray for VIP and special-event security. (In remembrance: CeeCee Lyles, Farrell Peter Lynch, James Francis Lynch)
  451. Under-vehicle inspection systems (UVIS) at gates. (In remembrance: James T. Lynch, Jr., Louise A. Lynch, Michael Cameron Lynch)
  452. Anti-drone nets and directed-energy counter-UAS research. (In remembrance: Michael Francis Lynch, Richard D. Lynch, Jr., Robert Henry Lynch, Jr.)
  453. Airport C-UAS detection layers recommended by FAA/DHS. (In remembrance: Sean P. Lynch, Sean Patrick Lynch, Terence M. Lynch)
  454. Stadium C-UAS monitoring during major events. (In remembrance: Michael J. Lyons, Monica Anne Lyons, Nehamon Lyons IV)
  455. Prison contraband drone detection systems. (In remembrance: Patrick John Lyons, Robert Francis Mace, Marianne MacFarlane)
  456. Border tunnel detection sensors and ground-penetrating radar. (In remembrance: Jan Maciejewski, Susan A. Mackay, Catherine Fairfax MacRae)
  457. Seismic and acoustic sensors for subterranean intrusion. (In remembrance: Richard Blaine Madden, Simon Maddison, Noell C. Maerz)
  458. Border surveillance aerostats and towers. (In remembrance: Jennieann Maffeo, Joseph Maffeo, Jay Robert Magazine)
  459. Autonomous border patrol ground robots (pilots). (In remembrance: Brian Magee, Charles W. Magee, Joseph V. Maggitti)
  460. Maritime domain awareness dashboards for ports. (In remembrance: Ronald Magnuson, Daniel L. Maher, Thomas A. Mahon)
  461. Dark vessel detection using RF and SAR satellites. (In remembrance: William J. Mahoney, Joseph Daniel Maio, Linda C. Mair-Grayling)
  462. AIS spoofing detection for maritime security. (In remembrance: Takashi Makimoto, Abdu Ali Malahi, Debora I. Maldonado)
  463. Port worker biometric access control. (In remembrance: Myrna T. Maldonado-Agosto, Alfred Russell Maler, Gregory James Malone)
  464. Cruise ship passenger accountability and muster tech. (In remembrance: Edward Francis Maloney III, Joseph E. Maloney, Gene Edward Maloy)
  465. Ferry terminal screening adaptations. (In remembrance: Christian H. Maltby, Francisco Miguel Mancini, Joseph Mangano)
  466. Bus and motorcoach operator security training. (In remembrance: Sara Elizabeth Manley, Debra M. Mannetta, Marion Victoria Manning)
  467. Over-the-road trucking hazmat security plans. (In remembrance: Terence John Manning, James Maounis, Alfred Gilles Padre Joseph Marchand)
  468. Highway watch / trucker tip programs. (In remembrance: Joseph Ross Marchbanks, Jr., Laura A. Marchese, Hilda Marcin)
  469. Rest-area and truck-stop security lighting CPTED. (In remembrance: Peter Edward Mardikian, Edward Joseph Mardovich, Charles Joseph Margiotta)
  470. Cargo theft analytics protecting supply chains. (In remembrance: Louis Neil Mariani, Kenneth Joseph Marino, Lester V. Marino)
  471. Seal and container integrity IoT sensors. (In remembrance: Vita Marino, Kevin D. Marlo, Jose Juan Marrero)
  472. Blockchain pilots for provenance of high-risk goods. (In remembrance: John Daniel Marshall, Shelley A. Marshall, James Martello)
  473. Pharmaceutical track-and-trace against counterfeit meds. (In remembrance: Michael A. Marti, Karen Ann Martin, Peter C. Martin)
  474. Opioid and fentanyl interdiction tools at mail facilities. (In remembrance: Teresa M. Martin, William J. Martin, Jr., Brian E. Martineau)
  475. Mail screening upgrades for chemical and explosive threats. (In remembrance: Betsy Martinez, Edward J. Martinez, Jose Angel Martinez, Jr.)
  476. USPS and private carrier hazardous mail protocols. (In remembrance: Robert Gabriel Martinez, Waleska Martinez, Lizie D. Martinez-Calderon)
  477. Anthrax and white-powder response SOPs for mailrooms. (In remembrance: Paul Richard Martini, Anne Marie Martino-Cramer, Joseph A. Mascali)
  478. Biological personal protective equipment for postal inspectors. (In remembrance: Bernard Mascarenhas, Stephen Frank Masi, Ada L. Mason-Acker)
  479. Environmental sampling robots for contaminated spaces. (In remembrance: Nicholas George Massa, Michael Massaroli, Philip William Mastrandrea, Jr.)
  480. UV and vaporized hydrogen peroxide decontamination systems. (In remembrance: Rudy Mastrocinque, Joseph Mathai, Charles William Mathers)
  481. Wide-area decontamination research after CBRN scenarios. (In remembrance: William A. Mathesen, Marcello Matricciano, Margaret Elaine Mattic)
  482. Indoor air quality sensors for building security operations. (In remembrance: Dean E. Mattson, Robert D. Mattson, Walter A. Matuza, Jr.)
  483. Smart building access control with identity federation. (In remembrance: Timothy J. Maude, Jill Maurer-Campbell, Charles A. Mauro, Jr.)
  484. Badgeless biometric entry for high-security labs. (In remembrance: Charles J. Mauro, Dorothy Mauro, Nancy T. Mauro)
  485. Visitor management systems with watchlist screening. (In remembrance: Robert J. Maxwell, Renée A. May, Tyrone May)
  486. Contractor escort and time-bound badge provisioning. (In remembrance: Keithroy Marcellus Maynard, Robert J. Mayo, Kathy N. Mazza)
  487. Tailgating detection at secure doors. (In remembrance: Edward Mazzella, Jr., Jennifer Lynn Mazzotta, Kaaria Mbaya)
  488. Mantrap / sally port designs for data centers and labs. (In remembrance: James Joseph McAlary, Jr., Brian Gerard McAleese, Patricia Ann McAneney)
  489. Faraday and TEMPEST-aware rooms for sensitive operations. (In remembrance: Colin R. McArthur, John Kevin McAvoy, Kenneth M. McBrayer)
  490. SCIF construction standards proliferation. (In remembrance: Brendan F. McCabe, Michael McCabe, Thomas Joseph McCann)
  491. Insider threat programs combining HR, cyber, and security. (In remembrance: Justin McCarthy, Kevin M. McCarthy, Michael Desmond McCarthy)
  492. User behavior analytics (UBA) for anomalous access. (In remembrance: Robert G. McCarthy, Stanley McCaskill, Katie Marie McCloskey)
  493. Data loss prevention (DLP) for sensitive government data. (In remembrance: Juliana Valentine McCourt, Ruth Magdaline McCourt, Charles Austin McCrann)
  494. CasB and SSE cloud security for hybrid workforces. (In remembrance: Tonyell F. McDay, Matthew T. McDermott, Joseph P. McDonald)
  495. Secure telework frameworks post-crisis remote work surges. (In remembrance: Brian Grady McDonnell, Michael P. McDonnell, John F. McDowell, Jr.)
  496. VDI and zero-trust remote access for cleared staff. (In remembrance: Eamon J. McEneaney, John Thomas McErlean, Jr., Daniel Francis McGinley)
  497. Continuous evaluation for security clearances. (In remembrance: Mark Ryan McGinly, William E. McGinn, Thomas Henry McGinnis)
  498. e-QIP / eApp modernization for clearance processing. (In remembrance: Michael Gregory McGinty, Ann Walsh McGovern, Scott Martin McGovern)
  499. Personnel vetting predictive analytics (careful, audited use). (In remembrance: William J. McGovern, Stacey Sennas McGowan, Francis Noel McGuinn)
  500. Polygraph and lifestyle investigation process reforms. (In remembrance: Thomas F. McGuinness, Jr., Patrick J. McGuire, Thomas M. McHale)
  501. Whistleblower channels for security concerns without retaliation. (In remembrance: Keith David McHeffey, Ann M. McHugh, Denis J. McHugh III)
  502. Protected disclosure frameworks for aviation and nuclear workers. (In remembrance: Dennis P. McHugh, Michael Edward McHugh, Jr., Robert G. McIlvaine)
  503. Just culture adaptations balancing accountability and learning. (In remembrance: Donald James McIntyre, Stephanie Marie McKenna, Molly L. McKenzie)
  504. National Transportation Safety Board lessons applied beyond aviation. (In remembrance: Barry J. McKeon, Evelyn C. McKinnedy, Darryl Leron McKinney)
  505. Serious incident learning systems in hospitals (PSI reporting). (In remembrance: George Patrick McLaughlin, Jr., Robert C. McLaughlin, Jr., Gavin McMahon)
  506. Near-miss reporting apps for first responders. (In remembrance: Robert D. McMahon, Edmund M. McNally, Daniel Walker McNeal)
  507. Blue-ocean safety culture research after high-reliability orgs. (In remembrance: Walter Arthur McNeil, Christine Sheila McNulty, Sean Peter McNulty)
  508. Crew resource management (CRM) adapted to emergency medicine. (In remembrance: Robert William McPadden, Terence A. McShane, Timothy Patrick McSweeney)
  509. Fireground CRM and mayday communications discipline. (In remembrance: Martin E. McWilliams, Rocco A. Medaglia, Abigail Medina)
  510. Police tactical communications brevity and clarity training. (In remembrance: Ana Iris Medina, Damian Meehan, William J. Meehan, Jr.)
  511. Interpreter on-scene video for multilingual emergencies. (In remembrance: Alok Kumar Mehta, Raymond Meisenheimer, Manuel Emilio Mejia)
  512. Body language and cultural competency training for responders. (In remembrance: Eskedar Melaku, Antonio Melendez, Mary P. Melendez)
  513. Community policing trust-building as terrorism prevention substrate. (In remembrance: Christopher D. Mello, Yelena Melnichenko, Stuart Todd Meltzer)
  514. Immigrant community liaison officers reducing tip hesitancy. (In remembrance: Diarelia Jovanah Mena, Dora Marie Menchaca, Charles R. Mendez)
  515. Hate incident hotlines after spikes in community fear. (In remembrance: Lizette Mendoza, Shevonne Olicia Mentis, Wolfgang Peter Menzel)
  516. Youth mentoring as violence-prevention social infrastructure. (In remembrance: Steve John Mercado, Wesley Mercer, Ralph Joseph Mercurio)
  517. After-school and opportunity programs reducing recruitment vulnerability. (In remembrance: Alan Harvey Merdinger, George L. Merino, Yamel Josefina Merino)
  518. Sports and arts programs as community resilience builders. (In remembrance: George Merkouris, Deborah Merrick, Raymond Joseph Metz III)
  519. Local journalism support as rumor-resistant information infrastructure. (In remembrance: Jill Ann Metzler, David Robert Meyer, Nurul H. Miah)
  520. Public media emergency information partnerships. (In remembrance: William Edward Micciulli, Martin Paul Michelstein, Patricia E. Mickley)
  521. Emergency manager–PIO joint information center (JIC) doctrine. (In remembrance: Ronald D. Milam, Peter Teague Milano, Gregory Milanowycz)
  522. Rumor control websites during major incidents. (In remembrance: Lukasz Tomasz Milewski, Sharon Christina Millan, Corey Peter Miller)
  523. Prebunking and inoculation messaging against extremist propaganda. (In remembrance: Craig J. Miller, Douglas C. Miller, Henry Alfred Miller, Jr.)
  524. Digital literacy curricula for deepfakes and scam emergencies. (In remembrance: Joel Miller, Michael Matthew Miller, Nicole Carol Miller)
  525. Elder fraud and terror-finance adjacent scam awareness. (In remembrance: Philip D. Miller, Robert Alan Miller, Robert Cromwell Miller, Jr.)
  526. Business email compromise defenses for critical operators. (In remembrance: Benny Millman, Charles M. Mills, Jr., Ronald Keith Milstein)
  527. SIM-swap and MFA resilience for executives of critical firms. (In remembrance: Robert J. Minara, William George Minardi, Louis Joseph Minervino)
  528. Executive protection digital threat monitoring. (In remembrance: Thomas Mingione, Wilbert Miraille, Domenick N. Mircovich)
  529. Doxxing response playbooks for public officials and journalists. (In remembrance: Rajesh Arjan Mirpuri, Joseph D. Mistrulli, Susan J. Miszkowicz)
  530. Newsroom security training after attacks on media. (In remembrance: Paul Thomas Mitchell, Richard P. Miuccio, Jeffrey Peter Mladenik)
  531. Journalist protective equipment and hostile environment courses. (In remembrance: Frank V. Moccia, Sr., Louis Joseph Modafferi, Boyie Mohammed)
  532. NGO worker security training for high-risk deployments. (In remembrance: Dennis Mojica, Manuel D. Mojica, Jr., Kleber Rolando Molina)
  533. Humanitarian notification systems to reduce mis-targeting. (In remembrance: Manuel De Jesus Molina, Carl Molinaro, Justin John Molisani, Jr.)
  534. Civilian harm mitigation cells in military operations. (In remembrance: Brian Patrick Monaghan, Franklyn Monahan, John Gerard Monahan)
  535. Battle damage assessment transparency reforms. (In remembrance: Kristen Leigh Montanaro, Craig Montano, Michael G. Montesi)
  536. Precision guidance and LOAC training reducing civilian harm. (In remembrance: Carlos Alberto Montoya, Antonio De Jesus Montoya Valdes, Cheryl Ann Monyak)
  537. No-strike list and cultural site protection in targeting systems. (In remembrance: Thomas Carlo Moody, Sharon Moore, Krishna V. Moorthy)
  538. Human rights attorney embedding in operational legal reviews. (In remembrance: Laura Lee Defazio Morabito, Abner Morales, Carlos Manuel Morales)
  539. International partner capacity building for aviation security. (In remembrance: Paula E. Morales, Sonia Mercedes Morales Puopolo, Gerard P. Moran, Jr.)
  540. ICAO aviation security standards updates post-9/11. (In remembrance: John Christopher Moran, John Michael Moran, Kathleen Moran)
  541. Foreign airport assessment programs for last-point-of-departure. (In remembrance: Lindsay Stapleton Morehouse, George William Morell, Steven P. Morello)
  542. Air marshals and in-cabin security international cooperation. (In remembrance: Vincent S. Morello, Yvette Nicole Moreno, Dorothy Morgan)
  543. Extradition and MLATs strengthened for terrorism cases. (In remembrance: Richard J. Morgan, Nancy Morgenstern, Sanae Mori)
  544. Military commission and federal prosecution pathways (debated, refined). (In remembrance: Blanca Robertina Morocho Morocho, Leonel Geronimo Morocho Morocho, Dennis Gerard Moroney)
  545. High-value detainee interrogation protocol reforms. (In remembrance: Lynne Irene Morris, Odessa V. Morris, Seth Allan Morris)
  546. Watchlisting redress (DHS TRIP) for misidentified travelers. (In remembrance: Steve Morris, Christopher Martel Morrison, Ferdinand V. Morrone)
  547. Privacy Impact Assessments mandated for new security tech. (In remembrance: William David Moskal, Brian A. Moss, Marco Motroni)
  548. Civil liberties oversight boards reviewing counterterror programs. (In remembrance: Cynthia Motus-Wilson, Iouri A. Mouchinski, Jude Joseph Moussa)
  549. FISA and surveillance law debates shaping oversight technology. (In remembrance: Peter Moutos, Damion O’Neil Mowatt, Teddington H. Moy)
  550. Minimization procedures in intelligence collection systems. (In remembrance: Christopher Michael Mozzillo, Stephen Vincent Mulderry, Richard T. Muldowney, Jr.)
  551. Audit logging for queries against sensitive databases. (In remembrance: Michael D. Mullan, Dennis Michael Mulligan, Peter James Mulligan)
  552. Role-based access to fusion center information. (In remembrance: Michael Joseph Mullin, James Donald Munhall, Nancy Muñiz)
  553. Privacy officers embedded in fusion centers. (In remembrance: Francisco Heladio Munoz, Carlos Mario Muñoz, Theresa Munson)
  554. Public dashboards for grant spending accountability. (In remembrance: Robert Michael Murach, Cesar Augusto Murillo, Marc A. Murolo)
  555. Performance metrics for homeland security grants. (In remembrance: Brian Joseph Murphy, Charles Anthony Murphy, Christopher W. Murphy)
  556. Threat Hazard Identification and Risk Assessment (THIRA) process. (In remembrance: Edward Charles Murphy, James F. Murphy IV, James Thomas Murphy)
  557. Stakeholder Preparedness Review (SPR) for capability gaps. (In remembrance: Kevin James Murphy, Patrick Jude Murphy, Patrick Sean Murphy)
  558. Emergency Management Accreditation Program (EMAP) standards. (In remembrance: Raymond E. Murphy, Robert Eddie Murphy, Jr., John Joseph Murray)
  559. NFPA 1600/1616 continuity and mass evacuation standards uptake. (In remembrance: Susan D. Murray, Valerie Victoria Murray, Richard Todd Myhre)
  560. ISO 22301 business continuity certification growth. (In remembrance: Louis J. Nacke II, Robert B. Nagel, Mildred Rose Naiman)
  561. NIST Cybersecurity Framework adoption across sectors. (In remembrance: Takuya Nakamura, Alexander John Robert Napier, Frank Joseph Naples III)
  562. NIST SP 800-53 control catalogs for federal systems. (In remembrance: John Philip Napolitano, Catherine Ann Nardella, Mario Nardone, Jr.)
  563. CMMC and defense industrial base cybersecurity requirements. (In remembrance: Manika K. Narula, Shawn M. Nassaney, Narender Nath)
  564. Defense Federal Acquisition cyber clauses. (In remembrance: Karen Susan Navarro, Joseph M. Navas, Francis Joseph Nazario)
  565. Software composition analysis for DoD and critical vendors. (In remembrance: Glenroy I. Neblett, Rayman Marcus Neblett, Jerome O. Nedd)
  566. Hardware Trojan detection research for trusted electronics. (In remembrance: Laurence F. Nedell, Luke G. Nee, Pete Negron)
  567. Trusted Foundry and secure microelectronics initiatives. (In remembrance: Laurie Ann Neira, Ann N. Nelson, David William Nelson)
  568. CHIPS Act-aligned domestic semiconductor resilience. (In remembrance: Ginger Risco Nelson, James A. Nelson, Michele Ann Nelson)
  569. Rare-earth and critical minerals supply diversification. (In remembrance: Peter Allen Nelson, Oscar Francis Nesbitt, Gerard Terence Nevins)
  570. Strategic materials stockpiles for defense production. (In remembrance: Renee Tetreault Newell, Christopher C. Newton, Christopher Newton-Carter)
  571. Defense Production Act use for emergency manufacturing. (In remembrance: Nancy Yuen Ngo, Khang Ngoc Nguyen, Jody Tepedino Nichilo)
  572. Ventilator and PPE DPA lessons for future surges. (In remembrance: Kathleen Ann Nicosia, Martin Stewart Niederer, Alfonse Joseph Niedermeyer)
  573. Domestic N95 manufacturing restart capacity. (In remembrance: Frank John Niestadt, Jr., Gloria Nieves, Juan Nieves, Jr.)
  574. Reusable elastomeric respirator programs for health workers. (In remembrance: Troy Edward Nilsen, Paul Nimbley, John Ballantine Niven)
  575. UV-C room disinfection robots in hospitals. (In remembrance: Katherine McGarry Noack, Curtis Terrance Noel, Michael A. Noeth)
  576. Copper and antimicrobial surface research for high-touch areas. (In remembrance: Daniel R. Nolan, Robert Walter Noonan, Jacqueline June Norton)
  577. Touchless building interfaces reducing fomite risk in crises. (In remembrance: Robert Grant Norton, Daniela Rosalia Notaro, Brian Christopher Novotny)
  578. Queue management reducing crowding at screening points. (In remembrance: Soichi Numata, Brian Nunez, Jose Nunez)
  579. Airport design: sterile vs. public flow separation refinements. (In remembrance: Jeffrey Roger Nussbaum, James A. Oakley, Dennis Patrick O’Berg)
  580. Blast-resistant airport glazing and check-in hall design. (In remembrance: James P. O’Brien, Jr., Michael P. O’Brien, Scott J. O’Brien)
  581. Landside vehicle standoff distances at terminals. (In remembrance: Timothy Michael O’Brien, Daniel O’Callaghan, Dennis James O’Connor, Jr.)
  582. Curbside management reducing VBIED exposure. (In remembrance: Diana J. O’Connor, Keith Kevin O’Connor, Richard J. O’Connor)
  583. Random employee screening at airports and ports. (In remembrance: Amy O’Doherty, Marni Pont O’Doherty, Douglas E. Oelschlager)
  584. Insider threat training for aviation employees. (In remembrance: Takashi Ogawa, Albert Ogletree, Philip Paul Ognibene)
  585. Sterile area access biometric pilots. (In remembrance: John A. Ogonowski, James Andrew O’Grady, Joseph J. Ogren)
  586. Airport worker fingerprint and CHRC process modernization. (In remembrance: Thomas G. O’Hagan, Samuel Oitice, Patrick J. O’Keefe)
  587. Flight kitchen and catering security seals. (In remembrance: William O’Keefe, Gerald Michael Olcott, Gerald Thomas O’Leary)
  588. Aircraft cleaning crew security protocols. (In remembrance: Christine Anne Olender, Linda Mary Oliva, Edward K. Oliver)
  589. Lavatory smoke detector and cabin surveillance policies (privacy-limited). (In remembrance: Leah Elizabeth Oliver, Eric Taube Olsen, Jeffrey James Olsen)
  590. Secondary screening algorithms reducing bias (ongoing work). (In remembrance: Barbara K. Olson, Maureen Lyons Olson, Steven John Olson)
  591. Disability and medical device traveler screening improvements. (In remembrance: Matthew Timothy O’Mahony, Toshihiro Onda, Seamus L. Oneal)
  592. TSA Cares and passenger support specialist programs. (In remembrance: John P. O’Neill, Peter J. O’Neill, Jr., Sean Gordon Corbett O’Neill)
  593. Family lane and military lane humane screening design. (In remembrance: Betty Ann Ong, Michael C. Opperman, Christopher T. Orgielewicz)
  594. AIT automated threat recognition reducing need for pat-downs. (In remembrance: Margaret Quinn Orloske, Virginia Anne Ormiston, Ruben S. Ornedo)
  595. Credential authentication reducing fake ID at checkpoints. (In remembrance: Kevin M. O’Rourke, Ronald Orsini, Peter Keith Ortale)
  596. Digital ID acceptance pilots at TSA with privacy controls. (In remembrance: Juan Ortega-Campos, Jane Marie Orth, Alexander Ortiz)
  597. CAT-2 and dynamic checkpoint resource allocation. (In remembrance: David Ortiz, Emilio Pete Ortiz, Pablo Ortiz)
  598. Wait-time prediction apps reducing sterile-area crowding risk. (In remembrance: Paul Ortiz, Jr., Sonia Ortiz, Masaru Ose)
  599. Exit lane breach detection systems. (In remembrance: Patrick J. O’Shea, Robert William O’Shea, Elsy Carolina Osorio Oliva)
  600. Sterile area intrusion alarms and camera analytics. (In remembrance: James R. Ostrowski, Timothy Franklin O’Sullivan, Jason Douglas Oswald)
  601. Baggage reconciliation systems preventing unaccompanied bags on aircraft. (In remembrance: Michael John Otten, Isidro D. Ottenwalder, Michael Chung Ou)
  602. Positive passenger bag matching international standards. (In remembrance: Todd Joseph Ouida, Jesus Ovalles, Peter J. Owens, Jr.)
  603. RFID baggage tracking reducing mishandling and security gaps. (In remembrance: Adianes Oyola, Angel M. Pabon, Jr., Israel Pabon, Jr.)
  604. Air cargo piece-level screening technologies. (In remembrance: Roland Pacheco, Michael Benjamin Packer, Diana B. Padro)
  605. Canine explosive detection team breeding and training science. (In remembrance: Deepa Pakkala, Jeffrey Matthew Palazzo, Thomas Palazzo)
  606. Electronic odor detection complements to canine teams. (In remembrance: Richard A. Palazzolo, Orio Joseph Palmer, Frank Anthony Palombo)
  607. Homemade explosive training aids for safer canine instruction. (In remembrance: Alan N. Palumbo, Christopher Matthew Panatier, Dominique Lisa Pandolfo)
  608. Render-safe procedures for vehicle-borne IEDs in cities. (In remembrance: Jonas Martin Panik, Paul J. Pansini, John M. Paolillo)
  609. Robotics: tracked platforms for suspicious package investigation. (In remembrance: Edward Joseph Papa, Salvatore T. Papasso, James Nicholas Pappageorge)
  610. Backpack robots and throwable cameras for SWAT. (In remembrance: Marie Pappalardo, Vinod Kumar Parakat, Vijayashanker Paramsothy)
  611. Through-wall radar for hostage and collapse rescue. (In remembrance: Nitin Ramesh Parandkar, Hardai Parbhu, James Wendell Parham)
  612. Acoustic sensors for trapped-victim location in rubble. (In remembrance: Debra Marie Paris, George Paris, Gye Hyong Park)
  613. Search camera systems for void spaces in collapses. (In remembrance: Philip Lacey Parker, Michael Alaine Parkes, Robert E. Parks, Jr.)
  614. Concrete-cutting and breaching tools for US&R. (In remembrance: Hashmukh C. Parmar, Robert Parro, Diane Marie Parsons)
  615. Listening devices and SEER technology for entombed survivors. (In remembrance: Leobardo Lopez Pascual, Michael J. Pascuma, Jr., Jerrold Hughes Paskins)
  616. GPS-denied navigation aids for interior firefighting. (In remembrance: Horace Robert Passananti, Suzanne H. Passaro, Avnish Ramanbhai Patel)
  617. PASS device improvements reducing false alarms and missed signals. (In remembrance: Dipti Patel, Manish Patel, Steven Bennett Paterson)
  618. Firefighter location systems (WIP/indoor tracking research). (In remembrance: James Matthew Patrick, Manuel D. Patrocino, Bernard E. Patterson)
  619. Accountability tags and electronic passport systems on firegrounds. (In remembrance: Clifford L. Patterson, Jr., Cira Marie Patti, Robert E. Pattison)
  620. Mayday button integration on radios. (In remembrance: James Robert Paul, Patrice Paz, Victor Hugo Paz)
  621. Emergency evacuation signal standards on firegrounds. (In remembrance: Stacey Lynn Peak, Richard Allen Pearlman, Durrell V. Pearsall, Jr.)
  622. High-rise hose pack and standpipe operations training updates. (In remembrance: Thomas Nicholas Pecorelli, Thomas Pedicini, Todd Douglas Pelino)
  623. Wind-driven fire research changing high-rise tactics. (In remembrance: Mike Adrian Pelletier, Anthony G. Peluso, Angel R. Pena)
  624. Positive pressure ventilation (PPV) doctrine refinements. (In remembrance: Robert Penninger, Richard Al Penny, Salvatore F. Pepe)
  625. Battery-powered extrication tools for quieter, faster rescues. (In remembrance: Carl Allen B. Peralta, Robert David Peraza, Jon A. Perconti, Jr.)
  626. Stabilization strut systems for vehicle and structural collapse. (In remembrance: Alejo Perez, Angel Perez, Jr., Angela Susan Perez)
  627. Airbag lifting systems for heavy debris. (In remembrance: Anthony Perez, Ivan Antonio Perez, Nancy E. Perez)
  628. Crane and heavy-rigging mutual aid for urban collapse. (In remembrance: Berry Berenson Perkins, Joseph John Perroncino, Edward J. Perrotta)
  629. USAR marking systems standardized internationally. (In remembrance: Emelda H. Perry, Glenn C. Perry, Sr., John William Perry)
  630. INSARAG guidelines for international search deployments. (In remembrance: Franklin Allan Pershep, Danny Pesce, Michael John Pescherine)
  631. Disaster Medical Assistance telehealth reach-back. (In remembrance: Davin N. Peterson, Donald Arthur Peterson, Jean Hoadley Peterson)
  632. Psychological first aid training for responders and volunteers. (In remembrance: William Russell Peterson, Mark James Petrocelli, Philip Scott Petti)
  633. Grief counseling models for mass terrorism bereavement. (In remembrance: Glen Kerrin Pettit, Dominick A. Pezzulo, Kaleen Elizabeth Pezzuti)
  634. Peer-led family support networks after 9/11. (In remembrance: Kevin J. Pfeifer, Tu-Anh Pham, Kenneth John Phelan, Sr.)
  635. Anniversary-aware mental health surge planning each September. (In remembrance: Sneha Anne Philip, Eugenia McCann Piantieri, Ludwig John Picarro)
  636. Trauma-informed journalism guidelines after mass violence. (In remembrance: Matthew Picerno, Joseph O. Pick, Christopher J. Pickford)
  637. School counselor protocols after national traumatic events. (In remembrance: Dennis J. Pierce, Bernard Pietronico, Nicholas P. Pietrunti)
  638. Child-friendly spaces in family assistance centers. (In remembrance: Theodoros Pigis, Susan Elizabeth Pinto, Joseph Piskadlo)
  639. Photo and DNA family reference collection SOPs. (In remembrance: Christopher Todd Pitman, Joshua Michael Piver, Robert R. Ploger III)
  640. Ante-mortem data management for victim identification. (In remembrance: Zandra F. Ploger, Joseph Plumitallo, John M. Pocher)
  641. INTERPOL DVI (Disaster Victim Identification) guide adoption. (In remembrance: William Howard Pohlmann, Laurence Michael Polatsch, Thomas H. Polhemus)
  642. Portable morgue refrigerated capacity planning. (In remembrance: Steve Pollicino, Susan M. Pollio, Darin H. Pontell)
  643. Virtual memorial and name-wall digital experiences. (In remembrance: Joshua Iosua Poptean, Giovanna Porras, Anthony Portillo)
  644. Online tribute walls with moderation against abuse. (In remembrance: James Edward Potorti, Daphne Pouletsos, Richard N. Poulos)
  645. Crowdsourced oral history archives of survivors and families. (In remembrance: Stephen Emanual Poulos, Brandon Jerome Powell, Scott Alan Powell)
  646. Digital preservation of 9/11 artifacts and oral histories. (In remembrance: Shawn Edward Powell, Antonio Dorsey Pratt, Gregory M. Preziose)
  647. Museum security and visitor screening at sensitive memorials. (In remembrance: Wanda Ivelisse Prince, Vincent A. Princiotta, Kevin M. Prior)
  648. Respectful photography policies at mourning sites. (In remembrance: Everett Martin Proctor III, Carrie Beth Progen, David Lee Pruim)
  649. Counter-drone protection for major memorial events. (In remembrance: Richard A. Prunty, John Foster Puckett, Robert David Pugliese)
  650. National Day of Service and Remembrance civic volunteering. (In remembrance: Edward F. Pullis, Patricia Ann Puma, Jack D. Punches)
  651. Youth service projects channeling grief into community care. (In remembrance: Hemanth Kumar Puttur, Joseph J. Pycior, Jr., Edward R. Pykon)
  652. Interfaith vigils and shared mourning protocols for cities. (In remembrance: Christopher Quackenbush, Lars Peter Qualben, Lincoln Quappé)
  653. Foreign service and embassy security upgrades worldwide. (In remembrance: Beth Ann Quigley, Patrick J. Quigley IV, Michael T. Quilty)
  654. Diplomatic facility setback and blast standards. (In remembrance: James Francis Quinn, Ricardo J. Quinn, Carol Millicent Rabalais)
  655. Marine Security Guards and compound surveillance upgrades. (In remembrance: Christopher Peter Anthony Racaniello, Leonard J. Ragaglia, Eugene J. Raggio)
  656. Soft-skill cultural training reducing overseas friction risks. (In remembrance: Laura Marie Ragonese-Snik, Michael Paul Ragusa, Peter Frank Raimondi)
  657. Travel alerts and Smart Traveler Enrollment Program (STEP). (In remembrance: Harry A. Raines, Lisa J. Raines, Ehtesham Raja)
  658. Airline dark-website and crisis comms for families after incidents. (In remembrance: Valsa Raju, Edward J. Rall, Lukas Rambousek)
  659. GoTeams and CARE team airline family assistance models. (In remembrance: Maria Ramirez, Harry Ramos, Vishnoo Ramsaroop)
  660. Airport family reception center designs. (In remembrance: Deborah A. Ramsaur, Lorenzo E. Ramzey, Alfred Todd Rancke)
  661. Manifest reconciliation tech for passenger accountability. (In remembrance: Adam David Rand, Jonathan C. Randall, Shreyas S. Ranganath)
  662. Next-of-kin notification process digitization with dignity checks. (In remembrance: Anne T. Ransom, Faina Rapoport, Rhonda Sue Rasmussen)
  663. Secure video visitation for isolated ICU families in crises. (In remembrance: Robert A. Rasmussen, Amenia Rasool, R. Mark Rasweiler)
  664. Hospital family briefing apps during mass-casualty events. (In remembrance: Marsha D. Ratchford, David Alan James Rathkey, William Ralph Raub)
  665. Bed boards and regional divert systems for trauma load-balancing. (In remembrance: Gerard F. Rauzi, Alexey Razuvaev, Gregory Reda)
  666. Statewide trauma bed dashboards. (In remembrance: Sarah Anne Redheffer, Michele Marie Reed, Judith Ann Reese)
  667. Burn bed national tracking concepts. (In remembrance: Donald J. Regan, Robert M. Regan, Thomas Michael Regan)
  668. ECMO capability registries for surge. (In remembrance: Christian Michael Otto Regenhard, Howard Reich, Gregg Reidy)
  669. Blood type inventory prediction using AI demand models. (In remembrance: James Brian Reilly, Kevin O. Reilly, Timothy E. Reilly)
  670. Walking blood bank protocols for austere military care. (In remembrance: Joseph Reina, Jr., Thomas Barnes Reinig, Frank Bennett Reisman)
  671. Field blood transfusion advances saving wounded troops. (In remembrance: Joshua Scott Reiss, Karen Renda, John Armand Reo)
  672. Junctional tourniquets for battlefield and civilian trauma. (In remembrance: Richard Cyril Rescorla, John Thomas Resta, Sylvia San Pio Resta)
  673. XStat and wound stamping hemostatics research. (In remembrance: Martha M. Reszke, David E. Retik, Todd H. Reuben)
  674. iTClamp and adjunct hemorrhage devices. (In remembrance: Luis Clodoaldo Revilla Mier, Eduvigis Reyes, Jr., Bruce Albert Reynolds)
  675. Pelvic binders as standard MCI equipment. (In remembrance: John Frederick Rhodes, Francis Saverio Riccardelli, Rudolph N. Riccio)
  676. Hypothermia prevention in trauma (ready-heat, hypothermia wraps). (In remembrance: Ann Marie Riccoboni, David Harlow Rice, Eileen Mary Rice)
  677. Damage control resuscitation doctrine in civilian trauma centers. (In remembrance: Kenneth Frederick Rice III, CeCelia E. Richard, Vernon Allan Richard)
  678. Whole blood revival in trauma systems. (In remembrance: Claude Daniel Richards, Gregory David Richards, Michael Richards)
  679. TXA (tranexamic acid) protocols for bleeding patients. (In remembrance: Venesha Orintia Richards, Jimmy Riches, Alan Jay Richman)
  680. REBOA training for trauma/surgical teams. (In remembrance: John M. Rigo, Frederick Charles Rimmele III, Rose Mary Riso)
  681. Forward surgical team concepts informing civilian MCI surgery. (In remembrance: Moises N. Rivas, Joseph R. Rivelli, Jr., Carmen Alicia Rivera)
  682. Tele-mentored surgery research for austere care. (In remembrance: Isaias Rivera, Juan William Rivera, Linda Ivelisse Rivera)
  683. 3D-printed surgical guides for complex reconstruction. (In remembrance: David E. Rivers, Joseph R. Riverso, Paul V. Rizza)
  684. Facial prosthetics and reconstructive advances for blast survivors. (In remembrance: John Frank Rizzo, Stephen Louis Roach, Joseph Roberto)
  685. Advanced prosthetics and myoelectric limbs for amputees. (In remembrance: Leo Arthur Roberts, Michael E. Roberts, Michael Edward Roberts)
  686. Osseointegration for higher-function prosthetic attachment. (In remembrance: Donald Walter Robertson, Jr., Jeffrey Robinson, Michell Lee Jean Robotham)
  687. PTSD treatment: prolonged exposure, EMDR, and adapted protocols. (In remembrance: Donald Arthur Robson, Antonio A. Rocha, Raymond James Rocha)
  688. Virtual reality exposure therapy for PTSD. (In remembrance: Laura Rockefeller, John Michael Rodak, Antonio José Rodrigues)
  689. Pharmacologic research adjuncts for trauma memory. (In remembrance: Anthony Rodriguez, Carmen Milagros Rodriguez, Gregory E. Rodriguez)
  690. Sleep and nightmare treatment programs for responders. (In remembrance: Marsha A. Rodriguez, Mayra Valdes Rodriguez, Richard Rodriguez)
  691. Peer support dogs for veterans and responders. (In remembrance: David Bartolo Rodriguez-Vargas, Matthew Rogan, Jean Destrehan Rogér)
  692. Service animal access policies in emergency shelters. (In remembrance: Karlie Rogers, Scott William Rohner, Keith Michael Roma)
  693. Adaptive sports programs for wounded veterans. (In remembrance: Joseph M. Romagnolo, Efrain Romero, Sr., Elvin Romero)
  694. Career transition programs for medically retired service members. (In remembrance: James A. Romito, Sean Paul Rooney, Eric Thomas Ropiteau)
  695. Veteran suicide prevention lifelines and gun safety partnerships. (In remembrance: Aida Rosario, Angela Rosario, Mark H. Rosen)
  696. Community-based veteran peer networks. (In remembrance: Brooke David Rosenbaum, Linda Rosenbaum, Sheryl Lynn Rosenbaum)
  697. Military family readiness and casualty assistance reforms. (In remembrance: Lloyd Daniel Rosenberg, Mark Louis Rosenberg, Andrew Ira Rosenblum)
  698. Gold Star family support organizations and official liaison offices. (In remembrance: Joshua M. Rosenblum, Joshua Alan Rosenthal, Richard David Rosenthal)
  699. Tragedy Assistance Program for Survivors (TAPS)-style models. (In remembrance: Philip Martin Rosenzweig, Daniel Rosetti, Richard Barry Ross)
  700. Scholarship funds for children of the fallen. (In remembrance: Norman S. Rossinow, Nicholas P. Rossomando, Michael Craig Rothberg)
  701. Workplace leave policies for bereavement after terrorism. (In remembrance: Donna Marie Rothenberg, Mark David Rothenberg, James Michael Roux)
  702. Financial counseling for families navigating victim funds. (In remembrance: Nicholas Charles Alexander Rowe, Edward V. Rowenhorst, Judy Rowlett)
  703. Pro bono legal clinics for victim families. (In remembrance: Timothy Alan Roy, Sr., Paul G. Ruback, Ronald J. Ruben)
  704. Immigration relief pathways for certain victim families (where applicable). (In remembrance: Joanne Rubino, David M. Ruddle, Bart Joseph Ruggiere)
  705. Consular assistance for foreign national victims’ families. (In remembrance: Susan A. Ruggiero, Adam Keith Ruhalter, Gilbert Ruiz)
  706. Multilingual memorial ceremonies and name readings. (In remembrance: Robert E. Russell, Stephen P. Russell, Steven Harris Russin)
  707. Name pronunciation guides for public readings of the fallen. (In remembrance: Michael Thomas Russo, Sr., Wayne Alan Russo, William R. Ruth)
  708. Paper and digital programs ensuring no name is omitted. (In remembrance: Edward Ryan, John Joseph Ryan, Jonathan Stephan Ryan)
  709. Accessibility: braille and audio name directories at memorials. (In remembrance: Matthew L. Ryan, Tatiana Ryjova, Christina Sunga Ryook)
  710. Tactile memorial design for blind and low-vision visitors. (In remembrance: Thierry Saada, Jason Elazar Sabbag, Thomas E. Sabella)
  711. Quiet hours and contemplation spaces in memorial museums. (In remembrance: Scott H. Saber, Charles E. Sabin, Sr., Joseph Francis Sacerdote)
  712. Trauma-informed docent training for difficult history sites. (In remembrance: Jessica Leigh Sachs, Francis John Sadocha, Jude Elias Safi)
  713. Age-appropriate education programs about 9/11 for students. (In remembrance: Brock Joel Safronoff, Edward Saiya, John Patrick Salamone)
  714. Primary source packets for teachers on civic resilience. (In remembrance: Marjorie C. Salamone, Hernando Rafael Salas, Juan G. Salas)
  715. Anti-bias education reducing backlash against communities after attacks. (In remembrance: Esmerlin Antonio Salcedo, John Pepe Salerno, Rahma Salie)
  716. Bystander intervention training against hate harassment. (In remembrance: Richard L. Salinardi, Jr., Wayne John Saloman, Nolbert Salomon)
  717. Rapid response networks protecting houses of worship after threats. (In remembrance: Catherine Patricia Salter, Frank G. Salvaterra, Paul Richard Salvio)
  718. Community patrol partnerships with clear nonviolence norms. (In remembrance: Samuel Robert Salvo, Jr., Carlos Alberto Samaniego, John P. Sammartino)
  719. Youth digital citizenship reducing online radicalization pathways. (In remembrance: James Kenneth Samuel, Jr., Michael San Phillip, Hugo M. Sanay)
  720. Parent guides for talking with children after national tragedies. (In remembrance: Alva Cynthia Jeffries Sanchez, Jacquelyn Patrice Sanchez, Jesus Sanchez)
  721. Pediatric bereavement programs. (In remembrance: Raymond Sanchez, Eric M. Sand, Stacey Leigh Sanders)
  722. School memorial and moment-of-silence best practices. (In remembrance: Herman S. Sandler, Jim Sands, Jr., Ayleen J. Santiago)
  723. Employee assistance programs after collective national trauma. (In remembrance: Kirsten Reese Santiago, Maria Theresa Concepcion Santillan, Susan Gayle Santo)
  724. Manager toolkits for supporting grieving colleagues. (In remembrance: Christopher A. Santora, John August Santore, Mario L. Santoro)
  725. Faith-community mutual aid networks activated after disasters. (In remembrance: Rafael Humberto Santos, Rufino C.F. Santos III, Victor J. Saracini)
  726. Diaper banks, food banks, and soft-power resilience logistics. (In remembrance: Kalyan K. Sarkar, Chapelle Renee Stewart Sarker, Paul F. Sarle)
  727. Cash assistance platforms delivering aid faster with fraud controls. (In remembrance: Deepika Kumar Sattaluri, Gregory Thomas Saucedo, Susan M. Sauer)
  728. Cryptocurrency tracing tools against terror finance (Chainalysis-class). (In remembrance: Anthony Savas, Vladimir Savinkin, John Michael Sbarbaro)
  729. Nonprofit transparency tech reducing charity fraud. (In remembrance: David M. Scales, Robert Louis Scandole, Michelle Scarpitta)
  730. Crowdfunding platform trust & safety against exploitation of tragedies. (In remembrance: Dennis Scauso, John Albert Schardt, John G. Scharf)
  731. Platform crisis protocols for mass violence events. (In remembrance: Fred C. Scheffold, Jr., Angela Susan Scheinberg, Scott Mitchell Schertzer)
  732. Throttling amplification of graphic violence while informing public. (In remembrance: Sean Schielke, Steven Francis Schlag, Robert A. Schlegel)
  733. Verified crisis resource panels in social products. (In remembrance: Jon Schlissel, Karen Helene Schmidt, Ian Schneider)
  734. Geofenced emergency information during active incidents. (In remembrance: Thomas G. Schoales, Frank G. Schott, Jr., Gerard Patrick Schrang)
  735. Wireless Emergency Alerts Spanish and additional language expansion. (In remembrance: Jeffrey H. Schreier, John T. Schroeder, Susan Lee Schuler)
  736. WEA Spanish and multipolygon geo-targeting improvements. (In remembrance: Edward W. Schunk, Mark Evan Schurmeier, John Burkhart Schwartz)
  737. Public warning originator authentication (to fight fake alerts). (In remembrance: Mark Schwartz, Adriane Victoria Scibetta, Raphael Scorca)
  738. Emergency alert false-alarm reduction after system mishaps. (In remembrance: Janice M. Scott, Randolph Scott, Christopher Jay Scudder)
  739. Opt-out transparency for marketing vs. true emergency alerts. (In remembrance: Arthur Warren Scullin, Michael H. Seaman, Margaret M. Seeliger)
  740. Siren-app hybrids for outdoor workers. (In remembrance: Anthony Segarra, Carlos Segarra, Jason M. Sekzer)
  741. Industrial plant emergency notification integration with counties. (In remembrance: Matthew Carmen Sellitto, Michael L. Selves, Howard Selwyn)
  742. Campus outdoor warning and desktop alert systems. (In remembrance: Larry John Senko, Arturo Angelo Sereno, Frankie Serrano)
  743. Hotel TV interrupt emergency messaging. (In remembrance: Marian H. Serva, Alena Sesinova, Adele Christine Sessa)
  744. Airplane seatback and gate-display emergency messaging standards. (In remembrance: Sita Nermalla Sewnarine, Karen Lynn Seymour, Davis Grier Sezna, Jr.)
  745. Cruise ship mustering e-accountability systems. (In remembrance: Thomas Joseph Sgroi, Jayesh Shantilal Shah, Khalid M. Shahid)
  746. Lifeboat assignment digital accountability. (In remembrance: Mohammed Shajahan, Gary Shamay, Earl Richard Shanahan)
  747. Man-overboard detection systems. (In remembrance: Dan F. Shanower, Neil G. Shastri, Kathryn Anne Shatzoff)
  748. Automatic identification for small craft in busy harbors. (In remembrance: Barbara A. Shaw, Jeffrey James Shaw, Robert John Shay, Jr.)
  749. Recreational boater safety apps with emergency beacons. (In remembrance: Daniel James Shea, Joseph Patrick Shea, Kathleen Shearer)
  750. Personal locator beacons (PLB) cost reductions and awareness. (In remembrance: Robert M. Shearer, Linda June Sheehan, Hagay Shefi)
  751. MEOSAR satellite upgrades improving distress beacon detection. (In remembrance: Antionette M. Sherman, John Anthony Sherry, Atsushi Shiratori)
  752. COSPAS-SARSAT modernization saving mariners and aviators. (In remembrance: Thomas Joseph Shubert, Mark Shulman, See Wong Shum)
  753. Mountain rescue smartphone pings and avalanche beacon tech. (In remembrance: Allan Abraham Shwartzstein, Clarin Shellie Siegel-Schwartz, Johanna Sigmund)
  754. National Park SAR GPS and radio improvements. (In remembrance: Dianne T. Signer, Gregory Sikorsky, Stephen Gerard Siller)
  755. Wildland firefighter tracking and crew location awareness. (In remembrance: David Silver, Craig A. Silverstein, Nasima H. Simjee)
  756. Fire shelter redesign research after entrapment lessons. (In remembrance: Bruce Edward Simmons, Diane M. Simmons, Donald D. Simmons)
  757. Protective fire clothing breathability vs. protection balance. (In remembrance: George W. Simmons, Arthur Simon, Kenneth Alan Simon)
  758. Heat stress monitors for responders in PPE. (In remembrance: Michael J. Simon, Paul Joseph Simon, Marianne Liquori Simone)
  759. Cooling vest systems for hazmat and bomb technicians. (In remembrance: Barry Simowitz, Jane Louise Simpkin, Jeff Lyal Simpson)
  760. Hydration and work-rest cycle apps for incident rehab. (In remembrance: Cheryle D. Sincock, Khamladai Khami Singh, Roshan Ramesh Singh)
  761. Incident rehab and medical monitoring standards (NFPA). (In remembrance: Thomas E. Sinton III, Peter A. Siracuse, Muriel F. Siskopoulos)
  762. Cancer presumptive legislation supporting firefighter health. (In remembrance: Joseph Michael Sisolak, John P. Skala, Francis Joseph Skidmore, Jr.)
  763. WTC Health Program expansions as model for occupational cohorts. (In remembrance: Toyena Corliss Skinner, Paul A. Skrzypek, Christopher Paul Slattery)
  764. Registry science for long-term disaster exposure. (In remembrance: Vincent Robert Slavin, Robert F. Sliwak, Paul Kenneth Sloan)
  765. Open data on hazards empowering community advocacy. (In remembrance: Stanley S. Smagala, Jr., Wendy L. Small, Gregg H. Smallwood)
  766. Community air monitoring after industrial and attack-related plumes. (In remembrance: Catherine T. Smith, Daniel Laurence Smith, Gary F. Smith)
  767. Low-cost sensor networks for neighborhood environmental health. (In remembrance: George Eric Smith, Heather Lee Smith, James Gregory Smith)
  768. Transparent after-action reports driving public trust. (In remembrance: Jeffrey R. Smith, Joyce Patricia Smith, Karl T. Smith, Sr.)
  769. Independent after-action authorities for major failures. (In remembrance: Kevin Joseph Smith, Leon Smith, Jr., Moira Ann Smith)
  770. Whistleblower-protected safety reporting in transit agencies. (In remembrance: Rosemary A. Smith, Bonnie Shihadeh Smithwick, Rochelle Monique Snell)
  771. Close-call transit reporting reducing accidents. (In remembrance: Christine Ann Snyder, Dianne Bullis Snyder, Leonard J. Snyder, Jr.)
  772. Positive safety culture programs in airlines (ASAP, FOQA). (In remembrance: Astrid Elizabeth Sohan, Sushil S. Solanki, Rubén Solares)
  773. Aviation Safety Action Program confidential reporting. (In remembrance: Naomi Leah Solomon, Daniel W. Song, Mari-Rae Sopper)
  774. Flight Operational Quality Assurance data for risk reduction. (In remembrance: Michael Charles Sorresse, Fabian Soto, Timothy Patrick Soulas)
  775. Unmanned traffic management safety cases. (In remembrance: Gregory Thomas Spagnoletti, Donald F. Spampinato, Jr., Thomas Sparacio)
  776. Urban air mobility security concepts. (In remembrance: John Anthony Spataro, Robert W. Spear, Jr., Robert Speisman)
  777. Vertiport security design guidance. (In remembrance: Maynard S. Spence, Jr., George Edward Spencer III, Robert Andrew Spencer)
  778. evtol geofencing and identity broadcast requirements. (In remembrance: Mary Rubina Sperando, Frank Spinelli, William E. Spitz)
  779. Critical infrastructure dependency analysis for cascading failures. (In remembrance: Joseph Patrick Spor, Jr., Klaus Johannes Sprockamp, Saranya Srinuan)
  780. Black-sky exercises for long-duration power outages. (In remembrance: Fitzroy St. Rose, Michael F. Stabile, Lawrence T. Stack)
  781. EMP and GMD (geomagnetic disturbance) hardening research. (In remembrance: Timothy M. Stackpole, Richard James Stadelberger, Eric Adam Stahlman)
  782. Grid-forming inverters supporting resilient microgrids. (In remembrance: Gregory Stajk, Alexandru Liviu Stan, Corina Stan)
  783. Hospital islanding capability for power independence. (In remembrance: Mary Domenica Stanley, Anthony Starita, Jeffrey Stark)
  784. Fuel cell backup pilots for cell towers. (In remembrance: Derek James Statkevicus, Patricia J. Statz, Craig William Staub)
  785. Hardened cellular sites on wheels for NSSEs. (In remembrance: William V. Steckman, Eric Thomas Steen, William R. Steiner)
  786. Public safety IoT standards reducing insecure device sprawl. (In remembrance: Alexander Robbins Steinman, Edna L. Stephens, Andrew Stergiopoulos)
  787. Medical device cybersecurity guidance (FDA). (In remembrance: Andrew J. Stern, Norma Lang Steuerle, Martha Jane Stevens)
  788. Infusion pump and imaging system segmentation in hospitals. (In remembrance: Michael James Stewart, Richard H. Stewart, Jr., Sanford M. Stoller)
  789. Legacy biomedical device isolation strategies. (In remembrance: Douglas Joel Stone, Lonny Jay Stone, Jimmy Nevill Storey)
  790. OR and ICU downtime procedures for cyber events. (In remembrance: Timothy Stout, Thomas Strada, James J. Straine, Jr.)
  791. Paper downtime kits revitalized for EHR outages. (In remembrance: Edward W. Straub, George J. Strauch, Jr., Edward Thomas Strauss)
  792. Cyber tabletop exercises for hospital executives. (In remembrance: Steven R. Strauss, Larry L. Strickland, Steven F. Strobert)
  793. Regional healthcare coalitions for cyber mutual aid. (In remembrance: Walwyn Wellington Stuart, Jr., Benjamin Suarez, David Scott Suarez)
  794. HHS HC3 threat intel for health sector. (In remembrance: Ramon Suarez, Dino Xavier Suarez Ramirez, Yoichi Sumiyama Sugiyama)
  795. 415/Health-ISAC membership growth. (In remembrance: William Christopher Sugra, Daniel Thomas Suhr, David Marc Sullins)
  796. Pipeline cyber-physical security after high-profile incidents. (In remembrance: Christopher P. Sullivan, Patrick Sullivan, Thomas G. Sullivan)
  797. Water sector cyber hygiene campaigns. (In remembrance: Hilario Soriano Sumaya, Jr., James Joseph Suozzo, Colleen M. Supinski)
  798. Agricultural GPS and precision-ag cyber awareness. (In remembrance: Robert Sutcliffe, Seline Sutter, Claudia Suzette Sutton)
  799. GPS spoofing detection for ports and aviation. (In remembrance: John Francis Swaine, Kristine M. Swearson, Brian David Sweeney)
  800. AIS and ADS-B anomaly detection research. (In remembrance: Brian Edward Sweeney, Madeline Amy Sweeney, Kenneth J. Swenson)
  801. Space domain awareness sharing for debris and threats. (In remembrance: Thomas F. Swift, Derek Ogilvie Sword, Kevin Thomas Szocik)
  802. Commercial SSA (space situational awareness) data for operators. (In remembrance: Gina Sztejnberg, Norbert P. Szurkowski, Harry Taback)
  803. Satellite jamming detection and reporting. (In remembrance: Joann C. Tabeek, Norma C. Taddei, Michael Taddonio)
  804. Resilient PNT complementary to GPS for first responders. (In remembrance: Keiichiro Takahashi, Keiji Takahashi, Phyllis Gail Talbot)
  805. eLoran and terrestrial timing backup pilots. (In remembrance: Robert R. Talhami, John Talignani, Sean Patrick Tallon)
  806. Fiber route diversity requirements for PSAPs. (In remembrance: Paul Talty, Maurita Tam, Rachel Tamares)
  807. NG911 ESINet diversely routed networks. (In remembrance: Hector Rogan Tamayo, Michael Andrew Tamuccio, Kenichiro Tanaka)
  808. PSAP backup facilities and mirrored call-taking. (In remembrance: Rhondelle Cherie Tankard, Michael Anthony Tanner, Dennis Gerard Taormina, Jr.)
  809. Cloud-native 911 call-taking with on-prem failback. (In remembrance: Kenneth Joseph Tarantino, Allan Tarasiewicz, Michael C. Tarrou)
  810. Remote telecommunicator surge staffing models. (In remembrance: Ronald Tartaro, Deborah Tavolarella, Darryl Anthony Taylor)
  811. 911 telecommunicator PTSD and wellness programs. (In remembrance: Donnie Brooks Taylor, Hilda E. Taylor, Kip P. Taylor)
  812. Quality assurance AI assisting (not replacing) call review. (In remembrance: Leonard E. Taylor, Lorisa Ceylon Taylor, Michael Morgan Taylor)
  813. Protocolized EMD (emergency medical dispatch) card updates. (In remembrance: Sandra C. Taylor, Sandra Dawn Teague, Karl W. Teepe)
  814. Pre-arrival instructions saving lives before EMS arrival. (In remembrance: Paul A. Tegtmeier, Yeshavant Moreshwar Tembe, Anthony Tempesta)
  815. Dispatcher-assisted CPR and AED location guidance. (In remembrance: Dorothy Pearl Temple, Stanley L. Temple, David Gustaf Peter Tengelin)
  816. Bleeding control pre-arrival instructions research. (In remembrance: Brian John Terrenzi, Lisa Marie Terry, Goumatie Thackurdeen)
  817. Active assailant pre-arrival instruction protocols. (In remembrance: Harshad Sham Thatte, Michael Theodoridis, Thomas F. Theurkauf, Jr.)
  818. Standardized plain-language radio replacing 10-codes (where adopted). (In remembrance: Lesley Anne Thomas, Brian Thomas Thompson, Clive Ian Thompson)
  819. ICS forms digitized for faster incident documentation. (In remembrance: Glenn Thompson, Nigel Bruce Thompson, Perry A. Thompson)
  820. Common operating picture layers: weather, traffic, cameras, units. (In remembrance: Vanavah Alexei Thompson, William H. Thompson, Eric Raymond Thorpe)
  821. Waze/connected-car data for emergency routing (privacy-aware). (In remembrance: Nichola Angela Thorpe, Tamara C. Thurman, Sal Edward Tieri, Jr.)
  822. Traffic signal preemption for fire apparatus. (In remembrance: John Patrick Tierney, Mary Ellen Tiesi, William Randolph Tieste)
  823. Emergency vehicle alerting systems to connected cars. (In remembrance: Kenneth Tietjen, Stephen Edward Tighe, Scott Charles Timmes)
  824. Smart corridor priority for EMS. (In remembrance: Michael E. Tinley, Jennifer M. Tino, Robert Frank Tipaldi)
  825. UAV traffic deconfliction near incident airspace. (In remembrance: John James Tipping II, David Tirado, Hector Luis Tirado, Jr.)
  826. Temporary Flight Restrictions automated notification to pilots. (In remembrance: Michelle Lee Titolo, Alicia Nicole Titus, John J. Tobin)
  827. LAANC for drone authorization near airports. (In remembrance: Richard J. Todisco, Otis V. Tolbert, Vladimir Tomasevic)
  828. Remote ID making drones accountable in sensitive airspace. (In remembrance: Stephen Kevin Tompsett, Thomas Tong, Doris Torres)
  829. Geo-awareness firmware restricting flight near prisons/airports. (In remembrance: Luis Eduardo Torres, Amy Elizabeth Toyen, Christopher Michael Traina)
  830. Public reporting apps for reckless drone operations. (In remembrance: Daniel Patrick Trant, Abdoul Karim Traore, Glenn J. Travers, Sr.)
  831. Stadium RF detection of unauthorized video downlinks. (In remembrance: Walter Philip Travers, Felicia Yvette Traylor-Bass, James Anthony Trentini)
  832. Secure wireless mics and comms for event security teams. (In remembrance: Mary Barbara Trentini, Lisa L. Trerotola, Karamo Baba Trerra)
  833. Credentialed media staging reducing chaos at scenes. (In remembrance: Michael Angel Trinidad, Francis Joseph Trombino, Gregory James Trost)
  834. Joint information system templates for PIOs. (In remembrance: Willie Q. Troy, William P. Tselepis, Jr., Zhanetta Valentinovna Tsoy)
  835. Multilingual press briefing practices. (In remembrance: Michael Patrick Tucker, Lance Richard Tumulty, Ching Ping Tung)
  836. Accessible press materials (ASL, captions) during emergencies. (In remembrance: Simon James Turner, Donald Joseph Tuzio, Robert T. Twomey)
  837. Rumor control officers embedded in JICs. (In remembrance: Jennifer Lynn Tzemis, John G. Ueltzhoeffer, Tyler Victor Ugolyn)
  838. Social listening dashboards for emergency PIOs. (In remembrance: Michael A. Uliano, Jonathan J. Uman, Anil Shivhari Umarkar)
  839. Verified government WhatsApp/Telegram channels in some cities. (In remembrance: Allen V. Upton, Diane Marie Urban, John Damien Vaccacio)
  840. SMS short codes for local emergency information. (In remembrance: Bradley Hodges Vadas, William Valcarcel, Felix Antonio Vale)
  841. Parking lot and curb management reducing VBIED residual risk. (In remembrance: Ivan Vale, Benito Valentin, Santos Valentin, Jr.)
  842. Pop-up vehicle barrier deployment training for police. (In remembrance: Carlton Francis Valvo II, Pendyala Vamsikrishna, Erica H. Van Acker)
  843. Hostile Vehicle Mitigation guidance from CISA/NCTC. (In remembrance: Kenneth W. Van Auken, R. Bruce Van Hine, Daniel M. Van Laere)
  844. Market and festival perimeter security kits. (In remembrance: Edward Raymond Vanacore, Jon Charles Vandevander, Frederick T. Varacchi)
  845. Holiday soft-target surge staffing playbooks. (In remembrance: Gopalakrishnan Varadhan, David Vargas, Scott C. Vasel)
  846. House of worship usher security training. (In remembrance: Azael Ismael Vasquez, Ronald J. Vauk, Arcangel Vazquez)
  847. Greeter roles trained to spot surveillance and hostile recon. (In remembrance: Santos Vazquez, Peter Vega, Sankara Sastry Velamuri)
  848. See Something training for parking attendants and janitors. (In remembrance: Jorge Velazquez, Lawrence G. Veling, Anthony Mark Ventura)
  849. Hospitality security: guest room and loading dock controls. (In remembrance: David Vera, Loretta Ann Vero, Christopher James Vialonga)
  850. Key control and electronic lock audit trails in hotels. (In remembrance: Matthew Gilbert Vianna, Robert Anthony Vicario, Celeste Torres Victoria)
  851. Panic buttons for hotel staff and hospital workers. (In remembrance: Joanna Vidal, John T. Vigiano II, Joseph Vincent Vigiano)
  852. Duress codes in schools and clinics. (In remembrance: Frank J. Vignola, Jr., Joseph Barry Vilardo, Claribel Villalobos Hernandez)
  853. Silent alarm apps for staff under threat. (In remembrance: Sergio Gabriel Villanueva, Chantal Vincelli, Melissa Renée Vincent)
  854. Classroom door locks operable from inside without hallway exposure. (In remembrance: Francine Ann Virgilio, Lawrence Virgilio, Joseph Gerard Visciano)
  855. Window privacy and ballistic film debates informing local policy. (In remembrance: Joshua S. Vitale, Maria Percoco Vola, Lynette D. Vosges)
  856. Anonymous reporting apps for students (with follow-up capacity). (In remembrance: Garo H. Voskerijian, Alfred Anton Vukosa, Gregory Kamal Bruno Wachtler)
  857. Behavioral threat assessment software assisting multidisciplinary teams. (In remembrance: Karen J. Wagner, Mary Alice Wahlstrom, Honor Elizabeth Wainio)
  858. Safer storage campaigns reducing firearm access in crises. (In remembrance: Gabriela Silvina Waisman, Wendy Alice Rosario Wakeford, Courtney Wainsworth Walcott)
  859. Extreme risk protection order implementation support tools. (In remembrance: Victor Wald, Kenneth E. Waldie, Benjamin James Walker)
  860. Child-access prevention education. (In remembrance: Glen Wall, Mitchel Scott Wallace, Peter Guyder Wallace)
  861. Suicide prevention lethal-means counseling for families. (In remembrance: Robert Francis Wallace, Roy Michael Wallace, Jeanmarie Wallendorf)
  862. Crisis Text Line partnerships with local 911. (In remembrance: Matthew Blake Wallens, Meta L. Waller, John Wallice, Jr.)
  863. 988–911 interoperability so crises reach the right help. (In remembrance: Barbara P. Walsh, Jim Walsh, Jeffrey P. Walz)
  864. Co-response vans pairing clinicians with officers. (In remembrance: Ching Wang, Weibin Wang, Michael Warchola)
  865. Mobile crisis units reducing unnecessary force encounters. (In remembrance: Stephen Gordon Ward, Timothy Ray Ward, James A. Waring)
  866. Crisis stabilization centers as ER alternatives. (In remembrance: Brian G. Warner, Derrick Christopher Washington, Charles Waters)
  867. Peer respite and trauma recovery centers. (In remembrance: James Thomas Waters, Jr., Patrick J. Waters, Kenneth Thomas Watson)
  868. Community resilience hubs with power, cooling, and information. (In remembrance: Michael Henry Waye, Todd Christopher Weaver, Walter Edward Weaver)
  869. Neighborhood emergency teams (NET/CERT) volunteer training. (In remembrance: Nathaniel Webb, Dinah Webster, William Michael Weems)
  870. Community Emergency Response Team curriculum updates. (In remembrance: Joanne Flora Weil, Michael T. Weinberg, Steven Weinberg)
  871. Map Your Neighborhood and similar hyperlocal preparedness. (In remembrance: Scott Jeffrey Weingard, Steven George Weinstein, Simon Weiser)
  872. Multifamily building floor warden programs. (In remembrance: David M. Weiss, David Thomas Weiss, Chin Sun Pak Wells)
  873. High-rise residential evacuation training for residents. (In remembrance: Vincent Michael Wells, Deborah Jacobs Welsh, Timothy Matthew Welty)
  874. Refuge area signage and disability evacuation planning. (In remembrance: Christian Hans Rudolf Wemmers, Ssu-Hui Wen, John Joseph Wenckus)
  875. Evacuation elevator use research for people with disabilities. (In remembrance: Oleh D. Wengerchuk, Peter M. West, Whitfield West, Jr.)
  876. Stair descent devices cached in high-rises. (In remembrance: Meredith Lynn Whalen, Eugene Michael Whelan, Adam S. White)
  877. Photoluminescent exit path markings in stairwells. (In remembrance: Edward James White III, James Patrick White, John Sylvester White)
  878. Talking signs and wayfinding for smoke and power loss. (In remembrance: Kenneth Wilburn White, Jr., Leonard Anthony White, Malissa Y. White)
  879. Battery-backed exit lighting standards enforcement. (In remembrance: Maudlyn A. White, Sandra L. White, Wayne White)
  880. Generator transfer switch testing regimes. (In remembrance: Leanne Marie Whiteside, Mark P. Whitford, Leslie A. Whittington)
  881. Fuel polishing and testing for emergency generators. (In remembrance: Michael T. Wholey, Mary Lenz Wieman, Jeffrey David Wiener)
  882. Load shed priorities protecting life safety circuits. (In remembrance: William J. Wik, Alison Marie Wildman, Glenn E. Wilkinson)
  883. Fire pump redundancy and pressure monitoring. (In remembrance: Ernest M. Willcher, John Charles Willett, Brian Patrick Williams)
  884. Sprinkler reliability and impairment management programs. (In remembrance: Candace Lee Williams, Crossley Richard Williams, Jr., David J. Williams)
  885. In-rack sprinkler and ESFR systems for warehouses. (In remembrance: David Lucian Williams, Debbie L. Williams, Dwayne Williams)
  886. Lithium battery storage occupancy separations in codes. (In remembrance: Kevin Michael Williams, Louie Anthony Williams, Louis Calvin Williams III)
  887. Hazardous material inventory digital reporting to fire departments. (In remembrance: John P. Williamson, Donna Ann Wilson, William Eben Wilson)
  888. Pre-incident planning software for fire companies. (In remembrance: David Harold Winton, Glenn J. Winuk, Thomas Francis Wise)
  889. Building information modeling (BIM) shared with first responders. (In remembrance: Alan L. Wisniewski, Frank Paul Wisniewski, David Wiswall)
  890. Knox-Box and secure key access modernization. (In remembrance: Sigrid Charlotte Wiswe, Michael R. Wittenstein, Christopher W. Wodenshek)
  891. Emergency elevator keys and firefighter service standardization. (In remembrance: Martin Phillips Wohlforth, Katherine Susan Wolf, Jennifer Yen Wong)
  892. Stairwell re-entry and unlock policies post-investigation lessons. (In remembrance: Siucheung Steve Wong, Yin Ping Wong, Yuk Ping Wong)
  893. Fire service access elevators in tall building codes. (In remembrance: Brent James Woodall, James John Woods, Marvin Roger Woods)
  894. Occupant evacuation elevators research and limited adoption. (In remembrance: Patrick J. Woods, Richard Herron Woodwell, David Terence Wooley)
  895. Voice evacuation systems with intelligible speech standards. (In remembrance: John Bentley Works, Martin Michael Wortley, Rodney James Wotton)
  896. Mass notification systems (MNS) in campuses and bases. (In remembrance: William Wren, Ret., John W. Wright, Jr., Neil Robin Wright)
  897. Giant voice outdoor speaker networks on military installations. (In remembrance: Sandra Lee Wright, Jupiter Yambem, John D. Yamnicky, Sr.)
  898. Installation entry control with vehicle barriers and ID systems. (In remembrance: Suresh Yanamadala, Vicki Yancey, Shuyin Yang)
  899. Base active shooter exercise programs (Eagle Eval-type). (In remembrance: Matthew David Yarnell, Myrna Yaskulka, Shakila Yasmin)
  900. Armory and weapons storage intrusion alarms. (In remembrance: Olabisi Shadie Layeni Yee, Kevin W. Yokum, Edward P. York)
  901. Recruit training on insider threat and espionage awareness. (In remembrance: Kevin Patrick York, Raymond R. York, Suzanne Martha Youmans)
  902. OPSEC training for military families on social media. (In remembrance: Barrington Leroy Young, Jr., Donald McArthur Young, Edmond G. Young, Jr.)
  903. Geotagging awareness to protect troop movements. (In remembrance: Jacqueline Young, Lisa L. Young, Elkin Yuen)
  904. Commercial imagery analysis for open-source defense intelligence. (In remembrance: Joseph C. Zaccoli, Adel Agayby Zakhary, Arkady Zaltsman)
  905. SAR satellite tasking for disaster and maritime distress. (In remembrance: Edwin J. Zambrana, Jr., Robert Alan Zampieri, Mark Zangrilli)
  906. Nighttime lights analysis for blackout and conflict monitoring. (In remembrance: Christopher R. Zarba, Jr., Ira Zaslow, Kenneth Albert Zelman)
  907. Crowdsourced damage mapping (HOT OSM) after disasters. (In remembrance: Abraham J. Zelmanowitz, Martin Morales Zempoaltecatl, Zhe Zeng)
  908. UAV orthomosaic maps for incident commanders within hours. (In remembrance: Marc Scott Zeplin, Jie Yao Justin Zhao, Yuguang Zheng)
  909. Digital elevation models for flood and plume planning. (In remembrance: Ivelin Ziminski, Michael Joseph Zinzi, Charles Alan Zion)
  910. Hydrologic sensors feeding real-time flood inundation maps. (In remembrance: Julie Lynne Zipper, Salvatore J. Zisa, Prokopios Paul Zois)
  911. Community flood gauges with public dashboards. (In remembrance: Joseph J. Zuccala, Andrew Steven Zucker, Igor Zukelman)

What Remains for the Next Twenty-Five Years?

Remembrance without action becomes ritual alone. Action without remembrance becomes machinery. The work ahead is both: keep saying the names, and keep designing protection that still feels human — security that does not require abandoning dignity, pluralism, or hope.

To every family still carrying September 11: you are not alone in the quiet. To every responder still answering the call: your courage is a living memorial. To the next generation: inherit the story as responsibility, not only as history.

We remember. We protect. We choose one another — again.

Further remembrance: National September 11 Memorial & Museum · Memorial Guide — find a name

Frequently Asked Questions

How many people died in the September 11 attacks?

Nearly 3,000 people were killed in the September 11, 2001 attacks at the World Trade Center, the Pentagon, and aboard Flights 11, 77, 93, and 175. Official memorial listings are maintained by the National September 11 Memorial & Museum.

What public safety innovations followed 9/11?

Major advances included new aviation screening and cockpit security, the Department of Homeland Security and fusion centers, interoperable responder communications, Next Generation 911 and wireless alerts, critical infrastructure and cybersecurity programs, trauma and hemorrhage-control practices such as Stop the Bleed, and stronger building and evacuation standards informed by the WTC investigations.

How should we commemorate the 25th anniversary of 9/11?

Commemorate with empathy for families and survivors, public remembrance of names, support for responders’ health and grief needs, civic service, and renewed commitment to safety practices that protect life without abandoning human dignity.

Where can I find a loved one’s name on the 9/11 Memorial?

Use the National September 11 Memorial & Museum Memorial Guide at names.911memorial.org to search by name and locate the panel on the Memorial.

Why pair innovations with victims’ names?

The pairing is a dedication, not a transaction: it keeps human lives at the center while acknowledging that many people responded to loss by building better ways to protect others. Progress does not replace grief; it can honor it.

Image Credits: Pexels

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Claude to clean up the article.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Merging Two Customer Experiences After M&A

Leave a reply

Where to Start

Merging Two Customer Experiences After M&A

by Braden Kelley and Art Inteligencia

Every M&A announcement talks about synergies, market position, and combined capabilities. Almost none of them talk about the fact that, on day one, you now have two customer bases who each learned to expect something different from the companies they chose — and neither of them signed up for the other company’s version of the relationship.

The assumption that quietly sinks post-merger CX

The default assumption in most integrations is that the better-resourced or larger company’s experience simply becomes the standard, and the other customer base adjusts. I’ve watched this assumption cost companies real customers, because it skips a step that matters enormously: nobody has actually compared the two experiences at the touchpoint level to know which one is genuinely better, versus just louder or more familiar to the leadership team making the call.

Two journeys, two sets of expectations, one deadline

Integration timelines are usually set by finance and legal milestones — closing conditions, systems cutover dates, reporting deadlines — not by how long it actually takes to understand two customer journeys well enough to merge them intelligently. That mismatch is where the damage happens. Support processes get unified before anyone’s mapped where they genuinely differ. Pricing and billing experiences get standardized before anyone’s identified which parts of each were actually working. By the time customer complaints start flagging the problems, the systems decisions are already locked in, and unwinding them costs far more than getting it right the first time would have.

Start by mapping both journeys independently, before merging anything

The instinct in an integration is to move fast toward one unified experience, because ambiguity feels risky to the deal’s momentum. I’d argue the opposite is true here: the riskiest move is unifying before you understand what you’re unifying. Mapping both customer journeys independently — validated personas, current-state touchpoints, the data each company has been collecting, and, critically, walking both journeys firsthand rather than trusting either side’s internal narrative about how good their own experience is — gives you an honest picture before any integration decision gets made instead of after.

Whose employees explain the friction matters as much as whose customers report it

In an acquisition especially, frontline employees from the acquired company often sit on institutional knowledge about their customers’ real pain points and workarounds that never made it into any deck during diligence. They also, often, feel like their side of the business is being absorbed rather than genuinely evaluated — which makes them less likely to volunteer that knowledge unless someone specifically goes looking for it. An audit that treats both organizations’ frontline teams as equally credible sources, rather than defaulting to whichever side is running the integration, tends to surface friction neither leadership team knew existed.

Benchmark both experiences against the market, not against each other

The other trap is treating this purely as an internal comparison — which company’s process wins. The more useful question is how each one stacks up against what customers in the combined market now expect, especially if the merger changes your competitive position or brings you into contact with a new set of competitors either customer base is now implicitly being compared against.

What this actually buys you

Getting this right doesn’t just avoid a bad integration story — it turns the merger into a genuine opportunity to build a better combined experience than either company had running independently, using the best of what each side was actually doing well. That’s a very different outcome than the default of one side’s process quietly winning by default and both customer bases losing something in the process.

If you’re heading into an integration and want an independent, evidence-based read on both customer experiences before any systems or process decisions get locked in, a Customer Experience Audit scoped to both organizations is exactly the kind of diagnostic this moment calls for. And if you want a rough sense of what experience misalignment could cost during an integration before you scope that engagement, the CX ROI Calculator is a fast place to start.

Customer Experience Audit Checklist

Download the Customer Experience Audit Checklist as a PDF

Image Credits: Pexels

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Claude to clean up the article.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

What Is Partner Experience — and Why Does It Matter?

Leave a reply

What Is Partner Experience — and Why Does It Matter?

by Braden Kelley and Art Inteligencia

What Is Partner Experience? (Short Answer)

Partner experience (PX) is how distributors, suppliers, agencies, developers, and other ecosystem partners experience working with an organization — contracting, onboarding, portals, enablement, support, getting paid, and joint go-to-market. It is not a partner portal alone or a quarterly business review. From the customer’s point of view, partners are often an extension of you. Their friction becomes your broken promise.

Partners are an extension of your brand from the customer’s point of view — their experience is your experience, whether you designed it or not.

Below you’ll find where PX actually happens, what the term is often confused with, why it matters for customers and the business, and how you know you are improving it rather than managing partners as a cost center. This definition aligns with the one in my Experience Design Glossary.

Where Does Partner Experience Actually Happen?

Partners do not experience your alliance slide. They experience the work of doing business with you.

  • Before the relationship is live — reputation as a partner worth committing to, evaluation, contracting, security reviews, and whether the path to “yes” is clear or exhausting.
  • Onboarding and enablement — access to systems, training that matches the real job, product updates that arrive in time to sell or deliver, and a first win that does not require heroics.
  • Day-to-day operations — portals that help or fight every task, support channels that answer, escalation paths that work, inventory and order status you can trust, and getting paid without a scavenger hunt.
  • Joint go-to-market and renewal — shared pipeline clarity, co-marketing that is usable, deal registration that feels fair, and renewals that reflect the lived relationship — not only the contract anniversary.

Operational partners (resellers, distributors, integrators, suppliers, agencies, technology providers) deliver on your behalf. Capital partners (investors, funders, and in some contexts donors) experience a different commercial dynamic, but clarity, reliability, and follow-through still shape how far they commit. Most organizations under-design the operational partner journey first — and customers feel that gap first.

If you cannot name the partner job that is failing — onboard, sell, deliver, get support, get paid — you are managing accounts, not partner experience.

What Is Partner Experience Not?

  • Not the partner portal alone. A login is a channel. PX includes contracting, enablement, human support, payment, and the seams between your teams when a partner is stuck.
  • Not only procurement or legal’s job. Those functions shape critical moments. The lived experience is also produced by channel ops, product, finance, support, marketing, and whoever owns deal registration and escalations.
  • Not channel marketing mistaken for the whole relationship. Co-branded assets matter. They do not fix slow onboarding, unpaid invoices, or a support queue that treats partners as second-class customers.
  • Not invisible until revenue misses. Partners often disengage quietly — fewer deals registered, slower responses, softer advocacy — long before the dashboard shows a cliff. By then, customers have already absorbed the friction.

A partner program slide is not a partner experience. Finishable partner jobs are.

Why Does Partner Experience Matter for Customers and the Business?

Customers rarely separate “your company” from “the partner who showed up.”

  • Brand inheritance. The reseller who onboards poorly, the distributor who cannot get a status update, the integrator who waits weeks for an answer — that delay and confusion lands as your customer experience. I define that customer side in What Is Customer Experience?.
  • Capacity you do not control directly. Partners extend your reach. If their tools, incentives, and support are broken, no amount of internal EX polish fully protects the outside journey. Employee experience still matters — see What Is Employee Experience — and Why Does It Shape CX? — but partners are a third link in the same chain.
  • Hidden risk. Slow payments, confusing onboarding, and unclear escalation paths rarely appear in customer surveys as “partner experience.” They appear as late delivery, wrong setup, unanswered questions, and quiet churn.

That is why partner experience belongs beside CX and EX — a case I made in Beyond Customer Experience: Other Experiences That Matter, and why planning should not stop at a customer-only audit.

Fixing only the customer-facing symptom often means treating a cause that sits in the partner relationship.

How Do You Know You Are Improving Partner Experience?

Improving PX means changing what partners can finish with you — not only how many attended the partner summit.

  1. Can partners complete the jobs that matter — get contracted, get enabled, sell or deliver, get support, get paid — without heroics or side channels?
  2. Is time-to-first-value shrinking for new partners, with clear owners when something stalls?
  3. Do escalation paths work across your internal seams, so partners are not bounced between product, support, and channel teams?
  4. Is payment and administrative friction going down, not dismissed as “just finance”?
  5. Are you learning from the lived partner journey, including quiet disengagement — not only QBR slides? A partner experience audit looks at what it is like to work with you; for planning PX beside customer and employee audits, see Customer, Employee & Partner Experience Audits for 2027 Planning.

If the partner portal looks modern and partners still cannot get paid, supported, or unstuck, you improved the channel — not the experience.

FAQ: What Is Partner Experience?

What is partner experience in simple words?

Partner experience is how it feels to do business with your organization as a distributor, supplier, agency, developer, or other ecosystem partner — from contracting and onboarding through portals, enablement, support, payment, and joint go-to-market. It is whether partners can finish real work with you without unnecessary friction.

Why does partner experience matter for customer experience?

From the customer’s point of view, partners often are an extension of your brand. When partners struggle to get answers, inventory, enablement, or support, customers experience delay, confusion, and broken promises — and they blame you, not the partner program.

Who are partners in partner experience?

Typically operational partners such as resellers, distributors, integrators, suppliers, agencies, and technology providers who create or deliver value with you. Some organizations also include capital partners such as investors or funders. The shared thread is an ongoing, designed relationship — not a one-off vendor transaction.

Is partner experience the same as a partner portal?

No. A portal is one channel. Partner experience also includes contracting, onboarding, human support, enablement, payment, deal registration, escalations, and the handoffs between your internal teams when a partner is stuck.

How do you improve partner experience?

Map the real partner jobs, shorten time-to-first-value, fix portal and payment friction, clarify support and escalation ownership, align incentives with shared success, and audit the lived relationship — then act on what you find, instead of only running summits and QBRs.

Image credits: Pexels

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Cursor to clean up the article, add images and create infographics.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Why Do People Resist Change?

Leave a reply

Why Do People Resist Change?

by Braden Kelley and Art Inteligencia

Why Do People Resist Change? (Short Answer)

People resist change when the new way costs them more than it returns — in effort, status, safety, time, or trust — or when they cannot see how to succeed at it. Much of what leaders call resistance is a rational response to the design of the change. Fear is sometimes part of the story. It is rarely the whole story.

Resistance is information. It tells you where the change asks people to lose something you have not replaced.

Below you’ll find what resistance actually signals, the reasons it shows up, how to tell design failure from unwillingness, and what to do before you diagnose someone’s character. Change management exists to achieve objectives in people’s behavior — see What Is Change Management? — and resistance is one of the clearest signals that those activities are missing or misaimed.

What Is Resistance to Change, Really?

Resistance is what people do when a proposed change threatens something they rely on and the replacement is unclear, unfair, or unworkable. It shows up as questions, workarounds, silence, delay, and sometimes open pushback.

Silence is easy to misread as agreement. In most transformations, the real objections travel in hallways because honesty has had a cost before. Those quiet questions — about jobs, power, time, metrics, and whether this effort is real — are catalogued in 10 Questions Employees Quietly Ask During Every Transformation.

Treat the signal as data about the change. People are telling you where the new way fails a basic test: Can I succeed at this, and is it worth what I give up?

What Are the Main Reasons People Resist Change?

  1. They cannot see themselves succeeding.
    The future state is described in slogans. The skills, the first week, and what “good” looks like for their role stay vague. Uncertainty reads as risk, so people stay with the work they already know how to do.
  2. They lose status, identity, or control.
    Expertise that took years to build can become less valuable overnight. A new system can move decisions away from the people who used to make them. That loss is concrete. Calling it “mindset” does not replace what was taken.
  3. The new way adds work and nothing stops.
    Another process, another tool, another meeting, stacked on the current job. If leaders cannot name what people will stop doing, the change is an extra load. People protect their capacity by dragging their feet.
  4. The old scorecard still pays.
    Promotions, bonuses, and manager praise still follow the behavior the change is supposed to replace. People follow the metric that affects their livelihood. They are responding to the system you still run.
  5. There is no time to practice.
    Training is scheduled. Practice on real work is not. People are asked to perform the new way in front of customers or leaders before they have been allowed to be clumsy at it. Avoidance is how they protect quality and reputation.
  6. Trust has already been spent.
    Earlier initiatives launched, faded, and left the extra work behind. People wait for proof that this one will change tools, decisions, and consequences — not only the branding. Belief returns when receipts show up in the work.
  7. The change itself is hard to use.
    Broken handoffs, missing authority, bad data, and tools that make the job slower produce “resistance” that is really feedback. The people closest to the work are often the first to discover that the design does not survive contact with a real day.

How Do You Tell a Design Problem from Unwillingness?

Ask where the friction sits before you decide who is “on board.”

  • If the same pushback shows up across teams that do not share a personality, look at the design: the job, the metric, the tool, the time, the loss.
  • If people can explain the change and still cannot do it on a normal day, you have an enablement gap, not a communications gap.
  • If a few people resist after the path is workable, the loss is named, practice is funded, and the old incentive is gone, then you are dealing with individual choice. That is a smaller group than most steering committees assume.

Leaders still reach for the shorter story: resistance means the people are the problem. That story feels efficient and skips the redesign. I treat it as one of the myths that keep showing up in 8 Change Myths Leaders Still Believe in 2026.

Diagnose the work before you diagnose the person.

How Do You Respond to Resistance to Change?

  1. Ask what they stand to lose, and answer in specifics: role, status, workload, and what happens if they speak up.
  2. Publish a stop list alongside the start list. If nothing stops, the change is additional work.
  3. Align one metric that still rewards the old behavior. People will not abandon a scoreboard that still decides their review.
  4. Fund practice on real work, with coaching, before you judge performance in the new way.
  5. Give sponsors levers, not only airtime: decision rights, staffing, and the authority to remove the old path.
  6. Fix the design people are tripping over — handoffs, permissions, data, tools — and say what you changed because they told you.

For how those activities sit inside a full change effort — planning, leadership, management, maintenance, and portfolio — see 5 Steps of Human-Centered Change That Survive Reality.

People move when the new way is safer and more workable than the old one. Make that true, then ask for commitment.

Ready to Take the Next Step?

Resistance gets quieter when people can see the whole change, name what they will stop, and practice the new way with sponsors who can actually change the work. That is a planning problem you can take on directly.

See the methodology. Explore Human-Centered Change™, my visual, collaborative approach to planning change so the people who must live it can see the whole effort and adopt the new way.

Get the toolkit. Read Charting Change, my practical guide to Human-Centered Change™, built around the Change Planning Canvas™ and 70+ visual tools for getting everyone on the same page.

Listen to the resistance long enough to redesign the change. Then give people a path they can actually walk.

FAQ: Why People Resist Change

Why do people resist change?

People resist change when the new way costs them more than it returns, in effort, status, safety, time, or trust, or when they cannot see how to succeed. The resistance often points to a design problem: unclear benefit, extra work, old incentives, no practice time, spent trust, or a change that is hard to use.

Why do employees resist organizational change?

Employees resist organizational change when their job, status, or workload is threatened and leaders have not said what stops, who decides, how performance will be judged, or whether speaking up is safe. They are often protecting their ability to do good work inside the system that still exists.

Is resistance to change normal?

Yes. Resistance is a normal response when a change threatens something people rely on and the replacement is unclear or unworkable. It is useful information about the change. It becomes a problem when leaders treat it only as a mindset issue and leave the design untouched.

How do you overcome resistance to change?

Name what people lose, publish what they will stop doing, align the metrics that still reward the old way, fund practice on real work, give sponsors real decision rights, and fix the parts of the design people are tripping over. Commitment follows a path that is safer and more workable than the status quo.

What are the main reasons people resist change?

The main reasons are inability to see how to succeed, loss of status or control, added work with nothing removed, incentives that still pay for the old behavior, no time to practice, broken trust from past initiatives, and a change that is genuinely harder to use than the current way.

Image credits: Cursor

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Cursor to clean up the article, add images and create infographics.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

How Do You Build a Culture of Innovation?

Leave a reply

How Do You Build a Culture of Innovation?

by Braden Kelley and Art Inteligencia

How Do You Build a Culture of Innovation? (Short Answer)

You build a culture of innovation by making innovating the easy, rewarded path — not by decorating the office or running more brainstorms. That means a shared definition and strategy, deep customer insight, a fair path from idea to adoption, resources that can move, psychological safety with accountability, clear roles, and leaders who remove friction. Culture is what people do when the poster isn’t watching.

An innovation culture isn’t what you put on the walls. It’s what gets funded, forgiven, and finished.

Below you’ll find what an innovation culture actually is, the theater that pretends to build one, seven building blocks that do, how to tell if it’s working, and where to start. One foundation first: without a shared definition of innovation, “culture of innovation” means whatever each leader wants it to mean. Start with What Is Innovation? A Clear Definition, With Examples.

What Is an Innovation Culture — Really?

An innovation culture is not free snacks, a quarterly hackathon, or a lab with cool furniture. It is not a slogan that “everyone is an innovator” while people have no time, permission, or path to finish anything.

An innovation culture is the habits, roles, permissions, incentives, and information flows that make innovating normal — not heroic. It shows up in how people get insights, generate and kill ideas, get time and money, collaborate across silos, and own adoption after launch.

In my experience writing Stoking Your Innovation Bonfire, organizations rarely fail innovation because they lack ideas. They fail because barriers — strategy, psychology, structure, information, and resources — extinguish good ideas before they can become widely adopted solutions. Culture is what people do under those conditions: what gets praised, promoted, punished, and ignored.

What Doesn’t Build an Innovation Culture?

A lot of well-intentioned activity builds a costume instead of a culture. Watch for these substitutes:

  • Pilot purgatory and demo days with no clear kill-or-scale decision
  • Idea contests and suggestion boxes with no path to development
  • Innovation labs that never touch the core business (for why labs stall, see 5 Reasons Innovation Labs Fail — and 5 Replacements That Work)
  • Celebrating creativity while punishing smart risk and bad news
  • Measuring idea volume instead of adoption and value

I catalog the most common costumes in 7 Types of Innovation Theater.

If your culture rewards the costume, you’ll get a costume.

How Do You Build an Innovation Culture? Seven Building Blocks

  1. Agree on what innovation means — and spread the definition.
    If one team means “new patents” and another means “adopted value,” you will fight over resources and celebrate different things. Choose a definition and teach it widely.
    First move: put your definition in every innovation review and funding request for the next quarter.
  2. Set an innovation strategy and goals.
    Where will you play? Which types of innovation will you fund — incremental, adjacent, radical, disruptive — and what does “good” look like this year? Innovation without strategy is experimentation; strategy without innovation is incrementalism forever. For the type lens, see What Are the Different Types of Innovation?
    First move: write one page: where we innovate, for whom, and how we’ll know.
  3. Start with human-centered insight.
    Brainstorms without insight produce noise. Sustainable innovation almost always starts with deep understanding of customer and employee jobs, frustrations, and unmet needs.
    First move: require a named insight (who, what job, what evidence) before any ideation workshop.
  4. Build a fair path from idea to adoption.
    Evaluation that only funds “safe” tweaks will starve bigger bets. Development needs real time and money. And someone must own adoption after launch — not only the build.
    First move: name the adoption owner for every funded innovation before work starts.
  5. Reduce resource and information friction.
    Culture dies when people and budget cannot move to the work that needs them, or when insights sit trapped in one silo. Leaders serious about innovation make resources and relevant information easier to move.
    First move: pick one policy that blocks cross-team funding or data sharing and fix it this quarter.
  6. Shape psychology on purpose.
    People need permission to experiment, safety to surface bad news, and accountability for learning and outcomes — not blame for every miss. Fear of failure and fear of looking foolish are culture, whether you designed them or not.
    First move: in the next review, praise a smart kill or a well-documented miss as loudly as a launch.
  7. Install roles and rhythms.
    A lone “innovation person” cannot carry a culture. You need multiple roles — champions, facilitators, implementers, and more — and a cadence for reviewing the portfolio. Reinforce the new norms with recognition and promotion. For the role map, see 10 Innovation Roles Every Enterprise Needs.
    First move: assign who owns insight, who owns evaluation, and who owns adoption for your top three bets.

How Do You Know If Your Innovation Culture Is Working?

Signs it’s working Signs it’s theater
Ideas from the edges get heard Only a favored few get airtime
Cross-functional work is normal Innovation lives only in a side building
Pilots have kill-or-scale owners Pilots renew forever with no decision
People can name the innovation strategy “We’re innovative” with no shared focus
Adoption has a named owner Success is measured at launch day
Leaders ask about learning, not only dates Bad news is hidden until it’s too late

Measure maturity with a baseline you can retake, and track a few outcome metrics — adoption, value, what got replaced — not poster counts or idea tallies. For measurement beyond idea count, see 12 Metrics That Actually Measure Innovation Value.

Where Should You Start Building an Innovation Culture?

Don’t try to change everything at once. Use this sequence:

  1. Diagnose barriers — don’t guess. Get a clear picture of where friction is highest.
  2. Pick one or two highest-friction barriers for this quarter — not ten initiatives.
  3. Fund a visible win that proves the new way is better than the old, and communicate it.
  4. Change one incentive or metric that still punishes the new behavior.
  5. Assign roles so culture isn’t “everyone and no one.”

Culture change often comes last, after new practices prove themselves. Friction, though, can be reduced now.

Start where the fire keeps going out.

Ready to Take the Next Step?

Building a culture of innovation starts with seeing your barriers clearly — then removing them with a roadmap, not another brainstorm.

Find out where you stand. Take the free Innovation Maturity Assessment: 50 questions, about 10–15 minutes, scored against a five-level Innovation Maturity Model so you can see your biggest barriers and set a baseline to improve from.

Learn how to remove the barriers. Read Stoking Your Innovation Bonfire, my roadmap for identifying what’s blocking innovation in your organization and building a culture where it can flourish.

Posters don’t build culture. Removing friction does — and that work starts with an honest baseline.

FAQ: Building a Culture of Innovation

How do you create a culture of innovation?

Create a culture of innovation by agreeing on a shared definition, setting an innovation strategy, starting from human-centered insight, building a fair path from idea to adoption, reducing resource and information friction, shaping psychological safety with accountability, and installing clear roles and review rhythms. Leaders remove barriers; they don’t just run brainstorms.

What is an innovation culture?

An innovation culture is the habits, roles, permissions, incentives, and information flows that make innovating normal — not heroic. It is what people do when it comes to funding, finishing, and adopting new solutions, not what appears on posters or in lab lounges.

What are the characteristics of an innovative culture?

Characteristics include a shared definition of innovation, clear strategy and goals, insight before ideation, a fair idea-to-adoption path, low friction for resources and information, psychological safety with accountability, cross-functional collaboration, and named ownership of adoption — not only launches.

How do leaders build an innovation culture?

Leaders build an innovation culture by diagnosing barriers, setting strategy, moving resources and information to where they’re needed, rewarding learning and smart kills as well as launches, assigning clear roles, and changing metrics that punish the new behavior. Culture follows what leaders fund, forgive, and finish.

Why do innovation culture initiatives fail?

They fail when organizations buy theater — hackathons, labs, and slogans — without removing barriers, aligning incentives, or owning adoption. Initiatives also fail when there is no shared definition or strategy, when fear blocks honesty, and when success is measured by activity instead of adopted value.

Image credits: Gemini

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Cursor to clean up the article, add images and create infographics.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

What Does a Futurist Do — and How Do You Become One?

Leave a reply

What Does a Futurist Do — and How Do You Become One?

by Braden Kelley and Art Inteligencia

What Is a Futurist? (Short Answer)

A futurist helps people and organizations explore several possible futures, not predict one. Futurists scan for early signals of change, map how those signals might evolve, build plausible scenarios, and translate them into decisions leaders can act on today. The goal isn’t being right about the future; it’s being prepared for it and helping shape it.

A futurist’s job isn’t to predict the future. It’s to help you stop being surprised by it — and start shaping it.

When I tell people I’m a futurist, the most common response is some version of “So what’s going to happen?” It’s a fair question, and it’s the wrong one. In my work with leadership teams, the value has never come from a single prediction. It comes from helping a room full of smart, busy people see several futures at once, notice the signals already pointing toward them, and decide what to do differently on Monday. Below I’ll explain what futurists actually do, how the role differs from forecasters and strategists, the skills involved, how to become one, and whether your organization needs one.

What Does a Futurist Actually Do?

Strip away the mystique and the work of a futurist comes down to six activities:

  • Scan for signals. Futurists look for early signs of change in technology, society, the economy, the environment, and politics — often at the edges, long before they reach the headlines.
  • Make sense of them. Not every signal matters. Futurists separate passing hype from real shifts and map how different signals interact, reinforce, or cancel each other out.
  • Build scenarios. Instead of one forecast, futurists construct several plausible futures — including the ones an organization would rather not think about.
  • Translate futures into decisions. Scenarios are only useful if they change what you fund, stop, prepare for, or redesign now.
  • Facilitate. Much of the job is helping leadership teams think together about uncertainty, in workshops, offsites, and strategy sessions, without collapsing into either hype or denial.
  • Communicate. Keynotes, articles, and stories make possible futures concrete enough that people can feel them — and act on them.

Futurists work in many settings: corporate strategic foresight teams, government and policy foresight units, consulting firms, design studios, and as independent speakers and authors. Many of us combine several of these roles.

Futurists don’t sell certainty. They sell better questions, earlier.

What Is the Difference Between a Futurist, a Forecaster, and a Strategist?

These roles get confused constantly, but they answer different questions:

Role Focus Time horizon Typical output
Futurist Multiple possible futures — possible, probable, and preferable Long (often 5–20+ years) Signals, scenarios, and their implications
Forecaster The single most likely outcome, often expressed as a number Short to medium A prediction with a probability or range
Trend analyst What is happening now and which direction it is heading Near term Trend reports
Strategist Choosing a path and executing it Medium Plans, priorities, and roadmaps

The key distinction: because long-range predictions are rarely right, futurists describe several plausible and preferable futures rather than betting on one expected outcome. Science-fiction writers imagine futures too — but for the sake of story. Futurists imagine futures for the sake of decisions, and often borrow from science fiction along the way.

Futurists and strategists need each other. Foresight without strategy is entertainment. Strategy without foresight is extrapolation.

What Skills Does a Futurist Need?

The best futurists I know come from wildly different backgrounds, but they share a common set of skills:

  • Curiosity across many fields — breadth matters more than deep expertise in one domain.
  • Pattern recognition and systems thinking — the ability to trace second- and third-order consequences, not just the obvious first one.
  • Comfort with uncertainty — holding several futures in mind without rushing to pick one.
  • Healthy skepticism — of hype, of vendor narratives, and of your own favorite ideas.
  • Storytelling — making abstract futures vivid enough that people can picture living in them.
  • Facilitation — helping groups disagree productively and reach shared understanding.
  • Human-centered empathy — understanding how real people will live, work, and feel in each future. Futures are lived by people, not by technologies.

Many of these overlap with the capabilities that grow more valuable as automation spreads, which I explore in 9 Skills That Age Well When Everything Else Automates.

How Do You Become a Futurist?

There’s no license and no single path. Futurists come from strategy, design, technology, journalism, research, innovation, and many other fields. If you want to build the capability, here are seven steps:

  1. Build a signal-scanning habit. Read widely outside your field and keep a running log of signals that surprise you.
  2. Learn a foresight method. Scenario planning, futures wheels, the three horizons framework, or a toolkit like FutureHacking™ gives your curiosity a structure.
  3. Practice on real decisions. Apply what you’re learning to your team’s strategy, your own career, or an issue in your community.
  4. Consider formal study if you want it. Graduate programs exist — the University of Houston’s Master of Science in Foresight, for example, describes itself as the longest-running academic foresight program in the world — along with shorter certificates and courses.
  5. Publish your thinking. Articles, talks, and posts sharpen your reasoning and build credibility at the same time.
  6. Build a portfolio of futures work. Document the scenarios you’ve built, the workshops you’ve run, and the decisions they influenced.
  7. Join the foresight community. Professional networks such as the Association of Professional Futurists connect practitioners, define professional competencies, and offer membership paths for students and experienced futurists.

The most important point: you don’t need the title to do the work. Foresight is a capability anyone can learn, which is exactly why I wrote 4 Simple Steps to Becoming Your Own Futurist.

Does Your Organization Need a Futurist — or Futures Thinking?

Most organizations need futures thinking. Whether they need a full-time futurist depends on how they plan to use it. Here are the signs your organization is short on foresight:

  • You keep getting surprised by changes that, in hindsight, were visible years earlier.
  • Your strategy is mostly last year’s plan plus ten percent.
  • Your biggest bets — technology platforms, facilities, capabilities — will outlive your planning cycle.
  • Your board asks about the next five years and nobody has a good answer.

Hire or build? An outside futurist brings fresh eyes, proven methods, and the freedom to say what insiders can’t. An internal capability turns foresight into a habit instead of an event. The best answer is usually both: outside expertise to get started and challenge assumptions, and internal practice to make it stick.

One warning: a futurist treated as an oracle at the annual offsite changes nothing. Foresight earns its keep only when it connects to real decisions about what to fund, stop, and redesign. For how to make that connection without the jargon, see 6 Ways to Practice Strategic Foresight Without Buzzword Bloat. For the questions boards should be asking, see 7 Questions Smart Boards Ask About the Next Five Years. And for help separating the predictions that matter from the noise, see 8 Predictions Leaders Can Ignore — and 8 They Cannot Afford To.

The organizations that get to the future first aren’t the ones with the best predictions. They’re the ones that practice imagining it together.

Ready to Take the Next Step?

You don’t have to hire a futurist or earn a title to start thinking like one. The skills and habits futurists rely on can be learned and practiced by anyone willing to look beyond the next quarter. That is why I created FutureHacking™, a strategic foresight methodology that helps individuals and teams become their own futurist.

FutureHacking™ gives you a simple four-step approach, supported by 20+ visual, collaborative tools:

  1. Pick the signals that matter — the shifts most likely to reshape your organization, industry, or career.
  2. Map how those signals evolve — so you can tell a passing headline from a real change.
  3. Explore possible, probable, and preferable futures — instead of betting everything on a single prediction.
  4. Make your preferable future a reality — with a roadmap, guideposts, and actions you can start now.

Whether you’re exploring foresight as a career or want your leadership team to stop being surprised by change, FutureHacking™ gives you the method and the tools to start doing the work of a futurist today.

Learn more about the FutureHacking™ methodology →

FAQ: What Does a Futurist Do?

What does a futurist do?

A futurist scans for early signals of change, makes sense of how they might evolve, builds several plausible future scenarios, and helps organizations translate those futures into decisions about what to fund, stop, prepare for, or redesign today. Futurists also facilitate leadership discussions and communicate possible futures through talks and writing.

How do I become a futurist?

There is no license or single path. Build a habit of scanning for signals, learn a foresight method, practice on real decisions, publish your thinking, and build a portfolio of futures work. Formal options include graduate programs such as the University of Houston’s Master of Science in Foresight and professional networks such as the Association of Professional Futurists.

Do futurists predict the future?

No. Because long-range predictions are rarely accurate, futurists explore several possible, probable, and preferable futures instead of predicting one. Their goal is to help people prepare for and shape the future, not to be right about a single outcome.

What is the difference between a futurist and a forecaster?

A forecaster estimates the single most likely outcome, often as a number with a probability, usually over a short to medium time frame. A futurist explores multiple plausible futures over longer horizons and focuses on their implications for decisions today.

Is futurist a real job?

Yes. Futurists work in corporate strategic foresight teams, government and policy units, consulting firms, and design studios, and as independent speakers, authors, and advisors. The field has dedicated graduate programs and professional associations, and many people also apply futures thinking within other roles.

Image credits: Cursor

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Google Gemini and M365 CoPilot to clean up the article, add images and create infographics.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.