top of page

Congrats on Your internal Silos. your Customer Still Has a Problem.

Writer: Jessica Humphreys
Jessica Humphreys
Oct 20
11 min read

Customer-centric marketing, sales and business development focused on solving customer problems instead of internal company silos.

The Real Argument: Your Internal Silos Are Not Your Customer's Problem.


The MISFIT Manifesto | CannaLife Press

October 20, 2026


One Customer. One Problem. One Company. Six Brochures.


I've spent a substantial portion of my career standing at conference booths, talking with prospective customers who have come looking for solutions to specific scientific, technical, regulatory, operational, or commercial challenges.


And I've spent an equally ridiculous amount of time trying to decide which combination of brochures, sell sheets, and capabilities materials I need to hand them.


One for toxicology. Another for laboratory services or analytical chemistry. A third for quality assurance or regulatory support. Perhaps another for genetics, cultivation, processing, or specialized technologies, depending on the industry.


Now I'm standing there assembling a paper representation of a company that should already know how to explain itself.


The customer has one problem. The company may have everything necessary to solve it. But first, somebody has to piece together the organizational puzzle.


One customer. One problem. One company. Six brochures.

And somehow, we call this customer-centric marketing.


Here's a thought: Unless this customer is genuinely working across multiple distinct verticals, why am I handing them six pieces of collateral when one thoughtfully developed document should communicate the relevant offering?


The customer didn't come to the booth to study our organizational structure. They came to find out whether we could help.


Yet we've managed to turn our internal architecture into their homework.

Congratulations on your silos. The customer still has a problem.


Silos Aren't Always Accidental. Sometimes They're Built Into the Business.

Before somebody starts preaching about breaking down silos, let's acknowledge something important: not every silo is the result of poor management, territorial behavior, or a dysfunctional organizational culture. Some are entirely intentional.


Across regulated and contract-driven industries, including cannabis, pharmaceuticals, biotechnology, healthcare, medical devices, agriculture, food production, environmental services, manufacturing, energy, defense, and government contracting, operational separation can be necessary.


Organizations may need to maintain:

  • Distinct cost centers: Separate accounting structures for tracking expenditures, resources, and financial performance.

  • Contract-specific obligations: Defined scopes of work, deliverables, funding restrictions, and reporting requirements.

  • Confidentiality boundaries: Protections for proprietary information, personal data, sensitive research, customer information, or classified materials.

  • Regulatory independence: Controls supporting appropriate oversight, decision-making authority, compliance, and quality assurance.

  • Separate operational teams: Specialized groups responsible for research, genetics, cultivation, processing, laboratory testing, toxicology, analytical chemistry, manufacturing, distribution, quality, regulatory affairs, retail operations, or customer-facing services.


These structures aren't necessarily signs of organizational failure. They may be essential to financial integrity, contractual performance, product safety, quality, and regulatory compliance.


And no, you cannot simply ignore contractual restrictions, combine restricted funding streams, compromise quality oversight, or share protected information because collaboration would be more convenient.


But here's where things get interesting.


Silos aren't always evidence of poor organizational design. Sometimes they're evidence of deliberate organizational design that nobody bothered to integrate into a functioning whole.


An organization can have legitimate reasons to separate its operations without having legitimate reasons to fragment its entire customer-facing identity.


Operational separation does not automatically require marketing fragmentation.


Yet organizations repeatedly behave as though it does.


When the Accounting Structure Becomes the Marketing Strategy

Somewhere along the way, companies begin treating their internal business structures as though they represent the natural way customers understand the marketplace.


The laboratory services group has its budget, leadership, sales objectives, and marketing materials. Toxicology operates under another cost center. Analytical chemistry may have its own targets. Genetics, cultivation, processing, quality assurance, regulatory affairs, distribution, and retail operations may each have separate management structures, depending on the business.


In other organizations, the divisions might involve research and development, manufacturing, clinical services, engineering, environmental testing, or government contract programs.


The specific departments change. The underlying problem doesn't.


Every division wants visibility. Every cost center wants attribution. Every business unit wants its own brochure, webpage, presentation, campaign, and little corner of the corporate universe.


Never mind that a customer may need capabilities from several of these groups to solve one problem.


The company has organized itself around internal accountability and then mistaken this organization for a customer journey.


