Ianthe Hernandez

When users cannot answer why a field matters, who should update it, whether anyone reads the report, or what happens if the data is wrong, they do not stop working — they work somewhere else.

• The result is a spreadsheet, an inbox, or a private notebook.
• The CRM stops being the source of truth and becomes one more place people have to type.
• Hernandez's remedy is process clarity, stakeholder input, useful enablement, reinforcement, buy-in, and leadership follow-through.
• The diagnostic question shifts from whether the CRM is configured correctly to whether people understand it, trust it, and use it consistently enough for the business to rely on it.

The post reproduces the questions users actually ask — "Why does this field matter?", "Who is supposed to update this?", "Is anyone actually looking at this report?" — and names the shadow workflows that follow, including a notebook no one else knows exists.

Read original

To demonstrate the method, they built an interactive plan builder that takes business goals, stakeholders, use cases, adoption risks, and success metrics as inputs, then organises them into an executive summary, stakeholder alignment, 30/60/90-day priorities, adoption risks, success criteria, and recommended next steps. The post says the tool is not a substitute for a customer success professional's judgement; it offers a more consistent starting point for turning customer goals into an actionable plan.

The live demo uses two fictional companies, FlowPilot CRM and PeopleFirst HR Partners, to show the framework without exposing a real client.

Read original

Goals are not carried forward, risks are not clearly documented, support issues are not connected to adoption, implementation decisions do not reach customer success, and leadership gets updates without the full picture.

• Customers may not know where the breakdown occurred, but they feel the friction.
• Hernandez's proposed fix is shared context, clear ownership, and fewer dropped details across sales-to-onboarding, implementation-to-customer-success, success-to-support, support-to-product, and technical teams back to customer-facing owners.
• More meetings are not the answer.

The post names five points where context gets lost: sales to onboarding, implementation to customer success, customer success to support, support to product, and technical teams back to customer-facing owners.

Read original

Warning signs appear earlier: product usage declines, key stakeholders stop attending meetings, the internal champion goes quiet, support issues stay unresolved, business value becomes difficult to explain, renewal approaches without clear success measures, and sentiment shifts from positive to uncertain.

• No single signal tells the whole story; the value comes from reading them together and asking what changed.
• Hernandez reduces the response to three questions — what is creating the risk, how urgent is it, and what action should happen next — and frames prevention as recognising patterns early enough to rebuild alignment, remove barriers, and reconnect the product to the customer's goals, rather than reacting faster at renewal.

The post lists seven checkable signals, from declining usage to a champion going quiet and renewal approaching without success measures.

Read original

A strong update makes four things easy to understand: progress (what has been completed and what is still moving), risk (what could affect the outcome), decision (what requires leadership input or approval), and impact (what it means for the customer or the business).

• The challenge is not collecting more information but translating complex work into what leaders need to act on — a task that takes judgement.
• Too little detail hides risk; too much buries the decision.
• The goal is to make the next decision easier, not to report everything.

Hernandez aims to create visibility without noise, measuring a good update by whether it makes the next decision easier.

Read original

A newcomer should open it first because it shows the method rather than describing it.

Hernandez built an interactive tool that takes customer inputs — business goals, stakeholders, use cases, adoption risks, success metrics — and organizes them into one structured plan with an executive summary, stakeholder alignment, 30/60/90-day priorities, adoption risks, success criteria, and recommended next steps.

• The demo runs on two fictional companies, FlowPilot CRM and PeopleFirst HR Partners.
• The post is explicit that the tool does not replace a customer success professional's judgment; it creates a more consistent starting point for turning customer goals into an actionable plan.

For brands planning a campaign

For a brief about improving handoffs and adoption, ask Hernandez to run this template against the client's own accounts. The 30/60/90-day and risk fields make a natural first deliverable.

The post traces a common sequence: a strong sales conversation, a solid kickoff, a sound implementation plan — then the handoff, after which customer goals are not carried forward, risks are not documented, support issues are not connected to adoption, and implementation decisions never reach customer success.

