The Bystander Effect Is Quietly Killing Your Marketing

There’s a famous bit of psychology that explains why a person can collapse on a busy footpath and twenty people walk past. It’s called the bystander effect. When responsibility is spread across a crowd, everyone assumes someone else will step in — so nobody does. The more people present, the less likely any single one of them acts.

I’ve come to believe the same thing happens in marketing, and most of us never notice it. We think the problem is that people are rejecting us. Usually they’re not. They’re just standing in the crowd, assuming the message was meant for the person next to them.

“Everyone” Is Nobody

When you write an email, a newsletter, or a webinar invitation addressed to everyone, you’ve accidentally recreated that footpath. The reader scans it, decides — without much thought — that it’s aimed at some other, more relevant person, and moves on. They don’t unsubscribe. They don’t send an angry reply. They simply file you under “not for me” and get back to their day.

That quiet non-decision is far more dangerous than a flat “no”. A rejection at least tells you the message landed. The bystander never even picks up the phone. You walk away thinking the offer was weak, when really the offer was fine — it just never felt personal enough for anyone to claim it.

I see this constantly with MSPs marketing to small business. We send a generic “we can help with your IT” message to a list of three hundred contacts and wonder why two people reply. The content isn’t the issue. The aim is. Three hundred people each assumed we were really talking to one of the other 299.

First Aid Trainers Got There First

Anyone who’s done a first aid course has been taught the fix already. When you’re standing over someone who needs help, you don’t shout “somebody call an ambulance” to the crowd. You point at one specific person — “you, in the blue jacket, call triple zero now.” The instant that individual realises they’ve been singled out, they move.

That’s the whole game. The moment a person understands you are talking to them, the bystander effect collapses and action becomes possible. Marketing is no different. The job isn’t to reach more people — it’s to make each person feel seen.

Naming the Person, Not the Crowd

So how do you point at the blue jacket without writing three hundred individual emails? This is where I think the tools we already pay for earn their keep.

Most MSPs sit on a goldmine of context they never use. You know which clients are still on ageing hardware, which ones asked about security last quarter, which ones have a renewal coming. That detail is scattered across Outlook threads, meeting notes, and a CRM nobody opens. The work of pulling it together used to be the reason we defaulted to “Dear valued customer”. It isn’t anymore.

I’ll draft a campaign in Word and ask Copilot to rewrite the same core message for three distinct groups — manufacturers worried about downtime, professional services worried about compliance, retailers worried about card data. Three versions in the time it used to take to write one bland one. Each reader recognises their own world in the words, and the bystander reflex never gets a chance to kick in.

Copilot in Outlook does the same thing one conversation at a time. Before I reply to a prospect, I can have it summarise everything we’ve ever discussed and surface the one concern they keep raising. The reply then opens with their problem, in their language — not my service menu. That’s the digital version of pointing across the room and saying the person’s name.

Even your segmentation gets easier. I’ll drop a client export into Excel and let Copilot group accounts by industry, size, or last contact, so the list I’m writing to is genuinely a room of similar people rather than a faceless mob. The narrower the room, the easier it is to talk to everyone in it as if they were one person.

One “Yes, You” Away

The shift here is small but it changes everything. Stop trying to be relevant to a crowd. Be unmistakably relevant to one type of person, and let them know you mean them.

Your next client is probably already on your list. They’re not ignoring you out of disinterest — they’re waiting in the crowd, quietly assuming the invitation belongs to someone else. The work isn’t louder marketing or a bigger list. It’s removing the doubt about who you’re speaking to.

Point at the blue jacket. Use the context you already have, the tools you already pay for, and address the person directly. You might be one moment of genuine recognition away from the conversation you’ve been chasing all quarter.

When the Fix Stops Being a Fix: Troubleshooting in the Age of Probabilistic IT

For most of my working life, troubleshooting an SMB environment was a hunt for a single, knowable cause. Something was broken, and somewhere there was a reason. A permission was wrong. A DNS record pointed at the wrong place. A service had stopped. You worked the chain backwards, found the link that had failed, fixed it, and the problem went away. The same input produced the same output, every time. That was the quiet contract underneath everything we did. IT was deterministic, and our whole troubleshooting craft was built on that assumption.

