If you missed the first two parts of this series, here’s the short version: I built a Google Apps Script to triage my inbox into three folders — Action Items, Read Later, and Noise — so I could stop treating email sorting like a productivity win and start dealing with the thing underneath it: the compulsive checking, the constant context switching. Part one covers the concept. Part two covers the build. This one is about what happened during testing — and what I kept getting wrong.

The script was running. Emails were moving. And I was still opening my inbox every hour or so to check on it.

Not to take action. Not because something felt urgent. Just to watch. To make sure it was doing what I told it to do.

That’s the moment I should have caught myself. I’d handed off the job — and then immediately started looking over its shoulder.

When Two Tools Are Running and Neither Is Enough

When the script wasn’t sorting things right, my first instinct was to run the same instructions through CoWork and see if it could do better. It could, in a way. CoWork read context well. It pulled from my Stripe customer list, identified who actually needed a response, and — this was the part that surprised me — it could explain why it was categorizing something the way it was.

But it couldn’t label. Couldn’t archive. Couldn’t do the actual mechanical job the script was built to do.

So for a stretch, I had both running. CoWork doing the reasoning. Google Script doing the moving. Two tools covering for each other’s gaps.

That’s not a solution. That’s a workaround.

And it told me something: the script wasn’t the problem. The instructions were.

The Brief Was the Problem, Not the Script

I’ve been hired as a consultant with ambiguous instructions. More than once.

It doesn’t just frustrate you — it makes it impossible to do the job well. You deliver something, and it’s wrong, but not because you’re bad at the work. The brief was bad. You built exactly what you were asked to build. It just wasn’t what they actually needed.

That’s what I did to my script.

I gave it instructions that were clear enough to get started but not specific enough to get it right.

When emails landed in the wrong folder, my instinct was to pull everything back and handle it myself. What I should have done was look at the instructions and figure out where they weren’t clear enough.

The other side of that analogy matters too. When you hire someone — or something — for their expertise, you have to trust that the expertise can do the work. Hovering doesn’t improve the output. It just signals that you didn’t actually hand off the job.

What I Actually Fixed

So I stopped looking at what the script was doing and started looking at what I’d told it to do.

I took CoWork’s reasoning — how it was categorizing, why it was making the calls it made — and fed that back into Gemini alongside the current script. Here’s what this tool understands about context. Here’s what it’s getting right. Now fix the script to match.

I added the Stripe customer list so the script had the context it was missing. Names and email addresses it could recognize, not just patterns it was guessing at.

I dropped the hourly recap entirely. It felt like a safety net — proof the system was working — but it was just noise. Subject lines and folder names with no explanation of the decision behind them. Once the script had better instructions, I didn’t need a report. I needed to trust the output.

And I changed the frequency. Every hour was recreating the exact problem I was trying to solve — constant interruption, constant context switching, just automated instead of manual. Four times a day:

• 8:00 am

• 12:00 pm

• 4:00 pm

• 9:00 pm

Enough to stay current. Not enough to give myself permission to check in between.

Before You Check the Output, Check the Instructions

The script is still running. Still working through the occasional sorting quirk. Triggers needed resetting at one point — a minor fix, easy to solve, and Gemini walked me through it clearly enough that someone with no coding experience could have handled it too.

But it’s working. Not because I found a better tool. Because I finally gave the tool I had instructions good enough to succeed.

Before you check whether the automation is working, check your gut — and check the instructions. Were they clear enough for the agent to actually do what you needed? If the output is wrong, that’s the first place to look. Not the inbox. Not the tool. The brief.

It’s the same question worth asking before you automate anything: have you defined the job clearly enough for someone else to do it?

Think about it the same way you would hiring a consultant or a contractor. You bring them in for their expertise. You give them the direction. And then you trust them to do the work — because hovering over their shoulder doesn’t make the output better. It just means you never actually handed off the job.

Your automation works the same way. Give it clear enough instructions, then let it run. If you haven’t, no tool is going to fix that for you.

If you’re working through something similar — an automation that’s half-working, instructions that aren’t landing, or just the general discomfort of letting a system do something you’ve always done yourself — that’s exactly the kind of decision DigiNav is built to help you think through. Start here.

This year’s winter jaunt was laid-back St. Augustine, Florida. Getting there and back meant two days in the car — the perfect stretch for catching up on work, reading, and whatever sparks come from hours of uninterrupted road time.

After my turn to drive, I decided to get an article or two into the pipeline. Except the work couldn’t be tackled on my iPad. Pulling out the laptop isn’t usually a big deal, but the computer bag was wedged in the back of the car and getting to it required some gymnastics I wasn’t in the mood for.

That’s where the rubber hit the road on my fancy Cursor content creation process.

The rubber being Cursor. The road being this: every conversation felt like starting from scratch. I was re-explaining myself every time. The context that makes working with Claude feel like working with someone who actually knows me — the memories, the context docs, the way I’ve built up how I operate over dozens of sessions — none of that was there. So while the AI agent was doing its job — technically — I was starting from scratch. Again.

That’s when it hit me: your AI workflow is only as good as what your AI actually knows about you.

Moving from Cursor back to ClaudeAI

The decision to move the full content pipeline out of Cursor had already been made — that part was clear. But mid-migration, something stopped me. The experiment docs were being glossed over and they’re the foundation of every article I write. Get that wrong and everything downstream is shakier than it needs to be.

So before anything else, I dealt with that first.

I had nine experiment files sitting in Cursor as markdown docs. I uploaded them all to Claude, and we assessed the existing Notion database together — what to keep, what to cut, what was missing entirely.

Claude fixed the schema.

The old template sections — Prompts, Inputs, Outputs, Artifacts, Notes, Next Iteration — got replaced with the structure that actually matched how I work: What I Built or Changed, How I Tested It, What Happened, Verdict.

Then the MCP applied all the existing records into the updated database. That’s where it got interesting. The first test run overwrote records instead of updating them. We fixed it and retested. Four rounds before it landed cleanly.

Once the existing data was solid, I added the forward workflow: at the end of any build session, ask Claude to document it directly into Notion. I live-tested this in the same conversation — one API call, all properties and body content written correctly in one shot.

The improvement I didn’t see coming: documenting the build directly through the conversation removes more friction than any tool switch ever could.

The breaking points, or not.

Nothing broke in the technical sense. Which is almost the point.

The friction in Cursor wasn’t loud. It didn’t throw errors or fail visibly. It just quietly required more from me than I realized — more re-explanation, more re-context, more process around the edges. The kind of thing you stop noticing because you’ve adapted around it.

What I didn’t expect was how much I relied on the build notes — the Experiment doc — as the actual foundation of each article. It adds the context, the actual conversation threads from AI and sometimes screenshots.

It was a structural piece that wasn’t getting its due. Cursor’s AI agent didn’t have access to the relationship Claude has built or the conversation memory. That’s not a Cursor problem — it’s just a fundamentally different thing.

Because sometimes broken isn’t when things don’t work, it’s when things are overlooked.

And if I’m honest, I’d been chasing a shinier setup instead of trusting the process I’d already built. The tools that had context — Claude, Notion — were right there. I just had a layer in the middle that didn’t.

If I had to do it again.

Trust the process you already built. Notion had been functioning as my persistent memory all along — storing context, tracking experiments, holding the thread between sessions. Claude had been the thinking partner. Those weren’t gaps to fill with a new tool. They were the foundation worth building deeper into.

I’d stacked a layer on top instead of doubling down on what was working. The switch didn’t require a complicated migration plan. It required recognizing that the combination I was working around was already solving the problem I needed solved.

New and shiny has a cost that’s easy to miss: it starts with zero context. And zero context means starting from scratch. Every time.

Decision one in the bag.

Kill Cursor for content creation. The decision wasn’t about features or capability — it was about context. Notion for persistent memory. Claude for thinking partner and automation. That’s the combination that already knew how I worked.

Cursor wasn’t a bad tool. It was the right tool for a moment that’s passed. The smarter move wasn’t finding something newer. It was recognizing what was already working and doubling down on it.

Notion remembers. Claude thinks and connects. That’s the pairing worth building on.

One more thing worth naming: things move fast in the AI space. What feels like a gap today may not be the stumbling block tomorrow. That’s not a reason to wait — it’s a reason to make decisions based on what’s working now, not what you’re hoping a new tool will eventually solve.

This is Part 1 of a short series on rebuilding the content workflow from the ground up. Getting the experiment documentation right — the soul of every article — was the foundation.

Next up: how the Article CEO workflow sits on top of it, and how the full pipeline runs from first spark to published piece.

One Thing You Can Try Today

Take five minutes and run this prompt against your current workflow:

“I use [tool/s] to do [specific job]. Given what I know about [the other tools I use daily], is this still the right fit — or am I working around it without realizing it?”

You’re not looking for a reason to switch anything. You’re just looking with fresh eyes. The answer might be: this still fits perfectly. That’s a useful thing to confirm too.

I thought I was ahead of the curve. I’d built Claude Skills—voice guidelines, content repurposing workflows, the works. Felt pretty good about it. Then put out a call last week asking people to share what they’d built. And to say people delivered is an understatement.

Writers maintaining voice across months of content. Consultants with context libraries that eliminate the “let me explain my business again” dance. Systems that work across any project, not just the one they were built for.

I looked at my setup. What I’d built was solid—but it was trapped. Locked inside specific projects as instructions. Every time I started something new, I was rebuilding context instead of deploying it. I’d been building rooms when I should’ve been building infrastructure.

The Real Gap Nobody Talks About

Most people think the problem with Claude is consistency. The AI gives you gold one day, garbage the next. So you save the prompts that worked. You build custom instructions for your projects. Maybe you create a Skill or two. You’re doing the right things.

But here’s what I discovered looking at what others had built: the real issue isn’t whether you’ve set things up. It’s whether you’re thinking big enough about what that setup could do.

I had good stuff. Voice guidelines that actually captured how I write. Content workflows that saved me hours. But they lived inside specific projects as instructions. My Substack project had one setup. My client's work project had another. My brainstorming space had... nothing, really. Just me re-explaining the context every time.

The people getting genuinely consistent results? They weren’t just building for individual projects. They were building for their whole process—voice that deployed whether they were writing a newsletter, drafting a client proposal, or outlining a workshop. Context that didn’t need to be copy-pasted or recreated. It just existed, ready to use wherever they were.

Here’s what that gap was costing me:

• Duplicate effort rebuilding context across projects

• Inconsistent outputs because each project had slightly different instructions

• The mental load of remembering which project had which setup

• Useful things I’d built that sat unused because they weren’t accessible elsewhere

The fix wasn’t building more. It was rethinking what I was building for. Not project-specific instructions. Something you set up once and stop thinking about—because it just works wherever you are.

So what does that actually look like?

