Studio Note 011: Your Organization Is Growing. Your Relationships Aren't.

In This Studio Note

• Why this matters: Growth creates more relationships than a founder can personally manage, making the organization's relational culture increasingly important.

• The common mistake: Organizations hire people who look qualified on paper without asking whether they genuinely care about the people they're being hired to serve.

• What we've observed: Relationships begin deteriorating when employees become focused on completing transactions instead of creating transformations.

• A better way to think about it: You don't need to replicate the founder's personality or methods. You need to replicate the founder's heart for the mission and concern for the people.

• Practical next steps: Build teams around purpose, SoulFire®, NERI®, relational standards, and enough autonomy for people to create meaningful relationships in their own authentic way.

Growth Changes Who Holds the Relationship

There is a point in almost every growing organization when something quietly changes. In the beginning, the founder is everywhere—answering emails, taking sales calls, talking with customers, solving problems, attending events, training employees, responding to complaints, and making sure people are taken care of.

If something doesn't feel right during those early years, the founder usually notices because they're close enough to the relationship to feel it. They can step in, make the phone call, correct the experience, or personally make sure someone understands what the organization was trying to do.

Then the organization grows, and suddenly the founder isn't answering every email or taking every call. Someone else is onboarding the customer, delivering the service, handling the problem, welcoming the guest, representing the organization at an event, or having the conversation that ultimately determines whether someone stays or leaves.

Growth changes who holds the relationship.

That's where organizations can begin losing something incredibly valuable without realizing it's happening. We tend to celebrate growth through numbers, more revenue, more employees, more customers, more locations, more programs, more reach, but every one of those numbers also represents an increase in human interactions happening without the founder in the room.

That's an entirely different challenge than simply increasing capacity. You're not just scaling operations; you're asking more people to carry relationships that were originally shaped by the founder's personal care, conviction, and understanding of why the organization exists.

The founder may have built the organization because they genuinely cared about solving a particular problem for a particular group of people. They saw something that bothered them enough that they were willing to sacrifice time, money, security, and probably quite a bit of sanity to do something about it.

That care naturally influenced how they treated people because the transaction was never really the point. The founder wasn't simply trying to process another sale, complete another service, or move another person through a system.

The transformation was the point.

Then organizations begin hiring, and this is where I see one of the most expensive mistakes growing organizations make. They hire people who are good on paper without stopping long enough to determine whether those people actually give a damn about the humans they're being hired to serve.

Someone has the right degree and has worked at the right companies. They have the certifications, understand the software, know the process, interview beautifully, and have a résumé that checks every box leadership has been told should matter.

But they don't actually care.

You can train a lot of skills. You can't train giving a damn.

If someone doesn't genuinely care about the purpose behind the organization or the people being served, eventually the work becomes transactional. The customer becomes another account, the donor becomes another contribution, the patient becomes another appointment, the volunteer becomes another name on the schedule, and the employee becomes another position that needs to be managed.

What's dangerous is that the organization may continue functioning perfectly well on paper. Tasks are being completed, calls are being answered, services are being delivered, and performance metrics may even look perfectly acceptable, while something entirely different is happening relationally.

People stop feeling cared for.

That's often when leadership begins trying to fix the wrong things. They introduce new scripts, build more SOPs, create customer-service standards, add training, implement another CRM, automate more communication, or write another employee handbook explaining exactly what someone should say and exactly what someone should do.

None of those things are inherently bad, and many of them are necessary as an organization grows. But they're tools for supporting behavior; they cannot create the motivation underneath the behavior.

A script cannot make someone care, an SOP cannot manufacture empathy, and a customer-service policy cannot create genuine concern for another human being. You can teach someone exactly what to say and still have the customer know they don't mean a damn word of it.

That's why I don't believe scaling relationships begins with teaching employees to behave more like the founder. The founder isn't the magic ingredient because of their particular personality, communication style, or way of completing a task; what matters is the heart underneath those behaviors.

Why does the founder care? Why does this work matter, why do these people matter, and what transformation are we actually here to create?

