I’m Using My Own Website as the Experiment | Make People Care — Part 3

BUILD · Make People Care · Part 3

I’m Using My Own Website as the Experiment

Enough theory. I am going to use the Make People Care story system on JackRighteous.com, hand the campaign into the existing Bee Righteous framework, and see whether changing how I tell the story changes what people do.

The goal is not more content. The goal is work you can keep building from.

Experiment #1 is already sitting in front of me.

Suno is changing.

Not just one feature. Not just one screen. Suno has announced a new generation of models while also pushing Studio, Voices, Custom Models, personalization and new workflow rules.

That gives me something better than a generic “new model features” article.

What happens to the way we use Suno when the model underneath our workflow changes?

That question can be investigated. It has consequences for beginners and experienced users. It has uncertainty. It gives me things I can test. And it creates a legitimate reason for readers to return as the answers develop.

First: I am not calling it V6 until Suno does.

There is already a useful lesson in that.

As of September 8, 2026, Suno’s public release notes still identify v5.5 as the newest named music model. Suno has officially announced a new generation of models and says previous models will be retired when the new generation launches, but I cannot verify “V6” as Suno’s official public name for the upcoming model.

I would rather build the campaign around what is true than gain a little attention from a name that is not confirmed.

Campaign rule: uncertainty is not a weakness when it is real. “What do we actually know?” can be part of the story.

Current references: Suno announcement · Suno release notes.

The story is bigger than the model name.

Studio 2.0 launched in August with MIDI, built-in synths, effects, automation and generative production tools. Suno followed it with more Studio updates in September. Voices, Custom Models and My Taste have pushed the platform toward more personalized creation. New terms and download rules also took effect September 3.

So the campaign question is expanding.

Is Suno becoming something different—and what does that mean for the creator who just wants to make better music?

See: Studio 2.0 · current release notes.

Run the story through Make People Care first.

CHANGESuno is moving into a new model generation while expanding the production environment around it.
STAKESCreators may need to rethink prompting, workflow, preservation, Studio use and what parts of existing training still apply.
CURIOSITYWhat actually changes in the result? Which old techniques survive? Where does the workflow improve or become harder?
EXPERIENCEI can run controlled tests instead of only repeating launch claims.
MOVEMENTThe story comes from what genuinely surprises, disappoints, changes or holds up during testing.
PROOFPrompts, audio comparisons, settings, screenshots, workflow notes and before/after results.
PAYOFFClear answers about what changed, what still works and what I would do now.
PARTICIPATIONReaders can run the same tests, request comparisons and report what happens in their genres and workflows.

That gives us the story brief.

Now it hands off to Bee Righteous.

Then score the campaign before scaling it.

The existing Bee Righteous Campaign Framework is the readiness filter. It tests Longevity, Clarity, Structure, Transparency, Alignment, Account Health and Repeatability, with a safety override for rights, voice, likeness, disclosure and trust problems.

That means Make People Care does not become a competing methodology. It supplies the story Bee Righteous needs to evaluate.

The handoff

Make People Care: Is there a real story here, and why should somebody follow it?

Bee Righteous: Is this campaign clear, aligned, honest, repeatable and safe enough to continue?

7-Post Sequence: What job does each post perform once the campaign earns execution?

The first Suno test plan.

I do not want the first article after launch to be fifteen conclusions based on five minutes of use. I want a repeatable set of tests that produces evidence.

TEST 1Same prompt. Current model versus new model.
TEST 2Simple prompt versus detailed prompt.
TEST 3One established JR genre prompt.
TEST 4Vocal direction and character.
TEST 5An unusual genre combination.
TEST 6A song I already know extremely well.
TEST 7Old workflow versus revised workflow.
TEST 8What changes when Studio becomes part of the process?

I also want the right to change the test plan as Suno confirms what the new model actually does. The structure should keep the comparison useful, not force the evidence into a conclusion I chose before testing.

The campaign begins before the model arrives.

1

BEFORE — Build the question.

What We Know: document only what Suno has officially announced.

What We Don’t: separate facts from assumptions, including the unconfirmed V6 name.

What I’m Testing: publish the test plan.