How I Rebuilt My Approach

The Creative QA Skill by Mariam Vossough stopped me cold.

Mariam had built something specifically for catching weak spots in drafts—not grammar or typos, but the structural stuff. Unclear transitions. Arguments that don’t land. Sections that drag. The kind of feedback you need after you’ve reworked something three times and can’t see it clearly anymore.

I’d been missing that. I thought my content process was solid, but I didn’t have anything that checked for weak spots after the drafting and redrafting were done. That was gap number one.

But then I started thinking bigger. A Creative QA check shouldn’t just work on Substack articles. What about YouTube scripts? Content repurposing? Website copy? The underlying need—catching weak spots in something I’ve already worked and reworked—shows up everywhere. Why would I build something that only works in one place?

That’s when the real pattern clicked.

I looked at what I’d already created. Voice guidelines, content workflows, repurposing frameworks. All solid. All trapped inside specific projects. My Substack project had context my YouTube project couldn’t access. My content repurposing project duplicated half of what lived in my drafting project. I’d built useful things, but they didn’t talk to each other.

Here’s what I tried:

1. Audited what I actually had. Listed every project and its instructions. Asked: is this specific to one use case, or is the underlying need something I hit repeatedly?

2. Identified the core that applied everywhere. My voice guidelines? Needed everywhere. My content pillar definitions? Same. A QA checklist? Definitely not a one-off.

3. Rebuilt as account-level tools. Pulled what I’d created out of individual projects and rebuilt them as standalone pieces that could be accessed from anywhere.

4. Tested across contexts. Took the rebuilt voice setup and used it for a Substack draft, a YouTube outline, and a landing page. Same foundation, three different outputs. It worked.

The surprising part wasn’t that this approach was better. It was how much mental overhead I’d been carrying without realizing it. Remembering which project had which instructions. Recreating context I’d already built. Wondering if my Substack voice guidelines matched what I’d set up for client work.

When I stopped building for single projects and started building for my whole process, that overhead disappeared.

Here’s what I finally understood: the question isn’t “what does this project need?” It’s “what’s a problem I solve over and over—and how do I build something once that handles it everywhere?”

How to Build for Your Whole Process

Why Project-Locked Instructions Were Costing Me

Every time I started a new project, I was rebuilding context. Copy-pasting instructions from one project to another. Wondering if my voice guidelines here matched my voice guidelines there. What I’d built was useful—but only in the single place I’d built it.

Which meant I was doing the same setup work repeatedly, just in different containers.

Here’s What Changed: Building at the Account Level

The shift was moving what I’d created out of individual projects and into account-level custom setups—where they’re available everywhere, triggered automatically based on what I’m working on.

You’ll find this under Settings > Profile > Settings > Capabilities > Skills in Claude. That’s where Skills live at the account level, separate from any individual project.

Now, when I ask Claude to help with DigiNav content, my voice setup activates. Not because I remembered to paste instructions. Because I built triggers that recognize the context.

The Structure That Makes It Work

I let Claude handle the formatting, but everything I build now has three parts:

• Metadata: What this is for and when to use it

• The Core: The actual instructions, guidelines, or framework

• Supporting Resources: Any documents it needs to reference

The Trigger Setup

This is the part I was missing. What you build needs to know when to activate. My voice setup triggers on:

• Requests to write DigiNav content

• Mentions of “Lee’s voice” or “DigiNav style”

• Content about AI/automation for thoughtful business owners

• Keywords like “clarity before automation” or “thinking partner”

No manual activation. No remembering which project has which instructions. It just shows up when it’s relevant.

The Question That Filters Everything

Before building anything now, I ask one question:

Am I using this in more than one project—or is this a one-off use case?

If it’s one project, it stays as project instructions. If it shows up across multiple contexts, it becomes something I build once and use everywhere.

Try This: Audit Your Current Setup (15 minutes)

1. List every project you’ve created in Claude—OR think about the threads you find yourself starting over and over again

2. Look at the custom instructions in your projects, or notice what context you keep re-explaining in those repeated threads

3. Ask: what’s duplicated? What do I rebuild or re-explain because I couldn’t access it elsewhere?

4. Those duplications are your first candidates for building bigger

What Others Are Actually Building

When AI Blew My Mind put out that call, the responses didn’t just show me what was possible. They showed me how differently people were thinking about the problem.

The article organized submissions into categories, and each one revealed a different angle on thinking bigger.

Writers and Content Creators built for voice consistency, editorial feedback, and content repurposing. Not "here's how to write a blog post"—but "here's how to maintain my voice whether I'm drafting a newsletter, scripting a video, or writing a sales page." One setup, multiple outputs.

Marketers built for audience analysis, campaign planning, and messaging frameworks. The pattern: instead of rebuilding their brand positioning every time they started a new project, they created something that carried that context forward automatically.

Business Ops built for process documentation, meeting summaries, and decision frameworks. These weren't tied to a single workflow—they were designed to plug into whatever came up.

The thread that connected all of them: nobody was building for one use case. They were building for repeated problems that showed up across their work.

That’s the shift I’d been missing. I was asking “what does this project need?” They were asking “what problem do I keep solving—and how do I stop solving it manually every time?”

Looking at what others built didn’t just give me new ideas; it also inspired me. It gave me a different question to start from.

The Shift

I started this thinking I was ahead. I’d built things. I was using Claude more intentionally than most people I know.

Then I saw what others were building, and realized the gap wasn’t effort—it was approach. I was building for projects. They were building for problems that repeat.

The shift isn’t complicated. It’s just a different question to start from:

What do I keep solving manually that I could solve once?

You don’t need to rebuild everything. Start with one thing—the context you’re most tired of re-explaining. Build it bigger. See what changes.

And if you want to see what sparked this whole rethink, check out the 6 Claude Skills examples from the AI Blew My Mind community. The examples might make you realize you’ve been thinking too small, too.

It worked for me.

Last week, I was updating a client's course content. New lessons, revised material, the usual.

The old me would have opened both documents side by side. Gone line by line. Compared, edited, revised. Checked my work. Revised again. It’s how I’ve done content updates for years... because that’s how you do it right.

I caught myself reaching for that familiar process. And then I stopped.

Instead, I uploaded both versions to Claude and asked it to compare them and suggest changes. Ten minutes later, I had a clear summary of what needed updating. But here’s where it got interesting. I grabbed the code from the existing page and asked Claude to make the adjustments directly.

What would have taken me half a day took less than an hour. Same quality. Fraction of the time. Saved my sanity and saved the client money.

That moment stuck with me. Not because of the time saved (though that was nice). Because I almost didn’t do it. My old rules were pulling me back toward the line-by-line approach, even though I knew a better way existed.

“The hardest part of working with AI isn’t learning the new stuff. It’s unlearning the rules I spent years acquiring.”

That line came out of my mouth during a conversation with Kim Doyal. She paused, said it was quite the aha moment, and told me I should share it.

So here I am.

Your experience is the problem.

Here’s what nobody tells you about being good at what you do.

The principles that made you successful? The hard-won knowledge from years of trial and error? The instincts you’ve built through thousands of hours of practice?

They can become the exact things holding you back.

Not because they were wrong. They weren’t. They worked beautifully... in the context where you learned them.

The problem is, context has changed. Dramatically. And we’re still running old programs in a new operating system.

I’ve been in this game for over seventeen years. I remember hand-coding HTML in a text editor. Building databases from scratch. Debugging systems line by line. Every one of those experiences taught me something valuable. Every one of them created a rule in my head about “how things work.”

Rules like:

• Research thoroughly before you start anything

• Build it yourself if you want to understand it

• Follow the established process because that’s how professionals work

These weren’t just habits. They were principles I’d earned. The kind of hard-won knowledge that becomes automatic.

And automatic is exactly the problem.

Here’s what unlearning actually looks like in practice.

You sit down to work. You know there’s a faster, smarter way to approach the problem. You’ve seen it. Maybe even used it once or twice. But something in your brain keeps pulling you back to the familiar path.

That pull isn’t ignorance. It’s experience.

And that’s what makes it so hard to override.

I catch myself doing this constantly. I’ll start a project with every intention of using AI tools to move faster. Halfway through, I’m back in my old patterns. Researching for hours before taking action. Following processes designed for a world that no longer exists.

The wheel spins, but the cart doesn’t move.

What’s actually happening is a conflict between two kinds of knowledge. There’s what I know intellectually (AI can handle certain tasks faster and often better). And there’s what I know in my bones (the accumulated instincts from thousands of hours of doing things a certain way).

When those two conflict? Bone-deep knowledge usually wins. Not because it’s right. Because it’s automatic.

The difference between people who adapt quickly and those who struggle isn’t intelligence or technical skill. It’s having clear context for what you’re actually trying to accomplish.

The breakthrough wasn’t forcing myself to use new tools.

It was building a foundation that made the shift feel natural.

When you know your business deeply (what makes it work, what makes it unique, what problems you’re actually solving), you can evaluate new approaches without losing yourself in them. You can ask, “Does this serve what I’m already doing well?” instead of “Should I do what everyone else is doing?”

That foundation becomes a filter. It helps you decide what to keep from your old playbook and what to let go of. Without it, you’re just grabbing at tactics with no way to evaluate whether they fit.

I’ve been building what I call a context library. A collection of documents that capture the essential context about my business, my approach, and my thinking. Sounds almost too simple to matter.

But here’s what I noticed: When I start a conversation with Claude using that context, the results are dramatically different. Not because the AI is smarter. Because it’s working with material that reflects my actual situation.

The irony?

Building that context library required me to unlearn one of my deepest habits. The assumption that context lives in my head and doesn’t need to be articulated.

For years, I operated with implicit knowledge. Things I understood so well I never bothered to write them down. That worked fine when I was the only one doing the work.

But AI can’t read your mind. It can only work with what you give it.

Catching old patterns is the key.

If you want to start noticing where your old rules might be creating friction, here’s something you can try this week.

Next time you sit down to work on something and feel that familiar pull toward your usual approach, pause. Ask yourself three questions:

1. What rule am I following right now?

Name it out loud. “I need to research this thoroughly before I start.” “I should figure this out myself before asking for help.” “I need to have all the information before I can make a decision.”

Just making the rule visible is half the battle.

2. Was this rule built for this situation?

Most of our rules were built in a different context. The rule might have been perfect for 2015. The question is whether it still fits in 2025.

3. What would I try if I loosened this rule for one hour?

You’re not abandoning the rule forever. You’re experimenting with holding it lightly. What would you do differently if you gave yourself permission to try another way?

Here’s what this looks like in practice.

Say you’re working on a proposal and catch yourself deep in research mode. Gathering information, reading articles, compiling notes.

Pause and name the rule: “I need to understand everything before I can write anything.”