• They note that customers rarely know where the breakdown happened, but feel the friction.
• The proposed fix is not more meetings, which the post rejects outright, but shared context, clear ownership, and fewer dropped details across sales-to-onboarding, implementation-to-customer-success, success-to-support, support-to-product, and technical teams back to customer-facing owners.

For brands planning a campaign

Use this as the diagnostic framing for a handoff engagement: the five seams listed are ready-made interview prompts, and the "not more meetings" line sets expectations about what the consultant will and will not add.

Hernandez argues that a CRM set up "correctly" and still failing is usually a trust problem, not a configuration problem.

• The post lists what users actually ask: why does this field matter, who updates it, is anyone reading this report, what happens if the data is wrong, why does this feel like extra work.
• When those go unanswered, people rebuild their own approach in spreadsheets, inboxes, or a notebook nobody else can find, and the CRM stops being a source of truth.
• The fix Hernandez names is process clarity, stakeholder input, enablement, reinforcement, buy-in, and leadership follow-through — and the diagnostic question shifts from "is it configured correctly?" to "do people understand it, trust it, and use it consistently enough for the business to rely on it?"

For brands planning a campaign

This gives the assessment lens for the CRM-adoption half of a brief and predicts where resistance will show up: field-level confusion, unanswered "who owns this," and shadow spreadsheets rather than technical gaps.

Hernandez's premise is that churn rarely begins with the cancellation notice.

• The post lists warning signs that appear earlier: declining product usage, key stakeholders missing meetings, the internal champion going quiet, unresolved support issues, business value becoming hard to explain, renewal approaching without clear success measures, and sentiment shifting from positive to uncertain.
• No single signal tells the whole story, so the value is in reading them together and asking what changed.
• They reduce the response to three questions — what is creating the risk, how urgent is it, what action should happen next — and frame prevention as recognizing patterns early enough to rebuild alignment and reconnect the product to the customer's goals.

For brands planning a campaign

These seven signals can become a health-scoring checklist for the client's accounts, and the three questions provide a simple triage format for a churn-risk review session.

Hernandez observes that executives rarely need every detail of a project or customer account; they need clarity.

• A strong update makes four things easy to understand: progress (what is done and what is still moving), risk (what could affect the outcome), decision (what requires leadership input or approval), and impact (what it means for the customer or the business).
• The challenge is translating complex work into what leaders need to act on: too little detail hides risk, while too much buries the decision.
• The goal is to make the next decision easier, not to report everything.

For brands planning a campaign

For an engagement that touches handoffs and adoption, agree on this reporting format upfront so the client's leadership sees risk and required decisions, not status volume.

To show how that works in practice, they built an interactive plan builder that takes business goals, stakeholders, use cases, adoption risks, and success metrics as inputs and organises them into an executive summary, stakeholder alignment, 30/60/90-day priorities, adoption risks, success criteria, and recommended next steps.

A structured template that takes customer inputs through to a written plan a CS team can act on, demonstrated end to end rather than described in the abstract.

The demonstration uses two fictional companies, FlowPilot CRM and PeopleFirst HR Partners. Ask for evidence from a live client deployment and measured outcomes before treating the framework as evidence of results.

For brands planning a campaign

A practical fit for onboarding or value-realisation briefs where the deliverable is a repeatable artefact a CS team can reuse with every account, not just a written assessment. A brand can point to the plan structure as the concrete output of the engagement.

Examples: Source 1

Users who cannot answer why a field matters, who owns an update, whether anyone reads the report, or what happens when data is wrong will build their own workflow in spreadsheets, inboxes, or private notes.

• Once that happens, the CRM stops being the source of truth and becomes one more place people are obliged to type.
• They recommend process clarity, stakeholder input, useful enablement, reinforcement, buy-in, and leadership follow-through.

A diagnostic sequence of user questions that surfaces where a CRM workflow has lost credibility, followed by a reframing question: do people understand, trust, and use the system consistently enough for the business to rely on it?

For brands planning a campaign

Useful for change-management, enablement, and internal-adoption campaigns aimed at operators rather than buyers of software features. The framing suits content or workshop formats that ask why adoption stalls instead of presenting configuration as the answer.