The consequences are predictable:

  • Marketing materials emphasize departments rather than customer problems.

  • Capabilities are described independently even when they contribute to the same solution.

  • Customers must identify which business unit provides which service.

  • Sales and marketing professionals become translators between internal structures and external needs.

  • Cross-functional opportunities are missed because nobody presents the complete picture.

  • Multiple departments compete for visibility while customers struggle to understand the offering.


The organization may be extraordinarily good at tracking where money is spent. It may be considerably less effective at communicating how its capabilities work together.


And that's an expensive contradiction.


The Psychology of Organizational Egocentrism

Here's where the problem becomes more interesting than an unfortunate collection of brochures.


Organizational egocentrism is what happens when a company becomes so immersed in its own internal reality that it begins treating this reality as though everyone else shares it.


It's not necessarily arrogance in the conventional sense. It's a collective failure of perspective-taking.

Inside the organization, everyone knows the divisions, reporting relationships, acronyms, cost centers, and internal distinctions. These structures become familiar, meaningful, and eventually unquestioned.


Outside the organization, the customer knows almost none of it.

And why should they?


Several psychological and organizational mechanisms can reinforce this disconnect:

  • The curse of knowledge: Once people become deeply familiar with information, they may underestimate how unfamiliar it is to others.

  • In-group identification: Employees develop loyalty to their departments, specialties, and business units, sometimes at the expense of the broader organizational mission.

  • Territorial behavior: Leaders and teams may protect budgets, authority, resources, and visibility.

  • Goal displacement: Internal targets and processes gradually become more important than the outcomes they were originally intended to support.

  • Diffusion of responsibility: When a customer need crosses several departments, accountability can become fragmented.

  • Institutional inertia: Organizations continue doing things a particular way because this is how they've always done them.


None of these mechanisms requires malicious intent.

In fact, this is part of the problem.


People can be working diligently, meeting expectations, protecting legitimate interests, and fulfilling their assigned responsibilities while collectively creating a remarkably poor customer experience.


Everyone can be doing their job correctly while the company gets the customer's experience completely wrong.


And when this happens repeatedly, year after year, across campaigns, conferences, websites, and sales processes, it stops being an isolated marketing problem.


It becomes an organizational behavior problem.


Congratulations. You've Made Your Customer Learn Your Org Chart.

Imagine walking into a restaurant and being handed six menus. One belongs to the vegetable department. Another to protein operations. A third to sauces and seasonings. The bread division operates independently, and beverages are managed under a separate cost center.


You're hungry. You'd like dinner.


Unfortunately, dinner is a cross-functional deliverable. You'll need to identify the relevant departments, understand their individual capabilities, and coordinate your selections accordingly.


The restaurant is very proud of its operational structure.

You are increasingly interested in eating somewhere else.


Absurd? Of course. But it's remarkably similar to what happens when companies organize their customer-facing communication around internal divisions.


A pharmaceutical developer may need analytical testing, toxicology, quality assurance, and regulatory support to advance one product.


A cannabis business may need genetics, cultivation, processing, laboratory testing, packaging, distribution, and retail expertise to bring a compliant product to market.


A food or beverage manufacturer may need formulation, microbiological testing, quality systems, packaging validation, and regulatory support.


An environmental client may need sampling, analytical chemistry, toxicological interpretation, and compliance reporting.


These customers are navigating different industries and regulatory frameworks, but they share a fundamental expectation: the organization should be able to explain how its capabilities address their needs.


The customer doesn't necessarily want to purchase each capability as an unrelated service. They want to understand the solution, the responsibilities involved, and how the work will be coordinated.


Your customer should not need to understand how your company is organized to understand how your company can help.


And the burden of integration should not fall on the customer (or the sales person) simply because the organization hasn't bothered to do it.


The Handoff Olympics: Everybody Wins Except the Customer

Marketing fragmentation is often the first visible symptom of a much larger problem.

Once the customer expresses interest, the internal relay race begins.


Sales identifies the opportunity. A technical group evaluates part of the scope. Laboratory services assess testing requirements. Quality assurance reviews applicable controls. Regulatory affairs considers compliance obligations. Operations determines capacity. Contracts examines terms. Finance evaluates cost allocation.


In a vertically integrated cannabis business, the handoffs might instead involve cultivation, genetics, processing, quality assurance, laboratory testing, inventory management, distribution, and retail personnel, including budtenders who ultimately interact with consumers.


All of these activities may be legitimate and necessary. The dysfunction begins when nobody is responsible for coordinating them into one coherent customer experience.


