NexTier Innovations

01/07/2026

The Hard Work Fallacy: Why Your Customers Do Not Care About Your "Effort" 😓

We are raised on a simple promise: "Hard work pays off."
I have learned that in the world of B2B relationships, this is often a lie.

We suffer from a compounded Egocentric Bias, reinforced by the “Effort Justification Effect”. We instinctively believe that if we worked hard on something, it must be valuable. We assume the customer will appreciate the sweat, the late nights, and the sheer volume of our activity.

The Truth: The customer does not care how hard you worked. They only care about what they got.

I see this dynamic constantly in CS teams.
o The CSM: Spends 15 hours manually formatting a QBR deck. They pull data from three different systems, color-code the charts, and work until midnight.
o The Feeling: The CSM feels proud. They feel like a hero. They think, "The client is going to love this because I poured my soul into it."
o The Reality: The client looks at the deck for 30 seconds, skips the vanity metrics, and asks, "So, did we save money or not?"

This is the Egocentric Gap.
o You (The Vendor) are anchored in your Effort. You view the deliverable through the lens of the pain it took to create it.
o The Client is anchored in their Outcome. They view the deliverable through the lens of utility.

When a CSM says, "I sent 50 emails and held 10 strategy sessions," they are reporting their labor, not value. The customer hears, "It took you 60 interactions to solve a problem that should have been automated."

To the customer, your "hard work" often looks like "inefficiency."

This bias is compounded by the Curse of Knowledge. Because we know how complex our product is behind the scenes, we mistake internal difficulty for external value.
o Vendor Logic: "Our backend is a mess, so me manually fixing this data for you is a huge favor!"
o Customer Logic: "Why is your product broken? I shouldn't have to thank you for fixing what I paid for."

This is why Customer Value Engineering (CVE) is the antidote to the Hero Complex.

A Value Engineer treats Effort as a cost, not a virtue, and separates it from Value.
o We do not measure "Hours Spent." We measure "Time to Value."
o We do not measure "Number of QBR Slides." We measure "Decisions Made."

If I can save a customer $1M in a 5-minute phone call, that is high value. If I spend 40 hours building a report that saves them $0, that is zero value.

Stop trying to impress your customers with how busy you are. Stop showing them the sweat.

Admit the bias: You are overvaluing your own deliverables because you made them.

Shift your focus from Input (Effort) to Output (Impact). At renewal time, your customer does not fund Effort. They fund Outcomes.

01/06/2026

The Dark Side of Customer Success: Are We Advisors or Manipulators? 🕵️‍♂️

We love to call ourselves "Trusted Advisors." It is the golden label of Customer Success.

But throughout my career, I have seen a darker dynamic at play. When product gaps widen and retention targets become desperate, some CS organizations stop being advisors and start being manipulators.

They stop relying on product value and start relying on psychological tricks.

There is a psychological concept called Paradoxical Persuasion.

At its core, it is the technique of aligning with resistance to disarm it. Instead of arguing with someone, you agree with their negative outlook so completely that they are forced to defend the other side to restore balance.

In the hands of an ethical leader, it can be a tool for radical empathy. But in the hands of an insecure CS organization trying to hide product failures and is under unreasonable retention targets, it is a weapon used to gaslight customers.

If you have worked in mission-critical enterprise SaaS, you have seen these toxic applications of Paradoxical Persuasion. You just did not have a name for them.

1. The "Complexity Bluff" (Hiding Product Gaps) The customer demands a feature that was demoed, but it barely works in a real-world environment. The CS leader cannot admit the product failure. So, he attacks the customer’s ego.
o The Toxic Paradox: "You know, you’re right to want that advanced feature. But honestly, most clients find it overwhelms their staff. It requires a level of operational maturity that, no offense, I don't think your team is ready for yet. We should stick to the basics so you don't fail."
o The Result: The customer backs down to "prove" they are mature, accepting a subpar product while the vendor dodges accountability.

2. The "Hotel California" (Trapping Through Fear) A frustrated customer threatens to churn to a competitor. The CS leader knows he cannot win on merit. So, he agrees with the churn but wraps it in terror.
o The Toxic Paradox: "I completely understand why you want to leave. Honestly, moving to ACME might be easier for a smaller scope. Just make sure your CIO is prepared for the 12-month data migration nightmare, $500k in consulting fees, and the compliance risks of ripping our platform out mid-audit... but if you’re willing to accept that risk, we’ll process the paperwork."
o The Result: The customer is paralyzed by the amplified fear of change. They stay, not because they see value, but because they are being held hostage by loss aversion.