That contract is now breaking, and AI is the reason. The more our clients lean on tools like Microsoft 365 Copilot, the more we find ourselves chasing problems that don’t have a single cause and don’t behave the same way twice. We’ve spent decades learning to solve deterministic problems. We’re now being asked to solve probabilistic ones, and most MSPs haven’t noticed the ground shift under their feet.

“It Worked Yesterday” Now Means Something Different

Here’s the scenario I keep running into. A client calls because Copilot gave them a wrong answer. It summarised a meeting and missed the one decision that mattered. Or it drafted a reply in Outlook that referenced a document the user swears they never mentioned. Yesterday it was brilliant. Today it’s confidently wrong. Nothing changed on your side. No update shipped. No setting moved.

Under the old model, “it worked yesterday and not today” was a clue. It told you something had changed, and you went looking for the change. With AI in the mix, that same sentence tells you almost nothing. Large language models are probabilistic by design. The same prompt can produce a different response on Tuesday than it did on Monday, and that’s not a bug you can ticket your way out of. It’s how the technology actually works.

So when a client reports that “Copilot is broken,” your first instinct — find what changed — quietly fails you. There may be nothing to find. The behaviour you’re chasing isn’t a fault in the wiring. It’s variance in the output. And variance doesn’t sit still long enough to be caught with the tools we’ve always used.

The Cause Isn’t Always in the System

The harder adjustment is accepting that the problem often isn’t technical at all. When Copilot returns a poor result, the cause is frequently the question, not the code. A vague prompt, missing context, the wrong document open in the background, permissions that quietly scope what Copilot can and can’t see — these shape the answer far more than any registry key ever did.

I had a client convinced Copilot in Teams couldn’t read their project files. The real issue was that the files lived in a SharePoint site the user didn’t have access to, so Copilot, correctly, never touched them. The system was working exactly as designed. The human’s mental model was the thing that was broken. There was no error in any log, because there was no error. Try writing that up in a standard ticket resolution.

This is the part that unsettles seasoned engineers. We are trained to distrust “user error” as a lazy diagnosis. But with AI, the boundary between the tool and the person using it has genuinely blurred. The quality of what Copilot produces is now a function of context, phrasing, data access, and the user’s own clarity of thought. Half of real-world “AI problems” are actually grounding problems — Copilot simply wasn’t given the right material to work with. You can’t fix that with a script. You fix it by teaching.

From Repair to Probability Management

So what does troubleshooting look like when certainty is gone? It looks less like repair and more like managing probability. Instead of asking “what’s broken,” you start asking “why is this likely happening, and how do we make the good outcome more likely next time.”

That changes the work in practical ways. You start checking what Copilot can actually see — the SharePoint and OneDrive permissions, the Purview sensitivity labels, the data the user assumes is in scope but isn’t. You look at how the question was asked, not just what the system returned. You reproduce the issue several times, because one bad answer is an anecdote, not a pattern. You document tendencies rather than root causes, because a tendency is often the most honest thing you can record.

It also changes what you sell. The deterministic world rewarded MSPs who could find and fix. The probabilistic world rewards MSPs who can guide, set expectations, and shape how AI gets used across a client’s day. The value moves from the repair to the relationship.

Sitting With Uncertainty

None of this means our old skills are worthless. Plenty of SMB problems are still gloriously deterministic — a licence didn’t assign, a mailbox didn’t migrate, a Conditional Access policy locked someone out. Find it, fix it, move on. That work isn’t going anywhere.

But a growing slice of what lands in your queue now has no clean answer, and pretending otherwise only frustrates everyone. The MSPs who’ll do well from here are the ones who can hold two modes at once — the precision of the engineer and the judgement of an advisor who’s comfortable saying “here’s what’s most likely, and here’s how we improve the odds.” Learning to sit with that uncertainty, rather than fight it, might be the most valuable troubleshooting skill of the next decade. I’m still getting used to it myself.

The Robots Didn’t Kill Sales. Relevance Did.

Let me be upfront: this isn’t a post about watching other people lose their footing. I’ve seen it happen — quietly, without announcement — but pointing at cautionary tales reads as smugness, and it doesn’t help anyone. What does help is understanding the mechanism. Because the mechanism doesn’t care whose career it applies to, including mine.

