Skip to content
Brett's Ramblings Brett's Ramblings Brett's Ramblings
Brett's Ramblings Brett's Ramblings Brett's Ramblings
  • Home
  • My books
  • About me
  • Hire me.
  • Contact
  • Home
  • My books
  • About me
  • Hire me.
  • Contact
Close

Search

  • Home
  • My books
  • About me
  • Hire me.
  • Contact
Subscribe
Brett's Ramblings Brett's Ramblings Brett's Ramblings
Brett's Ramblings Brett's Ramblings Brett's Ramblings
  • Home
  • My books
  • About me
  • Hire me.
  • Contact
  • Home
  • My books
  • About me
  • Hire me.
  • Contact
Close

Search

  • Home
  • My books
  • About me
  • Hire me.
  • Contact
Subscribe

I’ve Spent Nearly 40 Years Learning How to Teach. Now I’m Putting My Investigative Methods Under the Microscope.

By Brett Shavers
October 21, 2026
0

An Actual Investigation With No Script and No Predetermined Ending

I’ve spent years developing and teaching investigative methods based on my experiences as a criminal investigator, digital forensic examiner, and instructor. I’ve written books, developed frameworks, and built courses around something I believe is a critical part of digital forensics: How to actually investigate a DFIR case, not just interrogate devices and data.

Now I’m going to put those methods under a microscope by opening an actual, ongoing investigation to anyone interested in watching, questioning, and challenging how I work it.

This is not going to be a completed case packaged into a neat presentation. And it’s not a training exercise or CTF where I already know the evidence and control the outcome. This is a real investigation with real people, real records, unanswered questions, and no predetermined ending.

Register (free) here: https://www.suspectbehindthekeyboard.com/offers/Q5EZpEkq/checkout

Why a Public Records Investigation?

There’s a problem with using actual investigations as public training exercises.

You can’t simply open an ongoing criminal or civil investigation involving real people to the public. There are legal, ethical, confidentiality, and privacy issues. I have trained using actual cases in closed environments to some organizations because they wanted a different perspective in their cases, but doing so in public is another matter.

So, I looked for the closest thing I could use to demonstrate real investigative casework in an open setting. A public records investigation.

I found one in a public press release. I chose this matter because it provides an opportunity to demonstrate investigative principles and the practical work of developing a case. It includes questions involving forensic work on at least one smartphone, documentary evidence, possible inconsistencies, and decisions about what to investigate next.

Some records have been produced. Others remain outstanding. I’ll approach this public records matter much as I would a digital forensic investigation, incident response matter, eDiscovery case, or criminal investigation.

I’ll establish objectives, identify evidence sources, evaluate what the evidence establishes, consider alternative explanations, document my reasoning, and decide what steps are justified. But this time, I’ll be talking out loud so you will hear my thinking.

The legal procedures and subject matter may differ, but the underlying investigative principles are largely the same. I want you to see how I think, how I plan, how I document, and how I decide what to do next.

More importantly, I want you to see how I separate what I know from what I suspect, how I test my own assumptions, and what happens when new evidence changes my thinking.

You may find something useful to apply in your own work. That’s actually my goal for you. You may also recognize something I could do better. That’s a side benefit for me.

You’re Invited to Watch, Question, and Challenge My Work

I’m opening this investigation through a series of free, live online sessions, and the evidence will determine the schedule. When new records arrive or there’s enough investigative development to justify another discussion, I’ll schedule the next session.

That might mean two sessions or twenty. There could be a week between sessions or considerably longer. I’m not going to manufacture material to maintain a schedule.

Anyone can join, but obviously it should only be of interest to someone who is interested in seeing this type of training. Practically, my Zoom is limited to 500 attendees, but that should be plenty. Log in early to be sure..

Casework is like that. For real.

Each session will generally last 30–45 minutes. I’ll discuss the available evidence, the questions it raises, what remains unknown, and the investigative steps I’m considering. I’ll take input, suggestions, and questions as to why I am thinking a certain way or what I expect to happen.

You don’t need to be an expert. You don’t even need to agree with me.

Real People. Real Responsibilities. Real legal issues.

This isn’t an effort to prove allegations against an individual or an agency. It isn’t a campaign against a city or a person. The purpose is to demonstrate investigative thinking and decision-making using an actual public records matter.

I’ll remain responsible for the investigation, including what records I request, how I document my work, and what I publish. That also means understanding the legal authority and limitations governing each investigative step.

Unlike a fictional exercise, mistakes here can affect real people, just like in a real case.

I have a responsibility to distinguish allegations from established facts, avoid unsupported accusations, and make sure my conclusions don’t go beyond what the evidence supports. Just as if this were to become litigation in a legal case, which is possible.