Common symptoms include:

  • Customers repeatedly explaining the same project or need to different departments.

  • Inconsistent descriptions of capabilities, timelines, and deliverables.

  • Delayed proposals or decisions because internal ownership is unclear.

  • Conflicting recommendations from teams operating independently.

  • Opportunities divided according to internal reporting structures rather than customer needs.

  • Customers becoming the unofficial project managers of the organizations they've hired or purchased from.


And when something goes wrong?

"That's handled by another department."

What a wonderfully efficient way to explain that the company's internal structure matters more than the customer's problem.


The customer is dealing with an organization, not an organizational chart.

Even when contractual arrangements require separate scopes, agreements, or providers, the company should clearly communicate these distinctions and coordinate appropriately wherever authorized.


A legitimate handoff transfers responsibility. A dysfunctional handoff transfers inconvenience.


The KPI Hall of Mirrors

Perhaps the most fascinating consequence of siloed organizations is their ability to produce excellent internal performance reports alongside disappointing customer outcomes.


Every department has metrics. Marketing measures leads and engagement. Sales tracks pipeline and conversions. Operations measures utilization and throughput. Finance monitors margins and budgets. Technical teams track deliverables, quality, and timelines.


In regulated production environments, additional metrics may include cultivation yields, laboratory turnaround times, manufacturing efficiency, quality deviations, inventory accuracy, compliance performance, and retail sales.


These measurements can be valuable. But what happens when they're optimized independently?


Consider a hypothetical project:

  • Marketing: Campaign generated qualified leads. Target achieved.

  • Sales: Opportunity advanced through the pipeline. Target achieved.

  • Laboratory or technical team: Assigned work completed successfully. Target achieved.

  • Quality assurance: Required reviews and approvals completed. Target achieved.

  • Finance: Department remained within budget. Target achieved.

  • Customer: Project was delayed, communication was fragmented, and the experience was miserable.


Congratulations. Everybody hit their numbers. Except the person paying the bill.

The problem isn't measurement. It's measuring pieces without adequately evaluating the whole.


An organization can optimize departmental performance while allowing friction to accumulate between departments. And these gaps are exactly where customers experience delays, confusion, duplication, and frustration.


If every department is winning but the customer is losing, you're measuring the wrong definition of success.


Marketing Is Supposed to Translate, Not Reproduce, Internal Complexity

This is the part I find especially frustrating because it is often entirely avoidable. Marketing should help customers understand how an organization's capabilities address their needs. Instead, marketing frequently inherits the company's internal structure and reproduces it across every customer-facing channel.


The website navigation mirrors the departments. The brochures mirror the business units. The campaigns mirror the cost centers. The sales presentations mirror the reporting relationships.


And nobody seems particularly concerned that the customer has no reason to think this way.


Marketing becomes a mirror reflecting the organization back at itself instead of a window showing customers how their problems can be solved.


A customer-centric approach would start somewhere else.


Before developing another brochure, landing page, or campaign, ask:

  • Who is the customer, and what problem are they trying to solve?

  • Which capabilities are relevant to this problem?

  • How do these capabilities connect across the organization?

  • What does the customer actually need to understand to make a decision?

  • Which internal distinctions are genuinely relevant to the customer?

  • Can the offering be explained clearly in one coherent piece of collateral?

  • If multiple documents are necessary, is this because the customer's needs are genuinely diverse or because our organization is fragmented?


Sometimes a specialized technical document is exactly what's needed.

Sometimes a customer working across several verticals legitimately requires multiple materials.

But this decision should be driven by the customer's information needs, not by the number of departments wanting their own brochure.


The number of internal cost centers should not determine the number of documents required to explain one customer solution.


Customer-Centricity Is Not a Mission Statement

Nearly every organization claims to be customer-centric. It's become one of these wonderfully convenient phrases that can appear in annual reports, strategic plans, executive presentations, and corporate websites without requiring anyone to demonstrate what it actually means.


But customer-centricity is not a declaration.

It's an operating philosophy.

And this philosophy becomes visible in the decisions organizations make about structure, communication, accountability, and the allocation of resources.


A genuinely customer-centric organization makes deliberate efforts to:

  • Organize communication around customer needs: Present capabilities in the context of problems, applications, and outcomes.

  • Integrate customer-facing information: Make relevant offerings understandable without requiring customers to decode internal divisions.

  • Preserve necessary boundaries: Respect contractual, financial, confidentiality, quality, and regulatory requirements without unnecessarily transferring their complexity to customers.

  • Establish cross-functional ownership: Identify who is accountable for coordinating solutions involving multiple teams.

  • Align incentives with shared outcomes: Evaluate customer experience and overall project success alongside departmental performance.

  • Equip customer-facing employees: Provide coherent materials, clear escalation paths, and the authority to coordinate appropriately.

  • Listen to actual customer feedback: Examine where customers encounter confusion, delays, duplication, or unnecessary effort.


