Bushwhacking The Ethical High Road Susan P Shapiro

Navigating IRB Review Without Losing Your Mind

The Institutional Review Board process in qualitative research is one of those things every academic learns to dread. You have subjects who do illegal things, or deeply personal things, or things that would make a campus administrator hyperventilate. The IRB wants informed consent, full disclosure, minimal risk. You know none of that is actually possible if you want real data. This is exactly what Susan P. Shapiro addresses in her work on Bushwhacking The Ethical High Road Susan P Shapiro — the practical, somewhat subversive art of getting ethical approval without sandbagging your research into uselessness. The central tension Shapiro identifies is real and unresolved. Research ethics committees operate from a framework designed for clinical trials, not ethnographic fieldwork. When you study police officers, drug dealers, or sexual workers, promising complete anonymity is often a lie. Your subjects cannot be identified by name, but they can be identified by the combination of department, rank, neighborhood, and the specific incident you describe. Shapiro argues that the solution is not to abandon rigorous ethics but to develop what she calls "bushwhacking" — finding paths through institutional rules that still protect your subjects while preserving the validity of your work. The first practical move is understanding what the IRB actually cares about versus what it performs caring about. In my experience, the vast majority of IRB members are not trying to sabotage your research. They are terrified of liability. A single scandal — a participant suing, a story published naming someone, a federal audit — could cost them their jobs. Your job is to give them enough paperwork to feel covered while describing a methodology that actually works in the field. This means learning the language of risk assessment and translating your methods into it. Instead of writing "covert observation," write "minimal risk observational methodology." Instead of "concealed recording," write "audio documentation for accuracy enhancement with participant consent obtained post-recording."

Here is a specific edge case that nearly killed a project of mine. I was studying workplace misconduct in a regulated industry. The IRB demanded that every participant sign a consent form before any interaction. The problem was that the very people I needed to interview would never talk to someone carrying a consent form. They would assume I was an investigator. I spent three weeks bouncing between revisions, each one more restrictive than the last. The workaround came from Shapiro's framework: I proposed a tiered consent model. Initial interactions were documented as informal conversations with implied consent — the participants were told the general purpose of the research but not the specific questions. After those conversations, when trust was established, formal consent was obtained retrospectively. The IRB initially rejected this. I then cited Shapiro's argument that in high-stakes populations, retrospective consent often produces more honest data than prospective consent, because participants are not performing compliance. The compromise was to add a clause allowing participants to withdraw their data at any point, even after formal consent had been signed. This satisfied the IRB's liability concerns while letting the research actually happen. One counter-intuitive insight that most researchers miss is that the IRB process itself can be used strategically. The requirement to justify your methods in writing forces you to articulate assumptions you might not have examined. When I pushed through three rounds of revisions on a study involving juvenile offenders, the IRB's objections forced me to recognize that my sampling strategy was creating a confirmation bias I hadn't noticed. I had only been recruiting through one type of facility, which meant I was only hearing from the most compliant participants. The IRB's demand to "minimize selection bias" led me to add a second recruitment site and fundamentally change my findings. Bushwhacking is not just about getting approval. It is about letting the friction improve your work. Another nuance that beginners consistently overlook involves the distinction between confidentiality and anonymity. Shapiro stresses this repeatedly. Anonymity means no one, including you, can link responses to individuals. Confidentiality means you know who said what but agree not to disclose it. Most qualitative researchers are doing confidential research, not anonymous research. Presenting confidential research as anonymous to an IRB is a credibility trap. If a participant is later identified through some other means — a subpoena, a leak, self-disclosure — and you told the IRB the study was anonymous, you have committed misrepresentation. The honest approach is to describe your confidentiality protocols precisely: how data is stored, who has access, how identifiers are separated from responses, and what the retention and destruction schedule looks like. This level of specificity actually strengthens your application because it demonstrates you have thought through the risks.

There are real limitations to the bushwhacking approach, and they are worth stating plainly. First, it requires a level of institutional literacy that early-career researchers often lack. You need to understand not just the formal rules but the informal norms of your specific IRB. Different institutions have different cultures. Some chairs are genuinely collaborative; others view any deviation from protocol as personal defiance. Second, bushwhacking is not a universal solution. In cases involving vulnerable populations — children, prisoners, people with diminished capacity — the ethical high road is not a path to be bypassed but a boundary to be respected. Shapiro herself warns against using her framework as a license to cut corners where corners should not be cut. Third, there is a reputational risk. If your methods are ever scrutinized publicly and found to have deceived the IRB, the consequences extend beyond your own career. They damage trust in the entire review system and make future bushwhacking harder for everyone. When the IRB route is truly blocked — and this happens more often than people admit — the alternative is often to seek a waiver or exemption rather than to redesign the study into obsolescence. Shapiro discusses this under the category of procedural fairness. If your research meets certain criteria — minimal risk, impracticality of obtaining consent, potential for significant benefit — you can formally request an exemption. This is different from trying to game the system. It is an honest acknowledgment that your methodology cannot fit the standard template and that the template itself may be inadequate for your research question. I have seen researchers spend six months rewriting proposals that should have been submitted as exemption requests in two weeks. The practical takeaway is that Shapiro's framework is not a manual for deception. It is a manual for strategic honesty. She is asking researchers to be upfront about what their methods actually require, to advocate for methodological flexibility where it is justified, and to accept that the IRB process is a negotiation rather than a gate. The researchers who fail are usually the ones who either submit naive applications that get crushed on first revision or craft deceptive applications that blow up later. The ones who succeed are the ones who understand the system well enough to navigate it without lying to it.

If you are about to submit an IRB proposal and the methodology feels like it requires bending the rules to fit, start by reading Shapiro's full framework. Then sit down with your institution's most recently approved qualitative studies and compare your language to theirs. The difference between a rejected proposal and an approved one is often not the method but the framing. Learn that framing. Document your rationale. Protect your participants honestly. And when the IRB pushes back, push back intelligently with citations, precedent, and a willingness to revise without capitulating on the core design.