NNgroup — NuthinButta

← All creators

business

NNgroup

YouTube

Cleared insights: 30
Published protocols: 0
Sources analysed: 2

WHY · 30 cleared insights from 2 analysed sources · 0 protocols

+ Add to my sources Submit content from NNgroup

Extracted

What cleared the bar

Every result below came from this creator's own material, with its evidence attached.

Recommendation · Money

Explain changes clearly: what changed, why, and what it means for daily work

The first step to making legacy users more comfortable is explaining changes clearly. Don't assume users will notice what changed or understand why it happened. Tell them what changed, why it changed, and what it means for their daily work. Even better, give them a roadmap for when things are changing so they know what's coming and can mentally prepare.

NNgroup · Are You Supporting Legacy Users?

Recommendation from NNgroup

View full analysis →Watch the original ↗

Recommendation · Money

Give users control: gradual rollouts, opt-in, and temporary access to familiar views

Give users control through gradual rollouts, optional onboarding, or temporary access to familiar views so they feel prepared instead of surprised. Roll out a new experience in phases, letting users opt in before it becomes the default, and allow them to switch back to the old version while they learn the new one. Feeling informed and in control reduces anxiety even when change is necessary.

NNgroup · Are You Supporting Legacy Users?

Recommendation from NNgroup

View full analysis →Watch the original ↗

Recommendation · Money

Maintain familiar patterns whenever possible

Maintain familiar patterns whenever possible when changing software. Moving buttons, changing labels, or altering shortcuts forces users to stop and think, which slows them down. Keep core actions in the same place even if the surrounding UI changes, and preserve keyboard shortcuts. If you have to break or substantially change a workflow, acknowledge it and help users adjust.

NNgroup · Are You Supporting Legacy Users?

Recommendation from NNgroup

View full analysis →Watch the original ↗

Recommendation · Money

Before your next release, evaluate one legacy-affecting change against three questions

Before your next release, identify one change that affects legacy users and ask: have we clearly explained what's changing and why? Are we breaking any familiar workflows, and is that break truly necessary? Have we given users enough time or choice to adjust if they need to? If you can't confidently answer yes, your legacy users probably need more support.

NNgroup · Are You Supporting Legacy Users?

Recommendation from NNgroup

View full analysis →Watch the original ↗

Recommendation · Money

Lead with the so-what: open with the most important insight before methodology

The creator recommends leading with the so-what rather than the how: start with the insight that matters most and why it matters, since the audience doesn't need to understand methodology before understanding why they should care.

NNgroup · Why Your Research Findings Aren’t Landing

Recommendation from NNgroup

View full analysis →Watch the original ↗

Recommendation · Money

Give the audience one clear headline takeaway, not 12 findings

The creator recommends giving the audience one clear thing to walk away with — one headline, not 12 findings — so stakeholders can summarize the research to others.

NNgroup · Why Your Research Findings Aren’t Landing

Recommendation from NNgroup

View full analysis →Watch the original ↗

Recommendation · Money

Connect each finding to a goal, risk, or decision the audience already cares about

The creator recommends connecting each finding to something the audience already cares about — a goal, a risk, or a decision on the table — and explicitly tying findings to decisions currently on the table, since research that maps to nothing actionable is easy to ignore.

NNgroup · Why Your Research Findings Aren’t Landing

Recommendation from NNgroup

View full analysis →Watch the original ↗

Principle · Money

Three things matter most when changing software for long-time users

When making changes for long-time users, three things matter most: explaining changes clearly, maintaining familiar patterns, and giving users control. When teams do these three things well, legacy users are often much more open to change than expected.

NNgroup · Are You Supporting Legacy Users?

Claim from NNgroup

View full analysis →Watch the original ↗

Recommendation · Money

Introduce new workflows alongside existing ones instead of replacing them immediately

Introduce new workflows alongside existing ones instead of replacing them immediately. Replacing existing workflows immediately forces legacy users to stop and relearn, slowing them down and eroding the efficiency their learned workflows provide.

NNgroup · Are You Supporting Legacy Users?

Recommendation from NNgroup

View full analysis →Watch the original ↗

Creator perspective · Money

Findings alone don't convey stakes; stakes are what move people