That’s part of investigative work, and it’s part of what I intend to demonstrate.

There won’t be a fictional ending just because it’s time to finish the class. It ends when it ends and ends how it ends. We will just drive the investigation to the conclusion if there is one, because sometimes there isn’t.

Public interest

I also didn’t select this matter simply because I needed a case for training. I began requesting records because I had legitimate questions about a public announcement involving a government official. In my opinion, those questions concern a matter of public interest. The training opportunity developed from an investigation I was already pursuing.

Join the Live Investigation Series

The first session will be scheduled for next week. You’ll get the information in your email.

Sessions will be live, with no immediate replay. I may make recordings available after the series concludes, but I want these discussions to happen while the investigation is actually unfolding.

Register once to receive notifications as sessions are scheduled. There’s no fixed number of meetings, and you’re welcome to attend as many or as few as you like.

Your Anonymity

These sessions will be conducted as Zoom webinars.

Attendees won’t be able to see one another. Questions and comments can be submitted through the Q&A feature without being visible to other attendees.

You’ll also have the option to submit questions anonymously, so even I won’t know who submitted them through the webinar’s Q&A.

There’s a reason for this. I don’t want anyone hesitating to ask a question because they think it’s too basic, or holding back an observation because they’re worried someone might disagree. Maybe you’re new to investigations or been doing this longer than I have. Maybe you’re simply curious about how an investigation develops.

If you see something I’ve missed, say so. If something doesn’t make sense, ask. If you think I’m wrong, tell me. And when I say or do something you don’t understand, ask me why and I’ll explicitly say what I am thinking and why.

That’s part of why I’m doing this. The other part is something I’ve come to believe strongly over the years.

If you’re going to teach others how to investigate, explain why your methods work, and tell practitioners how they should approach DFIR cases, you should be willing to demonstrate that you can actually do what you’re teaching.

Not just explain it in a book, present it in a classroom, or demonstrate it with a case where you already know the ending. Do it with real evidence, unanswered questions, imperfect information, and decisions that have consequences.

And be willing to let others examine your work, question your reasoning, and point out your mistakes. I’m asking others to do that to me. I think that’s a reasonable standard for anyone teaching investigative methods, myself included.

I mean, I wrote a book and teach the DFIR Investigative Mindset. I think people should know if I know what I’m talking about…for real.


How I Got Here

I don’t particularly like talking about my accomplishments or listing credentials. I don’t like boasting, bragging, or taking credit for things.

When I introduce myself at a conference or before teaching a class, my introduction is usually something like, “Hi, I’m Brett, and I do forensics.”

That’s about it for my bio. But I do think it’s important for people to know where the ideas I teach come from.

How did I develop my approach to investigations? What experiences shaped my thinking? What have I done to test my methods? How do I know when something works, and how do I recognize when something doesn’t?

Those are fair questions, especially if I’m asking others to consider using my methods in their own work.

What follows isn’t intended to be a résumé or a list of accomplishments. It’s the history of how my approach developed over time, including the things that worked, the things that didn’t, and the lessons I learned along the way.

I’ve narrowed it to the experiences that most influenced how I investigate cases and how I teach others to do the same.

October 21, 2026

I had a phone conversation with someone I’ve respected in the digital forensics field for a really long time. Someone whose research, publications, and contributions to the profession go back decades.

The conversation started with a private message and turned into a phone call about the investigative methods and frameworks I’ve been developing and teaching.

What struck me wasn’t just that this person took the time to reach out. It was his willingness to offer assistance, review my work, ask difficult questions, and challenge my thinking.

He gave me his time, unsolicited, and was genuinely sincere. I take that seriously. During the conversation, he asked how I’d come up with the idea of using an actual, ongoing investigation as a live teaching environment.

Who was I working with? Had I collaborated with established researchers or practitioners? Had others helped develop the idea? He mentioned several people in DFIR whose work I respect and organizations like SANS, and if they were part of this idea. I was flattered, of course.

But the answer was simple.

The idea came from nearly 40 years of taking training, teaching others, working investigations, watching people make decisions, making plenty of mistakes myself, and continually making micro improvements.

I didn’t invent investigative thinking, realistic training, or scenario-based exercises.

What I’ve done is combine lessons from those experiences, question my own methods, and try to improve how I investigate and teach. Some of those lessons were expensive. Financially, professionally, and occasionally physically.

There are cases I worked that still bother me because I believe I should have done something differently, done it faster, or recognized something I missed. That’s forever.

Then there were the courtroom experiences. I’ve been on the witness stand wishing I could ask the judge for a little mercy while I figured out exactly what the court needed from me. In some cases, I wished I could be back home in my bed than on that hot seat.

I learned those lessons, too, mostly because I never got any mercy on the stand and all of it contributed to how I teach today.