Ask if it fits: “This rule helped me avoid embarrassing mistakes early in my career. But right now, I’m not writing a dissertation. I’m drafting a proposal I’ll revise anyway.”

Try loosening it: “What if I spent 20 minutes talking through my initial thinking with Claude, let it surface questions I haven’t considered, and then did targeted research on the gaps?”

Here’s a prompt you can copy and paste:

I'm working on [describe the task]. Before I dive into research, help me think through this:

1. What are the key questions I should be able to answer?
2. What assumptions am I probably making that I should check?
3. What's the minimum I need to know before I can start a rough draft?

Push back if you think I'm overcomplicating this.

That’s the shift. Not from careful to careless. From automatic to intentional.

Here’s what staying stuck in old patterns actually costs you.

• Time you can’t get back. Every hour spent on the line-by-line approach when a smarter method exists is an hour you could have spent on work that actually requires your judgment.

• Money (yours or your client’s). That course update I mentioned? The old approach would have cost my client significantly more. Not because I was padding hours. Because the process itself was inefficient.

• Mental energy for the wrong things. The cognitive load of grinding through tasks the hard way leaves you depleted for the work that matters. The strategic thinking, the creative problem-solving, the relationship building.

• Falling behind while feeling busy. This is the sneaky one. You’re working hard. Putting in the hours. But the people who’ve loosened their grip on old rules are moving faster with less effort. And the gap widens.

The friction you feel isn’t a sign that you’re behind or not getting it. It’s a sign that you’ve invested deeply in your craft.

The question isn’t whether you’ll feel resistance. It’s whether you’ll let that resistance make your decisions for you.

The weight of experience.

I want to say something that might sound obvious, but needs to be said anyway.

You’re allowed to find this hard.

If you’ve built a career doing things a certain way, and now the landscape is shifting, it’s completely reasonable to feel friction. That friction is evidence that you’ve invested deeply in your craft. That’s not a weakness. That’s the weight of experience.

The goal isn’t to become someone who never hesitates. It’s about becoming someone who can sit with the discomfort of not knowing, try a different approach, and honestly evaluate whether it worked.

I still catch myself spinning my wheels. I still default to old patterns more often than I’d like. But I’m getting better at noticing when it’s happening.

And that noticing? That’s the skill.

Sometimes you have to unlearn to relearn. That’s not failure. That’s growth with more layers.

I’m curious about your experience with this.

What’s one rule or process you learned years ago that you suspect might be holding you back now?

Not a general category. A specific thing. The way you research. How do you start projects? What do you think you need to know before you can begin?

One thing I’m working on:

I’ve been developing a Context Library Workshop. A structured exercise to help you build three cornerstone context pieces for your business. These are the documents that capture what makes your work valuable, how you approach problems, and what you’re actually trying to accomplish.

I’m looking for two people to work through this with me. Whether you’re just starting to explore AI tools or you see the opportunities and want to move more intentionally, getting this foundation in place changes how you work with AI.

If that sounds useful, mention it in your reply or send a DM. Tell me where you are in your AI journey, and I’ll follow up with details.

I read the tip in some organizing blog: turn all your hangers backward, then flip them forward as you wear each piece. After a few months, you’ll see exactly what you actually wear versus what’s just taking up space.

Simple. Clean. Done.

So I did it. Hung up all my clothes, flipped the hangers backward. And honestly? It worked for the first part of the purge.

Until it didn’t: half my closet isn’t hung up at all.

I have jeans folded in a drawer. Sweaters stacked on a shelf. Casual pieces in a separate section. Then there are the pieces that aren’t regular wear—the wedding outfit, the funeral dress, the timeless blazer I wear twice a year but absolutely need. The shoes, belts, scarves, and accessories that live in their own ecosystem.

The hanger method solved for some of my clothes, but it completely ignored the complexity that actually mattered. I could turn hangers backward all day and still have half my wardrobe making its own decisions in drawers and shelves I wasn’t tracking.

That’s when I realized something that changed how I approach everything—systems, frameworks, processes, even how I build things with AI.

Simple systems fail when you ignore what’s actually real.

Most people think the problem is that they need a simpler system.

They see elegant solutions that work for others and try to force them into their own situation. The hanger trick looks beautiful because it’s reductive. One rule. One action. One outcome. But the second you acknowledge what’s actually real about your situation, that elegant solution breaks.

But here’s what I discovered: the problem isn’t the system. The problem is pretending the complexity doesn’t exist.

I wasn’t being indecisive about my closet. I wasn’t hoarding. My clothes actually lived in different places for different reasons. The hanger trick was brilliant for one piece of the puzzle, but it was built on the assumption that all my clothes worked the same way. They didn’t.

And I see this pattern everywhere now—in how solo builders try to force one automation framework into a messy reality, in how we attempt to apply one template to processes that actually need multiple logic systems, in how we ignore the complexity that matters and then wonder why elegant solutions fall apart.

If you keep forcing simple systems over actual complexity, here’s what happens:

• You waste energy trying to make reality fit the system instead of building a system around reality

• The elegant solution actually costs you more time than it saves because you’re constantly working around exceptions

• You give up on the system entirely instead of acknowledging what’s actually real

• You lose authenticity because you’re overriding what you know to be true about your situation

The closet still got purged. But not because of the hanger trick. Because I finally mapped out the actual reality: what gets worn regularly (hung in rotation), what’s seasonal (rotated storage), what’s occasion-specific (accessible but separate), what’s accessory support (its own system).

Four different logic systems. Not one.

The False Start

Initially, I thought the fix was just better organization. The hanger method looked elegant enough, and organizing blogs swear by it. So I committed. Turned every hanger backward, checked the calendar to see how long I should wait, and felt productive about having a clear system.

For exactly two weeks, it felt like it was working. Then I hit the wall: all my seasonal pieces, all my occasion-wear, all my accessories—they lived outside this system entirely. I was tracking hangers on 40% of my wardrobe and completely ignoring the other 60%.

The Turning Point

The moment it clicked was when I stopped pretending the complexity wasn’t there. I sat down and actually mapped out how my clothes actually lived, not how they’re supposed to live in organizing blog theory.

Regularly worn pieces need one system (rotation). Seasonal storage needs another (accessibility + visibility). Occasion-specific needs a third (separate but accessible, because I wear that wedding dress every few years and I need to know where it is). Accessories need their own ecosystem entirely (because scarves don’t follow closet logic, they follow “what matches the outfit” logic).

None of these pieces worked with the same system. Forcing them into one hanger method would have meant ignoring what made each piece actually valuable to keep.

The Experiment

I built a hybrid system instead. The pieces I wear regularly? Hangers in rotation. The seasonal pieces? Labeled storage with visibility. The occasion-wear? Its own section where I know exactly where to find it without opening a drawer. Accessories? Organized by type and accessibility, not by “wear frequency.”

Suddenly, the system worked because it honored what was actually real instead of pretending reality didn’t exist.

The Connection

This same pattern showed up later when I was building a video creation system with Claude. I started by asking AI to write my scripts for me. Seemed simple. Elegant. Efficient. One tool does the thinking, I do the recording.

Then I realized: I was asking Claude to replace the part of me that actually matters—my thinking, my voice, my authenticity. The elegance came from ignoring the complexity that defines what I do.

So I pivoted. Instead of “write my script,” I asked Claude to structure my thinking. Instead of “create a finished product,” I asked for “talking points that reflect my actual approach.” Instead of replacement, amplification.

That’s when the system worked. Because it honored the complexity—that I need structure AND authenticity, efficiency AND my voice, systems AND staying personally involved.

The Breakthrough

Here’s what I finally understood: simple systems look good on paper because they’re built on the assumption that everything works the same way. But the moment you acknowledge what’s actually real—that some parts of your business need hands-on attention, that some content needs your specific thinking, that some decisions only you should make—elegance has to make room for complexity.

My Story Refiner Bank process clicked into place the same way. I kept trying to force stories into a single framework until I stopped pretending they worked the same way. Some stories teach through vulnerability. Some teach through systems. Some teach through real-world failure. Different logic. Different extraction process. Different downstream use.

The system only works when you build it around what’s actually real.

Why Oversimplified Systems Were Costing Me

Using one-size-fits-all approaches meant I spent energy forcing a fit instead of building systems. I wasted time working around exceptions instead of accounting for them. And I started losing authenticity because I was overriding what I actually knew to be true.

With the closet: I’d turn the hangers backward all week, then realize I still had no system for 60% of my wardrobe. With the Claude project: I’d get beautiful scripts that weren’t in my voice, then have to rewrite them anyway—which defeated the efficiency purpose entirely.

The cost wasn’t time saved. It was time wasted on a system that ignored reality.

Building Systems Around Complexity

Here’s exactly how I built systems that honored what’s actually real:

Step 1: Map Your Actual Reality (15 minutes)

Don’t imagine how things should work. Document how they actually work right now.

For closet: How do your clothes physically live? What gets worn how often? What needs a different logic?

For video creation: What do you actually need from AI? What thinking do you need to keep? What parts feel efficient vs. what parts feel like replacement?

For your business: Which processes involve decision-making that only you should do? Which are pure busywork? Which needs your authentic voice?

Step 2: Identify Your Logic Systems (10 minutes)

Not everything in your process follows the same logic. Name them explicitly.

Example from closet:

• Logic System 1: Daily rotation (hangers forward/backward tracking)

• Logic System 2: Seasonal storage (labeled, accessible, rotated quarterly)

• Logic System 3: Occasion-specific (separate, easily findable, worn rarely)

• Logic System 4: Accessories (organized by type and matching logic, not wear frequency)

Example from video creation:

• Logic System 1: Structure and talking points (AI collaboration)

• Logic System 2: Authentic voice and delivery (my thinking, live recording)

• Logic System 3: Visual flow and transitions (predetermined based on my teaching style)

• Logic System 4: Final refinement (testing if it feels like me, not if it’s perfect)

Step 3: Build a Different System for Each Logic (20 minutes)

Trying to force one elegant system means ignoring which pieces actually need different treatment.

For the closet: hangers for daily rotation, labeled bins for seasonal items, an accessible drawer for occasion wear, and an organized shelf for accessories.

For video: Claude collaboration for structure, my natural speaking for delivery, predetermined visual framework, refinement loop that asks “does this honor my voice?”

For your business: Automation for repetitive busywork, collaboration for thinking work, systematic tracking for decision-making, and authentic interaction for client relationships.

Step 4: Test and Adjust (Ongoing)

The system only works if it honors reality. If you find yourself working around the system constantly, it means you’re ignoring a piece of actual complexity.

Ask: Is this system honoring what’s actually real, or am I pretending complexity doesn’t exist?

If you’re constantly making exceptions, the system isn’t elegant. It’s ignoring you.