The Slow Fade

When AI started making headlines, a certain explanation took hold in IT circles: the robots came and took over. Clients automated their way out of needing you. Algorithms undercut your value. Technology made your expertise redundant overnight.

I’ve sat in rooms where that story got told with great conviction. And I understand the appeal — it’s clean, it’s external, and it lets everyone off the hook.

But I don’t think it’s the real story. At least not for most people.

What I’ve actually watched happen is something quieter, and frankly more avoidable. Skilled people — genuinely skilled, with real depth — stopping. Stopping posting, stopping presenting, stopping sharing what they were learning. Getting busy, or burned out, or simply assuming that reputation would carry. And then discovering, over months rather than days, that the market had quietly moved on.

The market doesn’t issue a formal notice. It just stops calling.

Presence Is a Practice, Not a Trophy

Here’s the thing about credibility in professional services: it behaves more like a subscription than an asset. You don’t acquire it once and keep it indefinitely. You maintain it — week by week, post by post, conversation by conversation — by staying present in the space where your clients and prospects are paying attention.

The people I see holding their ground right now aren’t necessarily the most technically brilliant. What they share is a habit of doing something worth knowing about and then talking about it. They’ve been working through how Copilot in Teams handles a fast-paced client meeting — the kind where the conversation moves faster than anyone can type — and they write up what actually happened. Not a polished case study. A genuine account of what worked, what surprised them, what the documentation didn’t quite prepare them for.

That’s what gets shared. That’s what gets remembered. That’s what gets you back into the conversation when a prospect is deciding who to ring.

The alternative — doing excellent work quietly, trusting that results will speak for themselves — used to be viable. It worked when markets were smaller and word of mouth moved reliably. I’m not sure it works the same way now. Attention spans are shorter, competition is louder, and the gap between the visible and the invisible keeps widening faster than most people expect.

The AI Angle Nobody Wants to Admit

Here’s where I’ll give the “robots did it” crowd a partial concession: the shift toward AI tools has accelerated everything. But not quite in the way most people mean.

What it’s accelerated is the gap between people who are actively inside the change and people who are observing it from a safe distance. Clients are asking questions about Copilot, about automation, about what Microsoft 365 actually means for how their team works day to day. The people who get those calls are the ones who have been publicly working through those questions — who’ve shared what Microsoft 365 Business Premium looks like in practice for a 40-person firm, or explained what Copilot in Outlook actually does to a full inbox on a Monday morning, drawing from real client experience rather than a vendor one-pager.

The others get found too. Just by someone else.

So if you’re waiting until you feel fully prepared to share — waiting for the perfect case study, the right moment, enough certainty — I’d gently push back on that. The market is not waiting with you. It’s watching whoever is showing up.

The Account Runs Down

I think of staying relevant the way I think about any recurring obligation: you can miss a payment here or there without immediate consequence, but the balance erodes. And by the time you notice the problem, you’re already working against a deficit. Rebuilding takes longer than maintaining ever did.

The fix is not complicated, even if it takes discipline. Engage with something genuinely new — a client challenge, a corner of the Microsoft 365 stack you haven’t properly explored, a question your market keeps circling. Arrive at a real view. Then share it, in your own voice, without waiting until it’s polished enough to be mistaken for marketing material.

Work on things that matter. Then put them where the people who should know can find them.

That’s the whole playbook.

The careers that fade aren’t usually the ones that got disrupted by technology. They’re the ones that went quiet. The ones that assumed the work would carry its own story forward.

It doesn’t. You have to carry it.

Don’t go quiet.

AI Governance Starts Before Copilot Does

Most AI conversations with business owners start in the wrong place. They ask whether Microsoft 365 Copilot is worth buying. I think the better question is whether the business is ready for what Copilot will reveal.

I have seen the same pattern often enough now. A client gets excited about Copilot in Outlook, Teams, Word and Excel. Someone wants meeting summaries. Someone else wants faster proposals. The owner wants staff to stop using random public AI tools with company data. All fair enough. But then we look underneath and find the real issue: years of loose permissions, old Teams, forgotten SharePoint sites, stale guests and no clear policy on what staff should or should not ask an AI system to do.

That is where AI governance starts.

Governance is not a document no one reads

