I Almost Called It Noise

I typed this into the control tower's chat window: "Create an English slogan for our service. Witty and intellectual."

After pressing Enter, an odd tension arrived. It hadn't been there when I asked for code. Code has answers. Errors get fixed. It works or it doesn't. Right or wrong. But when creating a slogan, there is no "correct." Every option has its reasons, and whichever you choose reshapes the service's entire impression.

Several candidates appeared. "Watch less. Know more." "Turn rabbit holes into goldmines." "The knowledge layer YouTube forgot to build."

The one that caught my eye was this:

"Turn noise into notes."

Four words. The one-letter rhythm between noise and notes. The duality of notes meaning both "memos" and "musical notes." YouTube (sound, video) compressed into knowledge (notes) in a single sentence. I liked it.

I asked the control tower what it thought.

The answer came. The strengths were clear, it said. But there was one consideration.

"The word 'noise' negatively frames the user's viewing behavior."

That sentence stuck. "Rabbit holes" is an "oh right, that's me" kind of empathy. Everyone knows the experience of falling endlessly into YouTube, and there's a tone of cheerful self-recognition. But "noise" can be read as "what you're watching is just static." This service.s users are people already watching meaningful content. People who use YouTube for learning. Is it appropriate to call their viewing "noise"?

The AI added: "If your brand tone is provocative and sharp, noise is stronger. If your brand tone leans toward empathy and power users, rabbit holes is safer. Both are excellent, but they're different in character."

Different in character.

This wasn't about word choice. It was about how I see my own service. Do I frame what users are doing as a problem, or do I add value to something good they're already doing? "What you're watching is noise—we'll organize it for you" and "That rabbit hole you fell into—let's mine it for gold" describe the same function but deliver entirely different emotions.

I dropped "Turn noise into notes." It was a good sentence. But the tone my service wanted to speak in wasn't that.

The slogan question didn't end there. Apart from StackTube's slogan, I needed to establish the overall brand name and tagline. StackTube is only the first of seven services.

unstackd.io. Meaning "to unstick what's stuck." The slogan: "Build it. Ship it. No drama."

But during this process, another moment of hesitation arrived.

The master plan detailed a portfolio of seven services. Pricing structure, launch sequence, cross-promotion strategy. Naturally, I'd planned to display all seven on the unstackd.io landing page. "Here's the suite we're preparing."

The direction changed during a conversation with the control tower. What's visible outside and what's planned inside are different things, it said. Inside, there's a seven-service roadmap. Outside, it just needs to look like "a workshop where things appear one by one." The site doesn't need to announce plans.

I'm a quiet person by nature. Self-promotion doesn't come naturally. So "here's something I made" felt far more comfortable than "announcing our suite." The direction the control tower gave matched who I am.

But I had to check whether it matched simply because it was comfortable. Making a strategically sound decision because it happens to be comfortable is fine. Making a strategically poor decision because it's comfortable is different. The conclusion—in this case, both aligned. Promoting six services that don't exist yet erodes trust. Showing what you've actually built earns it.

Building code, fixing errors, deploying servers—these are technical tasks. AI helps well. But "what should I call this service?" and "what face should I show the world?"—these aren't technology. They're judgment. AI creates good options. Choosing is my job.

I almost called it noise. The reason I didn't wasn't because the AI pointed it out—it was because, after hearing the AI's point, I judged: "That's not my service's tone."

That kind of judgment is something a person who can't code can still make.

---

🔧 Technical Terms in This Episode

Slogan / Tagline A service's identity compressed into one sentence. Not a technical term per se, but in SaaS the first sentence on a landing page becomes the service's first impression, making it part of product design.

Framing How presenting the same fact from different angles changes perception. Calling YouTube viewing "noise" versus calling it "a rabbit hole" frames the same behavior differently.

Landing Page The first page users arrive at. Where the service persuades visitors about what it is and why they should use it. Since first impressions are formed here, slogan and design are especially critical.

Cross Promotion A strategy where multiple services promote each other. Placing "Also try Service B" at the bottom of Service A. The structure where unstackd.io's seven services reference each other.