Relatedness and Competence
The narration between entries paraphrases; it never reads an entry aloud before the entry plays. Every entry in this lecture plays exactly as it does on its own page — same file, same speed, nothing laid over it.
What you can do after this
- Define relatedness, and name the two functions supportive relationships serve
- Explain why proximity is not connection, and how leaders model connection instead of mandating it
- Define competence, and name Bandura's four sources of self-efficacy
- Calibrate a stretch, and give feedback that builds competence
- Explain why the three needs must be supported together, and name the distortions when one is missing
What it covers
22 entries in 7 topics. Each number links to that entry on its own.
-
1. Relatedness
-
2. Marcus
-
3. Building connection
-
4. Competence
-
5. Diego
-
6. Developing competence
-
7. The complete ARC
Check yourself
What two support functions do Feeney and Collins describe?
A safe haven that offers comfort in adversity, and a secure base from which a person ventures out to take risks and grow.
According to the book, what does proximity produce, and what bridges the gap to connection?
Familiarity; the gap is bridged by vulnerability, reciprocity and intentional attention, not by time.
What are Bandura's four sources of self-efficacy?
Mastery experiences, vicarious experience, verbal persuasion, and how people read their own physical and emotional states.
What did Mueller and Dweck find about praise?
Children praised for intelligence persisted less and performed worse after failure than children praised for effort.
What distortion does the book say autonomy without relatedness produces?
Isolation: the person is free but alone.
Lecture transcript
The narration as recorded, in order. Where an entry plays, the transcript links to it rather than reprinting it — the entry plays from its own file, unaltered, and says the same thing on its own page.
This is Units Eight and Nine of The Lost ARC, covering relatedness, then competence and the complete ARC. The last lecture closed on autonomy, the first of the three needs. This one takes the other two, and then sets all three side by side. Carry one question through it: why does one good moment, a first connection or a first success, so rarely hold? Two stories answer half of it; the book's case for interdependence answers the rest. By the end you will be able to define relatedness, and name the two functions supportive relationships serve. To explain why proximity is not connection, and how leaders model connection. To define competence, and name Bandura's four sources of self-efficacy. To calibrate a stretch and give feedback that builds competence. And to explain why the three needs must be supported together.
Three entries on the second need, relatedness: what it is, what supportive relationships do, and what coworkers do.
The second need defined.
ARC 176 Relatedness
Self-Determination Theory's second need, relatedness, is feeling connected to, cared for by and significant to others, knowing your absence would leave a gap. The book's image: autonomy says our lives are self-authored; relatedness says we are not alone in the authoring. The book argues that identity is built through connection, and is less stable without it.
Two things supportive relationships do.
ARC 177 Safe Haven and Secure Base
Brooke Feeney and Nancy Collins's twenty fifteen model of thriving through relationships describes two support functions: a safe haven that offers comfort in adversity, and a secure base from which a person ventures out to take risks and grow. The book's leadership reading is that the second function is why relatedness drives growth, not only comfort.
What coworkers do to work.
ARC 178 Coworkers Matter
Daniel Chiaburu and David Harrison's two thousand eight meta-analysis, of one hundred sixty-one samples and nearly seventy-eight thousand employees, found coworker support and antagonism both related to people's role perceptions, attitudes, withdrawal and effectiveness. The effects held even after accounting for leaders' influence, which the book reads as relatedness being a structural advantage.
Two entries on the book's story of relatedness, and on why a single opening tends not to last.
The book's story of relatedness.
ARC 179 Marcus
In the book's composite story, gifted, isolated Marcus helps a struggling newcomer, Priya, at a whiteboard. The next day she invites him to lunch, and in meetings she asks for his view publicly, so he has to speak. For a few months he is visibly different. Then, the book says, the old distance slowly returns.
What Marcus's story teaches.
ARC 180 Openings Revert
The book's lesson from Marcus is that relatedness is sustained by continuous conditions, not single events, and an opening without structural support tends to revert. Two years on, Marcus says some things changed, not everything, more than before. That is the first half of this lecture's answer. The book calls it not failure but what the research predicts.
Four entries on building connection: familiarity, forced closeness, modelling, and a diagnostic.
Familiarity and connection are different.
ARC 181 Familiarity Is Not Connection
The book argues that proximity produces familiarity, not connection: knowing someone's name, schedule and role differs from trusting their judgment and investing in their success, like two colleagues who share a corridor for years without a real conversation. The gap, the book says, is bridged not by time but by vulnerability, reciprocity and intentional attention.
Why mandated closeness backfires.
ARC 182 Why Forced Team-Building Fails
The book warns that mandated team-building often backfires, because it forces intimacy in an artificial setting rather than making genuine connection safe: a compulsory trust exercise at an offsite, then the same guarded office on Monday. This is the book's own claim, drawn from experience rather than from a cited study.
What leaders can do instead.
ARC 183 How Leaders Model Connection
The book says leaders cultivate relatedness by modelling the behaviours that make connection safe, not by mandating it: asking real questions, remembering what people share and following up, treating a request for help as trust and disagreement as engagement. It adds acknowledging the whole person, not only the professional function, so people are known, not merely recognised.
How to check whether people feel connected.
ARC 184 Do People Feel Connected?
The book's relatedness chapter ends with five diagnostic questions, answered by what actually happens rather than by intention. Can you name one personal interest, concern or aspiration for each person who reports to you? Do people collaborate voluntarily, or only when required? Who might feel isolated, and when did you last act to include them? Do people seek you out beyond tasks? And when someone is absent, does the team notice? The matching practice is small: extend one genuine invitation this week to the person who seems most disconnected.
Four entries on the third need, competence: what it is, where the belief comes from, and what frustration does.
The third need defined.
ARC 201 Competence
Self-Determination Theory's third need, competence, is the experience of effectiveness: the belief that your actions can produce meaningful results, the conviction after finishing something hard that the effort was not futile. The book is careful that competence is not expertise, perfection or superiority over others; it is effectiveness experienced from the inside.
Where the belief comes from.
ARC 202 Mastery Experiences
Albert Bandura's research on self-efficacy found that belief in your own capability is learned, above all through mastery experiences: succeeding at tasks that stretch you. No amount of encouragement matches the evidence of having done something difficult. The book treats Bandura's self-efficacy as closely related to Self-Determination Theory's competence need.
Bandura's four sources.
ARC 203 Four Sources of Self-Efficacy
Bandura identified four sources of self-efficacy: mastery experiences, vicarious experience, verbal persuasion, and how people read their own physical and emotional states, like watching a peer succeed, a credible mentor saying you can, or reading a racing heart as excitement. Mastery remains the foundation, so the book urges challenges achievable with effort, not guaranteed ones.
When competence is frustrated.
ARC 204 Competence Frustrated
When competence is frustrated, the book says, people withdraw and avoid challenges that might expose them, drifting toward what Martin Seligman called learned helplessness: an employee repeatedly set up to fail stops trying, convinced effort changes nothing. The book adds that the damage reaches identity, as people start doubting they have anything to offer.
Two entries on the book's story of competence, and on what happened after the moment everyone remembers.
The book's story of competence.
ARC 205 Diego
In the book's composite story, quiet Diego spots the outdated schema breaking a stalled data model and fixes it in ten minutes: two weeks of stuck work resolved by the person at the end of the table, and someone calls it brilliant. The book's author admits he told the story for years ending there, because that ending was irresistible.
What happened next.
ARC 206 The Next Six Months
In the fuller version, Diego overreaches on a workstream and retreats, until a project lead says it was her fault for not scaffolding it, and gives him a smaller investigation that fits his strengths, then another. The book's lesson completes this lecture's second half: one mastery experience creates an opening; the six months after decide whether it becomes an identity.
Three entries on developing competence: the zone where it grows, the stretch, and feedback.
The space where competence grows.
ARC 207 The Zone of Proximal Development
The book borrows Lev Vygotsky's zone of proximal development: the space between what a person can do alone and what they can do with guidance, like a new analyst unable to build the model alone but able to with a colleague beside her. The book places the best development inside that zone.
How to set the level of challenge.
ARC 208 Calibrating the Stretch
The book's art of developing competence is calibrating the stretch: too little challenge produces boredom and erosion; too much produces anxiety and helplessness, like one assignment pitched slightly beyond comfort and another so far beyond that the person freezes. Competence grows through meaningful challenge and adequate support together; neither alone is sufficient.
Feedback that builds competence.
ARC 209 Feedback That Builds
Claudia Mueller and Carol Dweck found in nineteen ninety-eight that children praised for intelligence persisted less and performed worse after failure than children praised for effort, and came to see intelligence as fixed. The book applies the finding to leaders: feedback on effort and strategy builds competence; feedback on fixed ability makes failure threatening.
Four entries on the three needs together. The opening question is answered here.
The three needs together.
ARC 210 The ARC Complete
The book completes its ARC of identity: autonomy gives authorship, relatedness gives belonging, and competence gives confidence, the evidence that effort counts, as in a person who chooses their work, knows they matter to the people around them, and can see their results. With all three present, the book says, identities become stable and resilient.
When one need is missing.
ARC 211 When One Need Is Missing
The book's shorthand for a missing need: without autonomy, people comply but do not commit; without relatedness, they perform but do not connect; without competence, they try but do not persist, like three employees on one team, each struggling differently. Missing any one, the book warns, leaves identity fragile in predictable ways.
The payoff: the needs depend on each other.
ARC 212 Interdependence
Self-Determination Theory treats autonomy, relatedness and competence as distinct needs, but the book argues that in practice they are deeply interdependent, and supporting one while neglecting the others produces its own distortion. That answers this lecture's question: a single moment serves one need, and growth holds only when conditions serve all three. The book names three distortions. Autonomy without relatedness produces isolation: free, but alone. Relatedness without autonomy produces enmeshment: belonging, but lost within the group. Competence without relatedness produces arrogance or fragility: capable, but without the relationships that carry capability through setbacks. Against these the book sets a robust identity, built on all three at once. So leaders should build environments that serve all three needs together, rather than running three separate initiatives, and should look at all three in the particular person before reading them.
The three needs working together.
ARC 213 The Reconciliation Team
In the book's composite story, Mr. Washington gives a cross-functional team six months and binding authority to unify three departments' databases. A chaotic first month with walkouts gives way to productive argument by month three, and the team names itself the reconciliation team. He did not solve the data problem, the book says; he created the conditions for others to solve it.
Look at what you can now do. You can define relatedness, and name its two functions, a safe haven and a secure base. You can explain why proximity yields familiarity rather than connection, and why leaders model connection instead of mandating it. You can define competence as effectiveness experienced from the inside, and name Bandura's four sources, with mastery first. You can calibrate a stretch between boredom and helplessness, and praise effort and strategy rather than fixed ability. And you can explain why the three needs must be supported together, and name the distortions when one is missing. The next lecture turns to the climate those needs live in, beginning with trust. The full framework, with every story and tool, is in The Lost ARC by Justin Ryan Carver, available on Amazon.
This is free, and stays free. If it helped, here is what keeps it running.