Those are the things that have to survive growth.

The founder's how doesn't need to be replicated. Their heart for the mission does.

This is where SoulFire® becomes incredibly important inside an organization. If someone's deeper purpose has no meaningful connection to the work they're being asked to perform, the relationship can very easily become transactional, even if that person is exceptionally talented.

They may perform incredibly well for a while, hit their numbers, follow every procedure, and execute exactly what was asked of them. But if there is no deeper connection to why the work matters, eventually they're simply doing a job—and when another job offers more money, better hours, a different title, or an easier environment, there's very little emotionally connecting them to the work they're leaving behind.

When someone's SoulFire® meaningfully connects with the purpose of the organization, something different becomes possible. There is a reason for them to care beyond the paycheck, and the transformation matters to them personally even if their reason for caring isn't identical to the founder's.

That's when we can bring NERI® into the conversation and ask a completely different question. Instead of asking, "How do we make this person interact with customers exactly like the founder?" we can ask, "Given who this person naturally is, how can they create the same level of care, trust, and connection in a way that's authentic to them?"

One employee may be naturally warm and expressive, while another may build trust by being extraordinarily thoughtful and dependable. Someone else may connect through humor, another through knowledge, and another because they're exceptionally good at making people feel calm when something has gone wrong.

They don't need to become the same person.

They need to care about creating the same kind of transformation.

That's how relationships can grow without becoming manufactured. You preserve the heart of the organization while allowing the personalities of the people carrying that heart into the world to remain authentic.

An organization doesn't need fifty versions of its founder. It needs fifty people who genuinely care about why the organization exists and are empowered to express that care through who they naturally are.

That's when growth stops diluting relationships and starts multiplying them.

The Moment Transformation Becomes Transaction

One of the easiest ways to recognize that an organization's relationships aren't growing alongside the organization is to look at what people believe they're responsible for accomplishing. When the organization is small, the founder usually thinks about the outcome: Did we actually help this person? Did we solve the problem? Did we create the transformation we promised? As the organization grows, those questions can quietly become tasks, metrics, quotas, and processes.

That shift isn't automatically bad. Growing organizations need systems, measurements, accountability, and clear expectations because good intentions alone cannot run an organization. The problem begins when completing the process becomes more important than accomplishing the purpose the process was originally created to support.

That's the difference between transaction and transformation.

A transactional employee asks whether the task was completed. A transformational employee still completes the task, but they also understand why the task exists and pay attention to whether it actually accomplished what it was supposed to accomplish for the human being on the other side.

You can see the difference everywhere. A customer service representative can technically answer a question while leaving the customer feeling dismissed. A salesperson can successfully close a contract with someone who was never a good fit. A nonprofit can process hundreds of people through a program without asking whether their lives actually changed because of it.

On paper, all three organizations may appear successful. The boxes were checked, the numbers were recorded, and the transactions occurred, but the heart of the work was missed.

This is why I believe organizations need to be very careful about what they measure as they grow. Human beings naturally begin optimizing toward whatever leadership repeatedly tells them matters, so if all we celebrate is volume, speed, revenue, conversions, productivity, or completed tasks, we shouldn't be surprised when people begin prioritizing those things over relationships.

The numbers matter, but they need context. Revenue matters because organizations need money to survive, efficiency matters because resources shouldn't be wasted, and systems matter because chaos isn't a relationship strategy either. None of those things, however, should become disconnected from the transformation the organization exists to create.

The question isn't simply, "Did we complete the task?" It is, "Did completing the task accomplish what the task was created to accomplish?"

That distinction sounds obvious until you start looking closely at organizations. I've seen beautifully designed processes that everyone followed perfectly even though the process no longer served the people it was created for. No one questioned it because their responsibility had become following the system rather than understanding the purpose behind it.

This is also how organizations accidentally train good people to stop caring. Someone may begin a role deeply invested in helping people, but if they're repeatedly rewarded for speed instead of care, quantity instead of quality, or compliance instead of discernment, they learn very quickly what the organization actually values.

