For one week in spring 2026, Crumbl’s signature pink cookie isn’t pink. It’s cerulean. The same shade Miranda Priestly described twenty years ago in a four-minute monologue that has somehow become more relevant every year since the movie came out.

If you’ve worked in marketing long enough, you already know the speech by heart. Andy Sachs makes the mistake of laughing at the difference between two belts that look “exactly the same” to her. Miranda doesn’t yell. She doesn’t roll her eyes. She walks Andy backwards through the supply chain — Oscar de la Renta, Yves Saint Laurent, the casual corner, the department stores, the clearance bin — until the lumpy blue sweater on Andy’s body is revealed to be cerulean, and the choice she thought she made was made for her, by the people in the room, two seasons earlier.

The point of the monologue isn’t that fashion is powerful. The point is that culture is a current you’re already swimming in, whether you noticed it or not.

That’s why Crumbl made their cookie cerulean this week.

What Crumbl Actually Did

The Devil Wears Prada 2 hits theaters May 1, 2026. The marketing window is therefore the last week of April through opening weekend. A film studio in this position has the same options every studio has always had: trailers, billboards, late-night appearances, partnerships with fashion magazines, the press tour. These work. They are also expensive, predictable, and increasingly invisible to the audience the studio actually wants — the millennial women who saw the original in a theater in 2006 and are now in their late thirties and forties, who do not watch network television, do not read print magazines, and have learned to scroll past sponsored content without registering it.

What those women do is open Instagram on Sunday afternoon to see what flavor Crumbl dropped this week.

Crumbl’s weekly drop is one of the most reliable consumer rituals built in the last decade. Six rotating cookies, announced Sunday at 6 p.m. local time, available for one week only. The pink sugar cookie is the constant — the brand’s signature, the cookie that tells you what store you’re standing in. When Crumbl makes the pink cookie a different color, the whole audience notices. That is the entire point of having a signature in the first place.

So this week, the pink cookie is cerulean. The campaign doesn’t have to say Devil Wears Prada anywhere. The color does the work. And the color works because thousands of women between thirty-five and fifty look at it, recognize it instantly, and feel a small private smile of being in on it. Then they tell three friends, who tell three friends, and a partnership budget that would have bought eleven seconds of TV ad time during a streaming awards show instead becomes a week of organic Instagram impressions inside the exact demographic the studio paid Anne Hathaway to bring back.

This is what marketing looks like when it works the way Miranda Priestly described it. Top down. Deliberate. Invisible to most people standing inside it. And almost free.

The Cookie Isn’t About the Cookie

Here is the part that most marketers miss when they try to copy this kind of move.

Crumbl is not selling cookies. Crumbl has not been selling cookies for years. Crumbl is selling a weekly emotional event — a small, predictable, low-stakes moment of anticipation that thousands of people have built into their Sundays. The cookie is the artifact. The drop is the product. The flavor is the headline. And the customer is not paying $4.50 for a sugar cookie; they are paying $4.50 to be the kind of person who knows what dropped this week and can text their friend a photo of it.

When Crumbl turns the pink cookie cerulean, they are not running a movie tie-in. They are giving their audience a more interesting thing to text about. The Devil Wears Prada 2 connection is a gift to the audience, not a sales pitch. It says: we know you. We know what you grew up watching. We know what made you laugh in 2006 and what makes you laugh now. We’re paying attention to the same things you’re paying attention to.

That is a relationship. The cookie is the proof of the relationship.

What This Means for the Rest of Us

Most businesses do not have a Sunday cookie drop. Most businesses are not in a position to make a single product change that lands inside the cultural conversation by Tuesday morning. But every business has the same underlying opportunity Crumbl has, which is to notice what their audience is already paying attention to and then to participate in it without trying to monetize it directly.

The mistake most companies make is thinking the lesson here is “do a movie tie-in.” That isn’t the lesson. The lesson is that the cookie was already cerulean before Crumbl made it cerulean — the cultural moment existed, the audience was already there, the affection for the original film was already in the room. Crumbl’s only job was to notice and to translate that noticing into a one-week color change. The marketing was free because the meaning was already paid for, by twenty years of a movie that refuses to die.

For most operators, the equivalent move isn’t a cookie. It’s a one-line caption on a Tuesday post. It’s the color of the section header on your homepage. It’s whether you remembered the thing your customer said offhand six months ago and brought it up the next time they walked in.

