The Old/Bad Way: A stakeholder criticizes a new Salesforce Flow you built. You immediately get angry, take it personally, and fire back a defensive message on Slack.
Why this fails: The emotion completely controls your action before you even realize you are upset.
The New/Good Way: You notice the hot spike of frustration in your chest first. You pause, observe the feeling, and wait five minutes before typing a response.
The payoff: Your reply is driven by technical clarity and professionalism, rather than impulsive anger.
๐ง The Core Concept
In the AP Framework, The Observer refers to the fundamental awareness that can witness the movement of the mind. Thoughts, emotions, and memories constantly pass through us, but they are just temporary data—they are not the complete reality of who we are.
Self-enquiry challenges us to look directly at the observer itself: What is watching, and from where is it watching?
To understand this practically, we map out the hierarchy of our internal state:
Root: Awareness (The Observer) ├─ Thoughts: The constant stream of ideas appearing in the mind. ├─ Emotions: The physical and mental feelings that come and go. └─ Reactions: The physical actions or words triggered by inner movement.
๐ Key Points
- You are not your thoughts: Thoughts are just events happening in your mind; the Observer is the screen they play on.
- Distance brings clarity: Creating a buffer between a trigger and your reaction is the ultimate professional superpower.
- Observation is neutral: The Observer does not judge feelings as "good" or "bad"; it simply records that they exist, much like a system log.
Rule: Observe first, react later.
Gain: You gain a profound understanding of your own mental triggers and behaviors.
Price: It requires relentless patience and brutal self-honesty.
Limits: Observation is incredibly difficult to initiate when you are already completely lost in a heavy emotional reaction (e.g., severe panic).
Mirror (One Transaction): The next time someone criticizes your work, simply notice your very first defensive thought before opening your mouth.
Later: You will begin to recognize your own repeated emotional patterns across different projects.
At Volume: Deep awareness naturally integrates into your daily decision-making process.
❓ Core Q&A & Follow-ups
The Observer is not about creating a new, "better" idea to fight a bad idea. It is the pure act of noticing the activity of the mind. Practicing this helps us understand our thoughts and emotions without being automatically controlled by them.
A: Start with low-stakes micro-moments. When you are waiting for a page to load or a query to execute, notice if you feel impatient. Don't try to stop the impatience—just label it: "Impatience is here." This trains your brain's "muscle" to observe rather than act, which you can later use in high-stress situations like production outages.
A: Yes. Think of your emotions like Salesforce Debug Logs. When you read an error log, you don't judge the system as "evil"—you just read the data to understand what failed. Treat your negative emotions as internal data logs. Read them without moral judgment.
A: Thinking is the script actively running in your mind (e.g., "I'm going to fail this certification exam"). Observing is the background monitor watching the script run (e.g., "I am noticing that my brain is currently running a script about failing the exam").
A: In highly stressful moments, your brain enters a "fight or flight" state. Your amygdala overrides your prefrontal cortex (the logic center). It’s like a CPU hitting 100% capacity—there's no processing power left for the "Observer" program. Building the habit in calm times helps it trigger automatically during crises.
A: Absolutely. Emotions have a short biological half-life (often around 90 seconds). If you can observe the emotion without feeding it new thoughts ("adding wood to the fire"), the chemical reaction in your body dissipates, drastically reducing your outward emotional outburst.
A: It destroys the cycle of defensiveness. When a colleague points out a flaw in your architecture, your ego will want to fight back. If you observe that ego flare-up, you can let it pass and respond collaboratively. People love working with professionals who don't take feedback as a personal attack.
A: When learning complex systems like LWC, Apex, or Data Cloud, you will frequently hit walls of confusion. The mind often reacts with frustration: "I'm not smart enough for this." By stepping into the Observer role, you notice the frustration, realize it's just a temporary byproduct of learning, and calmly return to the documentation.