Why does this happen?

In economically compromised environments, when the "Green Dashboard" is a lie and the product road map is a mirage, psychology becomes a survival mechanism for the CS team. If you cannot deliver value, you deliver doubt.

This is not Customer Success. It is sophisticated manipulation designed to buy time for the vendor at the expense of the client.

Again, this is why I champion Customer Value Engineering (CVE).

CVE rejects psychological tricks in favor of mathematical truth. A true Trusted Advisor does not need to manipulate a customer's ego or fears because the TA is anchored in verifiable data.

An ethical leader uses the paradox to protect the client: "Don't buy that new module yet. Your team isn't ready to realize the value, and I won't let you waste your budget."

Look in the mirror today. When the product fails to deliver, do you lean on data to find a solution, or do you lean on psychology to hide the problem?

The industry needs fewer manipulators and more Engineers of Value. Which one are you?

01/05/2026

The Invisible Gorilla in Your QBR: Why Green Dashboards Hide Churn 📊

In 1999, psychologists Simons and Chabris ran the famous "Invisible Gorilla" experiment. They asked people to watch a video of basketball players and count the passes. Half the viewers were so focused on counting passes that they completely missed a person in a gorilla suit walking through the middle of the screen.

This is called Inattentional Blindness. When we hyper-focus on a specific task, our brains filter out the unexpected reality.

In my 30+ years in corporate America, I realized the modern QBR is just that basketball video. We are so busy counting "passes" (usage metrics, tickets, logins) that we miss the Gorilla staring us in the face.

I saw this play out vividly during my time at a major enterprise software firm. We had a large insurance customer: 6-year tenure, massive contract, and "Green" health scores across the board.

The account team was convinced the product was sticky. We had power users praising the solution, and usage was high. But this was a classic case of Misdirected Attention.

The usage was high not because they loved us, but because they had no other option. The "Green" dashboard distracted the team from reality: the customer was migrating to the Cloud, and our product had distinct gaps in calculating cloud costs to help ensure moving to the Cloud was prudent. Behind the scenes, their team was doing massive amounts of manual processing to make up for our feature deficits.

The crash came when a new CIO arrived. She came from a Microsoft shop and had zero loyalty to our legacy.

During her first QBR, the account team presented the standard "Vanity Metrics." I watched the CIO closely. She was nodding frequently. To the account team, that nod meant agreement.

But I was not looking at the slide deck; I was looking at her. That nod was rhythmic, detached, and empty. It was the nod of someone who had already made up her mind. That rhythmic and detached nod was the "Gorilla."

I pulled the account team and CS leader aside immediately: "We are going to lose this account. She is not buying the metrics being presented. They have no value to her."
Their response? "What do you mean? The customer is Green! Look at the usage!"

The customer did not renew.

Our account and CS team suffered from Inattentional Blindness. They were so focused on the "Happy Power User" data (the passes) that they were blind to the "Disengaged Buyer" (the Gorilla). They ignored the manual workarounds because the dashboard did not track "customer frustration," it only tracked "clicks."

This is why I champion Customer Value Engineering (CVE).

We must stop using Customer Success as a form of Misdirected Attention, using product road maps and white-glove service to distract from product gaps. If your dashboard says Green, but your Buyer is nodding in silence, you are not successful. You are just blind.

Open your eyes and really pay attention. Real attention requires looking past the dashboard. Adopt the CVE framework to strip away the noise of "activity" and focus on the signal of "value."

CVE will help to ensure you always see the Gorilla.

12/31/2025

The Business Analyst Revolution: How to Master Discernment and Data to Become a Strategic Analyst
The traditional Business Analyst (BA) is at an inflection point. The classic tasks of requirements gathering and documentation are rapidly being augmented or even automated by AI and intelligent tools. This is NOT a threat; it IS the greatest career opportunity to transform the role from a project support function into a strategic value driver.
The future is about blending data science insights with human discernment and acumen.
________________________________________