The cerulean cookie is a reminder that connection is not built on advertising spend. It is built on attention.

Why Tygart Media Is Cerulean Now

This article exists because of a cookie. Specifically, because Stefani Tygart — co-founder of Tygart Media and a person who has loved The Devil Wears Prada since the year it came out — saw the cerulean drop on Sunday, brought one home Monday, and made the connection out loud over coffee Tuesday morning. She didn’t pitch a campaign. She just noticed something and said it. By Wednesday, the homepage of Tygart Media was cerulean.

This is the part of running an AI-native media company that does not show up in any pitch deck. The infrastructure matters. The Notion control plane matters. The deployment pipelines and the model routing and the schema stack all matter. But none of it works without the human at the front of it noticing what’s worth paying attention to and saying it out loud at the right time.

Stef notices things. That is the job. The cookie noticed her back, and now we’re cerulean for a while, and somewhere a Crumbl marketer in Lindon, Utah is having a very good week.

That’s how culture moves. That’s the monologue. That’s the whole lesson.

The Devil Wears Prada 2 opens in theaters May 1, 2026. Crumbl’s cerulean pink cookie is available the week of April 28, 2026 only.

AI-Native Company Patterns: How Notion Agents Reshape the Org Chart

The 60-second version

The honest framing is uncomfortable: Custom Agents handle the work that historically required junior operational staff. Status reports, intake processing, lead enrichment, weekly digests, calendar prep, recurring deliverables. AI-native companies don’t add agents alongside that work — they replace that work with agents and reassign the humans to what humans actually do better. Editorial judgment. Client relationships. Strategic decisions. Handling exceptions. The org chart shifts. Pretending it doesn’t is denial.

What roles change first

Five roles where the work compresses fastest:
– Coordinator/admin work — meeting scheduling, calendar prep, follow-up tracking. Largely automatable.
– Junior analyst work — data pulls, report generation, basic synthesis. Largely automatable.
– First-tier intake — categorizing inbound leads, support tickets, content submissions. Largely automatable.
– Status communication — weekly updates, project digests, standup notes. Largely automatable.
– Documentation upkeep — keeping wikis, runbooks, and SOPs current. Largely automatable with Autofill + agents.
This isn’t a prediction; it’s already happening in operator-led companies that have built Custom Agents for these workflows.

What roles get more important

The same shift makes other roles more valuable:
– Editorial leadership — defining voice, judgment, standards. Agents follow standards; they don’t write them.
– Relationship work — sales relationships, client management, partnerships. Humans signal humanity.
– Exception handling — the 5% of cases that don’t fit the agent’s pattern. This becomes the human’s whole job.
– System design — building the agents, prompts, skills, and workflows themselves. The new ops role.
– Strategic work — deciding what the company should do, not how to do it.

The new org shape

A simple four-layer pattern:
1. Agent operators — humans who design, monitor, and improve agent workflows
2. Exception handlers — humans who catch what agents can’t handle
3. Relationship leads — humans who own external-facing work that requires being human
4. Strategists — humans who decide what to do
Notice what’s missing: layers of middle management whose primary job was coordinating between doers. Agents reduce coordination overhead because they don’t need it.

How to transition

For most operators, the shift looks like:
– Stop hiring for roles where agents could do 70% of the work. Build the agent instead.
– Reassign current staff toward exception handling, relationship work, and editorial judgment.
– Invest in agent operator skills — prompt design, workflow design, rubric design.
– Compress the org chart. Fewer layers, broader roles, sharper accountability.
This is a multi-year shift, not a quarter. But the operators who start now have years of compounding advantage over those who delay.

The risk

The risk is reorganizing too fast and losing institutional knowledge that lived in the eliminated roles. Agents don’t pick up tribal knowledge automatically. The transition needs to capture what departing staff knew and encode it in the second brain so the agents can use it.

What to read next

Editorial Surface Area, Second-Brain Architecture, ROI Math, When Not to Use a Notion Agent.

The Trust Gap in Agent-Generated Output: Closing It Without Killing the Speed

The 60-second version