Examples: Source 1

Goals are not carried forward, risks are not documented, support issues are not connected to adoption, implementation decisions do not reach customer success, and leadership gets updates without the full picture.

• Customers may not pinpoint the breakdown, but they feel the friction.
• The remedy is shared context, clear ownership, and fewer dropped details across sales-to-onboarding, implementation-to-CS, CS-to-support, support-to-product, and technical teams back to customer-facing owners.

A preference for tightening the information that travels between teams rather than adding meetings or status updates.

For brands planning a campaign

A strong angle for internal communications, RevOps, and CS platform campaigns that need to address the seams between departments. Brands selling handover, documentation, or customer-context tooling can use the before-and-after framing directly.

Examples: Source 1

Earlier signs include declining product usage, key stakeholders missing meetings, an internal champion going quiet, unresolved support issues, business value becoming hard to explain, renewal approaching without clear success measures, and sentiment shifting from positive to uncertain.

• No single signal tells the whole story; the value comes from reading them together and asking what changed.
• They frame a good CS response around three questions: what is creating the risk, how urgent is it, and what action should happen next.

An early-warning signal list plus a three-question triage (cause, urgency, next action) that turns scattered observations into a decision.

For brands planning a campaign

Directly relevant to retention, customer-health, and churn-prevention briefs. A brand can build a diagnostic, checklist, or scoring resource around this structure, and the triage questions make it easy for an audience to apply to their own accounts without extra training.

Examples: Source 1

The hard part is not gathering more information but translating complex work into what leaders need to act.

• Too little detail hides risk; too much buries the decision.
• The goal is to make the next decision easier, not to report everything.

A four-part update structure (progress, risk, decision, impact) that constrains what goes into a leadership summary.

For brands planning a campaign

Applies to programme delivery, account-management, and reporting briefs where the audience is senior and time-poor. The structure is simple enough to serve as a reusable template in a guide, workshop, or tool, making it easy for a brand to attach its product to a repeatable habit.

Examples: Source 1

Ravichandran's two posts make the case that every strong customer success manager must be a change agent: translating features into real-world impact, navigating internal resistance, and pushing past adoption toward measurable value realisation. Hernandez covers the same territory from the planning and handoff side, arguing that adoption and retention depend on how teams carry goals, ownership, and context between them.

Ravichandran writes motivational thought leadership for customer success professionals, ending each post with a question that invites readers to share their tactics.

• The material makes a case for mindset.
• Hernandez offers operational recipes—a plan template, a five-seam handoff list, a seven-signal churn checklist, and a four-part update format—that teams can copy and apply, with less focus on how individuals should think about the role.

Read original · Original 2

Søttrup's account of the first six weeks in a customer success role makes the point directly: many “retention problems” are implementation problems in disguise, and when customers struggle to get value early, the renewal conversation is already compromised.

• Hernandez reaches the same conclusion through handoff and onboarding material.
• Both treat implementation friction, integrations, and early quick wins as the real work.

Søttrup writes from inside a named company and role, reporting on building a customer success function from scratch across more than fifteen customers.

• They argue for tracking operational dependence—workflow breadth and depth rather than ARR—to decide where to look.
• Hernandez names no employer and keeps the posts framework-first, using a fictional demo company to show a plan structure.
• The operational detail is generic rather than drawn from a specific product's accounts; buyers seeking account-level examples should ask for them.

Read original · Original 2

Rao's incident post describes a failed software upgrade that locked customers out of a portal.

• The lesson: trust depends on how you show up when problems happen—escalating internally, keeping stakeholders informed, and delivering a root-cause analysis afterwards.
• Hernandez's handoff and churn material shares the underlying belief that customer experience depends on ownership, communication, and follow-through rather than the absence of problems.

Rao writes personal narratives: a career story about moving from development toward getting people unstuck, and a named escalation while the SE is away on vacation.

• The story carries the teaching.
• Hernandez stays abstract and structural, publishing plans, signal lists, and update formats rather than recounting incidents, and focuses on adoption, planning, and reporting rather than incident response and escalation.

Read original · Original 2