What Do You Want Tested? invite creators into the experiment before the answer exists.

2

ARRIVAL — Show the first evidence.

First generation. First reaction. Same-prompt comparison.

Not “everything changed.” Not a definitive guide. Just an honest first look at what happened.

3

LEARNING — Go deeper.

Genre behavior. Prompt structure. Lyrics. Vocals. Arrangement. Covers. Voices. Custom Models. Studio. Workflow changes.

This is where the campaign becomes genuinely useful instead of merely timely.

4

PAYOFF — What actually changed?

Once enough evidence exists, build the definitive JR guide.

What improved? What did not? What still works? What should beginners do? What should experienced users relearn? Which older JR instructions need updating?

One story. Different doors.

The campaign should not be the same post copied everywhere.

Short: “I’ve spent months teaching Suno prompts. What happens when the model changes underneath them?”

Article: What Suno has actually announced—and what it has not.

Audience post: What do you want me to test first?

Comparison: Same prompt. Old model versus new model.

Process content: What changed in my workflow?

Newsletter: What I learned this week.

Definitive guide: What Actually Changed?

The central story stays intact. The format and job change.

The Bee Righteous 7-post sequence for Experiment #1.

This is the initial sequence, not a rigid script. It gives the campaign enough shape to test.

1 · HOOK“I’ve spent months teaching Suno prompts. What happens when the model changes underneath them?”
2 · MEANINGWhy model changes matter to someone who has already invested time learning the tool.
3 · IDENTITYWho this experiment is for: beginners, active Suno creators and people trying to build repeatable AI-music workflows.
4 · PROCESSShow the controlled test plan and how I am separating claims from evidence.
5 · ENGAGEMENTAsk what creators want tested first—genre, vocals, prompting, Studio or another workflow.
6 · PROOFPublish a real comparison and show what changed.
7 · ACTIONSend readers to the living JR Suno guide, relevant training, Creator Starter Kit or deeper Find Your Sound road based on what they need.

The existing Bee Righteous system also gives us the discipline to stop or revise a post if the rights, disclosure, alignment or evidence are not ready.

Measure whether the story actually changed behaviour.

Publishing is not the end of the experiment.

  • Discovery: engaged views, early hold, click-through where relevant.
  • Story quality: retention, completion, spikes and dips.
  • Site movement: article entrances, next-page movement and route clicks.
  • Participation: comments, test requests, replies and creator-submitted comparisons.
  • Business: Creator Starter Kit, Find Your Sound and other relevant route clicks and conversions.
  • Return behaviour: returning visitors, returning viewers and newsletter engagement.

I also want to document what I expected to work that did not. A failed prediction is still useful evidence if I am willing to show it.

This is bigger than Suno.

Suno is Experiment #1 because it is current, relevant to my site and naturally testable.

The same method can work around a book launch, creator spotlight, Bee Righteous character, new AI tool, rights development, product, tutorial or something happening inside my own business.

What changed? Why does it matter? What do we not know? What can we experience? What moved? What can we prove? What did we learn? What can you do next?

That is what I mean by Make People Care.

Not “make people care about me.”

Make the thing worth caring about understandable.

Then tell the story clearly. Show the work. Deliver the payoff. Give people somewhere worthwhile to go next.

Create What You Love | Love What You Create.
Regresar al blog

Deja un comentario

Ten en cuenta que los comentarios deben aprobarse antes de que se publiquen.

articleall levels
On this page

    Your next move

    Turn the reading into useful work.

    Apply this now

    Complete one action before opening another guide.

    Write down the most important decision this article changes, then apply it to the project while the reasoning is still fresh.

    Continue learning

    Keep the subject connected.

    Use the public library to compare related guidance before changing the project.

    Continue with public guidance →
    Go deeper

    Use structured training for ordered work.

    Move into the member system when the project needs a sequence, templates and application—not another isolated tip.

    Explore structured training →
    Use a resource

    Support the next action.

    Use a workbook, checklist or ASK JACK route only when it reduces friction in the work.

    Open the supporting route →

    The Righteous Beat

    Get the week’s most useful creator guidance, platform changes and free resources.

    Join the free newsletter →