Augment, Do NOT Compete: Your New AI Toolkit
Your first step to becoming a strategic analyst is to embrace technology that frees your time from repetitive work.
o Automation of the Mundane: Leverage AI and RPA tools to handle the heavy lifting: data cleaning, routine report generation, and initial pattern identification. This creates bandwidth for strategic work and thinking differently.
o Prompt Engineering for Research: Master crafting specific, goal-oriented prompts for Generative AI. Use these tools to instantly synthesize competitor reports, summarize complex industry regulations, and draft initial problem statements. This dramatically accelerates the research and synthesis phase.
o The AI Translator Role: You do not need to code Machine Learning (ML) models, but you must be the interpreter. Understand the data inputs, limitations, accuracy, and potential biases of ML models so you can effectively translate the technical output into business impact for executive decision-makers. Framing the data in the relevant context leads to deeper insights and superlative outcomes.
________________________________________

The Core Strategic Shift: From "What" to "Why"
The most significant transformation is in your mindset. You must pivot from gathering what the business says it needs to deeply analyzing why those needs exist and how to achieve transformative outcomes.
o Master Data Storytelling: Raw data is inert. Your job is to transform predictive analytics and complex model outputs into clear, compelling business narratives. Every finding must be connected to the "so what?"; the measurable change in revenue, cost, risk, or competitive advantage.
o Lead with Discernment: This is the uniquely human element. AI provides data; you provide wisdom, context, and judgment turning the data into actionable information. Use your organizational knowledge and emotional intelligence (EQ) to interpret data against real-world constraints: market dynamics, culture, economic trends, and political uncertainty. Your discernment validates or challenges the data's raw conclusion.
o Architect Strategic Value: Push past feature-level requirements. Use data to define new strategic objectives, validate new business models, and recommend transformative technology road maps. You move from documenting a new feature to driving a new source of competitive advantage and differentiation.
The strategic analyst is no longer just a conduit between the business and IT; you are the Chief Interrogator of Value, fusing data with human judgment to chart the future.

12/29/2025

Series Installment #3: The Hidden Psychology Killing Your Renewals 🧠

Last week, I talked about Metric Overload and how to use Dimensionality Reduction to find the few data points that matter. But even with perfect data, renewals often fail because of a deeply ingrained psychological barrier: Zero-Sum Bias (ZSB).

My series, "Stop Scaling Platforms. Start Scaling Value," argues that when you scale vendor footprint over customer ROI, you kill loyalty. The reason this misalignment is so deadly is ZSB.

The Zero-Sum Trap: Why Your Customer Sees Loss, Not Gain
Zero-Sum Bias is a cognitive distortion — a primal belief that in any exchange, one party's gain must equal the other's loss. It is the fixed-pie mentality.

In the SaaS world, your own business model inadvertently fuels this bias:

o The Price Increase: When you ask for a higher subscription fee, ZSB makes the customer focus on the loss of that money, not the gain of the new features. They feel you are winning at their expense.
o The SKU Proliferation: When a needed feature is available only in the next, more expensive tier, the customer perceives that you are withholding value to coerce payment, rather than creating a new, higher-value offering.

This turns every renewal conversation into an adversarial negotiation, increasing friction and breeding resentment. To create the "Super Customer," we must consciously design non-zero-sum interactions.

The Strategic Shift: Engineering Positive-Sum Outcomes
The strategic P/CS leader must dismantle ZSB by demonstrating, repeatedly and unequivocally, that the customer's gain is exponentially larger than the vendor's gain.

1. Shift from Feature Gating to Value Compounding
Stop framing an upgrade as a cost to unlock and start framing it as an accelerator to existing, proven ROI.

o Old Script (Zero-Sum): "To get reporting module V2, you need to upgrade from $500 to $800." (Customer registers: +$300 loss for me; +$300 gain for vendor.)
o New Script (Positive-Sum): "Module V2 shortens your existing compliance reporting time from 4 hours to 30 minutes, freeing up 150 hours of internal resources annually. Your ROI will increase by 40%." (Customer registers: My gain in time/efficiency is far greater than their small increase in fee.)

2. Proactive "Give-First" to Build Trust
Counter the fixed-pie mentality by releasing high-value, friction-reducing features for free or into lower tiers.