The two posts argue that a customer success manager is a change agent by necessity, that the product is only half of what a customer buys, and that influence rather than authority moves a stakeholder group.

• The second post breaks that into five points a consultant can argue from with a client's own leadership: breaking old habits, influencing without control, aiming past adoption at measurable value, supplying a human champion for a wider digital transformation, and staying future-focused.
• That framing suits a stalled engagement where internal resistance, not the workflow, is the blocker and the client's leadership must be persuaded that adoption work belongs to customer success rather than IT.
• Hernandez's five posts largely assume that argument is settled and move straight to artefacts.

Ravichandran writes at the level of argument, not deliverable.

• Neither post contains a tool, template, workshop, checklist or scoring model; readers get a case for the change-agent role and prompts for reflection.
• The one checkable external figure — that over 70% of digital transformation initiatives miss expectations because of change management rather than technology — is attributed to Gartner, so a client can trace it.
• These are also the oldest comparison posts in the set, published 15 and 20 May 2025.
• If the need is a document the customer team can run against its own accounts, Hernandez is the closer match; use Ravichandran as a companion on the change-management half, not a substitute.

Examples: Source 1 · Source 2

The first post recounts the opening six weeks as Head of Customer Success: joining every implementation after the implementation specialist went on holiday, contacting each incoming customer personally without a deck or a process, and working with more than 15 customers across onboarding, integrations and support.

• Two claims matter to a buyer.
• Retention problems are frequently implementation problems wearing a different name: if the customer struggles to get value early, the renewal conversation is already compromised.
• Retention work belongs at the start of the journey, not three weeks before renewal.
• Where Hernandez supplies the plan structure and adoption diagnostic, Søttrup supplies evidence of the operating conditions under which those things get done, including what to standardise first and what to build (onboarding, integrations, reporting, workflows).

The second post holds the sharper idea, and the more conditional one.

• It argues that contract value measures the customer's importance to you, while workflow depth — breadth of core workflows, depth of feature use, integration into daily operations — measures your importance to them.
• Operational dependence, it says, should trigger a playbook instead of account reviews ranked by annual recurring revenue.
• That reframes the same churn problem Hernandez tackles with an early-warning signal list, and the two fit together: Søttrup supplies the exposure question; Hernandez supplies the signals and the three-question triage of cause, urgency and next action.
• Søttrup's model is sketched in one post rather than delivered as a tool, and the first post is a first-person account inside a single employer.
• Both posts are recent, published 26 August and 10 September 2026.
• Ask Søttrup what reusable playbook they would build for your business.
• Pick them when the buyer's question is who builds the function; pick Hernandez when it is what the first 90 days produce.

Examples: Source 1 · Source 2

The escalation post describes a software upgrade that locked a large client's own customers out of their portal, forced a rollback and reached the news, with the usual solutions engineer on holiday.

• The post documents a working method: escalate internally to the right technical resources, meet the customer's stakeholders throughout, give frequent updates rather than go silent, and deliver a root cause analysis covering what happened, why and how to prevent a repeat.
• The closing claim explains the case for hiring Rao: trust is not built by never having problems, but by how you show up when problems happen.
• Hernandez's churn material is about detecting risk earlier and triaging it; Rao's is about an account already inside the event.
• Those are different halves of churn prevention.
• The career post adds context: a path from programming through professional services and quality assurance management into technical account management, with the throughline described as getting people unstuck.

Rao's material is narrative from an experienced technical account manager, not a framework.

• It offers no plan builder, adoption diagnostic, health-score alternative or handoff map.
• The client would get judgment in the moment, plus a written root cause analysis that the post describes but does not supply as a template.
• This is the narrowest of the three comparison sets: escalation and trust recovery, plus one career reflection, with no equivalent of Hernandez's structured plan or CRM adoption questions.
• For a consultant hired to redesign handoffs and CRM process across a whole customer base, Hernandez's posts describe more of the engagement.
• Bring Rao in when the client's pain is a recent outage, a strained executive relationship or a technical account management gap; ask them to scope the deliverable rather than assume a template is available.

Examples: Source 1 · Source 2