Episode Overview

Have you been putting off a decision about AI — telling yourself you’ll deal with it when things slow down?

In this episode, I make a direct case for why that’s not a neutral choice. Not having a position on AI is itself a strategy. It just means someone else gets to define what it costs you.

I then break down three practical levels at which AI is already showing up in small and mid-sized businesses: information and support, automating activities, and evaluation and recommendations. I explain where most small and mid-sized organizations should start, how to build from there, and what to protect as your team begins to experiment.

If you’ve been waiting for the right moment to get serious about AI, this episode is it.

What You’ll Learn in This Episode 

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

Episode Overview

Have you ever invested in a system that your team quietly stopped using? Not because it was broken — but because it was just too complex to bother with on a busy day?

In this episode, I walk through the real story of a small organization that chose a capable CRM to manage their customer relationships — and watched it quietly create more problems than it solved. The system worked exactly as designed. But it was the wrong fit for the team that had to use it every day.

I break down six specific observations from this organization — from constant relearning and inadequate support, to data fragmentation and delayed action — and explains exactly how each one compounded the cost over time.

Then I turn those observations into a practical eight-question framework that any business leader can use when evaluating, selecting, or upgrading a system — regardless of industry, size, or the type of technology involved.

If your team is working around your systems instead of in them, this episode is for you.

What You’ll Learn in This Episode 

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

Episode Overview

Many businesses assume their technology is working simply because the systems are running.

But running isn’t the same as performing.

In this episode of End Business Tech Frustration, I explore a common problem that quietly drains productivity in small and mid-size businesses: systems that don’t talk to each other.

When software platforms aren’t integrated, employees often become the bridge between them—manually transferring information, verifying data, and reconciling records. Over time, this creates hidden costs that slow down operations, frustrate employees, and impact customer experience.

What You’ll Learn in This Episode

✔ Why people acting as the “integration layer” between systems is expensive

✔ The hidden operational costs of manual reconciliation and workarounds

✔ How disconnected systems create delays, bottlenecks, and key-person dependency

✔ Why technology that is “still running” may still be holding your business back

✔ The importance of evaluating whether your systems are aligned with your processes and growth

A Question for Business Leaders

Take a moment to reflect on your own organization:

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

Episode Overview

Most technology implementations don’t fail because of bad software.

They fail long before the system is ever turned on.

This episode reveals why, using a real-world case study of a mid-sized international manufacturer that replaced their  financial, procurement, manufacturing, and distribution systems. However, they never clearly defined what success needed to look like.

The result?

If you're a business leader planning a system upgrade, this episode will help you avoid the costly mistake of moving forward without measurable outcomes.

What You’ll Learn in This Episode

✔ Why undefined goals quietly derail technology initiatives

✔ How lack of measurable outcomes weakens organizational alignment

✔ How predictive AI features become “optional” without defined metrics

✔ Why process optimization suffers when performance targets are unclear

✔ How generic testing creates post–go-live surprises

✔ The decision-making framework that prevents implementation paralysis

✔ The one leadership question you must answer before signing a contract

The Core Lesson

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

Frequently technology implementations go-lives don't go smoothly. Orders get stuck, invoices can't be created, bills can't be paid, customers get angry, and teams spend weekends fixing what should have worked from day one. But some organizations turn on new systems and nothing breaks. This episode reveals exactly why, using a real-world case study of a mid-sized international manufacturer that replaced their core business systems without a single crisis.

What You'll Learn

Who Should Listen

Key Takeaways

Leadership Alignment Matters More Than Technology Success starts when senior leadership makes participation non-negotiable and communicates why the initiative matters to every level of the organization.

Test Real Work, Not Demos Critical workflows must be validated end-to-end under real conditions. If something doesn't work in testing, it won't magically work at go-live.

Answer the Critical Question What must work on day one for the business to operate? Prioritize those processes, validate them, and build contingency plans around them.

Readiness Over Training The real question isn't "Were people trained?" It's "Can people actually do their jobs in the new system under pressure?"

Plan for Problems Before They Exist Inventory staging, customer notifications, strategic timing, and contingency planning are all forms of intentional risk reduction.

Systems Fail Where Organizations Allow Gaps It's not bad luck when implementations fail. Systems break exactly where processes aren't documented, people aren't engaged, and assumptions replace validation.

Featured Case Study

A mid-sized international manufacturer and distributor replacing core systems for financials, procurement, manufacturing, distribution, and customer service. The initiative wasn't just a technology upgrade, it was a business-critical risk. Their approach eliminated go-live chaos through disciplined preparation, not larger budgets or complex tools.

Questions to Ask About Your Organization

Before your next technology initiative, consider:

Bottom Line

Technology implementations don't fail randomly. They fail exactly where organizations allow gaps to exist. The good news? Success is completely repeatable. It doesn't require massive budgets or complex tools. It just requires saying: "Before we turn this on, let's make sure it actually works for everybody who depends on it."

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

In this episode, I examine a cautionary tale about a well-funded, well-planned technology implementation that went horribly wrong—not because of bad technology, but because of organizational gaps that were never addressed. When a mid-size organization rolled out a new finance, purchasing, payroll, and CRM system, thousands of employees couldn't get paid, vendors went unpaid, and mortgages bounced. The hardest part? It was completely preventable.

This story isn't about technology failure—it's about what happens when people, processes, and organizational alignment are treated as optional rather than critical to success.

Key Takeaways

The Setup Was Sound

The Critical Mistake

What Went Wrong

The Root Cause This wasn't a technology failure—it was a people and process failure that manifested in the technology. The system did exactly what it was told to do; the problem was what it was never told.

Critical Questions for Your Organization

Before implementing any new system, ask yourself:

The Four Pillars That Must Align

Why This Matters for Every Organization

Size doesn't protect you. Small and mid-size businesses actually get hit harder when this happens because they have fewer people and less margin for error.

The cost of fixing always exceeds the cost of preventing. The organization in this story spent far more on emergency consultants, workarounds, and crisis management than they would have spent ensuring complete participation upfront.

Your system will fail exactly where it's weakest. If even one department opts out, that's where your system will break. It's not bad luck—it's simple physics.

How to Prevent This Disaster

The solution doesn't require fancy tools or massive budgets. It requires:

Bottom line: Before you turn the system on, make sure it actually works for everyone who depends on it.

Final Thought

Your technology will only ever be as strong as the people, processes, and organizational structure behind it. The next time you're planning a technology initiative, don't just ask "Is the technology ready?" Ask "Are we ready?"

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

A routine prescription refill should take two minutes. But when a healthcare provider botched their technology rollout, it turned into a two-day ordeal that cost them a long-term patient.

In this episode, I walk you through exactly what went wrong—and more importantly, the five simple steps that would have prevented the entire disaster. If you're a business leader planning any kind of technology change, this episode will show you how to avoid pushing your customers straight to your competitors.

This episode is for you if:

What You'll Learn

The Real Story Behind Technology Failures

The Five Elements Every Successful Rollout Needs

Why This Matters to Your Business

Key Takeaways

"Technology doesn't fail on its own. It fails when people, processes, and the organization aren't aligned around it."

"When technology disrupts and frustrates people, they don't blame the technology—they blame you."

"Poor technology, or good technology with poor rollout, pushes customers away. It costs you money, damages your reputation, and in competitive markets, those customers aren't coming back."

Action Items

Before your next technology rollout, ask yourself:

If you answered "not really" or "we'll figure it out" to any of these questions, you're setting yourself up for the exact disaster described in this episode.