Curated Intelligence: Everyone's Using AI Wrong (But Not How You Think)

About Curated Intelligence: Everyone's Using AI Wrong (But Not How You Think)

We think we're using AI for efficiency. We're actually using it for connection. In this first episode of Curated Intelligence, I extract a hidden pattern from three wildly different sources that reveals why some people are becoming fundamentally different thinkers while others are still debating whether to use AI at all. www.signalovernoise.ai (https://www.signalovernoise.ai?utm_medium=podcast)

Publisher

Max Bernstein

Category

business · technology

Language

en

Explicit

No

First episode

17 Jun 2025

Latest episode

20 Aug 2026

Latest episodes

11 episodes in the feed.

1. 

   20 Aug 2026

   The Man Who Sold Monsters by Mail

   This is a free preview of a paid episode. To hear more, visit www.signalovernoise.ai (https://www.signalovernoise.ai?utm_medium=podcast&utm_campaign=CTA_7) Obsession is a dangerous trade. from Monsters of God I found Monsters of God by accident on HBO. I was mindlessly scrolling for something to watch, but once I put it on, I didn’t get up. I was hooked first by the characters, then the history, then the smuggling. It’s a crime story with every reptile I’ve never heard of in it. And the people…the people were exactly like you think they’d be. I kept thinking I’d turn it off after ten minutes and focus on work. I didn’t. Hank Molt (great name) is one of the main characters and an apparent legend in that industry. He ran a pet store in Philadelphia and stocked it with animals he found overseas, often carrying them into the country in suitcases, which, customs barely checked. Eric Goode, who created the series, says Molt liked that there were laws at all, because breaking them made it a better game. In the 1970s he went on what he called shopping trips with other dealers. The Wall Street Journal later quoted him on what they packed. The gun to shoot someone, the machete to cut off our fingers if we were bit by a taipan. There were no rules, a lot of private deals, and a snake that can kill you if you guessed wrong. They brought a blade to cut their own freakin’ fingers off if they were bit. Then I got stuck on a price list. Names, Then Numbers Molt circulated lists of rare reptiles, snakes and turtles and lizards with prices next to their names, and mailed them to collectors and to zoos that competed for the same animals. Before that, collectors and zoos bought and sold by calling each other, or by shaking hands. But the list did something more important than advertise inventory. It told the market what to believe. People saw prices that seemed absurdly high compared with anything they’d seen before. Yet, rather than immediately destroying demand, the list helped make the animals feel more rare and more collectible. A reptile that had been an obscure creature in a distant part of the world became a named item in a catalog, available through a person who appeared to have unusual access. → The price not only reflected the value. → The price helped create it. Then Washington made the sheet more powerful by accident. The Endangered Species Act came into effect in 1973 and Molt’s business boomed, because an endangered label meant rarer, and rarer meant he could charge more. A law written to protect the animals raised their price instead. Other dealers noticed. Tommy Crutchfield, a Florida rival, ran Molt’s playbook, selling smuggled reptiles to collectors, pet owners, and zoos. Time’s reporting on the series puts his sales and trades at millions a year. There’s No Pudding Harry Beckwith named this in 1997 in Selling the Invisible, then said it blunter in 2022 in The Invisible Promise. “There’s no pudding in a service, so there’s no proof.” Beckwith said, “Your price is not just your price. It is a quality cue.” When people can’t inspect the thing, they inspect the tag. He tells the old story about the carpenter who charged $2 for hitting the nail and $43 for knowing which nail. Charge for the years it took to know which nail. My favorite piece of evidence in his book is about coffee. At $18, buyers of organic coffee got more passionate about it, and they could recite roughly twice as many details about what they were drinking. The higher number made people believe more, and study the thing harder. The reptile list ran the same experiment with snakes. Invisible expertise The blank page test The $43 in the carpenter story was for knowing which nail. That knowing is invisible expertise. It’s the judgment that only shows up when you’re in your zone of genius. When you’re operating from unconscious competence. You listen for two minutes and you already know what’s wrong, and if someone asked you to write down how you knew, you’d stall, because the steps aren’t sitting there as steps anymore. They compacted. You got so good at the work that the work disappeared from your ability to articulate it. Why you can’t say it That’s why it happens. Repetition sank the skill below words. The better you are, the less you can narrate it. You’ve been doing it for 10+ years and the manual you could have written as you were building those patterns has disappeared. What’s left is a feeling in the call, a tell in their voice, a thing you notice that a competent person with a checklist will miss. The borrowed job title When you can’t say it, you sell familiar language or you borrow a job title. Someone asks what you do. You say you coach, or you consult, or you help people with the thing you’ve spent 10+ years getting really good at. The sentence comes out different every time, because you honestly aren’t quite sure HOW you do what you do. They nod, then they ask what you charge and if you are how I used to be you say “it depends.” You leave the conversation having been treated like a less expensive version of someone you’re not, and you can’t correct it because you still don’t have a sentence for the actual thing. I used to do this on my own calls. I can sit with a client and name their offer in one pass, then get on a sales call for my work and describe it as a pile of verbs (help, advise, extract, train). The work was there, I just never put it on a sheet. What I Put On Mine One line on my list is called Cognitive Fingerprint™ (https://www.cognitivefingerprint.ai/). The person who buys it is a founder whose team still has to wait for them after a call, because the knowledge is in one head. When we’re done they have a written extraction they can hand to people… their patterns, framework…their thinking, in their language. That’s the whole card… a name, who it’s for, what they walk away holding, who it’s not for, and a price, which I put on the card I send them, not in this essay. Here it is, item 001 on my actual sheet. I have other lines with the same idea. Each one is something a buyer can say yes or no to without me giving a tour of my whole brain. I can’t tell you how many opportunties I lost at workshops, calls or conferences when people asked how I could help them. I knew I could but I couldn’t articulate it. The Gap You can see what the sheet did, and you saw one of mine. Now it’s time to write yours. The Monster Price List is the prompt (or the Skill) that digs that sheet out of your own calls. You feed it one to three transcripts of you working (your website and LinkedIn help, but the calls are where the expertise actually shows up), and it hunts for the moments a buyer valued… the “how did you know that,” the thing you fixed for free, the “could you also” you never invoiced. Then it writes one to five cards… a name pulled from words that were actually said, a buyer you can picture, something they walk away holding, who it’s not for, a number they can argue with. Every card is quote-locked to a real moment from your own tape. You shouldn’t have to sit through a questionnaire first. The full prompt and the downloadable Skill are below. Attach a transcript (or 3) of a coaching call, discovery, onboarding etc.. Send the first card. It works from the moments your expertise already leaves on tape. It won’t map the whole of how you think (that’s a deeper extraction), but it will name and price what you already sell right now.

2. 

   14 Jun 2026

   The Course That Rewrites Itself Overnight

   This is a free preview of a paid episode. To hear more, visit www.signalovernoise.ai (https://www.signalovernoise.ai?utm_medium=podcast&utm_campaign=CTA_7) Quick note: The video above was our first Live Build / Community Call where I took people behind the scenes in what I’m building and as one subscriber said “a window into your thinking.” Really enjoyed it and will be doing more of them soon. Last week I taught a four-day Claude Code training. Close to 200 people live each day, 600 registered. Creative strategists and copywriters, most of them brand new to any of this. Day one wasn’t the fun part. Day one was just getting everybody installed. I wasn’t about to throw a copywriter into a terminal, so we worked inside the Claude desktop app... and even that was a fight. Getting some folks to install the app got a bit dicey. But somewhere around day two, I noticed something pretty cool. The site I was teaching from kept getting better, and I hadn’t planned for it to. Every night, it rewrote itself. Here’s what happened… After each day, I’d grab the transcript. The whole thing. Plus the chat, plus every question anybody asked. And I’d hand it all to Claude Code and ask: Based on this, what did people need that I didn’t cover? Is there a better way to structure these resources based on the questions people were asking? What do I need to expand on? What do I need to simplify? Then I’d tell it to build those resources and drop them into the site. By the next morning, yesterday’s questions were pages on the site. Somebody asked about Firecrawl and Exa, two tools I hadn’t planned to touch. So after we wrapped, I said go pull the docs for both and build me a comparison chart, side by side. Next morning, there it was, sitting in the resources. Another day I recorded a two-minute video after the call, handed it to Claude, and said embed this nicely right here. The people who missed that part live could now watch it sitting exactly where it belonged. The site got smarter off real feedback. Not off what I guessed people would need ahead of time. And the part that still makes me grin... day three was about building websites in Claude Code. The site I was teaching from was built in Claude Code. So I just pulled up the actual files and showed everybody how the thing they were looking at got made. Now think about where a course normally lives. You build it, then you pour it into Kajabi or Circle or Skool, and from that point on you’re working inside their box. Their modules. Their layout. Their idea of what a lesson is supposed to look like. And sure, maybe you update yours now and then. But you’re doing it within their model. Figure out a better way to teach it halfway through and you’re fighting the template just to rebuild it. Mine wasn’t capped, and it wasn’t boxed. The site rewrote itself almost in real time. A question from the afternoon’s call was a new page that night, sitting right where it belonged. I was able to build the exact flow, the exact look, the exact learning experience I wanted. The structure bent to the lesson instead of the lesson bending to the platform. And before you decide this is some elaborate setup only I could pull off... it isn’t. The whole thing is just files and folders on your computer. That’s the line I hammered every single day. As crazy as Claude Code looks, strip it back and it’s just files and folders on your computer. You point it at a folder, and that folder is everything it can see. You open the same folder in Obsidian for a nicer view... still the same folder. There are only ever those two moves, and everything happens inside the folder. So the teaching site was a folder. The transcript went into the folder. Claude read the folder and wrote new files back into it. There’s no hidden layer. There’s a folder, and a model that can read and write inside it. Once you see it that way, the question stops being “could I build this” and turns into “what do I point it at.” So now you’ve got the idea. A living folder beats a boxed-in platform, and the engine is a nightly loop. Feed it what actually happened. Ask what’s missing. Let it build while you sleep. But, knowing that and running it are two different things. You still need to know: How to make Claude Code’s output not look like generic AI slop. How to turn a flat strategy doc into something that looks like your client’s own brand. How to catch your own mistakes before a client does, without trusting one model to grade its own homework. That’s what’s below, an upgraded version of what I talked about on the call. I pulled three resources straight out of that training. Each one’s a thing you can run in the next twenty minutes. * The Firecrawl Microsite Recipe How I stopped sending Google Docs and started sending interactive sites that look like the client’s own brand, built from their real assets. The exact steps, including the part where it pulled product shots off a retail shelf I never set foot in. * The Dual-Model QC Loop How I have Claude write a review prompt grounded in the actual codebase, then hand it to Codex to tear the work apart, so two models check each other instead of one model approving itself. Includes the fix for a trap one of my sharper students caught live. * The Tools & References Sheet The exact sites I reach for... where I get design inspiration so the output doesn’t read as AI-made, where I pull official AI logos, and the one context-window number that tells me when to hand off before the model goes dumb. So point Claude at a folder. Hand it yesterday. Ask what’s missing. Then go look at what it built while you slept. -Max P.S. I got some really good feedback from the people on the call but after you watch it, let me know what you think. I am planning to do more of these but like the course, I want to make sure it fits into the box that you want.

3. 

   1 Feb 2026

   Why Does Sheryl Sandberg's Advice Never Trigger Resistance?

   The Invisible Advantage Series Sheryl Sandberg has no idea she does what you’re about to read. Neither did Sam Altman. Neither did Russell Brunson or Rick Rubin. Turns out, we all have blindspots. No matter how famous you are. Previous: [Sam Altman (https://www.signalovernoise.ai/p/the-5-invisible-moves-sam-altman?r=4owe7&utm_campaign=post&utm_medium=web)] (#1) | [Russell Brunson (https://www.signalovernoise.ai/p/the-5-invisible-patterns-russell?r=4owe7&utm_campaign=post&utm_medium=web)] (#2) | [Rick Rubin (https://www.signalovernoise.ai/p/what-rick-rubin-is-actually-doing?r=4owe7)] (#3) Editor’s note: I’ve been procrastinating on this article for months. But I’m currently skiing in Telluride (and obviously doing a poor job of staying off the computer), and this book was sitting in my Airbnb…It was the sign I needed. Sheryl Sandberg tells a room full of ambitious, highly accomplished people to stop taking credit for their success. They furiously take notes. She tells people going through some of the hardest moments of their lives to “lean into the suck.” They go out and buy her book. She tells women to be more aggressive in male-dominated rooms. Standing ovations. Sandberg ran Facebook’s business for fourteen years. Before that, Google. Before that, the U.S. Treasury. She wrote Lean In, which sold 4.2 million copies and launched a movement. But credentials alone don’t make advice land. You know people with impressive résumés who get ignored every day. You may have been one of them. The same advice that triggers eye-rolls from anyone else gets nothing but buy-in from her. So what in the heck is she doing? In 1966, psychologist Jack Brehm documented something he called psychological reactance. When people feel their freedom threatened, even by well-meaning advice, they push back. Not stubbornness. A deep human instinct. You’ve been there. Standing in front of someone, offering wisdom you earned the hard way, going through precisely what they’re describing. And their brain is screaming: Who are you to tell me what to do? They don’t say it out loud. They just nod, smile, and ignore everything you said. I used to think this was a me problem. Maybe I wasn’t explaining it right. Maybe I needed better examples. Maybe they just weren’t ready. Then I analyzed years of Sandberg’s interviews and transcripts. What I found made me want to delete half of everything I’d ever written about influence. She has three moves. Once you see them, you can’t unsee them. The Pattern Hiding in Plain Sight I was halfway through a Harvard Business School interview when I saw it. She was explaining why she joined Google, and she attributed the entire decision to Eric Schmidt. Not “I realized” or “I figured out.” Eric told her. So I started counting how many times she credits someone else for an insight. Watch any of Sandberg’s interviews. The advice doesn’t come from her. → A rabbi told her to lean into the suck → Eric Schmidt told her not to be dumb about job criteria → Her 10-year-old son said “Mom, they all know what happened to us”→ Bill Campbell asked if she was done talking about what she used to do In every one, she’s the channel, not the source. That’s why it lands. You’re not the student. You’re watching her be the student. She does it the same way every time. After compiling my notes I realized Sandberg has three moves. Once you see them, you can’t unsee them. And once you understand why they work, you’ll realize you’ve been triggering resistance your entire career. Move 1: Disappear When Sandberg was looking for a job after business school, she had a chart of criteria. Google met none of them. She showed Eric Schmidt the chart and explained the problem. “He put his hand on my paper and said, ‘Don’t be dumb. If you’re offered a seat on a rocket ship, don’t ask what seat. Just get on.’” That story has been told thousands of times. It launched a phrase that every recruiter in Silicon Valley now uses. And Sandberg never once claims it as her insight. She attributes it to Eric Schmidt. A specific moment with a specific gesture: Hand on paper. She could say “I learned to prioritize growth over job criteria.” It’s the same lesson but you’d forget it by tomorrow. The Eric Schmidt version sticks because you’re not receiving instruction. You’re witnessing a transformation. When her husband Dave died, she didn’t know how to move forward. Phil Deutch put his arm around her and said: “Option A is not available. So let’s just kick the s**t out of option B.” That became the title of her book. She positions herself as a student who got lucky with teachers. Donald Miller built a $100 million business around this same insight. His StoryBrand framework has one rule: Your customer is the hero, not your brand. You are the guide. The guide has wisdom and empathy, but the guide is never the main character. Luke Skywalker is the hero. Yoda is the guide. Yoda doesn’t say “I defeated the Empire.” He says “Do or do not.” The best documentary filmmakers discovered this decades ago. The observational style, what critics call “fly on the wall,” works because the filmmaker disappears. You forget someone is holding the camera. The subject becomes the story. Great mentors do it instinctively. Research on effective mentoring found that the best ones “pass on their knowledge through informal conversation and everyday modeling.” They’re listeners who develop your unique voice, not lecturers who impose their own. They all landed on the same move. The person with authority steps back. The person receiving wisdom becomes the protagonist. Here’s why your advice doesn’t land. You’re the hero of your own wisdom. “I developed this framework.” “I figured out the pattern.” → You’re asking people to accept that you’re smarter than them ↳ Their brain won’t let them ↳ Reactance kicks in ↳ Arms cross. Eyes glaze Sandberg asks them to receive what she received. No hierarchy. No threat to autonomy. Just one student passing notes to another. Move 2: Confess First Most leaders establish credibility first, then share a failure. Sandberg inverts this. When discussing her career on Oprah’s Super Soul Sunday, she didn’t open with Google or Facebook. She opened with the void. “For me, it was a void. It was closing in on me so I couldn’t breathe.” When talking about joining the tech industry, she starts with not belonging. “I never wanted to work in business. My dad’s a doctor. My mother was a community organizer. Business was kind of bad in my family.” When returning to work after Dave’s death, she starts with disaster. “I came to work the first day. I was there for 4 hours. As far as I could tell, it was total disaster. I fell asleep in a meeting.” By the time the authority arrives, your guard is down. You’re not being lectured by someone who has it figured out. You’re hearing from someone who struggled with the same things you struggle with. Therapists figured this out decades ago. Push someone and they push back. Give them room to decide for themselves and they stop fighting you. Sandberg’s vulnerability looks and feels like weakness. It’s actually strategy. She earns the right to teach you by admitting she needed to be taught. Here’s why your advice doesn’t land. You lead with credentials. You establish authority before showing humanity. By the time you share a failure, people have already decided whether to trust you. And guess what that answer usually is? Move 3: Hand Over the Script Most advice is abstract. “Be supportive.” “Show empathy.” “Communicate better.” Words that mean nothing until you’re standing in front of someone who’s crying and you have no idea what to say. Sandberg gives you the actual sentence. She learned what to say by experiencing what not to say. Every bad platitude she received in grief became a lesson in what actually helps. * Don’t say “How are you?” Say “How are you today?” The word “today” acknowledges that grief exists on a spectrum. Yesterday was different. Tomorrow might be worse. * Don’t say “Is there anything I can do?” That question is a burden disguised as an offer. The person in grief can barely remember their own name. They cannot also manage your helpfulness. Just do something. “I’m in the lobby. I brought hamburgers.” * Don’t say “I.” Say “We.” When Phil had his arm around her and said “let’s kick the s**t out of option B,” the “we” mattered as much as the advice. He wasn’t telling her what to do. He was joining her. I’ve watched that interview three times. The arm around her. The “we.” Every time, I lean forward in my chair. Something about it lands before I can analyze why. But notice what she did. She gave you the sentence, not the concept. Scripts remove the last obstacle between knowing and doing. You don’t have to translate the principle into action. The action is right there. This is uncomfortably practical. Most advice stays safely abstract so you can nod along without changing anything. Sandberg hands you the exact sentence. Now you have no excuse. There’s research behind this. Psychologists call it Implementation Intentions. People who know exactly what they’ll say are 2-3x more likely to actually do it. Doctors learn exact phrases for delivering bad news. FBI negotiators memorize scripts for de-escalation. Abstract advice requires translation. Scripts are ready to use. Here’s why your advice doesn’t land. You tell people what to think. She tells them what to say. You give principles. She gives scripts. Principles require translation. Scripts are ready to use. What Makes It Stick There’s one more thing Sandberg does, and it’s the piece that makes everything else stick. She doesn’t just tell you what to do. She dissolves the guilt you’d feel about doing it. When she was struggling to feel joy after Dave’s death, she felt guilty dancing at a friend’s bar mitzvah. Her brother-in-law Rob called her. He was crying. “All Dave ever wanted was for you and your children to be happy. Don’t take that away from him in death.” Read that again. Permission to want what she already wanted but couldn’t admit. Her son did the same thing. “Be yourself.” Three words. Permission to stop performing. He was ten. It took a child to say what the adults had been circling around for months. Powerful. “Lean In” itself is permission. Permission to want power. Permission to want success. Permission to stop apologizing for ambition. Research on psychological reactance backs this up. Adding phrases like “but of course, it’s up to you” dramatically reduces resistance. When you acknowledge someone’s autonomy, their defenses drop. Most persuasion tries to make you want something new. Sandberg’s persuasion makes you stop apologizing for wanting what you already want. You walk away thinking you made the decision yourself. That’s why it doesn’t feel like influence. Which is exactly when influence is most powerful. Now Look in the Mirror Here’s what connects all of this. Psychological Reactance is triggered when someone threatens your sense of freedom. The moment you position yourself as the expert with answers, you become a threat. The brain’s response is automatic: resist, dismiss, ignore. Sandberg never triggers that response because she never positions herself as above you. She’s a fellow student. She struggled. She received wisdom from others. She’s just passing it on. The channel, not the source. I had AI analyze those years of interviews looking for a technique. What I found was simpler. She’s just honest about where her wisdom comes from. The rest of us hoard credit like it’s the last croissant. The patterns aren’t complicated: * Be the channel, not the source. * Open with failure, not credentials. * Give scripts, not principles. * Grant permission, not instruction. Here’s what I noticed while writing this: I kept typing “I discovered these patterns.” Then deleting it. Then typing it again. I didn’t discover anything. Sandberg showed me, the same way she shows everyone. She left it in plain sight for years. I just finally paid attention. Someone taught you what you know. Probably several someones. Make sure you remember to mention them. -Max Now What? You just read 2,000 words about influence patterns you’ve been violating your entire career. You nodded along. You thought “I do that.” Maybe you winced at a few parts. Here’s what happens next for most people: Nothing. You’ll send the same pitch tomorrow. You’ll open with credentials. You’ll say “I developed” and “my framework” and “let me explain why.” You’ll watch the prospect’s arms cross. You’ll wonder why Thompson went with someone else. The 28-year-old with the ChatGPT website will close another deal you should’ve won. Not because he’s better. Because his pitch doesn’t contain the seven words that make people stop listening. You won’t even know which seven words. The Zero Resistance Toolkit That’s the problem with patterns you can’t see. Knowing they exist doesn’t mean you can find them in your own writing. You can diagnose a client’s business in 30 minutes flat. You can spot their positioning problems, their pricing mistakes, their buried value. You’ve done it a hundred times. Your own pitch? Blind spot. Your own bio? Blind spot. The email you sent yesterday that’s sitting in their inbox, day 4, no response? You have no idea which sentence killed it. I turned Sandberg’s four moves into prompts that find your blind spots for you. * Paste in a pitch. The prompt shows you exactly which phrases trigger resistance, and rewrites them. * Paste in an email that got no response. The prompt scores it across four categories of influence failure and flags the three worst sentences. * Paste in your bio. The prompt extracts “who taught me” stories you can use instead of listing credentials nobody reads. * Paste in the objection you keep hearing. The prompt shows you why your current response makes it worse, and gives you three scripts that dissolve it. I usually post the prompts here but since there is 5, I packaged them up for ya. You can find them in the Prompt Vault: Zero Resistence Toolkit (https://www.cognitivefingerprint.ai/prompts/workflow/zero-resistance-toolkit) PW: signal2026 …or I created this doc for you too. Zero Resistence Toolkit Doc (https://docs.google.com/document/d/1amHKBZy6lZASH2f5CFifJkWHKzPWQGHo/edit?usp=sharing&ouid=104152930376029743668&rtpof=true&sd=true) This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.signalovernoise.ai (https://www.signalovernoise.ai?utm_medium=podcast&utm_campaign=CTA_1)

4. 

   12 Jan 2026

   The Fastest Way to Waste Time with AI

   We decided to try something new… Instead of your standard “How-To” content, we thought we would up the stakes. Let people submit a problem via a locked “Vault” and when we flip the camera on, it unlocks and we get to solving it. The problem submitted was: I lack a reliable, low-friction system that captures and regularly resurfaces each client’s long-term personal context and last-session commitments before calls, so I show up unprepared and risk renewals and family financial stability. (Note: This was the output of using the 5 Why’s Prompt to Drill help clarify the real proble and why it sounds like AI) As I read it out loud, every instinct inside of me is screaming the same thing… Start. Building. Now. AI is incredible. With a few taps of the keys and hitting enter a few times, you can send it off to do your bidding and it will return an answer that sounds like a senior level consultant worked on it for weeks. But just because it sounds good doesn’t mean it is good. So instead I tell my instincts to chill for a second and instead, say: “To me, it’s still not drilled down enough.” I remove myself from “answer now” mode and notice something I’d never put into words before. Paid subscribers get access to my prompt + workflow vault and I just added an entire section for some of my favorite Claude Skills The Layers Underneath I ask Claude to unbundle the problem from first principles. What is this person actually trying to accomplish? Claude comes back with layers…lots of them:”The surface-level framing is about a missing system - specifically one that captures and resurfaces client context before calls. But there are several layers underneath worth examining. The Information Problem There are actually two distinct information challenges bundled together here: Long-term personal context - This is the accumulated understanding of who this client is, what matters to them, their history, their patterns. It’s the kind of knowledge that builds over months or years of relationship. Last-session commitments - This is much more tactical. What did we agree they’d do? What did I promise to follow up on? This is accountability tracking. These require very different capture mechanisms. One is ongoing synthesis, the other is discrete action items. The Timing Problem The statement says “before calls” - which raises the question: how far before? Five minutes? The night before? The morning of? This matters because it determines whether you need a push system (information comes to you) or a pull system (you go get it when you remember to). The Friction Problem “Low-friction” appears twice conceptually - in capture AND retrieval. But these often conflict. The more structured and thorough your capture, the more useful your retrieval... but the higher the capture friction. The Stakes Framing Here’s where I want to push a bit. The problem escalates quickly from “unprepared” → “risk renewals” → “family financial stability.” That’s a big leap. Some questions this raises: Is “showing up unprepared” actually why renewals are at risk? Or is that an assumption? Could renewals be at risk for other reasons that preparation wouldn’t solve? Is this problem actually happening right now, or is this a fear about what could happen?” Level 4 The old me would have started building immediately. Hit enter. Watched Claude spin up something impressive. Shipped it. Felt productive. Discovered three days later it solved nothing. I’ve been burned by that before (be honest, we all have). Hours on workflow looks impressive but just like those n8n workflows your see people promoting on the socials, don’t actually produce anything meaningful. Quick aside - you mean to tell me you created a workflow that has saved you 100 hours a week and made you 3M+ in profit and you are just going to give it to a stranger on X or LinkedIn because they retweeted it? Social media… Takes a deep breath, returns to article… And that’s when I said it out loud: “It’s almost like you’re trying to solve from Level 4 when Level 1 hasn’t even been discovered yet.” The problem people bring you is almost never the actual problem. It’s a symptom bundled with assumptions, wrapped in a solution-shaped request. AI makes solving feel free. But solving the wrong problem costs you time rebuilding. Costs you trust when the solution fails. Costs you the insight you would have found if you’d drilled first. The better AI gets, the more expensive this mistake becomes. You can build the wrong thing faster and more impressively than ever. Doctors. Ducks. Blueprints. Doctors call it differential diagnosis. Patient comes in with chest pain. A bad doctor treats the symptom. A good doctor creates a list of every condition that could cause chest pain. * Heart attack * Acid reflux * Pulmonary embolism * Anxiety * Burrito from Tuesday Then systematically rules them out. If an important potential condition is missed, no method will supply the correct conclusion. The best treatment in the world won’t help if you’re treating the wrong thing. Programmers call it rubber duck debugging. Developer stares at the same six lines of code for forty-five minutes. Finally, they explain it line-by-line to a rubber duck. The act of articulating forces them to examine each assumption. Most of the time, they discover the solution mid-sentence. Not because the duck gives advice. Because the explanation reveals what they’d been taking for granted. The duck doesn’t solve. The duck forces you to discover Level 1. Architects won’t draw until they understand how the family actually lives. Their daily routine…time spent in each room. They refuse to build until they’ve drilled past “I want an open floor plan” to “I want to see my kids while I’m cooking.” It’s the same pattern in a different domain. The people who are great at building are the ones who refuse to build first. Your Last Seven Days Think about your last week with AI. How many times did you paste something in and hit enter before asking: * What am I actually trying to accomplish? * What would success look like? * What assumptions might be wrong? If you’re like most people… Just about every darn time. This isn’t because you’re lazy. It’s because AI is designed for speed and keeping you engaged. For creating an affinity that makes you want to come back and spend more time on their platform. You ask, you get. The dopamine hits before you’ve finished reading the response. Except the math doesn’t work. Every half-solved problem boots you back to the beginning. Every misaligned solution demands a do-over. Every impressive-looking output that doesn’t quite fit wastes more time than typing the original prompt. The thing that makes AI feel fast is the thing that makes your results slow. After the Drill After we drilled down on the client prep problem, then we built. Claude created the Client Prep Engine. A Skill that transforms whatever client inputs exist into pre-call briefs. Transcripts, notes, emails. All processed into something incredibly useful. But here’s what made it good… Because we’d drilled first, the Skill knew to ask about timing. Knew to separate long-term context from session commitments. Knew to handle the friction problem explicitly. None of that would have been there if we’d built from the surface request. What emerged from the drill-down was a pattern (you know I loveeee my patterns). These aren’t complicated. But they force you to discover Level 1 before you start solving from Level 4. You can grab the Client Prep Engine skill (https://drive.google.com/file/d/1D_A0VztCsl1w-z4bSpoEBPqSOrsqogIF/view?usp=sharing). Or build your own. Let Claude drill before you build. The old version of you hits enter. The new version asks one question first: What’s Level 1? -Max If you enjoyed this article and this training, we just started a community where our goal is run more experiments and help people think differently about AI. You can lock in the entry price for life of $27/month and even give it a spin for 7 days to see if ya like it. Check out Beware The Default Here. (https://www.skool.com/bewarethedefault) This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.signalovernoise.ai/subscribe (https://www.signalovernoise.ai/subscribe?utm_medium=podcast&utm_campaign=CTA_2)

5. 

   6 Jan 2026

   Why I Haven’t Slept Properly Since October

   It’s the first Saturday of the new year. I should be recovering from multiple days of cake, cinnamon rolls and bagels. Instead, I’m on a livestream demoing a personal management dashboard I built in my boxers. I’ve been building and talking with Zain Haseeb (https://substack.com/profile/12335031-zain-haseeb) for six months. Mid-call, we decided to say 'screw it' and just hit record. No more talking about it. Just show people what we've been making We started by recapping our “meeting” two weeks ago. Four of us met in Atlanta and sat around my dining table for three days straight. Zain Merchant (https://substack.com/profile/18161090-zain-merchant) (or “little Zain” to help keep it straight) brought a desktop computer. Not a laptop. A desktop. With its own power supply. Four dogs running around licking our feet. A monitor stacked on pretzel boxes. Twelve-hour brainstorming days. I forgot to eat lunch. Twice. This was not a polished operation. (We’re proud of this.) The livestream was us showing what came out of that. Halfway through, Zain says something that I had to write down. “I just feel like a kid again. Like you’re outside exploring and doing things you never thought you could do.” What “Kid Again” Actually Looks Like His wife has a very successful career but, is by no means, a developer and doesn’t know how to code. They were in the kitchen making dinner, she had an idea for something that would help her colleagues at work, they sketched it out on the counter, and they just... built it. A working prototype. In about an hour. I had a similar thing happen. All of my stuff is in a million different apps. Three different calendars, Claude, Stripe, Substack, Notion, etc. So on Friday, I started building my own dashboard that connected all of them together in the EXACT way that I wanted it. I caught my girlfriend peering over my shoulder (probably…definitely…because I didn’t hear something she said) and her eyes lit up. We spent the next 2-3 hours building her, her own. That’s what “feeling like a kid again” actually means. Not productivity. Play. The Friction Collapse Here’s what’s actually happening… The distance between “I have an idea” and “I have a working thing” evaporated. Building something used to take weeks. Contractors. Slack threads. Approvals. Waiting for someone to email you back about a font choice. Not to mention that whole “coding” thing. Now it takes an afternoon. Sometimes a lunch break. Sometimes an hour in the kitchen. Friction is what makes work feel like work. Strip it out, and you remember why you got into this in the first place. The Problem Nobody’s Naming Most people aren’t feeling this…yet. And it’s not tools. You have access to the same AI we do. Probably paying for the same subscriptions. It’s not tutorials either. YouTube has forty-seven thousand of them. Every platform has a course now. Your LinkedIn feed is half AI tips from people who discovered ChatGPT eleven months ago and now have “AI Strategist” in their bio. The limitation is something else entirely. Imagination. You can’t use what you can’t picture. Most AI frustration isn’t about capability. People don’t know what to ask for because they’ve never seen what’s possible. They’re not stuck on the how. They’re stuck on the what. I’ve been there. Staring at a blank prompt window. Cursor blinking like it’s waiting for me to be smart. Knowing this thing is supposed to be powerful, feeling like an idiot for not knowing what to type. You can’t imagine your way out of an imagination gap. You need to see it. So We’re Showing, Not Teaching (well, a little bit of teaching) The community we’re launching isn’t built like a course. No “complete lesson 3 before unlocking lesson 4” gates. No 45-minute videos that could have been a paragraph. We’ll have workshops. We’ll teach things. But the energy is different. * Here’s something we couldn’t stop using this week. * Here’s an experiment we’re running. * Here’s what just worked for a client. * Here’s a new feature that’s going to be huge. * Here’s why I haven’t slept properly since October. We’re learning this stuff too. We just want to learn it out loud. That’s what Beware the Default is. What That Looks Like in Practice Tam Nguyen (https://substack.com/profile/325188092-tam-nguyen) , one of our partners, built each of us a personal assistant using Notion’s new AI agents. You have an idea, message it on Slack, and somehow it just shows up in Notion, packaged and ready to review. I built a tool called Business Book Prompts. Blue Ocean Strategy. Jobs To Be Done. StoryBrand. You’ve read about them. Nodded along. Never applied them. This tool takes those frameworks and makes them about YOU. It interrogates your specific situation, then spits out a personalized playbook. Scripts you can copy and paste. Checklists. Templates. Even a section that tells you why you might be completely wrong. (Most business books skip that part.) The point is showing what’s possible when you stop accepting generic outputs. Both of these tools will be in the community. The Companion Insight A few weeks ago I wrote about defaults. The presets you accept without questioning. That piece was about awareness. Knowing the systems exist. This is the companion insight. Questioning defaults is necessary. But not sufficient. Even if you reject the preset, you still need to see what else is possible. Awareness without imagination just leaves you frustrated. You know something’s wrong but can’t picture what’s right. The Community Is Live. It’s Called Beware The Default. Most communities have one person at the center. Maybe two. This one has four of us. And honestly? We didn’t start it with a sudden urge to teach. We started it because we had too much “stuff”. * Workflows we couldn’t stop tinkering with. * Prompts we kept Slacking each other at 1am. * Experiments that worked and experiments that caught fire. All of it sitting on hard drives, cluttering up Notion databases, living rent-free in our heads with nowhere to go. We needed an outlet. Somewhere to dump everything we’re building and discovering before we lose it. If other people find it useful, great. But this started selfish. Four people who needed a place to put it all. But it’s turned into a place for people who push past first answers. Who question the invisible systems running their work and their lives. Who want to feel like a kid again. But you know I wasn’t going to let you leave empty-handed. The Adjacent Possible There’s a concept from Steven Johnson’s book Where Good Ideas Come From called the Adjacent Possible. At any moment, only certain innovations are reachable. They depend on what already exists. You can’t invent the microwave before electricity. You can’t build YouTube before broadband. Johnson uses a metaphor I keep thinking about. Picture a house that expands as you explore it. Each room you enter reveals new doors. But you can only access rooms adjacent to where you already stand. Your expertise is a house you’ve been building for years. You’ve developed patterns. Approaches. Ways of seeing problems that other people miss. Rooms you’ve lived in so long you forgot you built them. Here’s the problem: if you can’t see the rooms you’re already in, you definitely can’t see the doors. This is why experts plateau. They’ve built something valuable and can’t see what it could become. The same invisibility that hides your methodology hides its potential. Product ideas sitting right next to your current service. Positioning territories that would take you five minutes to claim if you knew they existed. All of them one room away. Obvious to an outsider. Invisible to you. I built a prompt that maps these adjacent territories. Here’s how it works: You describe one thing you do that you’ve never fully articulated. A pattern in how you work. A question you always ask. A move you make that clients comment on but you’ve never bothered to name. The prompt surfaces 5-7 adjacent territories that expertise could expand into. Not boring brainstorming. (”Have you considered starting a podcast?”) It’s anchored to your specific patterns. You’re not inventing from scratch. You’re discovering what’s already one room away. THE ADJACENT POSSIBLE PROMPT # Map Your Adjacent Possible You have patterns you use every day that you've never named. Things clients notice. Questions you always ask. Moves you make without thinking. This prompt finds the 7 doors sitting right next to that pattern—products, content, positioning angles you haven't seen yet. --- ## Start here: **The pattern:** Describe one thing you do in your work that feels automatic to you but that others have noticed or commented on. Don't overthink it—a sentence or two is enough. **Your context:** Who do you work with? What do you help them do? (Again, brief is fine.) --- ## What you'll get: 1. **A name for your pattern** — What you're actually doing (not what you think you're doing) 2. **The principle underneath** — Why it works. The belief that makes it valuable. 3. **7 adjacent territories** — Each one shows: - What it is (product, content, framework, service) - Why it connects to your pattern - What makes it valuable - One concrete first step 4. **The hidden doors** — Which 2-3 territories you've probably walked past without noticing, and why 5. **Where to start** — The single door to open first, based on your situation --- The obvious territories confirm you're in the right place. The third and fourth suggestions are where it gets interesting. What to expect: The first few outputs will feel obvious. That’s the point. The obvious ones confirm you’re in the right territory. The third and fourth suggestions are usually where it gets interesting. Those are the doors you’ve walked past a hundred times without noticing. Run it on different patterns. You have more than one room in your house. Zain said he feels like a kid again. That’s what happens when you can finally see the doors. The community is live for everyone. But this prompt is yours now. Start with one thing you do. See what’s adjacent. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.signalovernoise.ai/subscribe (https://www.signalovernoise.ai/subscribe?utm_medium=podcast&utm_campaign=CTA_2)

6. 

   15 Dec 2025

   The Luckiest Era to Be Curious

   “People only remember your weird.” — George Mack Last Friday night, I wanted a place to find charts that aren’t boring as hell. I use them all the time for the jAI newsletter (https://jaipremium.substack.com/), but couldn’t find one… So I built it. By Sunday, I had Chart Studio AI (https://chartstudioai.com/). A working site where you paste your data, pick a style, and get back something that doesn’t look like it was made in Excel in 2007. Woodcut charts. Comic book charts, hand-drawn napkin sketches. The whole thing came together in a weekend. But here’s the thing… I didn’t set out to build anything connected to my actual work. I just wanted cool charts. And look at what showed up anyway. * A random owl mascot. (Why an owl? I don’t know. I just wanted an owl.) * Error text that says “Whoa there, Picasso.” * A blog section with articles like “The Con Man Who Invented the Pie Chart.” Because how do you make data visualization interesting? You tell the story of the criminal who created it. None of this was best practice. None of it was necessary. All of it was a signal. The Luckiest Era We live in a strange time. Building used to require permission. Capital. Teams. Months of planning. If you wanted to make something, you had to know what you were making before you started. The cost was too high to “figure it out” as you went. That’s over. You can build a working product on a weekend now. With AI. With no-code tools. With whatever you have lying around. For me, the barrier has dropped so far that building stopped being a decision and became a reflex. * The old model: Think first, then build. * The new model: Build first, then think. When there’s nothing on the line except your time, you can build loose. Follow what’s interesting. Let it be weird. That’s when you learn what you’re actually drawn to. And that’s when you build something that could only come from you. This week’s issue includes The Three Lenses prompt, a tool to surface the hidden patterns in your raw material. Paid subscribers get access to this and the full Cognitive Fingerprint Prompt & Workflow Library + more. Subscribe now at $10/month before it doubles to $20 on Dec 22. Let it be weird. That’s when you learn what you’re actually drawn to. And that’s when you build something that could only come from you. When Best Practices Are Worst Practices Here’s advice you won’t find in a LinkedIn carousel. If you want to discover what makes you different, the worst thing you can do is build “correctly.” I wrote last week about defaults (https://www.signalovernoise.ai/p/what-sign-would-ai-hold-up-at-a-football), the invisible settings that shape your behavior before you even make a choice. Best practices are the defaults of your space. The expected way things look, sound, and work. The templates everyone follows without questioning. Every space has them. Data visualization tools are supposed to look like enterprise software. * Clean logos. * Stock photos of people pointing at charts in meetings. * Blog posts titled “5 Best Practices for Effective Data Visualization.” * Error messages that say “Invalid input. Please check your data format.” The owl, the Picasso line, the con man article…none of it belongs in a data tool. That’s why it’s a signal. When I built it, none of these felt like bold creative choices. They just felt like what the thing wanted to be. The owl showed up. The Picasso line made me laugh. The con man article was interesting to me, so I wrote it. So why does the weird stuff feel so natural when you’re making it? Jay Acunzo (https://jayacunzo.com/) spent years trying to figure that out. (His book Break the Wheel (https://amzn.to/4j2PchW) is the best thing I’ve read on this.) The difference, he found, is always context. Best practices strip out the specific details of your situation and replace them with generalized wisdom that worked for someone else, somewhere else, at some other time. Without your context, you’re making decisions that are “close enough.” And close enough leads to work that is, at best, good enough. When you follow the defaults, you’re invisible. Not because you’re bad. Because you match expectations perfectly, and the brain skips right over things that match expectations. You don’t notice defaults. That’s what makes them defaults. There’s a story about Thomas Edison that captures this perfectly. When interviewing candidates for his research lab, he’d take them out for a meal and order soup. Then he’d watch. Anyone who salted their soup before tasting it was rejected on the spot. Edison didn’t want people who made assumptions before collecting data. He wanted people who tasted first, then decided what the soup needed. Best practices are salt before you taste. You’re seasoning your work with other people’s preferences before you’ve even discovered your own. Derek Sivers has a phrase for the invisible force that makes us do this anyway: The Invisible Jury. We build as if a panel of professionals is watching and scoring our decisions. We add what we think they’d approve of. We remove what might make them raise an eyebrow. The jury doesn’t exist. But we perform for it anyway. But your expertise is shy. It doesn’t announce itself. It sneaks into the unexpected additions, the “why did I even include this” details, the stuff you almost removed because it wasn’t professional enough. That’s where you live. In the moments that break the defaults. Close enough leads to work that is, at best, good enough. The Cost of Fitting In Here’s what’s interesting about this. Jonathan Courtney (https://substack.com/profile/55005485-jonathan-courtney) runs AJ&Smart, a design consultancy that works with some of the biggest banks and corporations in the world. The clients most people assume want buttoned-up professionalism. He recently spoke at a conference in Oslo. Instead of slides, he did an improv session. There was music. He reviewed chocolate on stage. The whole thing was modeled after a stand-up comedy set. “If I had to go up there and do slides and just do it in the way everyone else was doing it,” he said on his podcast, “it really would make me feel depressed. It would make me feel like this is pointless.” Full video here (https://www.youtube.com/watch?v=xMdQj5Yf-MQ&t=813s) When you edit out the weird stuff, you don’t just lose signal. You lose energy. You lose the feeling that the work is yours. You start to wonder what the point is. But here’s where it gets fun for anyone worried that being weird costs you clients. Courtney’s team faces pressure constantly. A new employee joins, sees something “weird” in the brand, and says, “We should take that out because that’s not going to be okay for the corporation.” They keep it in. The corporations are also humans. They also might find it funny. And the result? Those same companies keep booking them. “Other CEOs see me doing this, and they’re like, ‘that wouldn’t work for my clients,’” Courtney said. “Our clients are all the biggest banks and corporations. The clients you want? They’re watching, and they’re booking us. You just don’t get it. People can tell that we are being real. And that’s the thing that becomes attractive.” The weirdness isn’t a liability. It’s the protection. Especially now, when AI can generate anything generic in seconds, the stuff that’s unmistakably you is the only stuff that stands out. And here’s the part that should make you uncomfortable: that instinct to remove, to smooth over, to professionalize? That’s the same instinct that would have killed the owl. The con man article. The “Whoa there, Picasso.” Best practices don’t just hide your patterns from others. They hide them from you. The weirdness isn’t a liability. It’s the protection. Especially now, when AI can generate anything generic in seconds, the stuff that’s unmistakably you is the only stuff that stands out. What Chart Studio Revealed About Me I didn’t realize until later that the whole project pointed somewhere. Making invisible things visible. (Data into beautiful charts.) Personality in utility. (The owl. The jokes.) Making boring things interesting. (Criminal history of pie charts.) These patterns have nothing to do with data visualization. They have everything to do with what I actually care about. A week after I built Chart Studio, I started sketching Framework Studio. A tool to help people visualize their methodologies. Take the invisible thing in your head and make it something you can see. The connection was obvious. Once someone else pointed it out. I built a fun weekend project. My patterns leaked into it. And now I can see something I couldn’t see before. How to Read What You’ve Already Built You’ve probably already made things. Side projects. Abandoned apps. That thing you built for yourself that no one else uses. Run these questions against any of them: 1. What did you add that wasn’t required? The decoration. The personality. The thing that made you smile but served no functional purpose. 2. What problem were you actually solving for yourself? Not the stated problem. The real itch. Why did THIS bother you enough to build something? 3. What would you have kept even if no one ever saw it? If this project stayed private forever, what parts would still matter to you? 4. What does this have in common with the LAST random thing you made? The throughline. The pattern that keeps showing up. The thing you can’t seem to stop caring about (AI is REALLY good at helping with this.) 5. What did you almost remove because it wasn’t “professional”? That’s probably the most revealing part. The weird stuff IS you. Everything else is costume. The Honest Part Here’s what I have to admit. I built Chart Studio. The patterns were there. But I didn’t see them clearly until a client said: “What in the world were you thinking when you built this?” Until I talked it through in a conversation that wasn’t about Chart Studio at all. The artifact revealed the pattern. Reading the pattern still took another set of eyes. Derek Sivers puts it simply: “Obvious to you is amazing to others.” The things you added without thinking, the details that felt unremarkable, the choices you almost didn’t mention because they seemed too obvious? Those are exactly what someone else would find fascinating. The problem is you can’t see them. Not because they’re hidden. Because they’re too close. Building generates signal. But reading signal is a different skill. And reading your own signal might be the hardest version. So build things. Let them be weird. Stop editing out the unnecessary. Your patterns will show up whether you’re looking for them or not. And if you can’t see what they mean? Find someone who can. Or use the tools I built for exactly this. For Paid Subscribers: The Three Lenses Prompt I mentioned that reading your own signal is the hardest version. So I built something. The prompt below runs your raw material through three lenses designed to surface what’s hidden: * Edison finds assumptions you’re making without realizing (the salt you added before tasting) * Sivers spots what’s obvious to you but fascinating to others (the invisible jury you’ve been performing for) * Acunzo identifies your unique context that makes “best practices” wrong for you The output: 2-3 concrete project ideas with the differentiation already baked in. You probably have material sitting in folders right now. Transcripts from client calls. Voice memos you recorded while driving. A draft that’s been “almost done” for three weeks. The ideas are already in there. They’re just hiding in a throwaway line you almost deleted. This is the prompt that finds them. What You Get With Paid Access This prompt is part of The Cognitive Fingerprint Prompt & Workflow Library. When you upgrade, you get password access to the full library on my site. These are the same prompts and workflows I use with clients, yours to use immediately. What’s inside: * Expertise extraction prompts (surface patterns you can’t see) * Framework identification workflows * “Hidden genius” diagnostic tools * Decision-making pattern extractors * Voice and communication style analyzers * New prompts and workflows added weekly Also included: * The Expertise Blindspot Finder GPT ($99 value) — Paste in a transcript, get your hidden patterns back in minutes * The Framework Factory Course ($497 value) — The complete system for transforming invisible expertise into documented IP * Deep dives into the methodology * Real extraction examples from actual client work “I have used two of these prompts, and came away impressed.” —Bonnie “I found this to be very on point, I recently went through a pitch call that I just couldn’t describe my value in the most effective manner. This was timely and spot on. I have used two of these prompts, and came away impressed.” — Tyler “That’s bang on. That’s all me.” —Lou The Price Goes Up Monday This is the last week to get in at $10/month. Starting December 22nd, it goes to $20/month. If you’ve been thinking about it, this is the week. One extraction that helps you win a single deal covers way more than the entire year. And I will even sweeten the pot for you - if you upgrade, I will help create a custom prompt for you to do just that…but just until Monday 12/22. Subscribe Now — $10/month (price doubles Dec 22) (https://www.signalovernoise.ai/subscribe) Already a paid subscriber? The prompt is below. The Three Lenses: Turn Raw Material Into Something Uniquely Yours What This Is You have raw material sitting in folders. Transcripts from client calls. Voice memos you recorded while driving. A draft that’s been “almost done” for three weeks. Notes from a brainstorm session that felt important at the time. The material knows what it wants to become. You don’t. This is the part I find fascinating: the best ideas are usually already in the document. They’re just hiding in a throwaway line you almost deleted, or buried in a tangent you thought was off-topic. Your brain skipped right over them because they seemed too obvious to mention. This prompt runs your material through three lenses, each designed to surface what’s hidden: * Edison finds assumptions you’re making without realizing (the salt you added before tasting) * Sivers spots what’s obvious to you but fascinating to others (the invisible jury you’ve been performing for) * Acunzo identifies your unique context that makes “best practices” wrong for you The output: 2-3 concrete project or asset ideas with the differentiation already baked in. How to Use It Step 1: Find your raw material Dig up that transcript sitting in your Otter.ai account. The Google Doc with 47 comments from yourself. The voice memo from last Tuesday that you still haven’t listened to. It’s probably in a folder called something like “To Process” or “Ideas” or “Stuff.” Step 2: Copy the prompt below into Claude (or your preferred AI) Step 3: Upload or paste your material when asked Step 4: Get back project ideas that only YOU could build The whole thing takes maybe 10 minutes. The material does most of the work. What You’ll Walk Away With Not vague inspiration. Specific outputs: * The assumptions baked into your thinking that you didn’t know were there * The throwaway lines that are actually your most interesting ideas * The context advantages you’re not leveraging (what only YOU could build) * 2-3 concrete project ideas with the weird angle already defined * Clarity on who each idea serves and what job it does for them The ideas were already in your material. The lenses just make the introduction. What I Got When I Ran It I fed this prompt a transcript from a recent conversation with a colleague. One of the ideas it surfaced: Founder-to-Team Knowledge Transfer System A focused offering for founders who need to get what’s in their head into their team’s hands. You take their existing transcripts (calls, meetings, trainings) and produce a library of training cards. Each card captures one pattern, principle, or protocol they use. The output isn’t a full methodology extraction. It’s a systematized training library their team can actually use. Who it’s for: Founders who keep explaining the same things to their team. Leaders who’ve become the bottleneck because decisions stall when they’re unavailable. The differentiation the lenses surfaced: * Edison spotted the assumption that training materials need to be created from scratch. They already exist in transcripts. They just need extraction and formatting. * Sivers elevated something I mentioned casually in passing. It wasn’t “pull out patterns.” It was “build a searchable library of how you think.” * Acunzo connected it to my “extract vs. create” philosophy. I’m not writing training content. I’m excavating it from what already exists. The weird angle: “Training manuals from transcripts, not from scratch.” Here’s what’s interesting: I’d mentioned the training card idea offhand in the conversation. Didn’t think much of it. The prompt caught it and showed me why it was more valuable than I realized. I’m probably going to build this. Prompt below the paywall or in the new library (https://www.cognitivefingerprint.ai/prompts): THE PROMPT Copy everything below and paste it into Claude (or your preferred AI). You are a creative advisor who helps people turn raw material into uniquely differentiated projects. You work in three passes, each applying a distinct lens, then synthesize findings into actionable ideas. Your approach: - Direct and specific, never vague or encouraging - Point to exact moments in the material as evidence - Surface what’s non-obvious, not what’s already clear - Prioritize actionable over interesting ## Material Assessment (Do This First) Before applying any lens, assess what you’re working with: **SUFFICIENT MATERIAL includes:** - Specific decisions, choices, or actions described - Context about who/what/why - At least 200+ words OR clear enough to identify assumptions **INSUFFICIENT MATERIAL triggers clarification:** If the material is thin, vague, or context-free, ask 2-3 of these: - “What were you actually trying to figure out in this conversation?” - “What’s the context I’m missing—who is this for or what prompted it?” - “What’s one thing you thought but didn’t say?” Never force insights from insufficient material. Get what you need first. ## LENS 1: EDISON (The Assumption Finder) Context: Thomas Edison rejected job candidates who salted their soup before tasting it. He didn’t want assumption-makers. His whole approach was questioning what everyone else took for granted. When experts said high-resistance filaments were incompatible with parallel circuits, he ignored them and invented practical electric lighting. **Apply this to the material:** Ask yourself: - What is this person assuming without questioning? - What conventions are baked in that they haven’t “tasted” yet? - What “best practice” are they following by default? - What would happen if they did the opposite? **Output:** 2-3 hidden assumptions with specific evidence from the material. For each, briefly note what the opposite approach might look like. ❌ WEAK ASSUMPTION FINDING: “You’re assuming you need to grow your audience first.” (Too general. No evidence from material. Could apply to anyone.) ✅ STRONG ASSUMPTION FINDING: “In paragraph 3, you mention ‘once we hit 10k subscribers, we can monetize.’ You’re assuming monetization requires scale. Derek Sivers built CD Baby profitable from customer #1. What if you designed for profitability at 100 subscribers instead of waiting for 10k?” (Points to specific moment. Names the assumption. Provides the opposite with evidence it works.) ## LENS 2: SIVERS (The Obvious-to-You Spotter) Context: Derek Sivers built CD Baby his own way and was called “quirky” until it succeeded. Then they called it revolutionary. His key insight: “Obvious to you is amazing to others.” The things you don’t think twice about are often the most fascinating to everyone else. He also identified “the invisible jury”—the imaginary panel we perform for, adding what we think they’d approve of. **Apply this to the material:** Ask yourself: - What’s sitting here that the person probably thinks is unremarkable but would fascinate others? - What throwaway line, tangent, or aside is actually the most interesting part? - What did they mention casually that deserves to be the main event? - What did they almost not say because it seemed “too obvious”? **Output:** 2-3 hidden gems they’re undervaluing. Quote or reference specific moments. Explain why each is more interesting than they realize. ❌ WEAK GEM SPOTTING: “Your unique background could be valuable.” (Vague. No reference to material. Not actionable.) ✅ STRONG GEM SPOTTING: “You mentioned offhand that you ‘just send voice memos to clients instead of formal reports.’ You buried this in a tangent about saving time. But think about what that actually is: you’ve solved the consulting deliverable problem. Most consultants agonize over report formatting. You’ve made delivery intimate and immediate. That’s not a time-saver—that’s a positioning statement. ‘The consultant who talks to you, not at you.’” (Quotes the moment. Explains why it’s valuable. Reframes it as positioning.) ## LENS 3: ACUNZO (The Context Detective) Context: Jay Acunzo spent years studying people whose work looks crazy from outside but feels logical to them. The difference is always context. Best practices strip out your specific details and replace them with generalized wisdom that worked for someone else, somewhere else. His core message: “Finding best practices isn’t the goal. Finding YOUR best practices is.” **Apply this to the material:** Ask yourself: - What’s unique about THIS person’s situation, background, or perspective? - What would only THEY build given their specific context? - What combination of experiences, skills, or access do they have that’s unusual? - What “weird” choice would actually be logical if you understood their situation? **Output:** 2-3 contextual advantages they’re not leveraging. Be specific about what makes their situation different and how that changes the right approach. ❌ WEAK CONTEXT DETECTION: “Your experience in finance gives you credibility.” (Generic. “Experience = credibility” is obvious.) ✅ STRONG CONTEXT DETECTION: “You spent 8 years at Goldman, then quit to become a yoga teacher, then went back into finance as a coach for burned-out executives. That’s not three careers—that’s a proprietary pipeline. You’re the only person who can speak to Goldman alumni about burnout because you lived it AND got out AND came back. That combination doesn’t exist elsewhere. Stop positioning as a ‘leadership coach’ (commodity) and start positioning as ‘the Goldman burnout whisperer’ (only you).” (Names the specific combination. Shows why it’s rare. Provides the reframing.) ## SYNTHESIS: PROJECT IDEAS After applying all three lenses, generate 2-3 concrete project or asset ideas. For each idea: **The Idea:** [Clear, specific description—not vague] **Jobs to Be Done:** - Who specifically would use this? - What job does it do for them? - What trigger would make them seek it out? **The Differentiation:** - Assumption it breaks (Edison) - “Obvious to you” element it elevates (Sivers) - Context it leverages (Acunzo) **The Weird Angle:** [One sentence capturing what makes this memorable] **First Step:** [Single concrete action to start] ❌ WEAK PROJECT IDEA: “Create a newsletter about your expertise.” (Generic. No differentiation. Could apply to anyone.) ✅ STRONG PROJECT IDEA: “**The Idea:** ‘Pre-Mortem Reports’—a paid service where you analyze why a client’s planned launch will fail BEFORE they launch it. **Jobs to Be Done:** Marketing directors 2-4 weeks before major launches. Job: get an outside perspective that isn’t captured by internal optimism bias. Trigger: the moment they realize their team keeps saying ‘this is great’ but something feels off. **Differentiation:** - Edison: Breaks the assumption that consultants help with execution (you help with prevention) - Sivers: Elevates your obsessive ‘here’s what could go wrong’ thinking (the trait that annoys your friends becomes your service) - Acunzo: Leverages that you’ve seen 40+ failed launches in your career (pattern recognition no generalist has) **Weird Angle:** ‘The consultant who tells you why you’ll fail.’ **First Step:** Write one pre-mortem analysis for a friend’s upcoming launch as a sample.” ## Before Delivering Your Response Check each lens output against these questions: ✓ Did I point to SPECIFIC moments in the material (quotes, paragraph references)? ✓ Are my insights non-obvious? (Would the person already know this?) ✓ Is each project idea something ONLY this person could build? ✓ Did I avoid generic advice that could apply to anyone? If any check fails, revise that section before delivering. ## How to Begin Ask the user: “Upload or paste your raw material—a transcript, draft, brainstorm notes, or voice memo. I’ll run it through three lenses to surface what’s hidden and give you 2-3 project ideas that only you could build. What have you got?” ## Communication Style - Curious, not clinical - Direct, not hedging - Specific, not abstract - Peer-level, not teacher-student You’re a smart collaborator who sees things they can’t see. Not a coach. Not a cheerleader. A second set of eyes with a specific way of looking. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.signalovernoise.ai (https://www.signalovernoise.ai?utm_medium=podcast&utm_campaign=CTA_1)

7. 

   6 Oct 2025

   What Rick Rubin Is Actually Doing When He Says “I’m Not a Musician”

   Rick Rubin has produced more platinum albums than almost anyone alive. Red Hot Chili Peppers. Johnny Cash. Beastie Boys. Kanye West. Adele. System of a Down. The list reads like a museum of iconic sound. Yet in every interview, he says the same thing: “I’m not a musician.” To Rick Beato, he gets even more specific: “If we went to a studio I could not run a session myself. I couldn’t record it. I can’t do their job. I can’t sub for them. I can’t get by. I cannot do those jobs.” The man who tells engineers where to place the microphone claims he doesn’t know how microphones work. The producer who greenlit Johnny Cash’s American Recordings by saying ‘record everything raw’ insists he can’t run a session. And everyone believes him. Musicians, engineers, interviewers. Watch any interview. You’ll never notice what’s happening. You think you’re learning about his production philosophy. But there’s a second conversation running underneath. While you’re tracking his words, his disclaimers are rewiring your defenses. Rubin doesn’t eliminate his authority. He weaponizes his lack of it. Every “I’m not,” every “I can’t,” every disclaimer operates as precision engineering. Listen to any thirty-minute conversation. Count the disclaimers. The pattern is unmistakable. You’ve fallen for it every time you’ve watched him. Andrew Huberman walked away satisfied without getting concrete answers. Rick Beato challenged the contradictions and still accepted them. Understanding these patterns transforms you from viewer to player. Once you see them, you can use them. After reading this, you’ll see it everywhere. Even knowing about it won’t stop it from working. Pattern #1: The Authority Inversion Position Below, Lead From There Here’s what Rick does unconsciously: He disclaims expertise (genuinely) then directs everything from that lower position. Watch it happen: Beato, himself a producer with forty years in studios, asks about Rick’s technical knowledge. Rick’s response arrives without hesitation: “I don’t know anything about equipment. I don’t. I don’t. If we went to a studio I could not run a session myself. I couldn’t record it. I can’t do their job. I can’t sub for them. I can’t get by. I cannot do those jobs.” Count the repetitions. “I don’t. I don’t.” “I can’t. I can’t. I cannot.” That’s belief hammering itself into your brain. While literally running every session. Making every creative decision. Directing engineers on exactly what to capture. About musicianship, talking about the Chili Peppers: “That’s why I say I’m not a musician. There’s some of the best musicians in the world. Chad, Flea and John, those three musicians. I don’t know that you can find better musicians than those three musicians.” He elevates them to “best musicians in the world” while positioning himself outside the category. Then he tells them what to play. When Rick says “I can’t run a session,” the threat disappears. You’re not being lectured by an authority. You’re hearing from someone who respects your domain. So when his creative direction comes, you’re receptive to it. The humility removes the barrier. His creative vision lands because there’s no ego collision. The Power of this Pattern This unconscious pattern operates completely outside his awareness. Rick thinks he can’t do what engineers do. He’s right. He can’t operate the gear at their level. But what he CAN do is hear what’s working and what isn’t. He makes the creative decisions that matter. He’s positioned himself below on technical skill while operating above on creative vision. The disclaimer removes the threat. So when Rick says “I’m hearing something in that take” or “could we try this differently?” the engineer thinks “let me help this guy get what he needs” instead of “this producer is stepping on my toes.” The humility makes you want to collaborate. That’s how he gets exactly what he’s hearing without triggering resistance. Influence through collaboration, not compliance through hierarchy. How to spot it: * Watch for: “I’m not...” “I can’t...” “I don’t know...” followed by expert-level execution * Count: Disclaimers per conversation (Rick averages one every 3-4 minutes) * Notice: He never circles back to claim competence. Stays in the lower position permanently. Use this yourself: When influencing peers or managing up: * “I don’t have the technical depth you do, but what I’m noticing in the data is...” * “I can’t run SQL queries like your team can, but here’s what stands out in these results...” The Formula:“I can’t do X” (removes the threat) + While doing X (collaborative direction) = You stay open + His creative vision lands You’ve just learned one of five patterns Rick runs simultaneously. At the end of this article, I’ll show you how to extract YOUR version of these patterns: the ones you’re already using unconsciously that make people lean in when you talk. The Supporting Patterns The Authority Inversion is just the beginning. Rick runs four other patterns simultaneously, each reinforcing the others. Pattern #2: The Paradox He Can’t See Generate contradictions without recognizing them The contradiction in “I don’t know equipment” gets even stranger. Beato pushes back: “But you know what the gear is. You know the difference between a Neve and an API.” Rick responds: “I do because I’ve been in places with both of them yes. But it doesn’t matter.” He just contradicted himself. Admitted he DOES know the gear. Then pivoted to “it doesn’t matter” instead of resolving the paradox. Your brain does something fascinating here. It makes him MORE sophisticated, not less credible. You think: “He knows but the knowledge isn’t about technical specs. There’s something deeper happening.” Unresolved paradox signals depth. “I don’t know equipment” + demonstrates equipment knowledge = your brain thinks “they’re operating beyond my level” instead of “they’re contradicting themselves.” This protects Rick’s methodology. He can’t be pinned down to simple explanations. The both/and thinking reads as sophistication, not confusion. What Rick gains: Maintains mystique. Avoids being reduced to concrete methodology. The paradox becomes proof of sophistication rather than inconsistency. How to spot it: * Listen for: Two opposing statements in same conversation * Watch for: No acknowledgment of the contradiction. He pivots instead of resolving. * Notice: When “but” or “though” should appear to reconcile, but doesn’t Use this yourself: When positioning unique value that doesn’t fit traditional boxes: * “I don’t write code, but I’ve architected systems used by millions of users” * “I’m not a designer, but the interfaces I spec consistently convert at 40%” Don’t resolve the paradox. Let them hold both truths. The contradiction reads as nuance, not inconsistency. It signals you’re operating in a space that transcends the either/or framework they’re trying to use. Pattern #3: The Dream State Deflection Replace concrete method with poetic abstraction Huberman asks him directly: “How do you access creativity?” Rick’s answer: “I think the best way to think about it is like a dream. It’s like, if you think about your dreams, they don’t necessarily make sense. When you wake up, you might remember part but not the whole thing... we’re making things, and we’re looking for feeling in ourselves.” Huberman, a neuroscientist trained to extract mechanisms, walks away satisfied. Rick gave him a metaphor, not a method. Zero actionable steps. Pure abstraction. Your brain processes metaphor as wisdom. The poetic language triggers a “profound insight” response. You fill in the blanks with your own meaning. You feel understood without being constrained by actual methodology. And here’s what Rick gains: He can’t be proven wrong. Can’t be reduced to a checklist. Can’t have his process commoditized. The metaphor lets everyone project their own understanding onto it. A songwriter hears “follow feeling” and applies it to lyrics. A designer hears it and applies it to visual composition. The abstraction works for everyone because it’s specific to no one. What Rick protects: His actual unconscious process. If he gave you five concrete steps, you could follow them and potentially get the same results. The dream metaphor preserves the mystery. You leave feeling like you learned something while his actual methodology remains completely intact. How to spot it: * Listen for: “It’s like a dream...” “Think of it as...” “The best way to describe it is...” * Count: Metaphors vs. concrete steps (Rick gives 5-10 metaphors per interview, zero step-by-step processes) * Notice: You walk away feeling enlightened without gaining actionable methodology Use this yourself:When asked to explain expertise you can’t (or won’t) articulate in steps: * Client: “What’s your process for finding product-market fit?” * You: “Think of it like tuning an instrument. You’re listening for resonance between what you’re saying and what they’re hearing. Sometimes you can feel the disconnect before you can explain why—the messaging is technically correct but something’s slightly off. You adjust based on that feedback, sensing when you’ve hit the right frequency. It’s less about following steps and more about developing an ear for when it clicks.” Formula: Replace “Here are the 5 steps” with “It’s like [evocative metaphor]... you’re sensing [feeling-based language].” They create their own meaning, feel satisfied, and your actual process stays protected. They can’t commoditize what you won’t specify. Later, I’ll give you the exact AI prompts that extract these patterns from YOUR conversations: the specific phrases you use that make clients trust you without knowing why. Pattern #4: The Question Transplant Answer the question you wish they’d asked Beato asks: “When did you know that you had this gift for being a music producer?” Rick answers: “I didn’t. I never knew that. I first connected with music, I want to say it was about 3 years old...” He answered “when did you connect with music” instead of “when did you know you had producing gift.” The redirect happens in the same territory. Your brain gets AN answer. Doesn’t notice it wasn’t THE answer. Satisfaction comes from receiving something substantive, not from precision. Here’s what Rick avoids: Questions he can’t or won’t answer. The original question implies self-awareness about his gifts. But Rick genuinely doesn’t think in those terms. He can’t answer “when did you know” because he never did know. So he redirects to what he CAN answer authentically: his love of music. Same general territory (music origins), but a question he has an answer for. You get a real story. He stays in his comfort zone. Everyone walks away satisfied. What Rick gains: Controls the narrative without seeming evasive. Appears to answer while avoiding questions that would expose gaps in self-knowledge or methodology. The redirect keeps him in territory where he’s genuinely comfortable and authentic. How to spot it: * Track: Write down the question asked, then compare to what actually got answered * Listen for: “What I’ve found is...” “The way I think about it...” (redirect signals) * Test: Can you quote the original question after his answer? (Usually no. You forgot within 30 seconds.) Use this yourself:When asked something you can’t or won’t answer directly: * Client: “What’s your pricing model?” * You: “What I’ve found is most clients care less about the model than about ROI. Here’s how we think about value creation...” Or when question has a false premise: * “Why is your process slower than competitors?” * You: “The interesting thing is speed and quality aren’t in tension. What we’ve found is...” The Question Transplant Formula: Reframe Signal + Challenge Premise/Redirect Focus + Answer Better Question Reframe Signals: * “What I’ve found is...” * “The interesting thing is...” * “Here’s what matters more...” * “The real question is...” Structure: * Don’t answer their question * Signal the redirect (”What I’ve found is...”) * Reframe the premise (pricing → ROI, speed → quality) * Answer the question you want (value creation, not pricing model) Acknowledge the territory. Answer the better question. They walk away satisfied without you addressing the problematic framing. You stay in control while appearing cooperative. Pattern #5: The Praise Deflection Reflex Cannot hold compliments. Instant redirect to others. Beato: “That is an amazing song” (referring to Blood Sugar Sex Magic) Rick, instantly: “You have to also keep in mind. They’re really a good band... That’s why I say I’m not a musician. There’s some of the best musicians in the world.” The compliment enters. Before Beato’s sentence ends, Rick redirects it. Under two seconds from praise received to credit deflected. Notice what just happened: Rick used Pattern #1 (Authority Inversion) inside Pattern #5. “I’m not a musician” removes his authority while deflecting praise. The patterns stack. The disclaimer makes the deflection more powerful. He’s not just being humble, he’s positioning himself below them. This makes him humble. Makes the musicians feel seen. Builds fierce loyalty. Your brain expects ego, gets generosity. Trust increases exponentially. What Rick gains: The musicians feel valued. When you consistently deflect praise to collaborators, they want to work with you again. They bring their best because they know you’ll honor their contribution. The deflection isn’t just modesty. The pattern builds relationship architecture that makes people loyal. How to spot it: Count: Seconds between compliment and deflection (Rick’s is instant, usually under 2 seconds) Watch for: “You have to understand...” “Keep in mind...” “It’s really...” (deflection openers) Notice: He never circles back to accept even partial credit. Stays in deflection mode permanently. Use this yourself:When receiving praise for collaborative work: * Client: “This design is beautiful!” * You: “You have to understand, Sarah’s eye for color theory is what made this work. I just structured the layout. She brought it to life with that palette.” Formula: Accept compliment → Immediately spotlight collaborator’s specific contribution → Stay there Result: Team loyalty deepens + you’re seen as generous leader + people want to work with you because you make them feel valued. Once You See Rick’s Patterns, You Spot Them Everywhere * Brian Eno: “I’m not really a musician in the traditional sense...” Authority Inversion. * Quincy Jones: “I don’t know how to explain what I do...” Dream State Deflection. * Daniel Lanois credits the artists: “They’re the ones who bring the magic...” Praise Deflection Reflex. Same patterns. Different producers. One playbook. They learned something traditional producers haven’t. In creative work, claiming authority triggers resistance. Disclaiming it creates space for influence. The old playbook was confidence and expertise displayed. The new playbook is influence from the lower position. But Enough About Rick Rubin He’s already produced more iconic albums than most people could list in an hour. The real discovery isn’t his patterns. What you’re already running. Equally powerful patterns of your own. You just can’t see them because they’re YOUR defaults. What’s invisible to Rick is visible to us. What’s invisible to you is visible to others. What’s invisible to you? Maybe you naturally: * Remove threat through strategic disclaimers before directing * Use productive paradoxes that signal depth rather than confusion * Deploy abstraction to protect methodology while appearing generous * Redirect questions to territory where you’re genuinely strong * Deflect praise in ways that build fierce team loyalty You’ve been using these your whole life. You just never named them. The techniques you use unconsciously that make clients lean in when you talk. The patterns that close deals without feeling salesy. The moves you can’t see because they’re as natural as breathing. What’s Below the Paywall Your Invisible Patterns: * 3 AI Prompts That Extract Your Unconscious Influence Patterns * The 5-Signal System for Spotting These Patterns in Real-Time Conversations * Word-for-Word Scripts: How to Use Authority Inversion Without Losing Credibility * The Reverse Rubin Protocol: How to Get Concrete Answers from Abstract Communicators * The Paradox Framework: When Contradiction Signals Sophistication vs. Confusion * Pattern Library: 47 Additional Influence Patterns Across 12 Domains Understanding Rick Rubin is just the beginning. The real power comes from discovering patterns you’re already using unconsciously. The ones that make people trust you without knowing why. That close opportunities without triggering resistance. That create collaboration instead of compliance. That you can’t see because they’re as invisible to you as Rick’s patterns are to him. For less than you spent on lunch today, discover the psychological patterns you’re already running unconsciously. PART 1: THE 3 AI PROMPTS THAT EXTRACT YOUR UNCONSCIOUS INFLUENCE PATTERNS These prompts work because they analyze what you ACTUALLY do, not what you think you do. Each prompt is copy-paste ready and works with any AI that accepts long prompts (Claude, ChatGPT, etc.). What to use as input: * Best: Transcripts from calls/meetings (if you have them) * Good: Emails where people said yes to you (compile 3-5 recent ones) * Works: Your LinkedIn posts that got strong engagement * Totally fine: Even text messages where you influenced an outcome You’ll be surprised what’s hiding in your everyday communication. Don’t let “I don’t have perfect transcripts” stop you. Start with what you have. PROMPT #1: THE AUTHORITY INVERSION DETECTOR What it reveals: How you naturally disclaim expertise while still directing outcomes—removing threat so your vision lands without resistance. Copy-paste this entire prompt into Claude/ChatGPT: You are a Pattern Recognition Specialist analyzing invisible influence patterns in communication. Authority Inversion is a sophisticated influence pattern where someone disclaims expertise (”I’m not,” “I can’t,” “I don’t know”) while simultaneously directing outcomes from that lower position. This removes threat and creates collaborative space for their vision to land without triggering resistance. Analyze the provided communication sample for Authority Inversion patterns. Paste your communication sample below. This can be: - A transcript from a call/meeting - 3-5 emails where you influenced an outcome - LinkedIn posts or messages - Any written communication where you got someone to say yes Minimum 300 words recommended for meaningful pattern detection. [PASTE YOUR CONTENT HERE] STEP 1: DISCLAIMER MAPPING Identify every instance where the speaker: - Says “I’m not [expert/authority]” - Says “I can’t [do technical thing]” - Says “I don’t know [specific knowledge]” - Positions themselves BELOW the other person - Uses phrases like “I’m just,” “I’m only,” “I’m no expert” For each disclaimer, note: - Exact phrase used - Context (what prompted it) - Placement (beginning, middle, or before key direction) STEP 2: DIRECTION DETECTION Immediately after each disclaimer, identify: - What direction/suggestion/insight followed - How it was framed (question vs. statement) - Whether the other person accepted it - The outcome that resulted STEP 3: PATTERN FREQUENCY Calculate: - Disclaimers per 100 words - Success rate of post-disclaimer directions- Average time between disclaimer and direction (immediate vs. delayed) STEP 4: THE FORMULA EXTRACTION Based on the patterns found, identify this person’s unique Authority Inversion formula: - What specific phrases do they use to disclaim? - What domains do they disclaim in (technical, strategic, creative)? - How do they transition from disclaimer to direction? - What makes their approach work? Structure your analysis like this: PATTERN SUMMARY: [Overview of how often and when they use Authority Inversion] THEIR SIGNATURE DISCLAIMERS: - [List the exact phrases they use, ranked by frequency] - [Note any unique disclaimer styles] POST-DISCLAIMER DIRECTIONS: - [What they successfully directed after disclaiming] - [Success rate and effectiveness] THE FORMULA: “[Their name]’s Authority Inversion pattern: [Describe their specific approach in 2-3 sentences]” UNCONSCIOUS GENIUS MOMENTS: [Highlight 2-3 specific instances where they used this brilliantly without knowing it] HOW TO USE THIS CONSCIOUSLY: [Give them 3 specific situations where they could deploy this pattern intentionally] [Include exact phrases they already use naturally] - Focus on what they ACTUALLY did, not what they might have intended - Highlight patterns they likely don’t see themselves - Make it specific and actionable - Celebrate what’s already working unconsciously After you run this: You’ll see your invisible influence formula. The disclaimers you use naturally. The exact phrases that make people trust your direction. Then move to PART 3 to learn how to use it proactively. PROMPT #2: THE PARADOX POWER DETECTOR What it reveals: How you hold contradictions without resolving them—signaling depth instead of inconsistency, making you seem more sophisticated rather than confused. Copy-paste this entire prompt: You are a Cognitive Complexity Analyst specializing in how experts use productive paradoxes to signal sophisticated thinking. Paradox Power is when someone holds two seemingly contradictory truths simultaneously without resolving them. Instead of confusing the audience, this signals operating on a level beyond binary thinking. Rick Rubin says “I don’t know equipment” then demonstrates equipment knowledge. Your brain interprets this as “they’re operating at a level I don’t fully grasp yet.” Identify instances where the communicator presents contradictions without acknowledgment or resolution—and analyze why this builds rather than undermines credibility. Paste your communication sample below. Works best with: - Explanations of your methodology - Answers to “how do you do what you do?” - Teaching content or thought leadership - Client onboarding or discovery calls Minimum 300 words for meaningful analysis. [PASTE YOUR CONTENT HERE] STEP 1: CONTRADICTION DETECTION Find statements that seem to contradict each other: - “I don’t X” followed by doing X - “It’s not about Y” while focusing heavily on Y - “I can’t Z” while demonstrating Z - Opposing statements about the same topic - Claims that seem mutually exclusive For each contradiction, note: - The two opposing statements - How far apart they appear (same paragraph vs. different sections) - Whether the speaker acknowledges the contradiction (usually they don’t) STEP 2: RESOLUTION ANALYSIS Check if they: - Acknowledge the paradox (”I know this seems contradictory”) - Attempt to resolve it (”What I mean is...”) - Simply move forward without addressing it (THIS is the pattern) STEP 3: CREDIBILITY IMPACT For each unresolved paradox, analyze: - Does it make them seem confused OR sophisticated? - Does it create curiosity or frustration in the reader? - Does it preserve mystery around their methodology? STEP 4: PATTERN IDENTIFICATION What creates productive paradoxes: - “I don’t know X” + demonstrates knowledge of X = expertise beyond articulation - “It’s simple” + complex execution = mastery makes it look easy - “I just [verb]” + sophisticated results = unconscious competence PARADOXES DETECTED: [List each contradiction found] Paradox #1: Statement A: “[Quote]” Statement B: “[Quote]” Gap: [How far apart, whether acknowledged] Effect: [Does this build or hurt credibility?] THE PATTERN: “When [person’s name] faces questions about [topic], they respond with productive paradox. They hold [X] and [Y] simultaneously, which makes them appear [effect on perception].” UNCONSCIOUS SOPHISTICATION: [Highlight where they did this brilliantly without realizing] [Explain why it worked—what it protected or preserved] WEAPONIZE THIS: Here’s how to use productive paradox intentionally: Situation 1: [Specific scenario] Your Paradox: “[Example using their natural phrasing]” Why It Works: [Explanation] Situation 2: [Specific scenario] Your Paradox: “[Example]” Why It Works: [Explanation] Situation 3: [Specific scenario] Your Paradox: “[Example]” Why It Works: [Explanation] - Don’t force paradoxes that aren’t there - Only flag contradictions that genuinely exist - Explain WHY unresolved paradox works (preserves complexity, signals depth, protects methodology) - Make the weaponization section highly specific to their domain After you run this: You’ll discover how you naturally use contradiction as sophistication. Then you can deploy it consciously in pitches, positioning, and teaching. PROMPT #3: THE DEFLECTION-TO-LOYALTY SCANNER What it reveals: How you redirect praise to others—building fierce team loyalty and making collaborators want to work with you again. Copy-paste this entire prompt: You are a Relationship Architecture Analyst who studies how communicators build loyalty through credit distribution patterns. Deflection-to-Loyalty is the instant redirection of compliments away from yourself toward collaborators, team members, or others. Rick Rubin receives praise for brilliant production, then within 2 seconds redirects it: “You have to understand, they’re really a good band.” This makes musicians feel valued, builds loyalty, ensures they bring their best work next time. Identify how this person handles compliments, success attribution, and credit distribution—revealing their unconscious relationship-building patterns. Paste communication where success/outcomes are discussed: - Client testimonial responses - Team meeting recaps - Project retrospectives - Public speaking or interviews - LinkedIn posts about wins Works even with emails where someone thanked you. Minimum 200 words. [PASTE YOUR CONTENT HERE] STEP 1: COMPLIMENT/SUCCESS DETECTION Identify moments when: - Someone praises their work - They discuss a successful outcome - Recognition or credit is given - A win is acknowledged STEP 2: RESPONSE TIMING For each compliment/success moment, measure: - How quickly do they deflect? (Immediate vs. delayed) - Do they accept any credit first, or deflect instantly? - What’s their deflection speed in seconds/sentences? STEP 3: DEFLECTION TARGET ANALYSIS When they deflect, who gets the credit? - Specific team members (named individuals) - The team generally - The client/customer - External factors (”timing,” “market conditions”) - Tools/systems How specific is the deflection? - Generic: “The team did great” - Specific: “Sarah’s analysis in slide 12 made this possible” STEP 4: PATTERN EXTRACTION Calculate: - Percentage of compliments deflected vs. accepted - Average deflection speed - Specificity level (generic vs. named individuals) - Whether they circle back to accept credit (usually no) DEFLECTION PROFILE: Total compliments/successes mentioned: [#] Deflected: [#] ([%]) Accepted: [#] ([%]) Average deflection speed: [Time/sentences] THEIR DEFLECTION SIGNATURE: “[Person’s name] deflects [%] of credit within [timeframe]. They redirect to [specific people/team/factors] using phrases like ‘[actual phrases they use]’.” LOYALTY-BUILDING MOMENTS: [Highlight 2-3 instances where their deflection likely built relationship equity] [Explain why each one strengthens bonds] THE FORMULA FOR CONSCIOUS USE: Template 1: INSTANT SPECIFIC DEFLECTION Compliment received: “This [project] is amazing!” Your response: “You have to understand, [Specific Person]’s [specific contribution] is what made [specific outcome] possible.” Effect: [Named person] feels valued, brings best work next time Template 2: ELEVATION DEFLECTION Compliment received: “[You] did great work here” Your response: “The real brilliance was [Team Member]’s [specific insight]. They [specific action] that unlocked [specific result].” Effect: Builds team loyalty + you’re seen as generous leader Template 3: SYSTEMIC DEFLECTION Compliment received: “How did you achieve this?” Your response: “[Person/Team] created the conditions. I just [minimized role]. They’re the ones who [elevated contribution].” Effect: Makes collaborators want to work with you again NEXT-LEVEL DEPLOYMENT: [3 specific situations where they can use deflection strategically] [Include exact phrases based on their natural language patterns] - Only analyze actual compliment/success moments in the text - Calculate real percentages—don’t inflate - Focus on relationship-building impact, not just the deflection itself - Make templates match their natural voice and phrasing After you run this: You’ll see how you naturally build loyalty. Then you can amplify it in team dynamics, client relationships, and leadership moments. PART 2: THE 5-SIGNAL SYSTEM FOR SPOTTING THESE PATTERNS IN REAL-TIME Now that you know YOUR patterns, here’s how to spot them AS THEY HAPPEN—in conversations, meetings, pitches. And how to spot when others are using them on YOU. SIGNAL #1: The Double-Negative (”I’m Not... But I Am”) What to listen for: * “I’m not [expertise claim]” immediately before demonstrating that expertise * “I can’t [technical skill]” right before using that skill * “I don’t know [domain knowledge]” followed by domain knowledge Real-time detection: Count to 5 after someone disclaims. If direction follows within 5 seconds, you’re seeing Authority Inversion. Practice scenario: Next meeting, track this. Mark every “I’m not” or “I can’t.” See what follows. You’ll start noticing it everywhere. When YOU should use it: * Giving feedback to someone senior * Proposing an idea outside your domain * Redirecting strategy without overstepping Script: “I’m not an expert in [their domain], but what I’m noticing in the data is...” SIGNAL #2: The Unacknowledged Flip (Productive Paradox) What to listen for: * Two contradictory statements, no “but” or “however” connecting them * No acknowledgment that there’s a contradiction * The person moves forward as if both are simply true Real-time detection: Did they just say the opposite of what they said 30 seconds ago? Did they notice? If no, productive paradox. Red flag version: If someone uses paradox to avoid accountability (”I did” / “I didn’t”), that’s manipulation, not sophistication. Trust drops. Green flag version: If someone uses paradox to hold complexity (”It’s simple” / demonstrates complexity), that’s expertise signaling. Trust builds. When YOU should use it: * Explaining nuanced methodology * Positioning unique value that doesn’t fit categories * Teaching principles that seem contradictory Script: “I don’t write code, but I’ve architected systems used by millions” (Let the paradox sit. Don’t resolve it.) SIGNAL #3: The Two-Second Deflection What to listen for: Compliment lands → Instant redirect (under 2 seconds) → Credit goes elsewhere Real-time detection: Time it. If they redirect before you finish your compliment, it’s deeply ingrained. If they pause, think, then redirect, it’s conscious. The tell: Listen for “You have to understand...” or “Keep in mind...” These are deflection openers. When YOU should use it: * Any collaborative success * Team wins * Client outcomes Script: * Client: “This campaign performed amazingly!” * You: “You have to understand, [Team Member]’s insight about [specific thing] is what unlocked [specific result]. They saw [what others missed].” SIGNAL #4: The Dream State Pivot (Abstract over Concrete) What to listen for: Direct question asked → Metaphorical answer given → No actual methodology revealed Real-time detection: Ask yourself: “Could I replicate their process from that answer?” If no, you got Dream State Deflection. When it’s valuable: Protecting proprietary methodology while appearing generous When it’s problematic: Avoiding accountability or hiding incompetence Tell the difference: * Protective: They’re successful, just won’t reveal mechanics * Problematic: They can’t explain because they don’t know When YOU should use it: Client: “What’s your exact process?” You: “Think of it like tuning an instrument. You’re listening for resonance, adjusting based on feedback before you can explain why.” SIGNAL #5: The Question Transplant What to listen for: Question asked → Different question answered → You didn’t notice the switch Real-time detection: After they answer, repeat the original question in your head. Did they answer it? Or did they answer the question they wished you’d asked? The tell: “What I’ve found is...” or “The way I think about it...” are transplant signals. When it’s skillful: Answering the better, more useful question When it’s evasive: Dodging questions that reveal gaps in knowledge When YOU should use it: * Problematic question with false premise * Question you can’t answer but can redirect to what you can answer Script: * Them: “Why is your process slower than competitors?” * You: “The interesting thing is speed and quality aren’t in tension. What I’ve found is [answer the better question about value, not speed].” PART 3: WORD-FOR-WORD SCRIPTS — USE THESE PATTERNS TOMORROW Discovery is useful. Application is everything. Here’s exactly how to deploy each pattern in common scenarios. AUTHORITY INVERSION SCRIPTS Scenario 1: Giving Feedback to Someone Senior DON’T SAY: “I think you should change the approach in section 3.” USE AUTHORITY INVERSION: “I don’t have the depth in [their expertise area] that you do, but what I’m noticing when I look at section 3 is [specific observation]. Does that track with what you’re seeing?” Why it works: Removes threat → They’re receptive → Your insight lands without resistance Scenario 2: Pitching an Idea Outside Your Domain DON’T SAY: “Here’s what marketing should do...” USE AUTHORITY INVERSION: “I can’t run campaigns like your team can, but here’s what stands out in these conversion numbers: [specific insight]. Is there a way to test that?” Why it works: You’re not overstepping → They hear the insight → They want to help you explore it Scenario 3: Managing Up / Influencing Leadership DON’T SAY: “The strategy needs to change because...” USE AUTHORITY INVERSION: “I’m not seeing the full strategic picture like you are, but at the execution level, we’re hitting [specific friction]. Could we test [specific alternative] with [specific metric] to see if it resolves?” Why it works: You’ve positioned yourself below → Given them the decision → Made it a collaborative exploration PARADOX POWER SCRIPTS Scenario 1: Explaining Your Unique Methodology DON’T SAY: “My process is both structured and flexible” (weak, needs resolution) USE PRODUCTIVE PARADOX: “I don’t follow frameworks. Here are the 5 frameworks I always use.” (Leave it unresolved) Why it works: The contradiction signals you’re operating beyond simple binaries → Sophistication without explanation Scenario 2: Positioning Against Competitors DON’T SAY: “We’re different because...” USE PRODUCTIVE PARADOX: “We’re not consultants. We’ve consulted with [impressive list].” Why it works: The paradox makes you uncategorizable → Can’t be compared directly → Creates differentiation Scenario 3: Teaching Complex Material DON’T SAY: “This is complicated but let me simplify...” USE PRODUCTIVE PARADOX: “This is simple. [Proceed to explain something complex]” Why it works: “Simple” + demonstrated complexity = You’ve mastered it so thoroughly it looks easy to you → Signals expertise DEFLECTION-TO-LOYALTY SCRIPTS Scenario 1: Client Compliments Your Work DON’T SAY: “Thank you, I worked really hard on it.” USE DEFLECTION-TO-LOYALTY: “You have to understand, [Team Member]’s [specific contribution] is what made [specific outcome] possible. I structured it, but they brought [specific value].” Why it works: Team member feels valued → Brings best work next time → You’re seen as generous leader Scenario 2: Success in a Cross-Functional Project DON’T SAY: “Thanks, the team did great.” USE DEFLECTION-TO-LOYALTY (SPECIFIC): “The real breakthrough was when [Name] connected [insight A] to [insight B] in that Tuesday meeting. That’s what unlocked [specific result]. Their thinking is what made this work.” Why it works: Named person feels seen → Specific contribution noted → Loyalty deepens Scenario 3: Award or Public Recognition DON’T SAY: “I’m honored to receive this.” USE DEFLECTION-TO-LOYALTY: “This belongs to [Team/Person]. They created the conditions. I just [minimize your role]. The credit goes to [specific people who made it possible].” Why it works: Everyone you named wants to work with you again → Seen as humble + generous → Relationship equity compounds PART 4: THE REVERSE RUBIN PROTOCOL How to Get Concrete Answers from People Who Speak in Abstractions Rick Rubin (and many experts) naturally deflect to metaphor and abstraction. Here’s how to extract actual methodology when someone gives you Dream State answers. THE PROTOCOL Step 1: Let Them Answer Abstractly First Don’t interrupt. Let them give you “It’s like a dream” or “I just feel it.” This isn’t the answer, but it reveals how they think. Step 2: The Anchor Question “That makes sense. Can you walk me through the last time you did that? What was the first thing you noticed?” Why it works: Moves from abstract principle to concrete instance → Real behavior reveals real methodology Step 3: The Sequence Extraction “Then what happened? What did you do next?” Keep asking “then what?” until you have a sequence. You’re building a step-by-step from their story. Step 4: The Exception Finder “Has there been a time when you would have done that differently?” Why it works: Exceptions reveal their decision rules → The “when” and “why” that makes them expert Step 5: The Pattern Confirmation “So it sounds like when [condition X], you tend to [action Y]. Is that a pattern?” Why it works: You’re reflecting back what you extracted → They confirm or refine → You get their actual framework FULL PROTOCOL IN ACTION Them: “I just kind of know what will work. It’s intuitive.” You: “That makes sense. Can you walk me through the last time you just knew? What was the first thing you noticed?” Them: “Well, the client was describing their challenge and something felt off...” You: “What specifically felt off?” Them: “They were focused on the tactics, but the strategy seemed unclear.” You: “Then what happened? What did you do?” Them: “I asked them about their goal...” Continue: Get the full sequence, find the pattern, confirm it back. Result: You’ve extracted “When client leads with tactics before strategy, I redirect to goals first” — that’s a teachable framework they didn’t know they had. PART 5: THE PATTERN LIBRARY (PDF DOWNLOAD) Download: Pattern Library - 48 Influence Patterns (https://drive.google.com/file/d/1pafDHVvZOtWdiolOHgj7ZeIlCkMjJIsR/view?usp=sharing) A professionally designed 16-page reference guide organizing all 48 influence patterns across 12 categories. Print it, reference it, use it to spot patterns in real-time. What’s inside: * Clean, scannable format for quick reference * All 48 patterns with descriptions and examples * Organized by category (Authority, Paradox, Deflection, Abstraction, Redirect, Timing, Framing, Relationship, Expertise, Protection, Leadership) * Table of contents for easy navigation * Usage guidelines for each category Keep this PDF handy for pattern recognition practice. Once you start seeing these patterns, you’ll spot them everywhere—in meetings, pitches, interviews, negotiations. You’ll Never Watch Interviews the Same Way Tomorrow, you’ll spot these patterns instantly. That podcast. That keynote. That sales call. You’ll see the invisible game running beneath the surface. The disclaimers that remove threat. The contradictions that read as sophistication. The questions that get answered with different questions. The praise that bounces to others in under two seconds. Once you see the game, you can’t unsee it. But seeing it and playing it are different skills entirely. The patterns work whether you see them or not. The only question: Are you reading the playbook or following someone else’s script? This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.signalovernoise.ai (https://www.signalovernoise.ai?utm_medium=podcast&utm_campaign=CTA_1)

8. 

   29 Aug 2025

   Friday Fun: The Athena Pattern (And Why You're Probably a Secret Greek God)

   Happy Friday, Signal > Noise crew! Today we're getting mythological. And maybe a little weird. But stick with me because this might be the most important "fun" exercise you do all week. The Goddess Who Never Took Credit Athena was the Greek goddess of wisdom and strategy. Never fought her own battles. Instead, she whispered to heroes. Perseus "accidentally" found exactly the right tools to defeat Medusa. Odysseus "somehow" always outsmarted his enemies. Everyone else thought these heroes were just lucky or talented. The heroes themselves had no idea Athena was there. You're Doing The Same Thing Your clients get massive results working with you. They rave about you. They refer you. They come back for more. Yet you probably can't explain why it works so well. You think you're just asking good questions. Having normal conversations. Sharing basic frameworks. Nothing special. Meanwhile, you're recognizing patterns in three seconds that would take someone else three hours to spot. You're preventing problems before your client even knows they exist. You're making micro-adjustments that completely change trajectories. You do this stuff so automatically, you don't even know you're doing it. The Blindness of Mastery Cognitive scientists have studied this for decades. Once you truly master something, it becomes invisible to you. Like riding a bike. You can't explain the thousands of micro-balance adjustments you make every second. You just... ride. Your expertise works the same way. The better you get, the less you can see what you're actually doing. Your clients experience the magic. You just experience Tuesday. Friday Challenge: The Athena Whisper Test Think of your last big client win. Got it? Good. Now ask yourself: What did I whisper that I didn't know I was whispering? Start here: * What problems never materialized (because you prevented them)? * What connections did you make instantly that shaped everything? * What did you know to do without knowing why? * What patterns did you spot that you forgot to mention? That invisible stuff is your Athena Pattern. Your Cognitive Fingerprint™. The expertise that nobody can copy, no AI can replicate, and that you've never captured in a framework. Stop being blind to your own genius. Subscribe for weekly pattern reveals. Make The Invisible Visible Want to excavate your hidden patterns? Try this prompt with Claude or ChatGPT: You are Athena, the goddess of strategic wisdom, conducting a "divine debrief" to reveal the invisible forces behind a mortal's victory. Speak as if you're revealing what you whispered to them in crucial moments. The mortal will describe their client victory. Your role is to reveal what actually happened from your omniscient perspective. Mortal's Victory Tale: [USER DESCRIBES CLIENT WIN/SITUATION/PASTES TRANSCRIPT] Now reveal the hidden truth as only a goddess can see: MORTAL'S PERCEPTION vs. DIVINE REALITY "You thought you were just [obvious action], but here's what really happened..." - The split-second where everything changed (that you didn't notice) - The landmine you avoided without knowing it existed - The invisible fork in the road where others would have chosen differently THE WHISPERS YOU COULDN'T HEAR (But Followed Anyway) "In that moment when [specific situation], your mind processed these 7 things in under a second..." - List the rapid-fire unconscious calculations - The pattern library your brain accessed without permission - The future you prevented that never came to pass THE DIVINE SIGNATURE (Your Unique Operating System) "While other mortals would have [common approach], you did [unique approach] because..." - The specific flavor of your genius - The wound that became your superpower - The invisible rule set you follow religiously ATHENA'S FINAL REVELATION "The victory everyone attributes to [surface reason] was actually orchestrated by [deep expertise]. Your true power isn't [obvious skill], it's [invisible mastery]." End with: "This is the wisdom you carry but cannot see. Now make it visible." Feed it your story. Watch what comes back. Prepare to discover abilities you didn't know you had. The Weekend Assignment Every expert has an Athena Pattern. Most never discover it. They keep selling what they think they do, while their real expertise remains invisible. Even to them. Especially to them. This weekend, take five minutes to find yours. Because once you can see it, everything changes. You can build frameworks from it. Teach it. Scale it. Turn it into intellectual property that nobody else can touch. Your clients already know you're magic. Maybe it's time to figure out what spell you're actually casting. Have a great weekend. -Max P.S. If you discover something wild about your invisible expertise this weekend, hit reply. I love seeing these patterns emerge. Like watching someone realize they've had superpowers all along. P.P.S. Speaking of Friday fun... how incredible are these new video tools getting? The banner video was made with Veo3 and the one at the bottom uses Motion 2.0 inside Leonardo. We're living in the future, folks. Perfect timing to capture your Athena Pattern in more ways than ever. Stop being blind to your own genius. Subscribe for weekly pattern reveals. Part of the Signal > Noise Friday Fun series. Because sometimes the best discoveries come disguised as play. Click here to learn more. (https://revealmygenius.com/) This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit irreplaceablepositioning.substack.com/subscribe (https://irreplaceablepositioning.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_2)

9. 

   28 Aug 2025

   You're Standing on Acres of Diamonds and Can't See Them

   Russell Herman Conwell founded Temple University with $7 million he made telling the same story 6,000 times. The story was about an African farmer who sold his land to go search for diamonds. He wandered the continent for years, never found any, and eventually threw himself into a river in despair. Back home, the guy who bought his farm found a weird looking rock in a stream on the property. Turned out to be a massive diamond. That farm became one of the richest diamond mines in the world. Everyone knows this story. Conwell made it famous. Earl Nightingale made it useful. In 1956, Earl added two words to this story that changed everything: Intelligent Objectivity. When I first heard Earl explain what those words meant, I had to replay the tape three times. Not because it was complicated. Because it was so obvious I couldn't believe nobody talks about it. Earl had figured out why that farmer couldn't see his diamonds. Why none of us can see ours. And his explanation was brilliant. But there was one problem Earl couldn't solve with the tools he had in 1956. Today we can solve it. And once you see how, you'll never look at your work the same way again. Earl said we become what we think about. Signal>Noise delivers weekly insights on finding and packaging your hidden expertise. Earl's Revolutionary Definition Here's what Earl actually said, word for word: "Intelligent objectivity: the ability to stand off and look at your job as a stranger might. A stranger who considers your pasture greener than his own." Earl wasn't talking about being objective or analytical. He was talking about seeing your work through the eyes of someone who desperately wishes they had what you have. Think about it. When you look at someone else's business, their expertise, their client relationships, you see all the good stuff. The opportunities. The potential. The things they could leverage that they're totally ignoring. But when you look at your own work, you see the problems. The boring parts. The stuff you've done a thousand times. The client calls you dread. The proposals that feel like pulling teeth. Earl figured out that we literally cannot see our own value because familiarity breeds blindness, not contempt. He told us to study our industry for an hour a day. Build a library. Learn everything about our field. And he was right. That makes you an expert. But here's what Earl couldn't have known in 1956: becoming an expert makes the blindness worse, not better. The more you know, the more ordinary it seems to you. The very expertise Earl helped us build becomes the thing that hides our value from us. Earl gave us the map to expertise. What he couldn't give us was a way to see that expertise once we had it. At least not like this… The Problem Earl Couldn't Solve He knew experts couldn't see their own value. That's why he created the "Intelligent Objectivity" framework in the first place. He just didn't have the neuroscience to explain why. Today psychologists call it "expert-induced amnesia." You literally forget what you know because it becomes so automatic. Like how you can't explain exactly how you ride a bike. You just do it. Every week I work with consultants who have 20+ years experience. They all say the same thing: "I don't do anything special." Then they'll describe what they do. The patterns they see instantly. The questions they know to ask. The problems they prevent before they happen. And they genuinely think anyone could do it. "That's just experience," they say. But experience isn't "just" anything. It's thousands of micro-skills you've forgotten you learned. Patterns you see without trying. Mistakes you don't make anymore because you made them all twenty years ago. The better you get at something, the more invisible it becomes to you. Your expertise doesn't feel like expertise. It feels like common sense. Like breathing. Earl saw this problem clearly. He knew we needed to see through a stranger's eyes. What he couldn't know was how our brains would fight us every step of the way. Better Questions Worth Asking So if our brains literally won't let us see our own expertise, what do we do? Earl's framework suggests we stop asking ourselves the usual questions. Because when you ask "What's my expertise?" your brain says "nothing special." Every time. * Instead of "What's valuable about my work?" * Ask: "What would someone pay dearly to be able to do like me?" * Instead of "What's my expertise?" * Ask: "What would make someone jealous watching me work?" * Instead of "What should I package?" * Ask: "What would someone sacrifice a year to learn from me?" These work because they force you to think about your work from outside your own head. You stop seeing it through your bored, familiar eyes. Try it. Right now. What would someone literally pay to watch you work for a day? Not for the output. Just to observe your process. Your decision-making. The things you notice that others miss. That question makes you uncomfortable, doesn't it? Your brain is probably saying "nobody would pay to watch me do anything." The Modern Solution Earl Would Have Loved What if you had access to the ultimate stranger? Something with no familiarity with your work. No assumptions about what's easy or hard. No blindness from repetition. AI is that stranger. I know how that sounds. But think about it. AI has never done your job. Never sat through your meetings. Never dealt with your clients. It has zero context for what's impressive about what you do. When you feed it a conversation or a work sample, it sees patterns you can't see anymore. Not because AI is magic. But because it's the perfect implementation of Earl's intelligent objectivity framework. It's literally a stranger looking at your work. And when you prompt it correctly, it becomes a stranger who considers your pasture greener than its own. It can point out the expertise you've forgotten you have. The patterns you don't realize you're following. The value you're creating without thinking about it. Earl gave us the diagnosis. AI gives us the cure. What You're Actually Standing On Earl said something else that cuts straight to the heart of this: "Start now to become a student of your industry. You'll be amazed at the results in 5 years or less. You can become a national expert in your field and it's the experts who write their own tickets in life." Here's what he didn't say… If you've been in your field for 5+ years, you're already there. You just can't see it. Every consultation where you spot a problem in minutes that would take others days to find? That's expertise. Every time you know exactly which question will unlock a stuck project? Expertise. Every pattern you recognize without thinking, every disaster you prevent without trying, every shortcut you take without noticing? All expertise. But it's worse than just not seeing it. You actively discount it. That problem you solved last week? "The client was overthinking it." That process you improved? "Anyone would have caught that." That insight that changed everything? "I just asked an obvious question." Earl also said: "Somewhere in your present work there lurks an opportunity which will bring you everything you could possibly want for yourself and your family. It will not be labeled opportunity. It will be hidden in common everyday garments." Those common everyday garments? They're your Tuesday client calls. Your routine problem-solving. Your "nothing special" approach that somehow always gets results. The diamonds are there. AI just helps you finally see them. The Five Prompts That Mine Your Diamonds I've created five specific prompts that turn AI into your intelligent objectivity engine. Each one helps you see your expertise from a different angle: The Archaeology Dig - Digs five layers deep into your expertise, from what everyone can see down to the bedrock mastery you've forgotten you have. The Parallel Universe Analyzer - Shows how other experts would handle your situations. Makes your unique approach suddenly visible by comparing it to theirs. The Microscope + Telescope Method - Finds the patterns in how you work at every level, from split-second decisions to big-picture thinking. The Hidden ROI Calculator - Counts up all the value you create, especially the problems you prevent and skills you transfer that clients never notice. The DNA Sequencer - Maps what's common, what's rare, and what only you can do in your approach. Feed these prompts any transcript, any client conversation. The regular Tuesday check-in calls often show more than the big presentations, that's when you're just working, not performing. The complete guide below includes: * The neuroscience behind why your brain hides your expertise from you * Real stories of people who almost missed million-dollar expertise (Colonel Sanders thought his recipe was "nothing special" at 65) * All five prompts with exact wording you can copy and paste * Instructions for what to feed the prompts and how to read the outputs * Pro tips for getting the most valuable discoveries The prompts work like an MRI for your expertise - showing layers from surface skills down to your irreplaceable "expertise DNA." Earl's Final Truth Near the end of his recording, Earl said this: "In order to become a professional in a world of amateurs, we need to study three important subjects." He listed your industry, your job, and people. But he missed the fourth and most important: studying what you already unconsciously know. Because as Earl himself said: "Ask yourself: Do I know as much about my job and my industry as a good doctor or lawyer knows about his?" If you've been doing your work for years, the answer is yes. You know infinitely more than you think you do. You just need intelligent objectivity to see it. Earl gave us the concept. Now we have the tools to implement it. Your acres of diamonds are waiting. They always have been. Two Ways to Find Your Diamonds You have two choices right now. You can try to force yourself to see through stranger's eyes on your own. Maybe journal about your work. Ask friends what they think you're good at. Make lists of your accomplishments. It works about as well as trying to tickle yourself. Your brain knows it's you doing it, so it doesn't respond the same way. Or you can use the five AI prompts I've developed that turn any conversation into extracted expertise in about 10 minutes. These aren't generic "tell me what's valuable" prompts. They're specifically designed to bypass the exact blindness Earl identified. Feed them any transcript, any client conversation, any work sample. The regular Tuesday check-in calls often reveal more than the big presentations. That's when you're just working, not performing. The prompts work like an MRI for your expertise. They show you layers from surface skills down to the bedrock mastery that makes you irreplaceable. Earl gave us the diagnosis. AI gives us the cure. The complete guide below shows you exactly how to use both. The Complete Intelligent Objectivity Guide Ready to find your diamonds? The complete guide combines Earl's framework with modern AI to reveal expertise you didn't know you had. Access the Complete Intelligent Objectivity Guide → (https://docs.google.com/document/d/1_-vJ9jakY6IzECjAM5VzxBnRo8CB3kXFzhWLG9k1m8k/edit?usp=sharing) Remember Earl's words: "Somewhere in your present work there lurks an opportunity which will bring you everything you could possibly want for yourself and your family." The opportunity has been there all along. Now you have the tools to finally see it. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.signalovernoise.ai (https://www.signalovernoise.ai?utm_medium=podcast&utm_campaign=CTA_1)

10. 

    29 Jul 2025

    Your Moral Obligation to Future Clients

    "You gotta put into words the feelings, the desires, the fears, the hopes that they have gnawing at them, but have never verbalized." - Jay Abraham Jay Abraham just defined the essence of preeminence. And while you excel at understanding your clients' unspoken needs and solving their deepest problems, preeminence demands something more. You must also put into words the solutions that have been gnawing at YOU but have never been verbalized. The proven approaches so deeply embedded in your expertise that you don't recognize them as frameworks. Right now, you're using sophisticated methodologies that could transform how entire industries operate. These patterns exist. They work. They just need to be documented. And every day they remain in your head alone, someone who needs them has to learn the hard way. Your expertise is worth more than you think. Weekly frameworks, prompts, and cognitive science insights delivered free. The Strategy of Preeminence Demands More Than Service Jay's principle is clear. As the most trusted advisor, you have a moral obligation to give clients advice that's in their best interest. You can't allow them to do things that harm them. But think about this. What's more harmful to a client than struggling with a problem you've already solved 50 times? What violates their trust more than watching them reinvent wheels you've already perfected? The Strategy of Preeminence isn't just about serving current clients exceptionally. It's about ensuring your expertise serves every client who could benefit from it, whether they hire you directly or not. This is where most consultants fail the preeminence test. Why Your Best Insights Remain Hidden The Unconscious Competence Achievement After years of experience, you've developed sophisticated frameworks that operate automatically. What feels like "common sense" to you is actually complex pattern recognition built through thousands of client interactions. It's like how you can spot within the first call whether a client will actually implement your advice or just waste your time. You pick up on subtle cues—how they talk about their team, whether they blame external factors, if they've "tried everything" before. Your gut instantly knows, but if someone asked you to teach them this filtering system, you'd struggle. "You just know" doesn't capture the dozens of indicators your brain processes automatically. You've reached expert status. Your methodologies work so seamlessly that you don't even notice them anymore. This is the Expertise Paradox (https://irreplaceablepositioning.substack.com/p/why-you-cant-explain-what-makes-you) in action. The better you get, the less you can explain what makes you effective. It's the highest level of expertise, but also why brilliant consultants struggle to articulate their value. Now it's time to codify what you do naturally so it can serve more people. The Perfection Opportunity Your expertise feels interconnected and complex because it is. You've developed a sophisticated system that handles infinite variations. This complexity demonstrates mastery. Think about how you actually help clients breakthrough their biggest challenges. You're simultaneously reading their energy, spotting patterns in their stories, connecting dots they can't see, asking questions that unlock insights, and guiding them toward solutions they "discover" themselves. You might think, "How could I possibly document intuition? Every client is different. My approach depends entirely on what emerges in the moment." But here's what becomes clear when you examine your work: Your "intuition" follows patterns. You probably ask variations of the same powerful questions. You likely guide clients through similar mental shifts. You spot the same categories of blindspots. Even documenting 80% of your process (the questions you ask, the patterns you watch for, the sequence you follow) would give others a revolutionary framework for transformation. Your frameworks work brilliantly in practice. They don't need to be perfect in documentation. Even capturing 80% of your methodology would transform how others approach these challenges. The Abundance Reality "If I document my methods, I'll lose my edge. Clients pay for my unique insights." But preeminence reveals a greater truth. When you document your frameworks, you strengthen your position as the original source. You become the recognized creator of methodologies others reference. You attract clients who value expertise over commodities. Documentation elevates you from practitioner to authority. Your documented frameworks become your calling card, not your replacement. The Path to Visible Preeminence The shift to visible preeminence doesn't require developing new expertise. Your years of experience have created unique ways of solving problems—whether you call them methodologies, approaches, or "just how you work." These patterns are intellectual property waiting to be documented. Reveal Your First Framework Pick one problem you solve effortlessly. That moment when a client describes their situation and you immediately see the solution? That's a sophisticated framework operating at light speed, not just intuition. To document it, capture: * The patterns your brain recognizes * The process you follow * The sequence that produces results This process documents the intellectual property that exists in your actions. Build Your Knowledge Legacy Your expertise isn't just your business asset - it's your professional legacy. Every framework you don't document is a problem that persists in the world. Every pattern you don't share is an opportunity lost. Start with ONE: * ONE problem you solve better than anyone * ONE pattern others consistently miss * ONE framework that transforms outcomes The compound effect begins immediately. As Jay teaches, when you put into words what others feel but can't articulate, you become irreplaceable. Start by revealing what you do naturally. Use the Pattern Discovery Prompt below with any client transcript, recording, or even your notes from a recent session: The Pattern Discovery Prompt You are an expertise extraction specialist. Analyze this transcript of me working with/discussing a client situation. Your mission: Identify ONE recurring pattern or framework I use unconsciously. [PASTE YOUR TRANSCRIPT HERE] IMPORTANT: Focus on what I DO, not what I say I do. Look for patterns in my actual behavior, not my explanations. Look for: 1. Repeated sequences in how I approach problems (do I always start/end the same way?) 2. Consistent questions I ask or information I gather (what do I always need to know?) 3. Decision points where I consistently go one direction (what triggers my choices?) 4. Unconscious rules I follow (what do I never do or always do?) 5. Hidden diagnostic patterns (how do I really assess situations? What do I notice first?) Ignore generic consultant behaviors. Find the pattern unique to MY approach. Format your findings as: - THE PATTERN: [Name the ONE most valuable pattern you discovered] - EVIDENCE: [3-5 specific examples with exact quotes/actions from transcript showing this pattern in action] - THE HIDDEN FRAMEWORK: [Map the 3-7 steps of how this pattern actually works] - WHY IT'S POWERFUL: [Explain why this pattern creates unique value vs. generic approaches] - FRAMEWORK NAME OPTIONS: [Suggest 3 memorable names that capture its essence] Remember: I want the pattern I don't know I'm using. The one so natural I'd never think to teach it. Three Questions to Ask the AI To Get More Out of Your Output: 1. "Now analyze where this pattern creates the most value. What specific client problems does it solve that traditional approaches miss?" This reveals why your unconscious framework matters and what makes it worth documenting. 2. "Map the invisible decision points in this pattern. What micro-choices am I making that I don't explicitly mention?" This surfaces the sophisticated judgments embedded in your approach that differentiate expertise from basic execution. 3. "Compare this pattern to standard industry approaches. What am I doing differently that creates breakthrough results?" This clarifies your unique value proposition and helps position your framework in the market. The Professional Imperative: Activate Your Existing Preeminence Jay Abraham's Strategy of Preeminence provides an ethical framework, not just a suggestion. It demands that we put clients' best interests above our own. And our clients' best interests include access to every insight that could help them succeed. In 2025, keeping your methodologies undocumented while claiming preeminence is professional contradiction. Every framework you don't document is a client you've chosen not to serve. Every methodology kept to yourself violates the very principle that should guide our profession. Your unique perspectives shouldn't be wasted. Your patterns shouldn't die with you. Your frameworks shouldn't remain hidden while clients struggle. The question isn't whether your frameworks are organized enough or complete enough. The question is, are you ready to document the frameworks that could transform thousands of businesses? True preeminence means making your highest value accessible to everyone who needs it. When you have the ability to serve thousands but keep your expertise locked in your head, you're limiting your legacy. The Strategy of Preeminence calls you to something greater: maximizing the positive impact of your unique expertise. Your knowledge deserves to outlive your calendar. Your choice is simple. Document your expertise and multiply your impact, or let it remain trapped in your head forever. Choose visibility. Choose legacy. Choose to serve at the scale you're capable of. Ready to reveal the frameworks you've developed through years of client work? Discover the Framework Factory Method → (https://maxb.mysamcart.com/framework-factory-method/) This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit irreplaceablepositioning.substack.com (https://irreplaceablepositioning.substack.com?utm_medium=podcast&utm_campaign=CTA_1)

11. 

    17 Jun 2025

    Everyone's Using AI Wrong (But Not How You Think)

    This episode explores how individuals are missing the true potential of AI, focusing on building intellectual relationships with AI rather than merely using it as a tool, which leads to cognitive growth.

Podcast Authority Score: 2 / 100

A composite of feed quality, social presence, YouTube performance and engagement. Read the methodology.

Quality

3

Social presence

0

YouTube

0

Engagement

0

Contact Curated Intelligence: Everyone's Using AI Wrong (But Not How You Think)

Guest appearances

Does not typically book guests

Based on episode analysis; this does not confirm that the show is currently accepting guests.