The Claude AI Video Script System (That Preserved My Authenticity) - Watch me walk through the 6-step collaboration loop I created with Claude, from first iteration through final refinement

When solo builders come to me with scattered processes and overwhelm, the conversation usually goes like this:

They say: “I need a simpler system.”

What they actually mean: “Everything I do feels complicated, and I want one elegant solution to fix it.”

But then we start mapping what’s actually real. And it always looks different.

One client thought she needed to automate her entire client intake process. Seemed simple. Elegant. Efficient. Until she realized: the first conversation with a client is where they decide if she understands their business. That conversation needs her thinking. Automation would have replaced the part that makes her valuable.

Here’s the pattern: people don’t actually need simpler systems. They need systems that honor the complexity that’s actually real.

The shift happens when they stop asking “How do I make this more efficient?” and start asking “What’s the actual logic underneath each piece of what I do?”

That’s when they see it. Some parts of the business should be automated (the busywork that doesn’t define them). Some parts should stay personal (the thinking that does). Some parts need AI collaboration (structure + thinking together). Some parts need their authentic voice (delivery, client relationships, final decisions).

Different logic systems. Not one elegant solution.

The Smarter Approach

The Old Way: Force Elegance Over Complexity

Apply one system to everything. Pretend reality will bend to fit theory. Work constantly around exceptions. Eventually, abandon the system because it keeps failing.

The Smarter Way: Build Systems Around Actual Complexity

Map what’s real, identify your logic systems, build differently for each one, test if it honors what you actually do.

Here’s exactly how:

Step 1: Closet Audit for Your Business (10 minutes)

List everything you do. Next to each item, write:

• How often do I do this?

• Does it require my thinking, or is it busywork?

• Is this part of what makes me valuable?

• What logic does this actually follow?

Don’t overthink it. Just dump it.

Step 2: Group by Logic (5 minutes)

You’ll start seeing patterns. Some things all follow the same logic. Others are completely different.

Example:

• Group A: Daily repetitive work (busywork, same logic, automate-friendly)

• Group B: Client-facing decisions (requires your thinking, different logic, keep personal)

• Group C: Creative process (needs your voice, different logic, amplify, don’t replace)

• Group D: Seasonal or occasional (different rhythm, different logic, separate system)

Step 3: Build or Adjust Systems One Logic at a Time (15 minutes)

For each logic system, ask: What would actually work here?

For busywork automation, use Make or Zapier to eliminate repetitive tasks.

For client-facing decisions: Use AI collaboration (Claude structures options, you decide).

For the creative process: Use frameworks that guide but keep you in the thinking.

For seasonal/occasional: Build visibility and accessibility, not forced into daily logic.

Step 4: Ask the Question (Ongoing)

Before you implement anything: Is this system honoring what’s actually real, or is it ignoring the complexity that matters?

If you’re constantly working around the system, it’s not elegant. It’s incomplete.

If the system makes you feel less authentic, it’s replacing something it should be amplifying.

The right system should feel like it works for you, not like you’re working for it.

Pretending The Solution Works

I could have kept turning hangers backward and pretending that an elegant solution would somehow solve the part of my closet that lives in drawers.

I could have let Claude write my scripts and convinced myself that efficiency was worth losing my voice.

I didn’t. Because the moment I acknowledged what was actually real, everything changed.

Simple systems look beautiful on paper. But they break the second you stop pretending complexity doesn’t exist.

The question that matters isn’t: How do I make this simpler?

The question is: Does this system honor what’s actually real about how I work?

When you start building around actual complexity instead of forcing reality to fit elegance, something shifts. The system starts working. Your energy goes into creating, not constantly working around exceptions. You stay authentically you instead of overriding what you know.

That’s not more complicated. That’s smarter.

I’ve always been directionally challenged. Map reading stressed me out. My husband used to tease that I could follow step-by-step instructions and still end up lost.

So when I downloaded Waze for the first time, I knew it would be my game-changer. Plug in the destination, follow the instructions. Simple.

Except when traveling routes I kind of knew.

Because “How do I get there fastest?” isn’t the same question as “What’s the best way for how I want to travel?”

The thing is, following the optimal path always felt wrong. It took away my “what if” moments. What if we turn down this side street? What if we stop at that interesting store? What if we take this side road that cuts traffic because I’ve driven it a hundred times?

The GPS didn’t factor in the shortcuts I already knew. It just gave me the statistically efficient route. And following it felt hollow like something essential got left behind.

I didn’t realize I was about to experience the exact same tension in my work.

Last week, I activated Claude’s newest feature: Skills. Perfect on paper. But for what I actually needed to accomplish? It didn’t land. The prescribed approach felt like I was forcing something that wasn’t built for my specific context.

So I started asking questions, lots of questions.

Not because Skills was wrong. Because I needed to understand the who, what, and why of what it was suggesting.

That curiosity changed everything.

Optimal Features Aren’t Always Optimal

Here’s what most people think when they encounter optimization features: “The system knows what’s best. I should follow it exactly. Deviating means I’m doing it wrong.”

It’s a reasonable assumption. Optimization sounds scientific. Authoritative. Like, there’s one right answer baked into the algorithm.

But here’s what I discovered: optimization assumes the “best route” is universal. It’s not.

The best route depends on what you already know, what you’re willing to explore, and what you’re actually trying to accomplish. When you follow a prescribed path without asking, “Does this fit my actual situation?” you’re not being efficient. You’re operating with blinders.

Which means the smarter move isn’t to follow optimization—it’s to question it.

Here’s what this costs you if you don’t:

• You implement solutions that work on paper but feel misaligned with your actual workflow

• You spend time forcing “best practices” into systems they weren’t designed for

• You lose the strategic shortcuts you’ve already discovered through experience

• You mistake following instructions for progress

The GPS gives me the fastest route based on traffic data. It doesn’t know I’ve driven these roads for years, and there’s a neighborhood shortcut that saves five minutes and avoids an intersection I hate. It’s optimizing for speed. I’m optimizing for how I want to travel.

When I activated Claude’s Skills, the same pattern emerged. The framework was solid. But my project needed a “side road” the Skill hadn’t accounted for—a nuance that shifted everything.

I could have forced it. Most people do.

Instead, I asked the nagging questions. The ones that felt like they might slow me down but kept surfacing anyway.

Those questions didn’t derail the process. They refined it.

Working Fine Is Not Working Fine

When I first started using Claude, I approached it like a GPS. Here’s my destination, show me the optimal path, and I’ll follow it.

That worked fine for simple tasks: basic writing, quick research, and straightforward questions.

But when I started building more complex workflows—specifically, automating my content creation process—I ran into a wall.

I realized I was manually copying and pasting refined stories from Claude into Notion. Each piece: headline, refined story, components. All separated, all requiring me to bounce between apps.

It didn’t take hours. But it took energy. That momentum-killing friction of flipping screens, losing focus, copying from here, pasting there, back and forth.

So I thought: I’ll just build a Skill. That’s the whole point of Skills—automate these repetitive things.

I started building it. And immediately hit confusion.

My process wasn’t linear. I had multiple Notion databases working together. So my first real question was: “How does it know which database to put this in?”

That’s when I realized the Skill was optimizing for a generic workflow. But my workflow had layers. Context that the prescribed solution hadn’t accounted for.

I could have scrapped it. Could have said “This doesn’t work for me” and gone back to manual copy-paste.

Instead, I got curious about the question itself.

I asked Claude: Why are you suggesting this approach? ” What if I have different databases? What if I need the instructions to account for this specific context?

We started recalculating.

The first attempts didn’t work. One day it would function perfectly. Next day, nothing. I kept hitting walls and I kept going down the wrong roads.

Watch me walk through the exact moment I realized the prescribed Skills approach wasn’t built for my workflow, and how asking clarifying questions led me to embed automation directly into my Claude project instructions instead.

But then something shifted.

I stopped asking “How do I make this work?” and started asking “What’s the actual problem I’m trying to solve?”

The actual problem wasn’t “automate this workflow.” It was “eliminate the friction of bouncing between apps while keeping the flexibility of my specific process.”

That’s different.

So instead of building a standalone Skill, I went back to Claude with everything I knew about my actual process. I gave it the full picture: Here’s my database structure. Here’s what I need extracted. Here’s where it goes. Here’s the specific format I want. Here’s the friction point I’m trying to eliminate.

Then I asked Claude directly: “Based on my actual workflow, how should I build this automation into my project instructions? What’s the simplest, most reliable way to structure this so it works every time?”

That question changed everything.

Claude walked me through exactly how to embed the automation. Instead of me guessing at the right syntax or structure, Claude recommended the specific approach that would work for my situation. It showed me where the trigger point should be, how to format the extraction logic, and what the verification step should look like.

The moment I implemented Claude’s recommendation, everything clicked.

Now, when I finish refining a story, I paste the title. Hit enter. The system extracts every component, formats it exactly as I need, saves it to Notion, and gives me a verification link.

No more bouncing between apps. No more copy-paste friction. Just intention meets automation.

Tools That Actually Work

Why Following Prescribed Optimization Was Costing Me

I was spending a few minutes per piece manually transferring content between apps. Seems small. But across my workflow, it meant losing focus repeatedly, context-switching energy drain, and the friction that makes you less likely to refine stories in the first place.

Real consequence: I was avoiding the full process because the back-end felt tedious.

Here’s What Changed: Context-Specific Instructions Over Generic Solutions

Instead of building a universal Skill, I embedded the automation into my specific Claude project, providing detailed context for my actual workflow.

Here’s exactly how to adapt this for your situation:

Step 1: Map Your Actual Process (10 minutes)

Don’t describe what you think your process should be. Document what you actually do:

• What’s the starting trigger? (For me: refined story)

• What happens in between? (Extraction, formatting)

• What’s the endpoint? (Notion database)

• Where do you currently lose energy bouncing between tools?

Write this down. Be specific about friction points.

Step 2: Identify Your Clarifying Question (5 minutes)

There’s usually one detail that shifts everything. For me, it was the multiple databases that were part of the process.

Ask yourself: What’s the one piece of information that would make this system know what to do without me explaining it every time?

That’s your clarifying question. Build it into your process.

Step 3: Give Claude Your Full Context (10 minutes)

Instead of: “Automate this”

Say: “Here’s my current process: [detail]. Here’s the friction point: [specific problem]. Here’s what I need the output to look like: [exact format]. Here’s my clarifying question: [the detail that triggers everything].”

Step 4: Let Claude Recommend How to Build It (5 minutes)

Paste this into Claude:

I need to automate this workflow into my Claude project instructions. Here’s the full context:

[Your process map from Step 1] [Your friction point] [Your desired output] [Your clarifying question] [Your destination system]

Based on my actual workflow, how should I structure this automation in my project instructions? What’s the most reliable way to embed this so it works consistently? Show me the specific approach you’d recommend.

