Reframe a Rejection as Diagnostic Data

Rejections arrive as events but we immediately convert them into stories about ourselves. That conversion is usually wrong and always premature. This separates what the rejection actually shows from what you are projecting onto it, finds the one signal worth keeping, and replaces the unanswerable question of why you failed with a practical question about what to do next.

I received a rejection from {REJECTION_SOURCE} for {WHAT_WAS_REJECTED}. My initial interpretation of why: {MY_INTERPRETATION}.

Reframe this rejection as diagnostic data by:
1. **Alternative explanations**: give me three plausible alternative reasons for the rejection that are not about my ability or worth, including timing, fit, and factors outside my control
2. **What the data actually shows**: distinguish between what I can reasonably infer from this single data point and what I am projecting onto it
3. **The one signal worth keeping**: if there is one thing from this rejection that might actually tell me something useful about how to adjust my approach, what is it?
4. **The question to ask instead of 'why did I fail?'**: reframe my situation as a practical question about what to do next