Culture isn't simply what leadership says matters. Culture is what the organization consistently rewards, tolerates, corrects, and celebrates.

That's why putting a mission statement on the wall isn't enough. If you say people matter but punish an employee for taking five extra minutes to solve someone's problem correctly, you've communicated what actually matters. If you say relationships matter but only celebrate the person who generates the most revenue, you've communicated what actually matters.

Your team is always watching the difference between what you say and what you reinforce.

This is where growth becomes dangerous for organizations that haven't intentionally translated the founder's heart into the culture. When the founder personally handled relationships, they could make judgment calls based on what felt right in the moment. They might spend extra time with someone, bend a process when it made sense, notice when a person needed something different, or choose the relationship over short-term efficiency.

Once the founder isn't there, someone else has to know what matters enough to make those decisions.

That doesn't mean employees should have unlimited freedom to ignore systems whenever they feel like it. Standards, financial boundaries, legal requirements, intellectual property, safety, and operational realities still matter. But within those boundaries, people need enough understanding of the organization's purpose to exercise intelligent judgment instead of simply following instructions.

That's why the answer isn't more scripts.

It's deeper alignment.

When someone understands the why, has a genuine personal connection to the mission through their SoulFire®, and understands their own relational patterns through NERI®, they have more information from which to make those decisions. Instead of impersonating the founder, they're learning how to carry the organization's intention through their own personality.

That creates a very different kind of consistency.

Traditional organizational consistency often means trying to make every person behave identically. Everyone follows the same script, uses the same words, performs the same gestures, and delivers the same standardized experience because leadership believes sameness creates reliability.

Relational consistency doesn't require sameness. It requires the same heart and the same standard of transformation, expressed authentically through different human beings.

That distinction matters because your customers are human beings too. They can feel the difference between someone performing care and someone actually caring, just as they can tell when an employee is reciting a required phrase rather than genuinely trying to help.

The goal isn't to eliminate the transaction. Every organization has transactions, whether that's exchanging money, processing paperwork, delivering a service, scheduling an appointment, accepting a donation, or completing a project. Transactions are simply the mechanics that allow organizations to function.

The problem begins when the mechanics become the mission because once that happens, you may continue growing your numbers while quietly shrinking the very thing that made people want a relationship with your organization in the first place.

You Don't Need More People Who Look Good on Paper

As organizations grow, hiring tends to become increasingly focused on competency. Leaders look at education, years of experience, certifications, previous employers, technical skills, and whether someone has already performed a similar role somewhere else. Those things matter, but I've found that organizations often spend enormous amounts of energy determining whether someone can do the work without spending nearly enough time determining whether they actually care about the reason the work exists.

That's an important distinction because skills and purpose play very different roles inside an organization. You can teach someone software, processes, systems, terminology, and even many technical skills, but it is much harder to manufacture genuine concern for people who don't naturally matter to them.

This is why I keep coming back to one incredibly unprofessional-sounding but very accurate standard: you can't train giving a damn.

Someone can perform care. They can memorize the approved language, follow the customer-service script, use someone's name three times during a conversation, send the appropriate follow-up email, and complete every required step. From an operational perspective, they may perform the role perfectly while the person on the receiving end still walks away feeling like a transaction.

That's because human beings aren't simply listening to words. We're continually gathering information from tone, behavior, timing, facial expressions, energy, consistency, responsiveness, environment, and hundreds of other cues that help us determine what another person actually means. Someone can say all the right things and still communicate that they'd rather be anywhere else.

That's where hiring solely for competency becomes dangerous.

The person may be extremely talented, but if they have no meaningful connection to the mission, every relational standard eventually requires effort. Caring becomes another task they're expected to perform instead of something naturally informing the way they perform the task.

This doesn't mean everyone in your organization needs to have the same personal story as the founder. They don't need identical backgrounds, personalities, motivations, or reasons for caring about the mission. In fact, I think organizations become stronger when people bring very different perspectives and ways of relating to the work.