Claude will recommend the exact structure that fits your situation. Not a generic template. The actual approach that works for your specific workflow.

The Result

You stop guessing at how to build automation. You let Claude analyze your specific situation and recommend the approach that actually works for you.

Most people either try to force generic solutions or spend weeks building custom ones. This 30-minute process saves you that friction by letting Claude recommend the right approach upfront.

SECTION 5: CLIENT REALITY CHECK (290 words)

When clients come to me frustrated with Claude or other AI tools, the conversation usually goes like this:

Them: “This feature is supposed to save me time, but I hate it. Everything feels off.”

Me: “That’s not a flaw in the tool. That’s your gut telling you it wasn’t built for your specific situation.”

Them: [Long pause] “So I’m not doing it wrong?”

Me: “No. You need to define the process to your needs and match the tool to it.”

That pause is everything.

Most prescribed solutions optimize for efficiency in general. They don’t account for the specific context that makes your workflow yours.

One client was using a template-based content system that technically worked—it saved time. But she hated using it. Everything felt generic. The output was fast but hollow.

When I asked her, “What would make this feel like your voice instead of the system’s voice?” she realized the template was stripping out the personality. The specific details that made her advice different from everyone else’s.

We didn’t need a better template. We needed instructions that preserved her specificity while automating the busywork.

Here’s the universal principle:

Permission to explore and question isn’t inefficiency. It’s strategic refinement.

When something feels off, it usually means the prescribed path doesn’t match your actual situation. That’s not a weakness. That’s strategic awareness.

The businesses I see winning aren’t the ones that blindly follow the suggestions. They’re the ones who ask: “Does this work for how I actually operate? If not, what needs to change?”

That questioning isn’t slow. It’s what makes automation actually work.

Most people try to force the generic solution first. Then they give up when it doesn’t fit. What works is asking the clarifying questions early—the ones that feel like they might complicate things but actually make everything simpler.

Your caution about following a prescribed path? That’s not overthinking.

That’s exactly the strategic thinking that separates working automation from frustrating solutions.

The Smarter Strategic Approach

The Old Way: Activate a feature or framework, hope it fits your specific situation, force it when it doesn’t.

The Smarter Way: Use Claude to map your actual workflow, identify friction points, and build instructions that account for your specific context.

Here’s exactly how:

Step 1: Audit Your Current Process (10 minutes)

In your Claude project or thread, paste this:

I’m trying to automate [specific task]. Right now, here’s how I do it manually:

1. [Starting point]
2. [Middle steps]
3. [End point]

The part that takes the most energy is: [specific friction point]

What I need the output to look like: [exact format/destination]

Step 2: Ask Claude to Identify Your Clarifying Question (5 minutes)

What’s the single piece of information I could provide that would tell the system how to route/handle this automatically? What’s my “story title” moment—the trigger that makes everything else clear?

Claude will help you surface this. It’s often simpler than you think.

Step 3: Build Your Instructions (10 minutes)

Instead of relying on a pre-built feature, embed this directly into your Claude project instructions:

When the user provides [clarifying question], follow this sequence:

• Extract [these components]

• Format as [specific format]

• Route to [specific location]

• Return [verification link/confirmation]

Step 4: Test With One Real Example (5 minutes)

Don’t build the whole system first. Test it with one actual piece of work.

Use your clarifying question trigger. See if it works. Adjust if needed.

The Result

You stop trying to force generic solutions into specific situations. You build automation that actually matches how you work—not how you think you should work.

Most people waste weeks trying to make prescribed frameworks fit. This 30-minute process removes that friction by starting with your reality, not an idealized version.

Permission To Explore

Permission to explore isn’t inefficiency. It’s strategic curiosity.

It’s knowing when to follow the prescribed path and when to trust that the questions surfacing—the ones that feel like they might slow you down—are actually pointing toward something more refined.

The GPS still gets me where I need to go. But I don’t always follow it exactly. That’s not stubbornness. That’s strategy.

The same applies to AI tools, frameworks, and features. The ones that work aren’t the ones you follow blindly. They’re the ones you questioned enough to make fit your actual situation.

This entire process—from realizing prescribed optimization doesn’t fit, to building context-specific instructions that actually work—is exactly what I’m building into the SHIFT Your Context Workshop. It’s designed to help you create the documents and context that make AI work smarter for you because the gap between needing help and getting the right-sized help is smaller than you think.

Seventeen years ago, I began my career as a virtual assistant.

Back then, that role was the rising trend in online business—a way to meet the needs of entrepreneurs trying to make digital work for them. But as my skills and the market evolved, I leaned into coding, stepping into web development and support long before drag-and-drop websites made things simple.

Eventually, I landed on WordPress and built my agency.

The sweet spot where customization and usability meet.

That willingness to pivot wasn’t about chasing fads. It was about meeting the intersection of my strengths, the tools available, and what my clients needed most. Each shift was less a leap and more a compass point, directing me toward the next chapter.

Recently, I launched the DigiNav Compass™ to help others find that same “next best move.” Tech keeps reshaping how we work and live, but the question isn’t “What’s the newest thing?”

It’s “What actually works for you, and where are you headed?”

Here’s what I’ve learned the hard way: technology shifts aren’t about chasing the newest thing—they’re about context fit.

The Real Problem With “Shiny Object Syndrome”

Here’s what I realized was actually happening when people asked if I’m abandoning WordPress now that AI and vibe coding are emerging.

The question itself reveals the deeper issue.

We’ve been conditioned to think that new automatically means better, and staying put means falling behind. But that’s not how sustainable businesses work.

“The real problem isn’t that people are slow to adopt new technology. It’s that they’re making adoption decisions based on fear instead of fit.”

When people approach tech decisions from anxiety, they end up with these issues:

• Digital Swiss Army knives — tools that do everything but excel at nothing

• Patchwork workflows — half-integrated solutions that create friction

• Decision paralysis — too many options, no clear framework for choosing

• Constant rebuilding — starting over every six months with new tools

Their workflows become a collection of solutions searching for problems instead of tools serving specific needs.

The same pattern shows up everywhere. ChatGPT Projects vs Custom GPTs. WordPress vs AI builders. Email platforms vs all-in-one solutions.

We’re asking “which is better?” instead of “which fits my actual workflow?”

From Trend Follower to Strategic Adopter

I considered abandoning WordPress for a moment when AI coding tools emerged, but WordPress continues to serve me and my clients well.

That pause made me realize something crucial.

I had already developed an unconscious framework for tech decisions. I just hadn’t articulated it yet.

Here’s my actual decision-making process:

I grew up analog. Even with the internet, smartphones, and constant connectivity, there are days I crave the simplicity of a landline.

Nostalgia aside, it’s grounding.

“Just because something new arrives, the old isn’t automatically obsolete. Sometimes it just needs an update, a tweak, or a new role.”

That’s why I created the DigiNav SHIFT System™. It’s about adjusting, not abandoning.

AI is now part of my toolkit — not as a replacement, but as a way to adapt to what’s ahead, because technology will continue to evolve.

The key is choosing what supports your work, your clients, and your lifestyle without losing the roots that still hold value.

What I tried first: Jumping on every new AI tool that promised to revolutionize my workflow. I spent more time learning new interfaces than actually working.

The mindset shift that changed everything: Realizing I needed a filter, not more options. I started asking, “Does this organize my work or automate my work?” instead of “Is this the latest thing?”

My breakthrough moment: Understanding that ChatGPT Projects and Custom GPTs serve completely different purposes. Projects are like digital filing cabinets for ongoing work. Custom GPTs are like specialized tools you build once and reuse.

Specific results: Instead of trying 15 different AI configurations, I now use Projects for client work organization and Custom GPTs for repeatable tasks. My decision time went from weeks to minutes.

Tools That Actually Cut Through the Noise

Here’s the exact framework I use before adopting any new technology:

The Two-Question Test:

1. Does it save time? Not just promise to save time — actually demonstrate time savings in a real scenario

2. Does it fit my workflow? Can I integrate it without rebuilding everything else I do

According to a recent study by McKinsey, 87% of businesses struggle with tool proliferation, which explains why this simple filter matters more than ever.

Here’s the exact decision matrix I use for AI tools:

ChatGPT Projects vs Custom GPTs:
- Exploring questions or keeping research organized? → Projects
- Need repeatable, consistent answers? → Custom GPTs
- Working with clients on ongoing projects? → Projects
- Building tools others will use? → Custom GPTs

Watch me walk through real examples of when to use Projects for organization versus when to build Custom GPTs for automation

For your situation, try this variation:

Before choosing between similar tools, map your actual use case:

• If you’re still exploring and need conversation history → Choose the organizing tool

• If you have a repeatable process that needs consistency → Choose the automation tool

• If you need to collaborate or share context → Choose the tool that handles external access better

The tool categories that actually matter:

• Organizing tools: Projects, Notion databases, file systems — for when you’re still figuring things out

• Automation tools: Custom GPTs, Zapier workflows, templates — for when you know exactly what you need

• Integration tools: APIs, connectors, webhooks — for when you need tools to talk to each other

The breakthrough that changed my client work:

Instead of debating which AI tool is “better,” I started asking clients: “Are you organizing information to make decisions, or are you automating decisions you’ve already made?”

Organizing needs: Use Projects with uploaded context documents and memory settings

Automating needs: Build Custom GPTs with specific instructions and knowledge bases

This clarity eliminated the decision fatigue that comes with having too many similar options.

Why Context Beats Trend-Chasing Every Time

This isn’t just about WordPress versus new coding tools or projects versus custom GPTs.

It’s about sustainable decision-making in a world where the next big thing arrives weekly.

The people building the most resilient businesses aren’t the early adopters or the late adopters. They’re the strategic adopters — people who evaluate tools based on context, not hype.

Consider this supporting example:
Basecamp still uses its own custom-built project management tool, rather than switching to newer alternatives. Not because they’re stuck in the past, but because it serves their specific workflow better than any other available option.

This same approach applies to:

• Hiring decisions — do you need a specialist or generalist?
• Partnership choices — do you need access to their network or their expertise?
• Business model pivots — are you solving a new problem or solving an old problem better?
• Content strategy changes — are you reaching new people or serving existing people better?
• Client onboarding processes — do you need more personal touch or more efficiency?

Every successful business you admire probably uses a mix of cutting-edge and “outdated” tools. They’re focused on what works for their specific situation right now.

What You Can Try Today

One specific, 30-minute experiment:

1. Pick one tool decision you’ve been debating (AI-related or otherwise)

2. Instead of researching features, spend 30 minutes mapping your actual workflow

3. Ask these specific questions:

   • Am I organizing information or automating processes?

   • Do I need conversation history or consistent outputs?

   • Will I use this weekly or just when I remember it exists?

   • Does this replace something I already use, or add a new step?