Speed without trust is theater. Agents that produce output you can’t ship aren’t saving time — they’re shifting time from doing to checking. The trust gap is real, and most operators handle it badly: either they review everything (which negates speed) or they trust everything (which propagates bad output until something breaks). The operator move is sampled review on a defined rubric with source attribution. Pick a percentage you can sustain. Make the rubric explicit. Demand the agent show its sources. That’s how trust scales.

What the trust gap is made of

Four components:
1. Factual accuracy uncertainty. Did the agent invent facts?
2. Voice mismatch. Does it sound like us or like ChatGPT?
3. Context blindness. Did it miss something only a human would catch?
4. Edge case fragility. Does it handle the 5% of cases that don’t fit the pattern?
Different agents have different gaps. A weekly digest agent’s gap is mostly voice. A lead-scoring agent’s gap is mostly accuracy. Diagnose the specific gap before designing the trust mechanism.

Three mechanisms that close the gap

1. The explicit rubric. Tell the agent the criteria for “good enough.” A 5-dimension scoring rubric (factual, voice, usefulness, coherence, format) makes “good” measurable. Agents can self-score. Humans can verify the score in 30 seconds instead of re-reading the whole output.
2. Sampled review. Don’t review everything. Review 10-20% randomly. Track what you find. If the failure rate is below threshold, the system is trustworthy at that volume.
3. Source attribution. Demand the agent cite sources for every factual claim. Page references inside Notion. URLs for external. This converts “is this right?” from a research task into a click. A trust gap closed in 5 seconds is functionally no gap.

The pattern that fails

Many operators try to close the trust gap with longer prompts (“be more careful, double-check, don’t hallucinate”). This doesn’t work. The agent already thinks it’s being careful. Adding adjectives doesn’t change behavior. Structural changes — rubrics, sampling, attribution — work. Adjectival prompts don’t.

How to operationalize this

Three steps:
1. Pick one agent. Not all of them. Start with the highest-volume one.
2. Define its rubric and threshold. Five dimensions, 0-2 scoring, lock at 8.5/10 average.
3. Set a 4-week observation window. Sample 20% of output, score it, log failures. At week 4, decide: tighten prompt, reduce sampling rate, or retire.
Repeat for the next agent. Don’t try to do this for the whole fleet at once.

The relationship to Editorial Surface Area

Trust gaps shrink when editorial surface area widens. An agent reading from a clean substrate makes fewer mistakes. The trust gap and the substrate are the same problem from two angles. Fix one and the other improves.

What to read next

Editorial Surface Area, Gates Before Volume, ROI Math.

Second-Brain Architecture in the Age of Notion Agents

The 60-second version

The pre-AI second brain was a personal information system. The post-AI second brain is a personal information system that an agent can also navigate. The two are different. A pile of brilliant unstructured notes is great for human recall and useless for agent synthesis. The shift is structural: more databases, fewer floating pages; controlled tags instead of free-text; cross-links between related items; an explicit glossary. Most second brains need to be partially rebuilt to work as agent substrate.

What changes with agents in the picture

Pre-agent, the second brain optimization was retrieval-for-humans: how fast can I find the thing I’m looking for. Post-agent, it’s retrieval-for-agents: how reliably can the agent find and synthesize across the right things without human guidance.
These are different optimizations. Humans use intuition, recent memory, and visual scanning. Agents use semantic search, structured queries, and link traversal. A second brain optimized for one isn’t optimized for the other.

Five structural shifts

1. Pages → Databases. Floating pages don’t query well. Databases with consistent properties do. If you have a “books I’ve read” pile of pages, convert it to a database with author, genre, key insight, related-projects properties.
2. Free tags → Controlled vocabulary. Twenty variations of “client” produces an agent that misses things. One canonical “Client” tag with defined scope works.
3. Standalone pages → Cross-linked graph. Notion’s link system is the agent’s navigation. A new page should link to at least 2-3 related existing pages. Pages with no inbound or outbound links are dead to the agent.
4. Implicit conventions → Explicit glossary. A page that captures “this is what we call things and how we structure projects” gives the agent rules instead of guesses.
5. Recent-memory archives → Continuously enriched archives. Old projects shouldn’t decay. AI Autofill can re-summarize, re-tag, and re-cross-link old pages so they stay queryable.

The agent-aware folder structure