What matters is that somewhere underneath those differences there is a genuine connection.

That's where SoulFire® becomes incredibly useful beyond the founder. Understanding someone's deeper purpose allows us to ask whether there is a meaningful intersection between what matters to that person and what the organization exists to accomplish.

That intersection doesn't have to be obvious.

Someone may care deeply about dignity, while your organization serves veterans. Someone may be driven by helping people feel capable, while your organization provides financial education. Someone may care about creating stronger families, while they're working inside an organization serving men. The employee doesn't have to share the founder's exact why; their own why simply needs a meaningful place to connect with the organization's purpose.

When that connection exists, work stops being purely transactional.

The employee begins seeing why their particular contribution matters. They understand that the email they're answering isn't just another email, the customer isn't simply another account, and the task they're completing is connected to a larger transformation they genuinely care about helping create.

Then we can begin thinking about personality.

This is where NERI® matters because caring about the same outcome doesn't mean people will—or should—create relationships in the same way. One of the mistakes leaders make when they finally find someone who deeply cares about the mission is attempting to turn that person into a smaller version of themselves.

That's unnecessary.

If the founder is charismatic and highly extroverted, the employee doesn't need to become charismatic and highly extroverted. If the founder builds relationships through humor, the employee doesn't need to become funny. If the founder is exceptionally nurturing, another leader doesn't have to imitate that nurturing style to create trust.

The question is whether their natural personality can create the relationship outcome the organization requires.

An introverted employee may make someone feel extraordinarily seen because they're a phenomenal listener. A highly analytical employee may create trust because they anticipate details other people overlook. Someone with a direct personality may make customers feel safe because they communicate clearly and never leave people guessing.

Different personality.

Same relational standard.

That's how I believe organizations should think about scaling culture. You aren't trying to preserve the founder's personality throughout the organization. You're preserving the founder's heart for the mission while allowing other people to express that heart through their own personalities.

This approach also creates a much healthier relationship between standards and autonomy. Employees understand what must remain true about the experience without being micromanaged into reproducing the founder's exact behaviors.

Leadership can say, "People who interact with us should feel seen, respected, and genuinely cared for." The organization can define what those standards mean, establish boundaries around them, and provide examples of what violates them, while still allowing different people to create those outcomes differently.

That's where autonomy becomes powerful rather than dangerous.

If someone understands the purpose, cares about the transformation, understands their own relational tendencies, and knows the organization's standards, you don't have to script every human interaction. You can trust them to use judgment.

And trust matters enormously as an organization grows.

Eventually, the founder cannot approve every conversation. They cannot monitor every customer interaction, read every email, attend every event, or personally correct every moment that doesn't feel right. Trying to do so simply recreates founder dependency at a larger scale.

The organization has to develop people capable of carrying the relationship without the founder being present. That's when hiring changes from asking, "Who has done this job before?" to asking something much more important:

"Who cares enough about what we're trying to accomplish that we can teach them how to help us accomplish it?"

Because the résumé may tell you whether someone can execute the transaction. Their purpose tells you whether they're capable of caring about the transformation.

The Founder's Job Is to Protect the Heart, Not Hold Every Relationship

Eventually, every successful founder reaches a point where being personally involved in every relationship is no longer evidence of commitment. It becomes a limitation on the organization. There are simply too many customers, employees, partners, donors, volunteers, vendors, and opportunities for one person to remain the relational center of everything.

That doesn't mean the founder becomes less important as the organization grows. Their role changes. Instead of personally carrying every relationship, they become responsible for protecting the heart that determines how those relationships should feel.

I believe founders generally have two incredibly valuable roles available to them as an organization matures, and those roles can certainly overlap. The first is becoming the visible face of the organization—the person who communicates its ideas, represents its beliefs, creates conversations, and keeps the organization human in the marketplace.

We see this model with founders such as Gary Vaynerchuk or Grant Cardone, where the founder's voice remains deeply connected to the organization even though they're obviously not executing every customer interaction. The founder becomes a recognizable expression of the organization's ideas while a much larger team carries the actual work.