4. Test with the simplest option first — regular ChatGPT before Custom GPTs, basic tools before all-in-one platforms.

Notice whether your energy goes toward learning the tool or solving your actual problem.

After 30 minutes, apply the two-question test. If it saves time and fits your workflow, schedule time to implement properly.

If it fails either question, move on without guilt.

The Real Shift That Matters

When people ask if I’m abandoning the tools that built my business, I think about that landline analogy.

Sometimes the most strategic move isn’t adopting the newest technology.

It’s being intentional about what you keep, what you adapt, and what you actually need to replace.

The shift from trend-chasing to strategic adoption changed everything for me. Instead of constantly learning new tools, I got better at the ones I already had.

Instead of rebuilding my systems every six months, I refined them.

What’s your current approach to new technology? Are you choosing tools based on what everyone else is doing, or are you choosing tools based on what actually moves your work forward?

Ready to build your strategic foundation? I’m launching a workshop on creating your personal context library — the decision-making foundation that helps you evaluate tools, partnerships, and business direction based on what actually fits your situation. Keep an eye out for the

What seems like many moons ago, I was offered a forced resignation, which I gladly accepted.

Was it on my terms and timeline? No.

Was it a blessing in disguise? You betcha.

For a good six months, I thought about leaving the company, but the salary was amazing and the schedule worked for me. Add to that, I’d built a dream team and hit every productivity mark.

The golden handcuffs were firmly in place.

Why it happened is a story for another day, but after the fact—when I had time to reflect—it was the universe talking to me.

I was overworked. Not as professionally driven. And my family needed me.

All the signs were there, but I was too comfortable (and too scared) to make the move myself.

“Here’s the thing about being pushed into change: it strips away all the comfortable lies we tell ourselves and forces us to see what actually matters.”

When Job Offers Flood In: How to Evaluate Opportunities Without Losing Yourself

In a highly competitive industry, I was one of the few without a no-compete clause. I could go anywhere and demand the world.

And the offers came in when word got out.

I was the needle in the haystack.

Every recruiter call felt like validation. Every offer felt like proof that I was valuable. For someone who’d just been pushed out of their comfort zone, this felt like the universe saying, “See? You’re going to be just fine.”

But then my better half reminded me of two things:

• I was stressed by the schedule and workload

• I would need to share secrets that most no-competes cover

Which was the deciding factor to pass on them all.

Here’s what I realized was actually happening: I wasn’t evaluating opportunities—I was reacting to them.

The real problem wasn’t finding the next job. It was figuring out what kind of work life I actually wanted to build.

Most people think the hard part about career transitions is finding opportunities.

It’s not. It’s knowing which ones to say no to.

The Integrity Test That Changed My Career Path Forever

Not because the workload would be heavy or the schedule wouldn’t fit.

Because integrity was the one thing that allowed me to soar at that company, and I was never going to compromise that.

This wasn’t just about non-compete clauses or trade secrets. This was about recognizing that my competitive advantage wasn’t what I knew—it was how I operated.

My integrity had been my differentiator all along.

What I’ve learned the hard way is that when you’re pushed into a corner, you discover what your actual boundaries are. Not the ones you think you have, but the ones you’ll actually defend when it matters.

I started with one simple experiment:

I wrote down what I would and wouldn’t do, regardless of the money offered.

The “wouldn’t do” list was shorter than I expected, but it was crystal clear. Any opportunity that asked me to cross those lines got an immediate no.

What worked was treating my values like a filter, not a suggestion.

What surprised me was how much easier decisions became once I knew where I wouldn’t bend. Instead of agonizing over every offer, I had a clear framework for evaluation.

“My next move became obvious: I was going to build something of my own, on terms that aligned with those non-negotiables.”

The forced resignation hadn’t just pushed me out of a job—it had pushed me toward clarity about what kind of business I wanted to build.

Decision-Making Framework: Build Your Personal Values Filter

Here’s the framework I developed from that experience, and what I now teach to avoid saying yes to opportunities that drain you:

The This or That Values Matrix: Start with trade-offs that show up often in your work. Create two columns and choose what feels more aligned with your current season:

• Deep engagement vs. Big audience

• Flexibility vs. Structure

• Privacy vs. Visibility

• Fast results vs. Sustainable growth

• High pay vs. Meaningful work

• Autonomy vs. Team collaboration

The Integrity Boundary Check: Before evaluating any opportunity, write down your non-negotiables. Not what you prefer, but what you absolutely won’t compromise on.

For me, it was integrity in how I handled confidential information.

For you, it might be:

• Family time boundaries

• Creative control requirements

• Financial transparency standards

• Work-life balance minimums

The Stress Test Question: Ask yourself: “If I took this path, what would I need to do that would make me lose respect for myself?”

This isn’t about being dramatic—it’s about being honest. The answer will tell you more about fit than any pro/con list.

The 10-Year Vision Filter: This is where I use a ChatGPT Project to build and refine my long-term vision over time. You can continuously add decisions, outcomes, and reflections to see patterns in what actually aligns with your bigger picture.

For one-time decision clarity, I created the Clara Decision Filter custom GPT that cuts through all the short-term pressure and gets to what actually matters. You can access it here: Clara Decision Filter.

According to a recent Harvard Business Review study, 67% of professionals report feeling overwhelmed by career decisions because they lack clear decision-making frameworks. This systematic approach helps cut through that overwhelm.

Build Your Personal Decision Filter in 15 Minutes

Watch me walk through the exact “this or that” matrix process I use to avoid saying yes to opportunities that drain me. You’ll get the ChatGPT prompts and Notion setup to create your own values-based decision system

Copy-Paste ChatGPT Prompt for Decision Questions:

I’m creating a set of tailored questions to help me make better decisions in my business that align with my needs. I started with a this or that matrix that reflects my preferences. Let’s talk about it.

[Paste your matrix choices and reflection notes here]

I prefer pinpointed reflective questions and would like you to factor in your findings, my matrix, and my core values to craft five key questions I can use when I need clarity on a decision.

Why Career Pressure Creates Better Decision-Making

This isn’t just about career transitions—it’s about recognizing that being pushed often reveals our clearest thinking.

We live in a world that celebrates the quick yes and the hustle mentality. However, the most successful builders I know have gotten really good at saying no to good opportunities so they can say yes to great ones.

The pattern is this: External pressure forces internal clarity.

When you’re comfortable, you can afford to be wishy-washy about your values. When you’re pushed, you find out what you actually stand for.

Here’s what I see happening with the entrepreneurs and creators I work with:

• They get stuck not because they lack opportunities

• But because they lack a clear framework for choosing between them

• They’re evaluating everything on individual merits

• Instead of filtering through their actual priorities

This same values-based filtering works for:

• Partnership decisions (like the partnership that drained me in two weeks)

• Client boundary setting

• Business opportunity evaluation

• Investment choices

“The most successful people aren’t the ones who say yes to everything—they’re the ones who know what to say no to.”

15-Minute Exercise: Find Your Decision-Making Framework

Pick one decision you’re currently wrestling with—could be a client opportunity, a partnership offer, or even a personal commitment.

Instead of making a pros and cons list, try this approach:

Step 1: Create your “this or that” matrix with 5-6 trade-offs relevant to this decision.

Step 2: Choose the option that feels more aligned with your current season (not what sounds good, but what feels right).

Step 3: Write down what these choices say about how you want to work.

Step 4: Use the ChatGPT prompt above to generate 5 core decision questions.

Step 5: Apply those questions to your current decision.

The goal isn’t to make the decision right now—it’s to build a system you can use repeatedly.

When Life Forces Clarity: Your Next Move

Looking back on that forced resignation, I realize it wasn’t just about leaving one job and finding another.

It was about being pushed into a moment of truth about what I actually valued and how I wanted to operate in the world.

The opportunities I turned down led to the business I built instead.

The integrity filter I developed in that moment of pressure became the foundation for every major decision I have made since then.

Here’s what I’m curious about: What decisions are you avoiding right now because you haven’t gotten clear on your own non-negotiables?

Sometimes, the best thing that can happen is life pushing you to find out.

Ready to build your own decision filter? The video above walks you through the complete system, and you can get the Clara Decision Filter custom GPT plus more frameworks like this at diginavcompass.news.

We’re building a space for you to experiment with these tools yourself, including creating a set of Context Library docs and a Story Refining system.

Because sometimes the best thinking partner isn’t human—it’s a well-designed system that helps you pause before you say yes to something that might not fit.

Not because I didn't know where I was going—I could see the direction clearly. But something was missing, something I couldn't quite put my finger on. The frustration of knowing your concepts are solid, but watching them turn fuzzy the moment you try to explain them to someone else.

You know that feeling when you're trying to describe a color to someone who's never seen it?

The Spiral Started With Words

Those niggly details that should be simple but somehow aren't.

"Community"—I know exactly what I mean when I say it, but it lands completely differently with my audience. "Thinking partner"—crystal clear in my head, sounds impossibly vague when I say it out loud. When words don't land right, your brain immediately jumps to "I must be doing something wrong."

Maybe I should pivot. Maybe this direction isn't right. Maybe I'm missing something fundamental.

But here's the thing—the direction felt solid. The concepts made sense. It was just the language that wasn't cooperating. Yet instead of trusting that and working on the clarity, I started questioning everything.

Dropoffs and Meltdowns

But then I remembered the times I dropped my daughter at her day care.

It took me back to those mornings dropping my daughter off at her child development center. She loved it there—I was right up the road, she knew the staff, had little friends waiting for her. But there were still those days when the first few moments were her own WTF moments.

The clinging. The tears. The "why can't I spend the day with you" look.

Beyond The Tears

On those tough mornings when she'd wrap around my leg, the teacher would always say the same thing: "Don't worry Mom, as soon as the door closes, the tears stop and she goes about her merry way."

And she was right. Every time.

My daughter struggled to articulate her needs and why she needed time before I left. She knew she wanted something—comfort, connection, understanding—but the words weren't there. The clarity wasn't there. Just the raw feeling that something was off.

Sound familiar?

The Right Words

The breakthrough wasn't about changing direction—it was about finding the right language for where I was already going.

Here's what I realized: My daughter and I were in the same boat. We both knew what we meant, but we couldn't make others understand. The temporary discomfort wasn't proof we were in the wrong place—it was proof we needed better clarity on the details.

Not the big picture. That was clear—the translation between what we knew and what others could grasp.

Most of us abandon ship when the words don't work. We think if we can't explain it clearly, the concept must be flawed. But what if the concept is solid and we just need to find our language?

What if the problem isn't what we're building, but how we're describing it?

Someone Who Gets It