None of this requires dismantling legitimate organizational structures.

It requires recognizing that internal efficiency and external effectiveness are not automatically the same thing.


You can maintain operational silos without forcing customers to navigate marketing silos.


Leadership Built the Maze. Marketing Keeps Printing the Maps.

It's tempting to blame the marketing department for fragmented messaging.

Sometimes this criticism is deserved.

But marketing (and sales) don't operate in a vacuum.


If every business unit controls its own budget, demands its own campaigns, protects its own branding, and measures success through its own departmental performance, marketing may have limited authority to present a unified offering.


The marketing team becomes responsible for communicating the organization without being empowered to organize the communication around the customer.


And so the brochures multiply.

The websites become increasingly complicated.

The campaigns compete for attention.

The customer journey starts looking suspiciously like an internal reporting structure.


Meanwhile, leadership continues discussing customer-centricity.

At some point, someone needs to recognize the contradiction.


If your organizational design repeatedly prevents your company from communicating its value clearly, this is a leadership problem, not merely a marketing problem.


Leaders determine incentives, decision-making authority, resource allocation, and the degree to which departments are expected to cooperate. Marketing can help translate complexity. It cannot single-handedly overcome a corporate culture that rewards fragmentation.


And adding another cross-functional committee to discuss the problem isn't necessarily the answer.

Sometimes the solution is considerably less glamorous.


Give someone responsibility for the whole customer experience. Give them the authority to coordinate the necessary people and resources. Measure whether the customer's problem actually gets solved.


And stop making every department's desire for individual visibility more important than the customer's ability to understand the company.


One Customer. One Problem. One Coherent Solution.

The irony is that many organizations struggling with these issues possess extraordinary technical and operational expertise. They employ talented scientists, engineers, researchers, growers, geneticists, analytical chemists, toxicologists, quality professionals, regulatory specialists, manufacturing personnel, retail teams, and commercial professionals.


They have sophisticated capabilities, specialized facilities, and decades of accumulated knowledge.

They may be perfectly equipped to solve complicated customer problems.

Yet somehow, communicating this value becomes an exercise in internal archaeology.


The customer has to excavate the capabilities, identify the relevant departments, decipher the terminology, and figure out how everything fits together. And we wonder why customers get confused.


Perhaps the problem isn't that the customer doesn't understand the company.

Perhaps the company has become so accustomed to understanding itself that it has forgotten to consider anyone else's perspective.


This is the egocentrism at the center of the entire discussion.

Not necessarily individual selfishness. Not necessarily intentional arrogance.


An institutional habit of prioritizing the organization's internal reality over the customer's external experience.


And when this habit becomes embedded in budgets, incentives, processes, websites, and marketing materials, it can persist for years without anyone seriously questioning it.


The solution isn't to pretend legitimate operational boundaries don't exist.

It's to stop treating these boundaries as though they define the customer's world.

Your contracts may require separation. Your accounting systems may require distinct cost centers. Your regulatory obligations may require confidentiality and independent oversight.


Fine.

Honor these requirements.

But don't confuse them with a marketing strategy.


Don't make your customer assemble your capabilities into a solution.

Don't call yourself customer-centric while asking people to navigate six brochures, four departments, and three layers of internal bureaucracy to understand one offering.

And don't mistake a beautifully organized internal structure for a coherent external experience.


Your internal silos are not your customer's problem.


Six brochures to explain one solution isn't a marketing strategy.

It's organizational dysfunction with a marketing budget.


I don't expect you'll agree with everything you read here.

But I do expect you'll at least think about it.


That's enough.


If this article made you think...


Share it.

Quote it.

Debate it.

Teach it.

Email it.

Text it to someone who needs to read it.

If you found value here, help someone else find it too.


Please keep my name attached and link back to the original article whenever you share it.


Because good ideas don't belong in echo chambers.

They belong in conversations.


Truth Is The Drug. All Warnings Ignored.


Founder | CannaLife® | CannaLife MISFITS™ | MC Jazzi O™ | CannaLife Press™ | CannaRx™


Comments


bottom of page