Context isn't background. It's half the equation. The same person becomes a different performer depending on what the arrangement asks for and allows.
Steven Rudolph · 4 min read
A teacher sits in a school where she designs her own curriculum. She pilots experiments. She builds relationships with parents her way. She invents structures for collaboration. She stays late. She redesigns things three times. She brings ideas to every meeting. Her energy fills the hallway. Her students' families request her by name.
The same teacher takes a job at a different school. Same credentials. Same skill. Same person. But this school has a rigid schedule. Textbooks are mandated. Curriculum is set. Any change requires committee approval. Her ideas go into a suggestion box that doesn't move. She teaches her classes well. She goes home at 3:30. Her evaluations say "competent but uninspired." Her colleagues describe her as solid but flat.
Both schools got the same teacher. They got different results. Not because she changed. Because the arrangement changed. And the arrangement was doing most of the work. (Lewin, 1951)
Context sits at the intersection of two Renergence domains. In Alignment, context determines whether someone's engagement needs get met — Multiple Natures maps those needs, but the arrangement decides whether they're fed or starved. In Structure, context determines whether the system itself is well-designed — whether load sits where it belongs or where it landed. A third domain, Positioning, governs how the people inside the arrangement see it — because the same context can look completely different depending on where you stand.
We credit the person for good outcomes and blame the person for bad ones. First school: "She's a natural leader." "She's energized by her work." "She has initiative." Second school: "She doesn't have what it takes." "She's not really someone who innovates." "She's just not that engaged." The person is the variable we fix our eyes on. We name her character based on the output we see.
But what if the arrangement is doing most of the work? What if the person who "doesn't have it" in one setup just hasn't been in a configuration that feeds what she needs? What if competence and energy and initiative are still there — but the structure starves them instead of feeding them?
Context isn't background noise. It's the set of constraints and permissions that shape every moment. (Gibson, 1979) The role itself. The team composition. The manager's expectations. The pace at which decisions move. What decisions you get to make. What's decided for you. How much autonomy exists. What kinds of engagement the work actually requires versus what the job description claims.
It's the difference between work that asks you to design systems and work that asks you to execute someone else's design. Between a team that requires vulnerability and a team where vulnerability is unsafe. Between a role that needs experimental thinking and a role that punishes deviation. Between work that has slack and work that's throttled by constant interruption.
The same person in two different arrangements is living in two different worlds. They'll show up differently. Not because they're different people. Because the setup invites different engagement patterns and feeds different ones.
Multiple Natures measures engagement patterns. It locates which natures you engage with and at what intensity. But here's what matters: the meaning of those patterns depends entirely on the arrangement.
Someone scores high in Administrative nature. That's real. It means they engage in organizing, structuring, making systems work. But in an arrangement that doesn't ask for systems thinking and doesn't value it when it shows up, that engagement drops. Not because they lost the capacity. Because the setup stopped activating it and feeding it. Someone might describe them as "not really an organizational person" — and they'd be right, given what they see. But they'd be wrong about what's happening.
Any assessment that measures a person without measuring their arrangement is measuring half the picture. You get a score. You get a name for the pattern. But you don't get the truth about what determines whether that pattern shows up and with what intensity.
The work isn't to change the person. The work is to design an arrangement that activates the engagement patterns you need and feeds them once they show up.
The manager who isn't detailed could be sent to a time-management seminar. Or you could redesign the role so detail work is required and valued. The team member who "isn't collaborative" could be enrolled in a communication workshop. Or you could build a team structure where genuine collaboration is necessary and supported. The person who "can't focus" could be given willpower training. Or you could remove the interruption architecture and give them work that claims their attention.
The person isn't the problem to solve. The fit is the problem to solve. And that's genuinely news, because fit is something you can actually change.
Instead of "What kind of person is this?" the useful question becomes: "What is this arrangement asking for, and what engagement does this person naturally bring?" Those are different questions that produce different answers.
The second question stops you from blaming. It stops you from trying to reprogram someone into a shape the system forced them into. It lets you see what actually works — not for a generic person, but for this person in an arrangement that fits.
You can't make someone "more detail-oriented" through effort. But you can structure a role where detail matters and the person who does it feels the value. You can't build collaboration from training. But you can design a team where collaboration is the only way forward. You can't force focus. But you can remove the noise and create conditions where attention is possible.
The insight is this: the same person becomes a different performer when the arrangement changes. Not a different kind of person. A different performer. And that difference — that responsiveness to context — is the most important thing to understand about anyone you're trying to work with, hire, develop, or build a team around.
Context isn't peripheral. It's foundational. Engagement patterns are real, consistent, and measurable. What people naturally bring to situations is stable. But that stability is conditional — it depends on what the arrangement asks for and allows. Development happens differently when the arrangement feeds engagement rather than fighting it. And clarity on engagement alone isn't enough to build sustainability. You also need clarity on whether the structure itself is well-designed.
Get new articles directly in your inbox.