– Marketing Strategist built her entire "Smarter Solopreneurs" newsletter around the precision of language. She took the fuzzy concept of "anti-hustle entrepreneurship" and made it crystal clear through consistent, specific messaging.

She doesn't chase trends—she finds the exact language that helps thoughtful solopreneurs understand what they're building. Her success comes from clarity, not complexity.

The Words Hitting Differently

The tears stop as soon as the door closes.

Those words hit differently now. It wasn't about my daughter being in the wrong place—it was about the temporary discomfort of not being able to see what came next.

The same way my business direction is right, but I'm still in that moment before the door closes. Still finding the words that will make everything click.

• • •

This wasn't about my concepts being wrong—it was about needing the right language to make them clear.

"Community" needs to become something more specific. The term "Thinking partner" needs context to be concrete rather than vague. Context Library needs examples that show rather than tell.

The direction is solid. The foundation is there. I just need to trust the process of finding words that match the clarity I already have inside.

What Would You Change

What would change if you stopped questioning your direction every time the words didn't work?

Instead of scrapping concepts that feel solid but sound fuzzy, what if you trusted the adjustment process? The minor tweaks that help others see what you already know clearly.

Sometimes the problem isn't your vision—it's finding the language that lets others into it.

Here's how to trust the process while you find your words:

1. Document what you actually mean - Write out the clear version that lives in your head, even if it's messy

2. Test small pieces - Share one concept at a time instead of trying to explain everything

3. Collect the confusion - When people look lost, ask "What part doesn't make sense?"

4. Build your translation bridge - Create a Context Library of language that actually lands

• • •

Ready to Build Your Context Library?

I'm putting together an on-demand workshop that walks through creating your own Context Library—the foundation that helps you find the right language for the right concepts at the right time.

If you're tired of having brilliant ideas that sound fuzzy when you explain them, this is for you. I'll keep you posted when it's ready.

P.S. The tears do stop. Trust me on this one.

Right until I squeezed the brake handles and nothing happened.

You know that feeling when you're committed to something and suddenly realize you're completely unprepared? That stomach-drop moment when the thing you thought would work... doesn't?

When the Obvious Comes Too Late

Growing up, I was fearless and curious, so I was always getting myself into predicaments, as my mom would say. Some led to broken bones or groundings, others to pats on the back or an "atta girl." This particular one included a bike ride down a steep hill after a heavy rainstorm.

The hill was slick with fresh rain, and I was picking up speed fast. The obvious kicked in too late—wet roads, steep hill, broken brakes. Classic recipe for disaster.

Which led to a hospital visit and an arm cast for the summer. The lesson seemed crystal clear: check your brakes before riding a bike down a hill, especially when the roads are wet.

The Lesson That Wasn’t the Lesson

But here's what I wasn't prepared for.

The funny thing about lessons is they're not learned until after the fact. Should I have ridden the bike without brakes? That's a big no. Should I have done things differently, like check the brakes first? Yes, why yes, I should have.

But the real question dawned on me later: should I have even been on the bike in the first place?

That answer was no—not because of the weather or the brakes, but because I was not supposed to be on the bike in the first place.

What We Miss When We Only Analyze the Crash

What hit me years later wasn't about better safety checks or improved decision-making skills.

"I was looking at the outcomes and not the parameters of what got me here," I realized, deep into running my own business.

It wasn't so much that the bike was forbidden. However, sometimes we analyze the crash without questioning whether we should have been on that particular path at that moment, given everything else that was happening.

I'd spent years thinking about checking the brakes when I should have been questioning the entire scenario.

Stop Fixing the Wrong Thing

Here's what drives me crazy about most business advice: we're obsessed with fixing our execution when we should be questioning our parameters.

Every week, I talk to others doing exactly what young me did. They're analyzing their "brake failures"—why their launch flopped, why their marketing didn't convert, why their strategy felt so hard to implement.

But they're asking the wrong questions:

• "How can I improve my email open rates?" instead of "Should I even be focusing on email right now, given my current situation?"

• "What's wrong with my sales process?" instead of "Are the parameters of my business supporting this approach?"

• "Why didn't this strategy work for me?" instead of "Should I have been pursuing this strategy in the first place?"

The most successful business owners I know aren't better at execution. They're better at reading their parameters before they commit to the hill.

Someone Who Asked a Better Question

from The Business Within: Kim could have continued to perfect her WordPress expertise and doubled down on what she was "supposed" to do as an established business owner.

Instead, she stepped back and asked a different question: what actually energizes me now? The answer led her to embrace AI and pivot to "vibe coding"—not because the old way was broken, but because the parameters of what fulfills her had shifted.

Even as GenXers, we don't have to follow the playbook of playing it safe. Sometimes the real change isn't about better execution—it's about bucking the norm for what lights you up.

The Real Lesson

The best business decisions aren't about having better brakes—they're about recognizing when you shouldn't be on the bike.

Sometimes the real lesson isn't about doing things differently. It's about questioning whether you should be doing them at all.

The Reframe That Changes Everything

This isn't about being more cautious or overthinking every decision. It's about looking at outcomes and parameters, not just tactics and execution.

Instead of: "How can I do this better?"
Ask: "Should I even be doing this given my current parameters?"

Instead of: "What went wrong with my approach?"
Ask: "Was I supposed to be on this path in the first place?"

What I Wish I’d Known Sooner

Here's what I wish someone had taught me earlier: most business struggles aren't execution problems—they're parameter problems.

What if your biggest challenge isn't that you need better tactics, but that you need to identify where you're actually stuck in the decision-making process?

Think about your last business "failure." Were you fixing the brakes or questioning whether you belonged on that bike?

A Better Way to Find Your Stuck Point

Stop guessing where you're stuck. I created the Problem Spotter specifically for this—it uses the proven SHIFT framework to help you identify exactly where you're hitting resistance in just 5 minutes.

Because here's what I've learned: you can't fix a problem you haven't properly identified.

1. Take the Problem Spotter Quiz - Find out if you're stuck at See, Harness, Implement, Focus and Filter, or Take Stock. Take the quiz.

2. Get your specific next steps based on your actual stuck point, not where you think you should be

3. Stop wasting time on solutions that don't match your real challenge

Don’t Just Work Harder. Think Smarter.

Ready to stop fixing the wrong things?

Make your next business move with confidence. I provide 'thinking partners' that help you filter out the hype and focus on the simple, right-for-you actions to grow your business.

Curious what a 'thinking partner' is? Try my free customGPT and experience one for yourself. It's a simple, guided chat that will give you clarity on your biggest challenge in the next few minutes.

Because sometimes the best lesson isn't about better execution—it's about better questions.

As someone who devours books, this felt like failure. Until I started flipping through them and realized something. The ones gathering dust weren't the problem. I was.

That highly recommended marketing book everyone said was "essential"? Outdated advice that had nothing to do with where my business was heading, wrapped in case studies from companies I'd never heard of, teaching strategies that felt like they belonged in 2015. The productivity guide that was supposed to revolutionize my workflow? I'd forced myself through 200 pages of rehashed time management tips I'd heard a dozen times before.

But here's what I noticed. The books I actually finished? I ripped through them in days, filling the margins with notes and walking away with a list of things to try immediately. The struggle-through books left me frustrated and uninspired. Like homework.

Maybe the problem wasn't my attention span.

Perhaps the problem was that I thought I had to finish everything just because I had started it.

Why Business Education Overwhelm Hurts Your Progress

We're drowning in business education. Courses. Podcasts. Books. Newsletters. Masterclasses. The message is everywhere: consume more, learn more, do more.

But here's what nobody talks about. Most of that content isn't meant for you. Not right now, anyway.

There's a notion that the more you consume, the more successful you'll become, as if knowledge accumulates like interest in a savings account and eventually reaches a magical tipping point where everything falls into place.

I've watched people collect courses like baseball cards, yet they still struggle with the same problems they had two years ago.

What if we flipped the script entirely?

I recently came across Pat Flynn's new book Lean Learning, and it made me realize I'd felt the same way about challenging everything we've been told about business education.

What if instead of learning everything about something, we learned just enough to take action? What if we stopped when we had what we needed instead of continuing until we were overwhelmed?

This approach has four simple steps:

1. Choose your next goal

2. Learn only what's essential

3. Take action

4. Reflect and repeat

Notice what's missing? The part where you consume everything available on the topic. The part where you research until you're paralyzed.

How to Focus on Essential Business Knowledge

How many times have you signed up for a course, bought a book, or started a training program only to realize halfway through that it wasn't what you needed?

I used to power through anyway. Because quitting felt like giving up.

But there's a difference between giving up and being strategic.

Sometimes, the most valuable thing you can extract from a 300-page book is one framework from chapter three. Othertimes, a $500 course teaches you exactly what you need in the first module. The rest? Filler.

Here's what I've started doing instead.

I browse for the timeless tips and information I can apply right now, regardless of where I am in my business journey. If a book isn't giving me inspiration or actionable insights within the first few chapters, I extract what's useful and move on.

No guilt. No forcing myself through irrelevant content just because someone else found it valuable.

It’s like drinking a glass of sour milk just because the glass was full.

Yet somehow, when it comes to business education, we torture ourselves through content that isn't serving us. We guilt ourselves into finishing courses that aren't relevant to our current stage. We push through books that feel like slogging through mud because someone on LinkedIn said it was a "must-read."

Why Action-Based Learning Gets Better Results

The traditional learning model goes like this: Study everything, then maybe do something.

Let’s rework that thinking. Learn just enough to take one meaningful action, then learn more based on what happens.

This isn't about being lazy or cutting corners.

It's about recognizing that real learning happens when you're doing, not when you're consuming. When you're getting feedback from real people about real results instead of theoretical knowledge about hypothetical situations.

I think about a client who spent six months researching email marketing platforms before sending a single email. She could tell you the features of every tool, the pros and cons of each pricing tier, and the technical specifications that didn't matter for her 100-person list. But she hadn't actually written an email. Or built a sequence. Or learned what her subscribers wanted to hear about.

What if she'd learned just enough to pick one platform and send one email?

What if she'd figured out what she actually needed by doing, instead of by researching?

She would have discovered that her subscribers were more interested in behind-the-scenes content than industry tips. She would have learned that her best open rates came from Tuesday sends, not the Wednesday schedule all the experts recommended. She would have found her voice by writing, not by studying other people's successful campaigns.

Action teaches you things research never will.

Why This Feels So Hard

People think that once you pick up a book, you need to struggle through and finish it. Same with courses. Same with offers. Anything.

There is a work ethic ingrained in business education that suggests struggle equals value. If it's not hard, it's not worth doing. If you didn't suffer through all 400 pages, you didn't really learn anything.

But here's what I've learned. The books that feel like work usually aren't teaching you anything. The courses that feel like slogging through mud aren't moving you forward. The content that leaves you frustrated and uninspired isn't helping you build anything.