The second role is equally important: visionary. The founder should continue asking where the organization is going next, what problem needs to be solved next, what the audience needs now, and what the next seemingly impossible goal should be.

The founder's responsibility shifts from personally making every relationship happen to continually protecting why the relationships matter. They become the keeper of the purpose while developing leaders capable of carrying that purpose into thousands of interactions they will never personally witness.

That's an entirely different form of leadership.

It requires founders to stop measuring their importance by how indispensable they are to daily operations. If the organization can only create extraordinary relationships when the founder is personally involved, then the organization hasn't actually learned how to create extraordinary relationships.

The founder has.

Those aren't the same thing.

A truly relationship-centered organization should eventually become capable of creating meaningful experiences whether the founder is in the room or not. Customers should still feel cared for, employees should still understand what matters, partners should still recognize the organization's character, and difficult decisions should still be made through the lens of the organization's purpose.

That's where Neuro Human Branding® becomes much bigger than an external brand exercise. The work has to move through the organization so that the relationship being promised externally is also understood and lived internally.

SoulFire® helps us understand why people care. NERI® helps us understand how different personalities naturally create and experience relationships. Intelligent Influence® helps us become intentional about the environments and circumstances in which those relationships occur, while Three Impressions® reminds us that every person representing the organization contributes to what someone ultimately believes about it.

Together, those ideas create something far more sustainable than a customer-service script.

They create relational alignment.

When that alignment exists, the founder no longer needs to teach everyone exactly what to say. The team understands what they're trying to create, why it matters, and what standards cannot be compromised. They have enough autonomy to use their own personalities, judgment, and strengths to create the appropriate outcome.

That's how relationships actually scale.

Not through sameness.

Through shared purpose.

The organization can have ten employees or ten thousand and still retain the heart that made people care about it in the beginning. The expressions will naturally become more diverse because more human beings are involved, but the underlying intention remains recognizable.

That's what founders should ultimately be protecting because growth shouldn't require choosing between becoming larger and remaining human. The goal is to build an organization where growth allows more people to experience the relationship, not a diluted version of it.

Practical Next Steps

• Identify the transformation your organization exists to create beyond the transaction required to deliver it.

• Define the relational standards that should remain true regardless of which employee, leader, volunteer, or representative someone encounters.

• Review your hiring criteria and ask how much weight you're giving to credentials and competency versus genuine connection to the mission.

• Explore how each team member's SoulFire® connects to the organization's purpose instead of assuming everyone should care for exactly the same reason.

• Use NERI® to understand how different personalities can authentically create the same desired relational outcome without imitating the founder.

• Audit what your organization rewards. Determine whether your metrics and recognition systems reinforce transformation or quietly teach people to prioritize transactions.

• Identify areas where scripts, policies, and SOPs are supporting good judgment—and areas where they may be replacing it.

• Finally, ask: If the founder disappeared from every customer interaction tomorrow, would people still feel the heart of the organization?

Thinking Behind This Studio Note

The ideas in this article are practical applications of Human Choice Theory™ and an evolving body of research exploring how human impressions become human relationships and how those relationships shape organizational outcomes.

This Studio Note applies SoulFire®, NERI®, Neuro Emotional Relationship Intelligence, Intelligent Influence®, Three Impressions®, and NeuroHuman Branding® to one of the central challenges of organizational growth: how to expand the number of people representing an organization without losing the care that made its relationships meaningful in the first place.

Organizations don't preserve relationships by cloning the founder. They preserve them by understanding what exists underneath the founder's behavior; the purpose, concern, standards, and genuine desire to create a particular transformation; and finding people whose own purpose can authentically connect with that work.

Skills matter. Systems matter. Processes matter. Metrics matter. But none of them can replace genuine care.

You can train a lot of skills. You can't train giving a damn.

The organizations that understand that distinction don't simply scale transactions. They create more people capable of carrying the transformation and that's how growth multiplies relationships instead of destroying them.

Explore the research at AliCraig.com.