o Product Management Action: Deliberately release critical, time-saving improvements — like a major UX overhaul, faster processing speed, or a highly requested minor integration — without changing the pricing.
o P/CS Action: Cleary articulate P/CS is a positive-sum resource for customers to leverage as new features are introduced. Explicitly communicate the value proposition of all offerings and be transparent about product road maps and how customer feedback influences decisions. Regularly highlight examples of how collaboration with customers led to significant wins for both the customer and you.
o The Psychological Win: This demonstrates a clear, unreciprocated gain. It reinforces the notion that you are investing in the customer's success independent of the financial transaction, directly increasing trust and reducing ZSB.

3. Quantify the "Expansion of the Pie"
Your dashboards must stop tracking just usage and start visualizing value creation in the customer's own language.

o Reporting Redesign: Instead of showing "75% adoption of Feature X," show: "Feature X saved you $15,000 in labor costs last quarter" or "Feature Y processed 10,000 transactions, leading to $200,000 in traceable revenue."
o The Strategic Outcome: By proving the pie is not fixed, but constantly expanding because of your platform, the customer views the subscription fee not as a drain, but as a minor investment in a massive engine of self-generated wealth.

Overcoming Zero-Sum Bias is the strategic key to moving the customer relationship from a defensive tug-of-war to a trust-powered ecosystem. This is how you engineer loyalty and create champions.

12/29/2025

Stop Drowning in Metrics: The Data Science Secret to Engineered Product Success

I mentioned this in the first article of the series: "Generic segmentation is dead; dynamic intent is the future."

But how do you find that "dynamic intent" when your Product/Customer Success (P/CS) team is drowning in a dashboard with 50+ customer metrics?

The truth is, most teams are paralyzed by data complexity. The solution is NOT better reporting; it IS adopting a strategic weapon from data science: Dimensionality Reduction.

This powerful technique allows Product/Customer Success (P/CS) leaders to cut the noise, reveal the simple truth, and create predictable outcomes.

Death of the Composite Score: The Rise of Archetypes
Traditional customer segmentation often relies on averaging metrics into one-size-fits-all scores. Dimensionality Reduction (DR) — using techniques like Principal Component Analysis (PCA) — unmasks the complex, interconnected dimensions of customer value.

o The Problem: Your customer dataset has dozens of variables: support tickets, login frequency, feature usage, tenure, renewal status, NPS, etc. Analyzing all 50 dimensions at once is overwhelming, noisy, and obscures genuine insights.
o The DR Solution: PCA compresses those 50 correlated variables into 3-5 core, underlying "Archetypes" or "Factors" that explain 80% of your customer behavior.

Application: Discovering the True Customer DNA
Instead of seeing "User ID 456," you see:

o Factor 1: "The Optimization Architect": High feature adoption + low support tickets + high API usage. (The power user who needs technical documentation, not a P/CSM check-in.)
o Factor 2: "The Cost-Sensitive Seeker": Low initial purchase price + high login frequency + low spend on add-ons. (The segment most vulnerable to price-based churn.)

This shift moves P/CS from managing metrics to managing predictive behaviors.

Noise Filtering: Predicting Churn with Surgical Precision
Churn models often fail because they are built on noisy, redundant, or irrelevant features. Dimensionality Reduction acts as a sophisticated noise filter, ensuring every action taken by a P/CSM truly matters.

o From "Features" to "Drivers": Your churn model might technically track 100 features. DR feature selection methods surgically remove the noise (e.g., customer’s choice of browser), leaving only the truly impactful churn drivers (e.g., recent decline in feature X usage, login frequency below the 3-day average).

The Strategic Benefit: By focusing your intervention efforts on the 10 most critical drivers identified by DR, your predictive models become more accurate, faster to train, and —most importantly —your Product/Customer Success Managers (P/CSMs) know exactly which behaviors require proactive intervention. This is how you optimize resource allocation and stop chasing ghosts.

The New Empathy Engine: Recommendations & Scalability
Dimensionality Reduction turbocharges the Empathy Engine we discussed in the previous article, by turning abstract preference data into concise, actionable profiles.

o Concise Customer Profiles: By reducing the dimensionality of interaction data (past purchases, content viewed, features used), you create a concise "Preference Vector". This vector is a highly efficient profile that powers personalized recommendation engines for new features or support resources. Customers feel understood because the recommendations are laser-focused on their core needs.
o Scaling Team Effort (Topic Modeling): DR techniques like Latent Dirichlet Allocation (LDA) applied to text data (support tickets, call transcripts, email) can reduce thousands of unstructured notes into 3-4 core underlying pain points (e.g., "Integration Frustration," "Reporting Clarity," "Permissions Error"). This allows Product teams to build scalable solutions that address common pain points across the entire customer base, rather than solving one-off tickets.