I also believe it’s important to know who you’re learning from.

What have they done? What have they studied? What are they qualified to teach? Have they actually performed the work they’re teaching you how to do?

Practical experience isn’t the only form of expertise, but it matters when someone is teaching practical skills.

I once attended a two-week computer forensics course taught by someone who had never worked a forensic case or even acquired a forensic image from a hard drive. The material came from a book. The credentials were impressive, but the instructor couldn’t demonstrate the work being taught, had not a single experience to share from the real world, and literally read from the book written by someone else.

That was frustrating.

And it reinforced something I’d been learning for years: knowing about a subject, knowing how to perform it, and knowing both the subject and how to teach it are different things.

My own education in that difference started in the Marine Corps.

The 1980s: The Marine Corps and Learning How to Teach

For most of 1988 and part of 1989, I served as an instructor in the Marine Corps in Hawaii.

Yes, it was a tough assignment. I was all of 20 years old and probably had the judgment of a 15-year-old at the time teaching Marines how to survive.

The process of becoming an instructor was competitive. Marines who met the requirements were selected through boards at their unit for an opportunity to attend instructor training. Marines in that training competed for the opportunity to design and teach a course to the cadre. Then the cadre picked who they wanted. That cadre, as ‘students’ in the presentation, were the worst students you can imagine, because they made it rough with hard questions and heckling.

You either were picked or went back to your unit. I made it.

That Marine Corps instructor course remains one of the most impactful and practical courses on how to teach that I’ve ever attended. And I’ve attended a lot of instructor courses since.

The Marine Corps taught me about lesson plans, objectives, standards, classroom management, delivery, and evaluating whether students actually learned something.

We taught the established curriculum by the book. But we also had room to experiment with how we delivered training and, when appropriate, improve tactics and procedures.

If we thought something could be taught more effectively, we could try it without getting into trouble simply because it was different. Some of the improvements we developed were adopted Marine Corps wide and that was cool for a young Marine instructor.

More importantly, I learned that following established standards didn’t mean we couldn’t improve the methods used to meet those standards, or even improve the standards. I also learned the difference between being knowledgeable about a subject and being able to teach someone else how to apply that knowledge.

When the Ending Was Already Decided

The Marines introduced me to realistic training exercises involving opposing forces, simulated combat, tactical problems, and operational objectives.

Instead of sitting in a classroom learning about combat, we went into the field and applied what we’d learned. I liked that.

But during one exercise, I discovered that the outcome had essentially been predetermined and my commanding officer later confirmed it. I can’t say whether this was true of every exercise, or even most exercises. I only know that it happened.

Regardless of how well or badly we performed, the ending had already been decided. We were going to win against the opposing force. That bothered me.

Why go through the effort of simulating a real operation if the decisions made by the participants don’t actually change the outcome?

Now, I understand that some training requires controlled scenarios. Sometimes an instructor needs a particular event to occur so students can practice a specific skill. There’s nothing inherently wrong with that.

But when the objective is to teach decision-making during an evolving operation, shouldn’t those decisions matter? Shouldn’t good decisions improve the outcome? Shouldn’t poor decisions have consequences?

At the time, I learned something that stayed with me: Realistic equipment and realistic conditions don’t automatically create realistic decision-making. I have no doubt that Marine Corps training today far surpasses during my era (saying ‘era’ makes me feel old..).

I carried that lesson into law enforcement.

The 1990s: Law Enforcement and Taking Realistic Training Further

During my time in law enforcement, I had a strong appreciation for practical instruction. Over the years, I attended more than 2,000 hours of basic and advanced law enforcement training.

Patrol tactics, defensive tactics, firearms, narcotics, undercover operations, SWAT, search warrants, interviews, surveillance, investigations, and just about anything else that might help me perform the work.

Some courses were excellent while others were disappointing. I began noticing that courses with Investigation in the title didn’t necessarily teach students how to conduct an investigation.

They might cover interviewing, evidence collection, a particular type of crime, or an individual investigative technique. All useful subjects but I rarely encountered training that taught someone how to take an investigation from the initial allegation through lead development, evidence evaluation, alternative explanations, documentation, and eventual courtroom presentation.

Learning individual skills isn’t the same as learning how to put those skills together. Knowing how to perform a particular task doesn’t mean you know when, why, or whether that task is necessary.

As a new detective, I learned that many agencies have a ‘sink or swim’ method of teaching how to investigate. I was sinking for a while until “I got it.” Eventually, I became an instructor in different aspects of police work.

Naturally, I began applying lessons I’d learned in the Marines.

1997–1999: Developing Integrated Use-of-Force Training

In 1997, while working as a defensive tactics instructor, I began researching how to improve use-of-force training. My concern was that we were teaching individual skills and expecting officers to put them together correctly during a real confrontation.

