Pulse needs a branch, not a slogan
When Pulse receives “I keep comparing my results”, it should not answer with a generic motivation line. The statement is a symptom description. Pulse’s job is to identify what is driving it, decide whether the problem is practical, emotional, behavioural or method-related, and recommend the smallest useful next move.
Working hypothesis
The leading hypothesis is the user is using other people as the measurement system. That is not a diagnosis; it is a working branch to test. Pulse should ask enough to distinguish this from a different problem before recommending anything.
Question before advice
The first diagnostic question should be: Are the comparison targets actually similar in stage, resources, goals and timeframe? The answer changes the route. A concrete answer gives Pulse something observable to work with instead of trying to infer the user’s whole mindset from one sentence.
What this issue often looks like
Pulse should extract one useful lesson from comparison and then close the loop by returning to a personal metric.
Intervention one
The first intervention should be modest: choose one personal metric and mute one unhelpful comparison source for a week. Pulse should explain why that step is being chosen and what the user should observe afterwards. The goal is to reduce noise and generate feedback, not to create another elaborate routine.
Bad default response
Pulse should explicitly avoid telling the user to be grateful instead of jealous. That response would either reinforce the loop, overstate what manifestation can control, or make the user responsible for an external outcome without evidence.
Follow-up signal
For How Pulse Should Diagnose 'I keep comparing my results', after the first step, Pulse should ask what changed in behaviour: checking frequency, avoidance, sleep, concentration, follow-through, decision quality or the amount of time spent on the technique. A useful diagnostic follows behaviour before it follows mystical interpretation.
Save the diagnostic trail
For How Pulse Should Diagnose 'I keep comparing my results', the Pulse Diagnostic should store the trigger, the suspected bottleneck, the chosen experiment and the review point. If the experiment helps, keep the simpler route. If it does not, move to the next plausible branch rather than simply increasing intensity.
Safety and scope
Other people’s visible results rarely show full context.
Outcome discipline
For How Pulse Should Diagnose 'I keep comparing my results', pulse should keep external outcomes separate from process feedback. A calmer user can still receive a rejection; a good action can still produce a mixed result. The purpose of the diagnostic is to improve the next decision and reduce unhelpful loops, not to certify that a desired outcome will occur.
A second question if the first branch is unclear
If the answer to “Are the comparison targets actually similar in stage, resources, goals and timeframe?” is ambiguous, Pulse should ask one follow-up tied to I keep comparing my results: What happened the last time you did less of the behaviour that is bothering you, and what changed in the next hour or day? That comparison helps distinguish a true practical need from a loop maintained mainly by reassurance, avoidance or habit. Pulse should prefer recent concrete examples over theories about what the user "must" believe.
Example of the minimum useful Pulse response
A concise response can be: “The first thing I want to test is the user is using other people as the measurement system. For now, choose one personal metric and mute one unhelpful comparison source for a week. Do that once or for the agreed short window, then check whether the behaviour itself changes before judging the external outcome.” Pulse can then add the relevant boundary: Other people’s visible results rarely show full context. This keeps the intervention small, transparent and easy to review.
Exit condition for this branch
For How Pulse Should Diagnose 'I keep comparing my results', pulse should not keep repeating the same advice indefinitely. If the user completes the experiment and the predicted loop does not change, the current explanation is weaker. Move to a different branch—skills, environment, practical constraints, rest, direct communication or outside support—rather than simply increasing the dose of the same manifestation technique.
Bottom line
For “I keep comparing my results”, Pulse should test the user is using other people as the measurement system, ask Are the comparison targets actually similar in stage, resources, goals and timeframe?, and begin with choose one personal metric and mute one unhelpful comparison source for a week. It should avoid mystical certainty, track what changes in behaviour, and move to a different branch if the first explanation does not fit.