I’ve been pondering three words lately.
Seen. Known. Valued.
Maybe that is what most of us are looking for. Promotions, awards, titles, degrees, and résumé lines all matter, sometimes. Underneath much of what drives us, though, may be something considerably simpler.
We want to be seen. We want to be known. And we want to know that, having been seen and known, we are still valued.
There is a difference between the three. Increasingly, I wonder whether they help explain something we seem to be missing in leadership today: trust.
Seen
Being seen means someone notices you. Position, rank, résumé, and output are the easy things to notice. You are harder.
That sounds almost embarrassingly simple until you consider how many people spend their professional lives feeling invisible. Think of the junior Airman whose work quietly keeps everything moving, the faculty member whose ideas never quite make it into the meeting, or the employee who has delivered excellent work for fifteen years and hears from the boss primarily when something goes wrong. Think of the spouse carrying a hundred things nobody notices. Sometimes leadership begins with something as simple as noticing.
There is something deeply human, and perhaps deeply spiritual, about this need. One of the more remarkable moments in the Old Testament comes from Hagar. She was an enslaved woman, mistreated and pregnant, who had fled into the wilderness with nowhere to go. There she encountered God and gave Him a name: “the God who sees me.” Out of every name she could have chosen, that is the one she reached for. The Hebrew is El Roi, and the well where it happened became known as Beer Lahai Roi, the well of the Living One who sees me.
Psychologist William Kahn found something similar in organizations. His 1990 study of personal engagement identified psychological safety, meaning, and availability as the conditions under which people bring their full selves to work. A person has to feel noticed before any of that can happen.
Known
But being seen isn’t the same as being known, and knowing requires investment. What is this person good at, and what are they trying to become? What gives them energy, what frustrates them, and what are they afraid of? What do they care about when they aren’t at work, and what experiences shaped the person standing in front of you?
Organizations are actually pretty good at collecting information about people. We have résumés, performance reports, personnel files, talent-management systems, surveys, metrics, dashboards, and endless databases. We can possess enormous amounts of data about someone without actually knowing them. That distinction matters.
Psalm 139 takes the spiritual dimension from seeing to knowing: “You have searched me, Lord, and you know me.”
Being known is considerably riskier than being seen. You can see the polished version of me. Knowing me means encountering the contradictions, insecurities, failures, aspirations, strengths, weaknesses, and unfinished parts. Which creates one of the great tensions of being human. We desperately want to be known, and sometimes we are terrified that someone actually might know us.
Because being truly known raises another question:
If you really knew me, would you still value me?
Valued
This may be the hardest one, because being valued is different from being useful, and I wonder whether modern organizations increasingly confuse the two.
Organizations are very good at valuing usefulness. Can you produce, solve this problem, fill this billet, make the numbers, get this across the finish line? There is nothing inherently wrong with any of that. Organizations exist to accomplish things, and missions and performance matter. But human beings quickly figure out whether an organization values them or merely values what it can extract from them.
The trust literature has language for this. In their widely cited 1995 model of organizational trust, Mayer, Davis, and Schoorman argue that a leader’s trustworthiness rests on three factors: ability (the skill to do the job), integrity (adherence to principles the follower finds acceptable), and benevolence (the belief that the leader wants to do good by you). Organizations invest heavily in the first, talk often about the second, and quietly neglect the third. Benevolence is where being seen, known, and valued lives. It is also the factor that no dashboard captures.
Praise from someone who doesn’t know you feels good. Being valued by someone who actually knows you feels different. It says, I see you, I know you, and you matter. Maybe that is one of the most powerful messages one human being can communicate to another.
And perhaps it gets us to trust.
Trust Is the Oil
We talk about trust constantly in leadership. Build trust, empower your teams, create psychological safety, practice mission command, push decisions downward, encourage initiative. All good advice.
But there is something strange about telling people to trust one another. Trust isn’t an instruction. And I’m not sure it belongs alongside Seen, Known, and Valued as a fourth item, either.
Maybe trust is the oil. It is what keeps the machinery of leadership moving. Without it, everything creates friction: more oversight, more approvals, more meetings, more reporting, more checking, more coordination, and more rules designed to prevent the last thing that went wrong. There are always more people making sure they have an email proving that whatever happens next wasn’t their fault.
Mayer and his colleagues define trust as a willingness to be vulnerable to another party irrespective of the ability to monitor or control that party. Hold that definition up against the machinery above. Every added layer of oversight is an attempt to substitute monitoring for trust. An organization can operate that way for a surprisingly long time. But eventually we begin confusing all that machinery with leadership.
Trust changes the equation. When it is abundant, organizations don’t need to expend nearly as much energy protecting themselves from themselves. Intent can replace instruction, and conversation can replace coordination. Initiative can replace permission, and candor can replace compliance. People move faster because they aren’t constantly calculating the personal consequences of being wrong.
But trust isn’t something leaders suddenly manufacture when they need it. We should be swimming in it every day. It accumulates through thousands of interactions that seem insignificant at the time. Did you listen when I disagreed with you? What happened when I brought you bad news? Did you defend me when I took a reasonable risk and failed, and give me credit when things went well? Were you interested in me when you didn’t need something, and did you notice when I was struggling? Did you keep your word and tell me the truth?
And perhaps most importantly: did you trust me when trusting me carried some risk for you?
That is where Seen. Known. Valued. comes back into the picture. Think of them as the daily maintenance that keeps the oil in the system. Leaders who see people, know people, and value people continually put trust back in, and over time it begins to saturate the environment.
Why People Stop Taking Initiative
This also makes me wonder whether we ask the wrong questions when organizations become overly cautious. We ask why people don’t take initiative, when maybe we should ask what the organization has taught them happens to people who do. We ask why they won’t speak candidly, when the better question may be what happened the last time someone did. We ask why they won’t tell leadership the truth, when perhaps we should ask what happens to the person who brings bad news.
Amy Edmondson’s 1999 study of 51 manufacturing teams gave this idea its research name: psychological safety, a shared belief that the team is safe for interpersonal risk-taking. Teams with it showed more learning behavior. Teams without it learned less, because the truth stayed hidden.
And when we ask why they don’t trust leadership, perhaps the first questions ought to be whether they believe leadership sees them, knows them, and values them. Those are much harder questions, because they turn the examination back toward the leader.
Mission Command Starts Here
This matters enormously for mission command. We tend to describe it through doctrine: commander’s intent, disciplined initiative, decentralized execution, mutual trust. In Army doctrine, the first of the six principles is to build cohesive teams through mutual trust, and doctrine treats trust as an imperative for accepting calculated risk and exercising disciplined initiative without fear of reprisal. General Dempsey’s mission command white paper went further, calling on leader development to create the climate for greater trust.
Yet perhaps we begin too far downstream. Mission command ultimately asks people to do some remarkably difficult things. Tell me when I’m wrong, and tell me the bad news early. Admit your mistakes and challenge my assumptions. Take initiative without asking permission, make decisions when I am not there, take intelligent risks, and accept responsibility.
Those actions require vulnerability, and vulnerability requires some expectation about what happens next. If experience tells me that mistakes are punished, dissent is remembered, bad news damages careers, and people are valued primarily for their usefulness, then the rational response is self-protection. No amount of rhetoric about empowerment changes that calculation.
Mission command cannot be switched on when the shooting starts. The trust required for decentralized execution has to exist before the organization needs it. It is built on ordinary Tuesdays, in meetings and hallways, during disagreements, after mistakes, and when somebody tells the boss something the boss doesn’t particularly want to hear. That is when we discover whether trust is actually present.
And Then There Is Adaptation
This may go one step further. I’ve spent a lot of time thinking about adaptability, particularly why some organizations can change when their environment changes and others seem incapable of doing so. Perhaps there is a human layer underneath organizational adaptability that we don’t discuss enough.
Adaptation requires someone, somewhere, to recognize:
This isn’t working anymore.
Then that person has to be willing to say it, and someone else has to be willing to listen. The organization has to tolerate the possibility that the established answer is wrong. Someone has to propose something different, and eventually somebody has to take the risk of trying it.
Every step in that process depends upon trust. Without it, inconvenient information gets suppressed and dissent becomes dangerous. People wait for permission, and failure becomes something to hide rather than something to learn from. Organizations become very good at continuing to do what they already know how to do, even as the world changes around them.
So perhaps there is a relationship here:
Seen → Known → Valued creates the conditions for Trust, which enables Initiative, which makes possible Adaptation.
I’m not ready to call that a model. Maybe it isn’t even linear. Human beings and organizations are rarely that tidy. But I think there is something here worth pondering.
We spend enormous amounts of money trying to build better leaders, with competency models, leadership courses, assessment systems, doctrine, talent-management processes, and professional military education. All important. But perhaps occasionally we should ask leaders three much simpler questions:
Do your people believe you see them?
Do they believe you know them?
Do they believe they matter to you?
And then one more:
What did you do today that gave them a reason to trust you?
Trust gets built or eroded in every interaction, every day, and no demand, rank, or line in a command philosophy changes that.
Seen. Known. Valued.
Maybe that’s where trust begins. And maybe trust is what keeps the whole thing running.
Sources linked above: Genesis 16:13–14; Psalm 139:1; Kahn (1990), Academy of Management Journal; Mayer, Davis, and Schoorman (1995), Academy of Management Review; Edmondson (1999), Administrative Science Quarterly; ADP 6-0 principles via Modern War Institute and Army.mil, including the Dempsey white paper discussion.
