Sean O'Meara

You really meant to "finally" get it done.

Like, getting Claude set up properly for how your business actually runs.

Maybe 3 months ago, or 6 ...

You launched it, typed something into a chat, got decent output, switched to one of your other 30+ open tabs (not judging) and moved on.

Told yourself you'd actually get to the most simple, basic setup for yourself "later."

(And, not try to use the "Here Are the 52 Best Claude Prompts Every Business Must Have" from a viral post that the LinkedIn algorithm has posted to everyone's feed)

And, "later" kept not happening.

It's usually less about discipline and way more about priorities.

If you're running your business ... "Personally Optimize AI for My Biz" probably doesn't make it into the top 5 items on a busy Wednesday.

I do get it.

In many ways, I initially used my non-free Claude account like a fancy Google.

Here's what I usually say to people when they finally circle back to it:
➡️ You don't need another course
➡️ You don't need 3 workflows overhauled
➡️ You don't need an entire afternoon (well, 30-mins on the phone with me) to build ONE Skill file for one specific task

That's really it.

We do it (virtually) live.

AND, you walk away with a working file and your Skill implemented.

$97, one session and ...
.. one thing that finally gets done ✅

Reply or DM if you want the details.

He absolutely had the right steps.

But, in the wrong order.

He's a creative producer helping host monthly events.

He had a documented promotional workflow.

(Woo-hoo! A documented workflow - huge props from me.)

However, he was resizing graphics last.

Which doesn't sound that bad until you realize:
➡️ Every time he caught a typo
➡️ Every time a date changed
➡️ Every time the featured image OR video got updated

He had to resize again.

The same work, sometimes twice.

And on occasion, three or more times.

When we re-mapped his workflow, the fix took about 4 minutes.

** Move final content approval BEFORE the resize step

Do not touch exported dimensions UNTIL the content is locked in.

The same tasks, the same tools BUT ...
.. a different order.

And, dramatically less rework.

(Leaving the drama for the live events, ahem)

A lot of broken workflows aren't necessarily missing steps.

They're missing the optimized order.

A step done too early can easily become the task you have to do twice.

A step done in the right order kinda disappears once checked off.

You just get to the end faster

One question helps cut through most of the cruft:
✅️ What has to be true BEFORE this step can happen?

Answer that in reverse order - from output back to the first step.

The sequence naturally surfaces issues for you ...

*****onArchitecture

I'm not shy about being pretty nerdy & geeky.

I still love to learn new things, even if it's not for a certification or specifically for a client.

I also love
.. to learn things (strategically) from social media, including LinkedIn.

But.

That cult of comparison can trigger my big time if I'm not careful.

Here's a reminder phrase I use that works for me:

➡️ "Am I choosing to be data-driven or allowing a detail to become my dictator?!"

Why does this matter?

(Some of the neural bits)

When we're working towards a goal, it's easy to overly identify with certain metrics or steps.

And if we're feeling frustrated with our progress?

Well, our brains are built to protect us, find a QUICK way to relieve the pain.

Even if the posted "hack" from a guru really isn't aligned for us.

(But, wow, does it look appealing and the post got TONS of engagement so ...)

That doesn't mean the trigger is really in our best interest ...

So, if my reminder phrase works, feel free to share it or use it yourself!

Or ignore it completely if it doesn't 😉

"We don't need that. We don't need to complicate things ..."

She genuinely meant that.

She was trying to keep things simpler for her boss.

The problem?

She didn't have the full picture when saying that ...

We were in the midst of the compliance setup for their solo therapist practice.

The item in question?

An SMS consent form.

She assumed that wasn't needed since the office was already using a tele-health consent form which covered everything.

It doesn't, these are two different documents covering two different gaps.

Having one doesn't mean you automatically have the other.

Once I explained the difference between the two, she understood and was completely on board.

No resistance, just incomplete information that looked like an easy and complete decision.

This is a pattern I see a lot.

Confidence WITHOUT full context doesn't look like knowledge gap.

It kinda looks like a decision ... and this is why it's harder to catch.

There's a difference between simplifying a process and simplifying AWAY a requirement.

The 1st thing makes it easier, the 2nd creates a gap that looks "fine" right up until it doesn't.

Resistance? It's usually not for the right thing, it's for the unknown thing.

That's a very different problem and has a different fix

Have you run into a version of this?

I'm guessing it shows in many operations, not just compliance work but ...

*****onArchitecture

So ... what happens when the LinkedIn guru's "top 3 tips to get to 10K+ followers in 30 days?" isn't really moving the needle for you?!

Well, I can't tell you what will work for you but ...
.. I'm sharing my ideas here if it helps a few others like me.

#1: That guru hasn't talked to you and is not on your exact path ... maybe some of the tips apply for you, maybe they don't at all

#2: Keep showing up authentically, even when it's like "one hand (not) clapping in the forest" for the majority of your posts

#3: Strategically focus time consistently to add helpful & genuine comments to real posts

Since I can be very literal & specific (and trusting), I often fall into the trap of:

"Well, that EXPERT posted I should do THIS to fix the problem."

And, then later realize their viral hook isn't necessarily going to mean a personal victory for me.

Doh!

(Still) learning as I go ...

I genuinely thought I was being helpful and transparent ...

I was deep into the steps for a HIPAA compliance tech engagement with a solo therapist in their private practice.

There was a tool in the stack with published configuration steps.

Like, a recipe book from the provider's own documentation.

I pulled them up onto my laptop and offered to let her read through some of them so she'd understand a bit more about what I was helping tackle next.

"Would you like to read through these to understand what's getting set up next?"

She looked at me and said:

"Just shoot me now."

She was kinda joking. Mostly.

But she was also completely right ...

The fact that someone CAN follow or read the description of a technical process does NOT mean it should be on their list of TODO's.

She's a licensed therapist ... her time is committed to her clients and her practice.

A 15+ step configuration checklist is not her job.

It was never her job and that's partly why she hired me.

I had almost handed her a problem (even just to read the configuration checklist) I should have been carrying.

This is an example of the: "capable but shouldn't have to" problem.

It shows up a lot for founders.

Like, the founder who can build their own onboarding sequence BUT loses two days a month (or more) to something a system should handle.

The coach who can manage their own schedule BUT spends 33 mins a day (or more) on emails a booking link and mini sequence would eliminate.

Capability ... and ... the correct USE of capability aren't the same thing.

Back to the therapist office and the configuration guide ...

After she had told me to just shoot her instead, I smiled, closed the guide and said "no problem, I'll tackle this next."

"All yours!", she said. "Enjoy ..."

She then left that room to follow up with a client re-scheduling session.

As she should - that was her job and exactly where she needed to focus next.

There's a moment that often shows up for me when working with new clients.

It's when someone is answering a question I've asked ...
.. about how something works.

And it's usually some form of, "Ehh, it's just always been this way."

Not: "This is the current version we set up because ..."
Not: "We chose this path at the time because ..."

"It's always been this way" is almost always a GREAT place to investigate further.

Because there's usually friction and problems there, sometimes just barely visible or hiding in plain sight.

*****onArchitecture

"It's never been a problem ..." ...

is one of the MOST dangerous sentences in any business.

Not because it's wrong about what happened but ...

because it confuses the past with a plan.

(Oops!)

A streak describes what has (or hasn't) happened.

A strategic system outlines what will occur.

A lot of operations keep running on streaks yet call them systems.

The difference usually shows up once something is truly tested ...

*****onArchitecture

I've worked in quite a few industries over the years.

And, in many different roles including sales.

Many people REALLY love the HUNT.

The pursuit.

You know, like tons of cold-calling, fierce competition and combative dialogue to be heard and seen as right.

I do not.

At least not much at all these days.

You know what I truly enjoy these days?

Helping overwhelmed yet committed clients (like a recent therapist and a creative/producer musician) FINALLY get help addressing those nagging tech & AI things that have buzzing around in their head.

For quite a while.

Helping over the hunt.

That's just me. I'm cool with that.