We might spend two hours hitting a bag and call it officer survival training. Literally, hitting a bag for two hours was considering meeting standards of training.

I wanted training that required officers to make those decisions under realistic conditions, where instructors could observe their actions, discuss what happened, correct problems, and try again. So, I applied, competed, and was selected to be a ‘defensive tactics instructor’ and was able to go to lots of instructor training plus getting quite a bit of mat time and hair pull time. 

I also pursued firearms instructor qualifications so that I could integrate firearms and defensive tactics rather than treating them as entirely separate disciplines. In 1998, I proposed and implemented an integrated scenario-based use-of-force training program for my agency.

It combined firearms, defensive tactics, tactical movement, decision-making, and force-on-force scenarios using Simunitions and protective suits, including FIST and REDMAN. I wasn’t inventing force-on-force training. Similar concepts existed elsewhere, including approaches discussed in law enforcement publications.

But the integrated approach I was developing wasn’t something I had encountered as an established practice among the Washington agencies I was working with.

And I’d looked. I found no agency in the state doing it. None in adjacent states either. Actually, I didn’t find any but I am sure that there were some. We just didn’t have Internet at the time..

In 1999, I helped other agencies develop similar training programs.

That same year, the Washington State Criminal Justice Training Commission learned about my program through another agency. The commission director contacted me, discussed the approach I’d implemented, and asked whether I’d help develop the state’s version.

I declined, not because I didn’t want to help. I was buried in narcotics investigations, handling more work than I could comfortably manage, along with several other responsibilities.

Also in 1999, I published a training manual titled Integrating Use of Force Training, documenting much of the approach. It sold some copies, is long out of print, and I lost my only copy years ago. It’s still online for sale in some bookstores, so maybe I should buy a copy for nostalgia’s sake.

Today, integrated scenario-based training is a normal part of law enforcement instruction. The program I developed at my former agency continued after I left, and from what I’ve seen, they’ve improved it. That’s exactly what I’d hope to see.

If a training program can’t improve after the person who created it leaves, something is wrong with the program or with how people are treating it.

The Grumpiest Officer in the Department

One officer at my agency had more than 30 years of experience and was among the grumpiest officers I’d ever known. He complained about the upcoming training more than practically anyone else. I expected him to hate it.

I figured he’d finish the training and complain to the chief about being forced to put on a big protective suit and participate in role-playing exercises, where he may have to shoot a role player or wrestle one.

Then he went through his first immersive scenario. He performed exceptionally well. His decisions were sound. His tactics were solid. He handled the scenario better than I expected. I was seriously impressed and told him so.

Maybe he surprised himself. Maybe he simply felt vindicated after more than three decades of law enforcement work. I can’t know what he was thinking. But I do know what happened afterward.

He wrote a memo to the chief describing it as the best officer survival training he’d ever experienced in his career. Coming from him, that meant something.

An Officer’s Hug

Another officer at my agency was later involved in a deadly-force shooting. After the shooting, he found me, hugged me, and credited the training I’d developed. He told me that things I had said during training were replaying in his head during the encounter.

I’ll never forget that or the words that he heard.

I can’t claim the training changed the outcome of the shooting. Nobody can say what would have happened without it. But the officer believed the training mattered enough to seek me out afterward.

And he survived. That meant more to me than any course evaluation. It reinforced why I believed training should do more than present information. It should prepare people to make decisions when those decisions matter.

Teaching Narcotics Investigations by Working Narcotics Investigations

One of the most influential experiences in developing my investigative training approach came while working narcotics. I was assigned to a six-member drug task force that wasn’t functioning particularly well.

Actually, it was dysfunctional. At times, dangerously so.

Some members had decades of law enforcement experience. Others came from patrol with little investigative experience. Training was uneven. Casework went in different directions. We weren’t functioning as a team.

Our supervisor had patrol experience but no background supervising investigations, let alone drug investigations.

By this time, I had substantial investigative and instructor training, SWAT experience, and was doing all of the undercover work for this task force and three federal agencies at the same time for several years prior.

I was also nearly shot several times because of circumstances involving that team. That period of narcotics work gave me acid reflux. Literal, medically diagnosed acid reflux.

I had more active cases than I could handle. I was referring cases elsewhere and turning away additional work. Whenever I handed one of my cases to another detective in the unit, it seemed to go nowhere. Then I’d hear complaints that I’d given someone a junk case.

I didn’t see it that way. Every case I handed off had investigative potential, even if it didn’t promise a major seizure or an immediate arrest. To me, the problem wasn’t a lack of cases.

The problem was a lack of case development.

The Telephone Rang at Exactly the Right Time