Findings alone don't tell people what's at risk — stakes do. Presenting findings without stakes causes stakeholders to nod without acting.

NNgroup · Why Your Research Findings Aren’t Landing

Claim from NNgroup

View full analysis →Watch the original ↗

Principle · Money

A researcher's job is to make meaning and stakes clear, not just report findings

The creator argues a researcher's job isn't just to report back what they found; it's to make clear what it means and what happens if it gets ignored — which includes framing what is at risk if findings are ignored.

NNgroup · Why Your Research Findings Aren’t Landing

Claim from NNgroup

View full analysis →Watch the original ↗

Creator perspective · Money

Legacy users' resistance to change is about workflow risk, not preference

In complex applications, legacy users' apparent resistance to change is usually about risk to their workflow rather than personal preference. They rely on learned workflows to do their jobs quickly and accurately, and are skilled at specific workflows they've used for years, having built habits and workarounds around the system as it exists today, even if those workflows aren't the most efficient.

NNgroup · Are You Supporting Legacy Users?

Claim from NNgroup

View full analysis →Watch the original ↗

Recommendation · Money

Order findings by importance and actionability, not discovery sequence

The creator recommends ordering findings by importance and actionability rather than by the sequence in which they were discovered, so the audience can connect findings to next steps.

NNgroup · Why Your Research Findings Aren’t Landing

Recommendation from NNgroup

View full analysis →Watch the original ↗

Recommendation · Money

Schedule a live walkthrough of the research deck instead of only emailing it

The creator recommends scheduling a live walkthrough of the research deck with stakeholders rather than only sending it by email, since decks without a walkthrough get skimmed and misunderstood.

NNgroup · Why Your Research Findings Aren’t Landing

Recommendation from NNgroup

View full analysis →Watch the original ↗

Recommendation · Money

Test the readout with the hallway question: what one sentence should stakeholders repeat?

The creator recommends asking: if someone asked the audience in the hallway what the research said, what's the one sentence you'd want them to say? Write that sentence down when preparing the readout.

NNgroup · Why Your Research Findings Aren’t Landing

Recommendation from NNgroup

View full analysis →Watch the original ↗

Recommendation · Money

Concrete channels for communicating changes

Communicate changes via a short message when users visit the page, a brief note in the interface pointing to what's new, or a release note that focuses on the impact of the feature rather than just what it is.

NNgroup · Are You Supporting Legacy Users?

Recommendation from NNgroup

View full analysis →Watch the original ↗

Creator perspective · Money

A research readout exists to build shared understanding and make action easy

The readout's purpose is to get the right people in a room, give them a shared understanding of what users need, and make it easy to act — it is for making the story easy to act on, not for covering everything.

NNgroup · Why Your Research Findings Aren’t Landing

Claim from NNgroup

View full analysis →Watch the original ↗

Creator perspective · Money

Ask 'does this story make it easy to act?' rather than 'did I cover everything?'

Most researchers ask 'did I cover everything?' when preparing a readout, but the better question is 'does this story make it easy to act?' — that's what a research readout is actually for.

NNgroup · Why Your Research Findings Aren’t Landing

Claim from NNgroup

View full analysis →Watch the original ↗

Creator perspective · Money

Anti-patterns: unsupported, surprised, or overwhelmed legacy users become anxious

Failing to explain changes clearly, breaking familiar workflows without acknowledgment, or surprising users with forced rollouts leaves legacy users unsupported and anxious about necessary change. Surprising legacy users instead of letting them opt in and prepare leaves them feeling unprepared and anxious rather than informed and in control. Overwhelming them with excessive change details instead of removing uncertainty creates anxiety rather than confidence. Assuming they will notice what changed and understand why on their own leaves them uncertain about how changes affect their daily work.

NNgroup · Are You Supporting Legacy Users?

Claim from NNgroup

View full analysis →Watch the original ↗

Principle · Money

Support legacy users through change; help them move forward without losing confidence or efficiency

When change is needed, support legacy users through it. The goal isn't to keep legacy users comfortable with the same workflows forever; it's to help them move forward without losing confidence or efficiency.

NNgroup · Are You Supporting Legacy Users?

Claim from NNgroup

View full analysis →Watch the original ↗