A policy is useful, but only if it changes behaviour. If the policy says “use AI responsibly” and nothing else, it has failed before it starts.

For Copilot, I want plain rules. What data can be used? What data must not be used? When does a human need to review the answer? Who owns the final output? What happens if Copilot surfaces something the user did not expect to see?

That last question matters. Copilot does not need to break into your tenant to create a problem. If a user already has access to a file, Copilot may be able to use that file as part of an answer. The silent risk is not Copilot ignoring permissions. The risk is that the permissions were never cleaned up in the first place.

The technology follows the tenant

This is why I keep coming back to the Microsoft 365 basics. Entra ID, MFA, Conditional Access, SharePoint permissions, Teams lifecycle, Purview sensitivity labels and Data Loss Prevention are not side issues. They are the foundation.

If identity is weak, every AI answer sits on a weak account. If SharePoint is overshared, Copilot can make that oversharing easier to discover. If labels do not exist, users have no clear signal that a document is sensitive. If DLP is sitting in test mode forever, the business has a policy theatre problem, not a protection model.

I would rather see a small, controlled Copilot pilot in a tidy tenant than a broad deployment in a messy one. Start with a few users. Pick real scenarios. Meeting follow-ups in Teams. Draft replies in Outlook. Summaries from known SharePoint libraries. Then watch what happens. What worked? What surprised people? What data did Copilot find that no one expected?

Guardrails should be practical

The best guardrails are boring. That is a compliment.

Require MFA. Tighten external sharing. Review old guests. Publish simple sensitivity labels. Apply DLP where it matters. Use Restricted SharePoint Search where the content estate needs time to be cleaned up. Train users to verify answers before sending anything to a client. Make it normal to say, “Copilot drafted this, but I approved it.”

That is not anti-AI. That is responsible adoption.

The businesses that do this well will not be the ones with the flashiest prompts. They will be the ones that treat Copilot as part of their operating model. Policy, security, people and process all moving together.

My view is simple. Do not start with the licence. Start with the trust model. If you can trust the identity, the data, the permissions and the controls, then Copilot becomes much easier to use with confidence.

AI governance is not there to slow the business down. It is there so the business can move without pretending the risks are someone else’s problem.

When the Product Is the Answer

A few years ago, I paid real money for an online course about something I could have googled. Not because the information wasn’t out there — it was — but because someone had packaged it up into a tidy sequence, with a PDF checklist at the end. That felt like value. I’d trade some cash for the shortcut.

I’m not sure that trade still makes sense.

There’s a question worth sitting with if you sell courses, run a newsletter, or operate any kind of advice business: what exactly are you selling? If the core of your offer is “I know how to do X, and for a fee, I’ll explain it to you,” then you’re competing — right now, today — with a chat interface that will do the same thing for free, in plain language, at any hour, and answer every follow-up question without sighing.

That’s not pessimism. It’s just arithmetic.

The Commodity Shift

The thing is, knowledge transfer was already becoming cheaper. YouTube, forums, documentation sites — the raw material was free or nearly so long before any of us had heard of a large language model. What the structured course or the curated newsletter offered was organisation and trust. Someone had done the sorting for you.

AI has now taken that arrangement apart. Ask Copilot in Microsoft 365 how to build a pivot table, how to structure a client proposal, how to read a balance sheet, or how to write a meeting agenda — and you’ll get a clear, accurate, step-by-step answer in seconds. It knows context. It remembers what you asked two prompts ago. It adjusts when you say “that’s too complicated, simplify it.” The experience of learning from it is genuinely conversational in a way that a pre-recorded video module is not.

For anyone whose business rests primarily on the instruction layer — here’s how to do the thing — that shift deserves honest attention.

What Doesn’t Commoditise

I don’t think this means the advice economy is finished. But I do think it clarifies what was always the actual product, beneath the packaging.

What an AI won’t give you is accountability. It won’t check whether you actually implemented what it told you, or notice that you’ve been stuck on step three for six weeks because there’s something uncomfortable underneath the technical question. A good advisor, coach, or community does that.

It also won’t give you judgement built from real exposure to your specific industry, your clients, your context. I can ask Copilot about pricing strategy for an MSP, and I’ll get a reasonable answer. But the answer from someone who has personally renegotiated forty MSP contracts and remembers what went wrong — that carries a different weight.