One day at our regular meeting, the task force was arguing about productivity and what some believed was a shortage of investigations. Seizures were down, cases were down. No active informants. I was arguing the opposite. My case draw was full. Informants called me all the time.

We didn’t lack cases. We weren’t developing the ones we already had. I said I could take an anonymous drug tip and develop it into an investigation that could reach federal court.

And then, the anonymous drug-tip telephone rang.

One of the detectives looked right at me and said: “There’s your chance, big guy.”

Normally, unanswered calls went to a recording. I was usually the one following up on anonymous tips anyway since no one else did. This time, I answered.

The caller had information about a cocaine dealer, wanted to remain anonymous, and provided a fairly basic tip. Something along the lines of a guy selling cocaine on the corner of walk-and-don’t-walk. Nothing particularly remarkable.

I put the caller on hold. Then I turned to the team and told them to watch.

I picked the telephone back up and continued the conversation, asking questions, developing the information, and eventually getting the caller to agree to work as a paid confidential informant.

When I hung up, I told the team we’d have several cases by the end of the week from this one call. We started by picking up our new informant.

Four Days of Actual Casework

Over the next four working days, I effectively served as the ad hoc supervisor, directing the investigations that week. One case led to an arrest. That arrest led to another investigation.

Additional developments produced information, informants, and more investigations. I assigned different responsibilities to different detectives.

Some worked as case investigators. Others handled informants, evidence collection, surveillance, body-wire operations, or undercover responsibilities. Then we changed roles as cases developed.

Everyone had real work to perform. Real evidence with real legal requirements, real investigative decisions, and real consequences for mistakes.

A poor decision could result in lost evidence, an unlawful arrest, inadmissible evidence, or someone getting hurt. It was actual casework, but it was also a practical teaching opportunity.

The team started seeing how investigations developed when leads were followed, opportunities were recognized, and people took responsibility for moving the case forward.

Something else became apparent. Not everyone was equally good at every investigative task. One was better at working informants. Others were stronger at surveillance, planning, evidence collection, or managing an investigation. One particularly enjoyed working the body wire.

Nobody wanted to do undercover work.

Experience and seniority didn’t necessarily predict who would perform best in a particular role. By rotating responsibilities, people had the opportunity to develop skills and recognize their strengths.

The cases were filed, with charges following the next week. The final major investigation at the end of the week involved multiple kilograms of cocaine. All of it developed from that one anonymous drug tip.

Our subsequent casework improved, too.

Two Days With Another Drug Unit

I later used a similar approach while assisting a smaller narcotics unit consisting of two detectives, with a request from their sergeant.

I had two days available. Rather than lecture about narcotics investigations, I suggested we work actual cases and see how far we could develop them together.

We started by driving through town in an unmarked narcotics car. One of the narcs pointed out a local crack dealer known as Pops, who was walking on the sidewalk.

“We can never get a case on him.”

I told the detective to slow down and as we drove past Pops, I rolled down my window.

“Yo, Pops! Got any rock?!”

As it turned out, Pops had rocks. And we had the first case that started some very productive investigative work.

We developed informants, additional investigations, seizures involving pounds of methamphetamine and stolen firearms, and multiple arrests.

I’m not telling these stories to suggest that every anonymous drug tip can turn into a federal case or that every investigation should produce arrests within a few days. Or that this is directly related to DFIR cases. It’s the principles I am trying to get across.

The lessons were how to work an investigation, in real time, with real pressures and risks. How to recognize opportunities, develop questions, identify objectives, pursue lawful evidence, evaluate information, document decisions, and know when to change direction.

There’s a difference between attending a class about confidential informants and actually developing and managing one.

Those experiences influenced how I later approached digital forensics training.

The 2000s: Entering Computer Forensics

When I moved into what we then commonly called computer forensics, I had a tremendous amount of technical knowledge to learn. I was starting from scratch and didn’t know much. In high school, I took a BASIC programming class and spent much of the semester rigging the machines before class to auto wipe the floppies so when the class started, homework got wiped. It took a week before getting caught. That’s my programming days. And no, I don’t feel bad about doing that, especially since I usually didn’t do my homework.

I’d worked criminal investigations for years, but computer hardware, operating systems, file systems, forensic imaging, and digital artifacts were an entirely different world.

I attended course after course. NW3C, FLETC, PCERT, BCERT, ACERT, and training from private vendors including Guidance Software, AccessData, X-Ways, and others. I took some courses more than once because the material was hard.

My first computer forensic laboratory was literally a converted storage closet. It was small, cramped, and had previously been used to store junk. I taped a sheet of paper on the door that said “Computer Forensic Lab.” My agency didn’t want forensics, and they didn’t send me to any training. I paid for half the training and figured out a way to have the feds send me to the rest, all without my department knowing. That’s another story.