The stuff that's actually useful? You can't put it down. You finish it quickly because it's speaking directly to what you need right now. Because it's solving a problem you actually have instead of a problem someone thinks you should have.

What This Looks Like in Practice

Since adopting this approach, my learning has become more focused and targeted. I pick a specific challenge I'm facing - let's say improving client retention. I don't read three books about customer success and take two courses on relationship building.

I find one resource that addresses my specific situation. I extract what I need. I try it. I see what happens.

If it works, great. If it doesn't, I learned something valuable about what doesn't work for my situation. Either way, I'm moving forward instead of staying stuck in preparation mode.

This doesn't mean I've stopped learning. I probably learn more now than I did when I was trying to consume everything. But I learn something specific, not just to accumulate knowledge.

The Real Rebellion

In a world that profits from keeping you perpetually learning, choosing to learn less is actually radical.

The course creators want you to believe you need their entire system, from foundation to advanced strategies, even if you only need help with one specific challenge.

The productivity gurus want you to think you need to optimize everything, from your morning routine to your email signature, when maybe you just need to stop checking Instagram during work hours.

Business books want you to believe that more information equals more success, that somewhere in those 300 pages lies the secret that will transform everything.

But what if the opposite is true?

What if learning less, but applying more, is actually the path to better results? What if the people who are getting ahead aren't the ones consuming the most content, but rather the ones who know when they have enough to move forward?

This approach isn't just about efficiency.

It's about recognizing that your time and attention are finite resources. Every hour you spend consuming content that isn't directly applicable to your current challenge is an hour you're not spending building something real. Testing something. Learning from actual experience instead of someone else's theory.

Your Turn

So here's what I'm curious about: What's one thing you're over-learning right now?

What course are you halfway through that isn't giving you what you need? What book are you forcing yourself to finish even though it lost you three chapters ago? What area of your business are you researching instead of testing?

Maybe it's time to close the book. Mine what's useful. Move to action.

The rest will be there when you actually need it.

Want to organize your learning around what actually matters? I've created a Learning Central Notion board—a free template that helps you track only the essential knowledge you need for your current goals. It's a small part of the Digital Navigator HQ resources I share with my community. Get your copy here and start learning less, but applying more.

Each was promising to improve my workflow. Write my articles while I slept. Generate social posts that would attract new readers. Transform my scattered thoughts into cohesive content.

The only problem? My best-performing articles come from the messy, unscalable stuff—the random thoughts I try to get out of my head.

Each promised magic. Faster output. Smarter results. All the bells and whistles.

I spent three hours reading reviews, watching demos, and comparing features designed to streamline my entire writing process. My brain buzzed with possibility. My excitement built with every feature I discovered. What if one of these gave me an added edge?

Something in me hesitated. I looked at the kind of work I actually create—messy first drafts, ideas sparked by so many before me, voice memos taken while riding or doing cardio.

None of those things is scalable. Or templated. Or could be done without my input.

I emptied my cart and moved on.

The Lies We Tell Ourselves

You’ve probably heard some version of this advice: “Good business owners stay plugged in”. They listen to popular podcasts, follow industry leaders, and invest in tools that give them a competitive edge.

It sounds so responsible. And smart.

But in practice? It creates chaos under everything. A sense that you’re always behind, no matter how much you consume or try to catch up.

Building unrealistic steps for the conversion funnel. Signing up for the “best” time-saving productivity system. Bookmarking the YouTube influencers who are crushing it.

Before long, your instincts get buried under a pile of other people's methods.

It’s the kind of pressure that doesn’t just drain your energy—it hijacks your instincts. Instead of feeling focused, you feel reactive. Scattered. Scrambling to keep pace with a game no one seems to be winning.

The most dangerous business advice I ever followed was "always be learning." Because constant learning became my excuse to avoid doing the actual work that I already knew how to do.

The Day I Realized I Was Sabotaging Myself

Ten years ago, I joined a beta program for a project management tool that promised to “revolutionize how solo business owners organize their workflows.”

Why? Because someone with 350K followers called it a "game-changer," and well, with that many followers, they must know something.

I spent a weekend setting it up. Created sections for my three main projects. Color-coded my tasks. Built automated workflows that would trigger when I moved items from one status to the next.

It was beautiful. Sophisticated.

There was just one problem: I had two leads in the pipeline and one project underway. I could have tracked them on a spreadsheet.

Instead of spending that time following up with those two leads or finding more projects, I was working on improving someone else's system and product.

That's when it hit me. I wasn't solving my business problem. I was procrastinating on the real work—the conversations, the proposals, the uncomfortable follow-ups that actually grow a business.

I dropped out on Monday.

The Filter Test That Changed Everything

Now I use what I call the "In-the-Weeds Check” for every new tool, system, or strategy that is on my radar.

It’s simple: Would I reach for this on a random Monday when I’m just trying to get work done?

Not when I’m feeling motivated and in the zone. Not when I’m inspired by someone else who’s crushing it. Just a regular old Monday morning when I have a week of deadlines to meet and clients to help.

If the answer is no, out it goes.

The test has saved me from:

• A client onboarding system with 15 steps that would completely overwhelm my clients (who want to pay me and get started)

• A content calendar that plans and schedules six months ahead (my best stuff comes from the results of things I did last week)

• A $99/month membership with a 50-lesson course and as many different templates (who has time to sort through those templates after that course)

What I Do Instead of Chasing The Trends

Here’s what I live by now:

1. Does this simplify or complicate? If I need an in-depth tutorial to understand it, it's probably more complex than my actual problem requires.

2. Will I still use this in three months? Most tools get abandoned when the initial motivation wears off. I look at what I have and how I can make it work better.

3. Does it fit how I naturally work? I'm all for a good system and strategic thinking, but I know the difference between tools that support my planning and tools that become projects themselves.

4. Am I solving a real problem or avoiding real work? Sometimes the tool isn't the issue. Sometimes I just don't want to have the difficult conversation or face the uncomfortable decision.

If something doesn't pass all four questions, it doesn't belong in my business.

The Unexpected Impact

Here's what happened when I stopped trying to keep up with every new strategy and started trusting my instincts:

Business Decisions: I stopped second-guessing my approach based on what others were doing and started leaning into my strengths.

Client Relationships: Without the distraction of constantly tweaking my systems, I could focus on delivering results that mattered.

Personal Wellbeing: I wasn't constantly learning new methods. I was getting better at the methods I'd already chosen, and my energy soared.

The truth? Limiting inputs increased my momentum. When I stopped consuming every piece of business information, I started trusting my judgment again.

Overcoming Resistance to Change

The hardest part? Letting go of the idea that more input equals smarter action.

Conventional wisdom suggests that the more informed you are, the better your decisions will be.

But information overload isn’t clarity. It’s paralysis dressed up as productivity.

Your Filter Practice Starts Here

Look at your bookmarks folder. Your list of subscriptions. The apps on your phone.

How many of these tools would pass the In-the-Weeds Check?

Which ones are you keeping "just in case" but never actually use?

What are you learning about that you're never going to implement?

Your instincts aren't wrong or outdated. They're just being drowned out by everyone else's noise.

The path forward isn't about finding better tools or smarter strategies; it's about finding the right ones. It's about trusting what you already know and protecting that knowing from the constant stream of other people's solutions.

Start there. Let everything else be background noise.

That tension used to keep me stuck. I’d push harder, double down on effort, or throw more tools at the problem. But none of it fixed the core issue: I wasn’t clear on why I was doing what I was doing. It wasn’t that I needed another answer. I needed to ask a better question.

I still remember one afternoon clearly. I was scheduling a website launch and a big product reveal that had been put off more than once. I wasn't feeling the excitement. Finally, I stopped, took a breath, and asked myself, "Why am I forcing this into my schedule?"

That moment changed everything—not because it gave me the strength to schedule it, but because it clarified that forcing the schedule wasn’t the solution; recognizing my actual needs was.

We think we need to do more to fix our problems.

More strategies, more tools, more hacks. But often, it’s not a lack of action—it’s a lack of clarity.

This mindset sticks because the culture around us celebrates hustle, overcomplication, and constant busyness. It tells us that slowing down to reflect is lazy or inefficient. But skipping the self-questioning phase leads to burnout and work that we resent.

I’ve learned that I build things I don’t want without good questions. And then I have to undo them.

The Moment of Truth

My shift happened gradually. I started noticing that whenever I paused to ask myself a few key questions, I moved forward faster, not slower. This wasn't an attempt to stop forward motion; it was about finding the right route.

A coach once told me, “Your best comes when you trust yourself enough to ask the hard questions.” That hit. I realized I needed to design a set of anchor questions—not as a checklist, but as a compass.

The New Mindset: Core Principles and Go-To Questions

Here are the questions that anchor me:

1. Does this fit the way I want to live and work?

It’s probably not a good fit if something disrupts my lifestyle.

2. Am I doing this to prove something or because it’s aligned?

This checks if I’m chasing external validation or making choices that genuinely serve me.

3. What would this look like if it felt easier?

Ease isn’t laziness. It's embracing ease instead of struggle.

4. What’s the actual goal here?

Not the feel-good or ego-driven goal—the real, practical milestones that move me forward.

5. What am I afraid will happen if I do it differently?

This uncovers where fear—not strategy—is guiding decisions.

6. Who am I trying to be with this choice—and do I even like that version of me?

Sometimes, the person I’m trying to be isn’t someone I respect or want to become.

7. What would I do if no one else were watching?

This strips away the need to impress others and focuses on what truly resonates with me.

Living This Mindset: Real-World Impact

Business Decisions: I regularly use these questions before adding new tasks or tools, helping me avoid busywork.

Client Relationships: I bring these questions into consulting to help clients reconnect with their true motivations.

Personal Wellbeing: These questions keep me aligned and focused and lower my stress.

Long-term Vision: They help ensure I’m designing a business I want to live inside, not just one that looks good on the outside.

Overcoming Resistance to Change

Common resistance sounds like:

• “I don’t have time to stop and reflect.” → Reframe: What’s the cost of not stopping?

• “I should already know the answers.” → Reflection: What if the power is in admitting you don’t?

• “Slowing down will make me fall behind.” → Reminder: Clarity accelerates the right progress.

  ---

Invitation to Reflect

• Which of these questions resonates most with you right now?

• Where are you making decisions on autopilot?

• What might open up if you asked one of these questions today?

• How could you build a habit of pausing for reflection in your own process?

The Bigger Journey

For me, questions aren’t just tools—they’re lifelines. They pull me back to myself when I drift. They remind me that success isn’t about keeping up but staying aligned.

Wherever you are, remember: the right question can open a door you didn’t even know was there.

I’d love to hear—what’s your go-to question when things feel off?