Connectable Summary: Build Team Connection Without Forced Socializing

Key Ideas

1. Distinguish a lack of connection from a lack of contact

The book's central subject is not simply the number of people an employee encounters. Jenkins's explanation distinguishes the absence of meaningful connection from the absence of people. This matters because a team can create more contact without changing the experience that made the contact unsatisfying in the first place.

Imagine a colleague who attends every meeting but leaves without understanding why their work matters or whom they can ask for help. Another meeting may increase their workload while leaving those questions unanswered. A more relevant conversation could clarify the contribution expected from them and identify a person who can provide timely context.

Begin by asking about a specific part of the work. Where does the person have enough information? Where do they encounter uncertainty? Which exchanges help them move forward, and which leave them waiting? These questions invite useful descriptions without requiring the person to adopt a label about their emotional state.

Look for differences between participants rather than assuming that a single arrangement serves everyone. An office-based employee may have informal access to a specialist that a remote colleague lacks. A worker on another shift may receive decisions without hearing the questions that shaped them.

The practical test is whether people can participate and contribute more meaningfully, not whether they become more visibly outgoing. Contact can support connection, but the two are not interchangeable. Keeping the distinction clear can prevent a well-intentioned leader from responding to an access or purpose problem with an unwanted increase in compulsory social activity.

2. Look with curiosity while protecting privacy

Looking at loneliness is the first part of LINK, but a manager should not translate that invitation into an unofficial diagnostic exercise. A person's silence, camera preference, or decision to skip an activity cannot establish what they feel. Observation can suggest a question; it does not supply the answer.

Ask about the conditions the person experiences. For example, invite a new employee to explain where they can currently obtain feedback and which questions have been hard to raise. Let them choose how much personal context to share. A description of a missing handover may be more useful to the manager than an intimate account the employee did not wish to give.

Provide more than one suitable route for feedback. A private conversation, a written comment, or a follow-up after a meeting may make different concerns easier to express. Explain what will happen to the information and avoid promising confidentiality that the organization cannot provide. Where a concern needs a different support route, acknowledge that limit instead of turning the check-in into an amateur assessment.

The useful outcome is a clearer account of the relationship between work and connection. It may identify something the leader can change. It should not become a record ranking employees by how much they reveal or how successfully they perform friendliness.

3. Invest through helpful, responsive working relationships

The investment part of LINK directs attention to relationships that need more than occasional enthusiasm. Jenkins's related explanation emphasizes prosocial behavior and psychological safety. A practical communication application is to make small acts of help reliable and to respond constructively when someone uses the opportunity you offered.

Suppose a colleague is invited to ask questions but receives an impatient answer whenever a question interrupts the team's routine. The stated invitation and the experienced response are in conflict. A leader can improve the arrangement by agreeing on a realistic help channel, allocating time for recurring questions, and acknowledging when the team's instructions were incomplete.

Helpful behavior also needs boundaries. Offering assistance does not require someone to be available at every hour or take over another person's responsibilities indefinitely. Ask what kind of help is wanted, identify who can provide it, and agree when it is reasonable to expect a response. Clear limits can make support more dependable.

In a meeting, make space for contributions before supplying your preferred answer. Ask for an example, acknowledge a correction, and follow through on a concern that could not be resolved immediately. These are original applications of the relationship emphasis, not a claim that a precise script appears in the book.

Avoid making one employee the unofficial host for everybody's connection needs. Support should not depend entirely on an unusually generous colleague doing invisible extra work. Investment is more credible when the manager makes it possible within the work itself and recognizes the effort involved, rather than simply praising a culture of kindness.

4. Narrow attention to purpose, contribution, and clear direction

Narrowing the focus is the third part of the authors' framework. For a communication reader, this is a reminder that belonging involves a relationship to the work as well as to other people. A person may enjoy their colleagues but remain unsure whether their contribution matters or how to judge an appropriate priority.

Use a real assignment to discuss that uncertainty. Ask what the person thinks a good result would look like, who relies on it, and which decisions they can make independently. If their answers differ from the manager's, investigate the instructions and expectations before judging motivation. A missing explanation can resemble a lack of commitment from a distance.

Connect the task to a concrete recipient or use. An archive assistant does not merely finish a spreadsheet; another colleague needs its identifiers to locate the right image. Explaining that connection gives the assistant a meaningful reason to ask about ambiguous entries and gives the team a shared basis for discussing quality.

Narrowing also involves choosing what to leave out. A leader who names every request as the highest priority has not provided useful direction. Discuss tradeoffs and make decisions that the employee is not authorized to make alone. Also explain how to flag a priority that becomes unworkable.

5. Kindle connection through a repeatable cycle of feedback

Kindling the momentum is the fourth part of LINK. The diagram presents a cycle rather than a finish line. One warm conversation cannot establish that every future exchange will be helpful, just as a successful introduction does not guarantee that a new colleague will continue to receive the information they need.

Choose a routine the team can maintain. A short handover that identifies open questions may be more useful than an ambitious event that nobody has time to organize again. Specify who will host the routine, how participants can suggest changes, and when the team will decide whether to keep it.

Use feedback that relates to the original problem. If employees could not obtain clarification, ask whether they can now find the right person and receive a usable answer. If priorities were confusing, inspect whether the next handover leaves the same ambiguity unresolved. Attendance and message volume are easy to count but may not answer either question.

Notice uneven effects. A change that works for the main office may still exclude another shift or a colleague using a different communication channel. Invite those perspectives without demanding that someone publicly justify a personal circumstance.

Sustaining progress can include stopping an activity. If a practice becomes burdensome or intrusive, explain what you learned and replace it with something more suitable. The point is to maintain attention to connection, not loyalty to a particular ritual.