Administration wasn’t particularly interested in having a forensic lab, and the detectives hadn’t yet developed much need for one. But I wrote up the proposal, policy, obtained equipment through grants and training opportunities, and built something I could use to work cases. Mind you, this is all before everything being online for templates and material.

As my technical skills improved, something about the training continued to bother me.

I’d already written hundreds of search warrant affidavits, served more warrants than I’d written, conducted interviews, worked undercover, developed informants, handled physical evidence, and testified in court more times than I wanted.

I understood how to conduct investigations, yet after more than 1,000 (probably upwards of 1,500) hours of computer forensic classroom training, I hadn’t encountered a course that taught the entire investigative process within a forensic case.

I learned how to operate tools. I learned about artifacts, data acquisition, recovery techniques, and where certain evidence might be found. All of that knowledge was necessary and actually fun to learn.

But I wasn’t seeing much training about developing investigative strategies, recognizing missing evidence, evaluating competing explanations, connecting technical findings to the broader investigation, or knowing when another investigative approach was needed.

It was almost as if we were teaching people how to swing a hammer without teaching them how to build a house. That isn’t a criticism of technical training itself.

A course about a forensic application should teach the application. A practitioner needs to understand operating systems, file systems, artifacts, software, and technical limitations.

But becoming proficient with forensic software doesn’t automatically make someone a proficient investigator. I could teach someone how to acquire a forensic image or parse an artifact but that wouldn’t necessarily teach them what investigative question needed answering, whether the evidence actually answered it, or what to do when the available evidence contradicted their theory.

Those are different skills.

When I transitioned into private-sector forensic work, I encountered incredibly technically capable practitioners who had little investigative experience outside examining digital evidence. But examining evidence and conducting an investigation aren’t necessarily the same thing.

That gap of skill and knowledge became central to my writing and teaching.

2012–2013: Placing the Suspect Behind the Keyboard

In 2013, Syngress published my book Placing the Suspect Behind the Keyboard: Using Digital Forensics and Investigative Techniques to Identify Cybercrime Suspects.

Several chapters had been released in 2012. And I believe I started writing that book in 2011 at the earliest. Harlan Carvey served as the technical editor, and Troy Larson wrote the foreword.

I owe both of them a lot, and not just for their input with the book. Mostly for me making it as far as I did in this line of work.

The book grew out of a problem I’d encountered repeatedly in actual investigations. Finding evidence of activity on a computer doesn’t automatically establish who performed that activity.

An account isn’t a person and a computer isn’t a person. In a case, any case where accountability is being sought, the investigator needs to tie the act to the actor.

In the book, I described two police officers standing beside each other, looking at the same street corner. One officer might observe activity that raises several questions. The other might see nothing particularly interesting.

Same location, people, and activity. Two different perceptions of what is actually happening. The difference is what each officer notices and what questions follow.

Why is that person standing there? Why did those people exchange something? Why did someone suddenly leave? Is there an innocent explanation? What information would reduce my suspicion? What if I am wrong?

Those observations don’t establish criminal activity but they are reasons to ask questions and determine whether further investigation is justified.

Digital forensics isn’t much different.

Why does a file have a modification timestamp earlier than its creation timestamp? What evidence connects an account to a particular person? Could someone else have used the device? Could remote access explain the activity? Is there evidence that contradicts our interpretation? What am I missing? What if I am wrong?

A forensic examiner who recognizes an artifact but never considers its meaning within the investigation may overlook something important. An investigator focused entirely on proving one theory may overlook evidence that disproves it.

These ideas were central to what I was writing in my first book. They also became the foundation for later books, the DFIR Investigative Mindset, the FACT Attribution Framework, and CASEWORK.

I didn’t sit down one afternoon and invent an investigative philosophy. It developed through years of work, teaching, mistakes, and small adjustments. And it’s still developing.

What I’ve Learned About Training and Education

Over the years, I’ve developed some strong opinions about how we train investigators.

Those opinions come from experience as both a student and an instructor, including completing overhauling the digital forensics continuing education program at the University of Washington and teaching there for five years.

That experience also gave me a look inside academia. I learned about program development, departmental priorities, institutional funding, and the difficulties of getting educational programs approved and operating.

Some of that experience was enlightening and frustrating at the same time. It helped shape my views on the relationship between academic education and intensive professional training.

Training Should Have a Practical Purpose

Students should leave a course with knowledge they can apply to their work. That doesn’t mean every class needs to be a full investigative simulation. Theory still matters as does research and technical specialization.

Students should understand what they’re learning, why it matters, and how it relates to the work they perform. A tool course should teach the tool. There’s nothing wrong with specialized technical training when that’s what the course promises.

Principles Matter More Than Memorized Tactics