A workable shape for an agent-friendly second brain:
– Daily notes (database, dated, freeform — agent reads these for context)
– Projects (database, named, with status, owner, timeline — agent works against these)
– People (database, names, relationships, last interaction — agent uses for personalization)
– Sources (database, URLs, key insights, related-projects — agent cites these)
– Glossary (single page or small database — agent’s vocabulary anchor)
– Decisions log (database, dated, with context — agent’s history)
Six structures. That’s it. Most second-brain sprawl can be consolidated to this.

What this enables

Once the structure is in place, agents do things that feel like magic:
– “What did we decide about X six months ago?” returns the actual decision plus the context.
– “Summarize what I’ve learned about Y this year” produces a real synthesis.
– “Draft a brief on Z” pulls from sources, projects, decisions, and prior work.
None of this works without the substrate. All of it is trivial with it.

What to read next

Editorial Surface Area, Gates Before Volume, AI-Native Company Patterns.

Editorial Surface Area: Why Notion AI Only Works as Well as Your Inputs

The 60-second version

Notion AI doesn’t make you smarter. It makes your existing editorial infrastructure faster. If your workspace is well-organized, well-tagged, and well-written, the agent produces output that feels like a sharp teammate. If your workspace is sparse, contradictory, or under-tagged, the agent produces output that feels generic. Editorial Surface Area is the operator’s term for the substrate the agent runs on. The smartest move before scaling agents is widening that surface — not buying more credits.

Why this matters more than tooling debates

Most operator conversations about AI fixate on which model is best, which platform is winning, and which prompts to use. Those debates miss the underlying mechanic: the agent’s output is a function of the input substrate. A great agent on a thin substrate produces thin work. A mediocre agent on a deep substrate produces strong work. The substrate is the leverage point.
This is why two operators using the same Notion AI on the same plan get wildly different value. The one with three years of organized project notes, tagged client databases, and structured meeting archives gets an agent that can synthesize anything. The one who joined Notion last month and hasn’t filled in fields gets an agent that hallucinates plausibly.

What editorial surface area actually consists of

Five layers, in rough order of impact:
1. Structured databases with consistent properties. Not pages, databases. With named columns, controlled vocabularies, and reliable filling. This is the substrate agents query best.
2. Cross-linked pages. Pages that reference each other through Notion’s link system give the agent a navigable graph. Standalone pages are dead ends.
3. Tagged content with controlled taxonomy. Tags only help if they’re consistent. Twenty different spellings of “client” produces an agent that can’t find anything.
4. Written-down conventions. A page that says “this is how we name projects, this is how we structure client folders” gives the agent the rules of your house.
5. Historical archives. Old meeting notes, decided projects, retired playbooks. Agents synthesize patterns from history. The deeper the archive, the better the synthesis.

The operator’s mistake

The mistake is treating AI as a substitute for editorial work rather than as an amplifier of it. The pattern goes:
1. Operator decides to “use AI more”
2. Operator turns on Custom Agents
3. Outputs feel underwhelming
4. Operator concludes AI isn’t ready
5. Real conclusion: the substrate wasn’t ready
The fix isn’t different prompts or different models. The fix is widening the surface. Spend two weeks tightening database schemas, cross-linking pages, normalizing tags. Then run the agent again. The improvement is dramatic.

How to widen your editorial surface area

Five moves that pay back fast:
1. Pick three databases and standardize their properties. Same column types, same controlled vocabularies, same filling discipline.
2. Add a “context” page to every major project. A short page that captures decisions made, constraints, and stakeholder map.
3. Build a glossary page. What you call things. Your acronyms. Your team conventions.
4. Migrate Slack-quality conversations into Notion. The decisions that happen in Slack but never make it to a Notion page are invisible to the agent.
5. Set a “tag review” calendar event monthly. Twenty minutes to clean up taxonomy drift.

The Tygart Media thesis

This idea has a name in the Tygart Media editorial line: gates before volume. You don’t scale by adding more outputs. You scale by tightening the gates that produce the outputs. AI amplifies whatever you point it at. If you point it at a sloppy substrate, you get sloppy output at scale. If you point it at a tight substrate, you get tight output at scale.
The work that feels boring — schema cleanup, tag discipline, archive organization — is the work that makes AI worth running.

What to read next

Gates Before Volume (the operational version of this idea), Second-Brain Architecture (how to structure the substrate), Trust Gap (why even good substrate doesn’t eliminate human review).