Locus of control is an expectancy assembled from experience, which tells you exactly how to change it and why most advice fails. Affirmations do not work, because the belief was not built from statements. What works is accumulating evidence that your actions produce outcomes — deliberately, at a scale small enough that the evidence actually arrives. This is the practical version, including the boundary that stops the whole project turning into self-blame.
Start by Catching the Attribution
You cannot change a default you do not notice. For a couple of weeks, when something goes noticeably well or badly, write one line about what you think caused it. The point is not to judge the answer but to see the pattern, and the pattern usually becomes obvious faster than people expect.
Read it back looking for one thing: does the explanation ever imply a different action? An attribution that always lands on circumstance never generates a next step, and an attribution that always lands on you generates guilt rather than a step. Both are visible on paper in a way they are not in your head.
Build Evidence at a Size You Can Finish
The expectancy responds to completed cause-and-effect loops: you did something, and something happened because of it. Large, long, ambiguous projects supply very few of those loops. Small self-directed ones — a thing shipped, a conversation had, a skill practised to a visible result — supply many.
The unglamorous implication is that quantity matters more than significance. Ten small completed loops move the expectancy more than one ambitious project that has not concluded yet, because the belief is built from repetition rather than from magnitude.
Split Every Situation Into Two Columns
This is the core habit and also the safety mechanism. For any difficult situation, write two columns: what responds to my actions, and what does not. A redundancy goes in the second column; how you use the following three months goes in the first. A client's internal politics go in the second; the quality of your proposal goes in the first.
The split does two jobs at once. It concentrates effort where effort works, and it explicitly licenses you not to take responsibility for the rest. Skipping it is how a project to become more internal turns into a project to blame yourself for everything, which is a worse position than the one you started from.
Change the Question After a Setback
Two questions are available after something goes wrong: why did this happen, and what would I do differently. The first invites a story, and stories tend to arrive pre-shaped by whichever default you already hold. The second demands a specific action, and if there genuinely is not one, that is a real answer telling you the event was outside your control.
Asking the second question consistently does most of the work of this whole article. It is also the version that shows up well in interviews, where an answer naming what you changed is heard as judgement and an answer describing conditions is heard as deflection.
Watch the Environment, Not Just Yourself
External expectancies are often learned correctly. If you spend years somewhere your effort genuinely changes nothing — no feedback, no discretion, decisions made elsewhere — you will develop an external default, and that default is an accurate summary of that place. No amount of internal work overwrites accurate evidence.
So the honest version of this advice includes an environmental check: is there anywhere in your work or life where your actions reliably produce visible results? If the answer is nowhere, the intervention is not attributional, it is situational. See where your default currently sits with the locus of control test, and read locus of control and your career for where it bites hardest.