The strategic P/CS leader of the future will not manage a dashboard full of numbers; they will manage a handful of statistically validated behavioral drivers that dictate success. By embracing Dimensionality Reduction, you stop being reactive data observers and become Proactive Value Engineers.

12/29/2025

The Empathy Engine: Designing Product Success with Lexical and Audience Intelligence

Product and Customer Success (P/CS) have a singular mission: scale customer value and maximize retention. But in a noisy, data-rich world, generic communication is failing. The solution lies in a hyper-focused, strategic application of linguistic principles, treating every touchpoint as a deliberate act of communication design.

How can this be accomplished? Leveraging Audience Design and Lexical Sophistication to engineer predictable customer success are two methods that can be applied to eliminate the noise and simplify the data to context relevancy.

1. Dynamic Audience Design for Hyper-Contextual Journeys
Audience Design means we continuously tailor our messaging based on the customer’s current intent and relationship with the product. Generic segmentation is dead and irrelevant; dynamic intent is the future.

Design the "Language of Intent": Use real-time product usage data (e.g., clicks, time-in-app, API calls) to categorize a user's current task and immediately redesign the communication environment:

o Goal: Feature Activation --> Communication is Directive (short tooltips, one button to click).
o Goal: Usage Optimization --> Communication is Technical (shortcuts, pro-tips, advanced docs).
o Goal: Strategic Reporting --> Communication is Formal (executive summaries, ROI reports).

Optimize for Emotional State: If usage data suggests struggle (e.g., repeatedly failing a step), the Audience Design dictates a shift to Supportive and Empathetic language, triggering proactive outreach (a Success Manager or in-app guidance) designed to lower anxiety.

2. Lexical Sophistication: The Diagnostic Tool for Empathy
Lexical Sophistication — the complexity of language — becomes your P/CS diagnostic and corrective lever.

The Diagnostic Signal: Analyze the lexical sophistication of inbound communications (support tickets, feature requests, forum posts).

o High Sophistication (Jargon, Complex Syntax): Signals a high-expertise user with a complex problem. They value technical accuracy and speed.
o Low Sophistication (Simple Words, Basic Terms): Signals a novice user or a major usability barrier. They need simple, reassuring, and step-by-step guidance.

The Empathetic Response Engine: Use this diagnosis to dynamically adjust your response — especially for automated systems (chatbots, auto-replies).

o Mirroring Sophistication: Respond to the high-expertise user with precise technical language to build credibility and accelerate resolution. Respond to the novice with deliberately simple, low-jargon language to lower cognitive load and build confidence.

Impact on Metrics: This approach directly reduces the Customer Effort Score (CES) and increases the perceived quality of service, turning a transactional guidance or support interaction into a strategic loyalty building moment.

The strategic P/CS professional is the Designer of Value Language, ensuring that every word, document, and interface element is precisely tailored to propel the customer toward their next success milestone.

05/21/2025

HBCUs Innovating:

Fayetteville, N.C. – Dr. Shirley Chao, Fayetteville State University biology professor, has been approved for a grant of approximately $1.1 million from NCInnovation to help bring to the market a groundbreaking non-toxic pesticide that can keep agricultural products safe from insect pests. Subject...

07/10/2024

https://shorturl.at/7YihH

North Carolina A&T State University has partnered with Merck, a major pharmaceutical company, to establish the Merck Biotechnology Learning Center, which will provide students with advanced academic opportunities in biopharmaceutical manufacturing.

07/30/2023

https://tinyurl.com/4sfszf8n

Homepage

10/17/2021

Hey Friends & Supporters!

It is that time of year again! Teens with Dreams is hosting our annual fundraising event with a highly competitive and fun game of VIRTUAL TRIVIA! The WINNER gets a 4-DAY CARIBBEAN VACATION FOR 2- air & hotel! You can RSVP and purchase tickets here: https://www.teenswithdreams.us/event-tickets

Please feel free to share the event on social media and with your colleagues, friends, and family. All proceeds from the ticket sales go towards our scholarship fund and are tax deductible.

05/19/2021

https://bit.ly/3u6T5Hk

At 5:29 am on the morning of 16 July 1945, in the state of New Mexico, a dreadful slice of history was made.