The value proposition that survives isn’t “I’ll explain the concept.” It’s “I’ve seen this pattern before, here’s what it usually means, and here’s what I’d actually do.” That’s the part that takes years to earn and can’t be scraped.

What I’m Watching

My own approach has shifted. The things I now put into writing — whether that’s a post, a session, or anything structured — I try to hold to a higher bar than “here’s how to do X.” Anyone can get that from Copilot. What I’m aiming for is the observation behind the explanation: the why, the tradeoff, the thing that only becomes clear once you’ve been surprised by the edge case.

The knowledge economy isn’t dying. It’s just shedding the parts that were never really the point.

Stop Hoping Your Team Will “Figure Out Copilot”

Microsoft 365 Copilot is one of the most powerful productivity tools Microsoft has ever released. Yet many organisations are still struggling to get consistent value from it.

Why?

Because giving people access to Copilot is not the same as teaching them how to use it effectively.

The reality is that most users start with enthusiasm, ask a few basic prompts, get mixed results, and then drift back to their old ways of working. The opportunity remains, but the outcomes never arrive.

That’s exactly why I created the Microsoft 365 Copilot Team Training Guide.

Moving Beyond Random Prompting

Successful Copilot users don’t rely on luck.

They understand:

How to structure prompts
Which Copilot tool to use for specific tasks
How to refine outputs
How to work with Copilot rather than simply ask questions
How to safely use AI within a business environment

This guide provides practical, repeatable approaches that teams can use every day rather than theoretical discussions about AI.

What’s Included?

The guide covers:

Microsoft Word
Outlook
Teams
PowerPoint
Excel
Copilot Chat

You’ll also learn practical prompting techniques, prompt frameworks, governance considerations, adoption strategies, and ways to measure success across your organisation.

Unlike many AI resources that focus on concepts, every principle is designed to be immediately applied with examples, expected outcomes, tips, and common mistakes to avoid.

Designed For Real Teams

Whether you’re:

A business owner investing in Copilot licences
An IT manager responsible for adoption
A team leader looking to improve productivity
An MSP helping clients get value from Copilot
A user wanting to work smarter

This guide provides a structured path to getting measurable results from Microsoft 365 Copilot.

Copilot Success Requires More Than a Licence

The organisations seeing the biggest productivity gains are not necessarily those with the most licences.

They’re the organisations that invest in education, consistency, and repeatable ways of working.

The good news is that learning how to use Copilot effectively doesn’t need to be complicated. With the right guidance, your team can quickly move from experimentation to real business outcomes.

Ready to Become a Copilot Champion?

If you want a practical, no-nonsense guide that helps your team use Microsoft 365 Copilot more effectively, then the Microsoft 365 Copilot Team Training Guide is for you.

Get your copy here: Microsoft 365 Copilot Team Training Guide

Stop experimenting. Start mastering Copilot.

Your organisation has already invested in AI. Now it’s time to make sure everyone knows how to use it.

The Season Before the Leap

There’s a pattern I’ve noticed in almost every business that makes it through a genuine rough patch. It doesn’t show up on a spreadsheet or in a quarterly review. It shows up in the moments just before things turn — when most people would have stepped back and waited.

The hard season doesn’t announce itself as preparation. It just feels like pressure.

I’ve had stretches in my own work where the effort seemed disproportionate to the outcome. Clients weren’t growing as fast as I’d hoped. The pipeline felt thin. Tools I’d invested time in weren’t paying off yet. That combination — sustained effort, visible slowness, creeping doubt — is the exact moment most people quietly pull back and start looking for a simpler path.

But here’s what I’ve come to believe: the difficulty is often the signal, not the obstacle.

Reframing Isn’t Wishful Thinking

There’s an important difference between telling yourself “this will be fine” and actually changing what a challenge means to you. The first is denial. The second is something closer to strategic clarity.

When I hit a difficult period, I’ve started using Copilot in Microsoft 365 not just to triage my inbox or summarise a meeting, but to think through the problem itself. I’ll take a messy situation — a stalled project, a client relationship that feels off-track — and ask Copilot in Teams to reflect it back to me plainly. What’s the actual constraint? What am I not asking? What would this look like from the other side?