Technology changes. Tools change. Procedures change. Circumstances change.

A practitioner who understands the underlying principles is better prepared to adapt when a familiar tool or procedure no longer applies because although knowing which button to press is useful, it is as important in knowing why you’re pressing it, what you expect to learn, and what the result does or doesn’t establish is more important.

Course Length Doesn’t Establish Value

I’ve attended 80-hour courses that could have been taught in eight hours. I’ve attended eight-hour courses that deserved 40. The number of hours doesn’t automatically tell you how valuable the training is. It matters what is taught, how effectively it’s taught, and what the student can do afterward.

I don’t need to spend five days in a classroom earning a certificate if the necessary material can be taught effectively in one day.

Students Have Responsibilities, Too

I’ve been guilty of attending training without putting in the effort I should have. I’ve collected certificates and later realized I hadn’t learned as much as I could have. I’ve even taken courses again because I recognized I’d missed things the first time.

In 2024, I wrote about taking Jessica Hyde’s Mobile Data Structures course and learning things I hadn’t previously considered despite years of experience working with digital evidence.

I’m still a student and I expect I’ll remain one as long as I’m working.

Academia and Practitioners Need Each Other

This brings me back to that recent phone conversation. I have tremendous respect for academic research.

We need people developing theories, examining cognitive biases, testing methods, researching investigative effectiveness, and challenging assumptions.

We also need practitioners bringing problems from actual investigations into those discussions. Research and practical experience shouldn’t exist in separate worlds.

A practitioner might encounter an operational problem that deserves formal research and a researcher might identify a weakness in an investigative practice that has gone unnoticed for decades.

Both contribute to professional knowledge, and both can be wrong.

A practitioner with 30 years of experience isn’t automatically correct because of those 30 years. Neither is someone with a PhD automatically correct because of those three letters.

Credentials and experience tell us something about a person’s background and expertise, but neither substitutes for examining the actual work.

I’ve seen practitioners dismiss academic research because the researcher has never worked a particular type of case. Conversely, I’ve seen practitioner contributions treated as less important because they didn’t come from a university or a peer-reviewed publication.

Neither attitude makes sense to me. Professional knowledge shouldn’t be treated as someone’s personal territory.

An idea should be evaluated on its merits, whether it comes from a university researcher, police detective, forensic examiner, or student asking a difficult question.

I also believe practical observations deserve consideration. An anecdote isn’t scientific proof. But actual experiences can reveal problems worth researching, generate hypotheses, and identify questions that deserve systematic examination.

Formal research may then establish that an apparent pattern doesn’t hold up. Good.

That’s how knowledge improves.

Likewise, research conducted under controlled conditions may identify methods that need further evaluation in actual investigative environments.

That’s where researchers and practitioners can help each other. That’s why I took that recent offer of outside review so seriously. I don’t need someone telling me my work is wonderful.

I need someone asking whether my assumptions are sound, whether my reasoning holds up, whether a concept has already been studied, and whether there’s a better approach.

Sometimes the answer will be that I need to change something. Good. That’s the point.

Why I Developed CASEWORK

Everything I’ve described eventually contributed to CASEWORK.

The Marine Corps taught me how to teach and showed me the strengths and limitations of realistic exercises.

The integrated use-of-force program showed me the value of combining skills in evolving scenarios where decisions really mattered legally and physically.

The narcotics investigations showed me what happened when people learned investigative responsibilities while working real cases.

Digital forensics showed me an industry with exceptional technical training but, in my experience, comparatively less attention to complete investigative casework.

I wanted to bring those lessons together. So I developed CASEWORK.

One day. One case. A complete investigation. Not a series of disconnected forensic exercises and not a race to determine who can operate a forensic application the fastest to find the known trophy.

CASEWORK is an investigation that requires students to evaluate information, develop strategies, assign responsibilities, identify evidence sources, consider alternative explanations, document decisions, and explain their findings.

And the clock is running. While students deliberate, other developments may occur.

Information can change. Opportunities can be lost. Decisions can affect what happens next. Different participants assume different investigative responsibilities.

The objective is to get students thinking and acting like investigators.

Why are you taking this action? What are you trying to establish? What evidence would support your theory? What would contradict it? What happens if you’re wrong? What will you do next? How will you document and explain your decision?

Other training providers offer excellent scenario-based exercises. I’m not suggesting otherwise.

But there’s a difference between a scenario designed to teach technical aspects of an incident and one designed to make students work through an entire investigation.

Both have value and CASEWORK is my attempt to teach the latter. It’s also something I expect to continue improving.

Another topic brought up in the phone call I was talking about, was that it’s been recently that “investigative mindset” and “investigation skills” have become important. I thought that to be a little funny because I’ve always thought it was important, so important that I wrote a book about the investigation aspect of forensics and a book on the investigative mindset aspect of forensics.

