So instead of: How do I decrease adoption?
You think: How do I avoid decreasing adoption?
I think this works anyway. Another example:
Goal: Fly to Spain
Question: How do I fly to Spain?
The inverted question should not be "How do I not fly to Spain?" (answer: get put on a flying ban or don't buy a ticket) but "How do I avoid not flying to Spain?" (answer: pick a date and book tickets)
The example given is "how do I keep my pilots alive?" with the inversion "what could kill my pilots?". Your result would be "how do I avoid not keeping my pilots alive?", which is just the original question.
Wald instead flipped it and recommended armor be added to the areas with less or no combat damage on returning airplanes because the shot-up areas were the parts of the plane that COULD withstand damage, since the plane had made it back.
Pretty much that, except in any long-standing industry, it's framed as "what does kill pilots?" and "Lets study the last few decades of pilot mortality data and identify causes". Safety standard improve one Air-crash Investigation at a time.
"The Field Guide to Understanding 'Human Error'" by Sidney Dekker is probably where to start with that field.
In general, instead of "how do we achieve $X?" the inversion is "what is stopping $X?" or "what would cause $X to fail?".
If you want to be in Spain, why aren't you there right now?
("How do I not not fly to Spain?")
How do I not lose money? - Don’t gamble.
How do I not not make money? - Take more risks.
A true inversion with a negative works better than the not-not structure, and it is easier to wrap your head around.
> Instead of asking how do we increase the adoption of a product or feature? You could instead consider - what are some of things preventing adoption?
Surely to invert the question you'd want to consider how do I deliberately decrease adoption of the product? It might lead to some of the same answers, like make it slower. But also to different ones, like constantly bad-mouth my own product on social media. (Which would indicate a path to adoption is to rigorously rebut criticism using Google Alerts.)
Edit: I think the difference is if I'm only looking for what about my current product prevents adoption, then I've narrowed my scope to looking at aspects of my current product. Whereas if I blue-sky think about ways to make the product bad, that allows a broader range of solutions for making it good.