When you’re inside a problem, having something surface a different angle can shift your perspective faster than another hour of turning it over yourself. That’s reframing in practice. Not pretending things are easier than they are. Finding the angle you couldn’t see while standing too close to it.

Most People Opt Out Early

The reason hard seasons tend to precede the big leaps isn’t some hidden law of the universe. It’s selection.

When conditions get difficult, people and businesses that don’t have a genuine reason to push through — or haven’t built the habits that carry them when motivation fades — tend to step back. They wait for things to improve before committing again, before investing again, before showing up with full energy again.

That sorting is exactly why the ones who lean in come out with an advantage that simply wasn’t available during easier conditions. The competition thins. The clarity sharpens. Decisions made under real pressure tend to be more durable than the ones made when everything is comfortable.

I use Copilot in Outlook to stay on top of client communication even when my capacity feels stretched — a quick thread summary, a draft response I can refine rather than build from scratch. That keeps me present in conversations I’d otherwise let slip during a hard stretch. Not automation for its own sake. Staying in the game when it would be easy to go quiet.

What You Actually Build

The leap doesn’t come from surviving the difficulty. It comes from what you construct while you’re in it.

The habits, the thinking, the client relationships you kept up, the decisions you made with less certainty than you’d have liked — those compound. They show up later as capability that wasn’t there before, because it couldn’t have been developed any other way.

I don’t look back on the hard stretches as things I got through. I look at them as where most of the real work happened.

If you’re in one of those seasons right now, lean into it. Not because it’s comfortable — it isn’t. But because most people won’t. And that gap is exactly where your next leap begins.

You Don’t Have a Business Problem. You Have an Owner Problem.

I’ve watched a lot of MSP owners over the years, and the pattern is almost always the same. They tell me their business runs on hard work. Long days, early starts, the willingness to do whatever it takes. And for a while, that’s exactly what built the thing.

But here’s the uncomfortable bit. All that effort didn’t make them an owner. It made them the best technician in the building — the one person who can’t leave the room.

The tell-tale signs aren’t technical

You know the feeling. The phone buzzes and your stomach tightens before you’ve even looked at it. You’re “on holiday”, but you’re really just answering tickets from a nicer chair. The people at home get whatever’s left after the business has taken the good hours.

I used to think those were signs of a busy business. They’re not. They’re signs of an owner who has wired the whole operation around themselves. Every approval, every escalation, every “let me just check that” runs through one person. That’s not a scaling problem. That’s an identity problem.

A business is a mirror. It reflects whoever built it — their habits, their fears, their inability to let go. If you can’t step away, it’s usually because, somewhere along the line, you decided being needed was the same as being valuable.

Hard work hides the real bottleneck

The reason this is so hard to see is that effort feels like progress. You’re busy, so you must be building. But more hours rarely fix a business that depends on your hours.

What actually moves the needle is taking the knowledge living in your head and putting it somewhere the team can reach without you. This is where the tools earn their keep. When a senior tech finishes a tricky onboarding, Copilot in Teams can pull a clean summary of what was decided and who owns what, so the next person isn’t starting from your memory. Ask Copilot in Word to turn that into a repeatable runbook, drop it into a SharePoint site, and suddenly the process belongs to the business, not to you.

Same with the inbox that owns your attention. Instead of being the human router for every client question, let Copilot in Outlook draft the first reply and surface what genuinely needs your judgement. The goal isn’t to answer faster. It’s to stop being the only one who can answer at all.

Build the owner first

This is the shift I keep coming back to. You don’t escape the trap by working less or hiring more. You escape it by changing who you are inside the business — from the person who does the work to the person who builds the thing that does the work.

That means writing down how decisions get made, not just making them. It means letting Planner and Loop hold the to-do list so it isn’t all in your head at 11pm. It means being okay with the team doing it 80% your way instead of 100% your way and the work never getting done without you.

I’ve seen owners break through a ceiling they’d been stuck under for years, and it almost never starts with the business. It starts with them deciding to stop being indispensable.

Your business will only ever grow to the size of the owner behind it. So the real question isn’t how to work harder. It’s who you’d need to become for the business to run beautifully on a day you don’t show up.