I’ve noticed more DFIR training emphasizing investigative mindset and investigative skills, and I welcome that. Whether this reflects changing courtroom expectations, the needs of practitioners, or recognition of gaps in traditional training, I hope these subjects receive more than a passing mention in a course description.

I only hope that slapping “investigative mindset” or “scenario-based training” on a course really does teach it and not use these as marketing terms only.

Back to the Real Investigation

CASEWORK brings together many of the lessons I’ve learned, but it’s still a controlled training exercise. I develop the scenario, determine what evidence is available, and create the investigative developments. Even though students can make decisions that affect the outcome, I’m still the one who built the exercise.

The public records investigation removes much of that control.

I don’t know what the next records production will contain. I don’t know whether a particular lead will produce useful information. I can’t decide what the evidence will ultimately establish.

I can only decide what to ask, where to look, how to evaluate what I receive, and when the available information justifies another investigative step. Those decisions are what I want other practitioners to examine.

This isn’t going to scientifically validate everything I’ve developed or taught. One investigation can’t do that. But it will demonstrate how I apply those methods to real information, under real constraints, while other people have the opportunity to question the work.

You may recognize weaknesses in my approach or may offer better ways to pursue an issue or evaluate a finding. And I may need to change direction because of what they identify.

That’s worth it for sure.

Putting My Own Methods Under the Microscope

I’ve been teaching since 1988, before I was old enough to legally drink. That doesn’t mean I didn’t drink. I was in the Marines…

I’ve worked criminal investigations, built training programs, written books, developed frameworks, taught university and professional courses, and made plenty of mistakes along the way.

I’m still learning.

And the longer I work in this field, the more convinced I become that anyone teaching investigative methods should be willing to have their own work examined.

It’s easy to explain a method using an example where you already know the correct answer. It’s different when you don’t know what the next piece of evidence will establish. It’s different when someone can challenge your interpretation before you reach a conclusion.

It’s really different when a mistake has consequences beyond getting an answer wrong in a classroom. Mistakes of loss of money, business, liberty, or life.

If I’m going to tell investigators to question their assumptions, consider alternative explanations, document their reasoning, and follow the evidence wherever it leads, I should be willing to do exactly that myself.

I don’t expect this to be a flawless investigation. I expect to make mistakes, recognize decisions I could have made differently, and learn from practitioners who see something I missed. What matters is whether I can recognize those problems, explain my reasoning, and change direction when the evidence calls for it.

The objective isn’t to prove that my methods are the only correct way to investigate. It’s to show how I apply them, invite criticism, and improve what can be improved.

And if something I’ve been teaching turns out to be wrong, incomplete, or less effective than another approach, I want to know.

You can watch, question my decisions, and suggest a better approach. And when I’m wrong, I expect you to tell me. That’s not a problem with this exercise.

That’s actually the point.


Join the Free Live Investigation Series

The investigation is already underway. The first live session is planned for next week, with additional sessions scheduled as records arrive and the investigation develops.

There is no predetermined number of sessions and no guaranteed outcome.

You’ll be able to follow the investigative decisions, examine the reasoning behind them, and contribute questions or alternative approaches through Zoom’s Q&A.

Sign up to receive invitations to the live sessions.

Registration is free. Attend as many or as few sessions as you like.

Come with questions. If you think there’s a better way to work the case, I want to hear it. Seats are limited to 500 (per my Zoom account), but that will probably be enough for everyone interested with time to join in.

Share this:

  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on X (Opens in new window) X
  • Share on Telegram (Opens in new window) Telegram
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Reddit (Opens in new window) Reddit
  • Share on Bluesky (Opens in new window) Bluesky

Like this:

Like Loading…

Discover more from Brett's Ramblings

Subscribe to get the latest posts sent to your email.

Author

Brett Shavers

Follow Me
Other Articles
Previous

DON’T FOLLOW THE NARRATIVE. FOLLOW THE EVIDENCE.

Next

I Applied a DFIR Investigative Mindset to a Police Chief’s Retirement. Here’s What the Records Show.

No Comment! Be the first one.

    Leave a ReplyCancel reply

    • X
    • LinkedIn
    • Bluesky
    • Instagram
    • Mastodon
    • FACT Attribution Framework
    • https://www.dfir.training
    • https://winfe.wordpress.com
    • https://xwaysforensics.wordpress.com

    My recent interview on a really good DFIR podcast (Parsing the Truth).

    • X
    • LinkedIn
    • Instagram
    • Bluesky
    • Facebook
    • Mastodon
    • YouTube
    Copyright 2026 — Brett's Ramblings. All rights reserved.

    %d