A system replacement case study and how CLEAR would have set the right date

Episode Overview

How many times has a go-live date moved on one of your technology projects? In this case-study episode, Jim Kineon walks through an electric utility that replaced its old customer system (CRM) so call-center staff could see everything about a customer in one place. The plan was right, and the project eventually succeeded, but go-live slipped several times as data migration, custom functionality, and undefined processes surfaced one after another. Jim then replays the project through the CLEAR Framework to show where each delay could have been caught and how the right go-live date would have been set from the start. If you're planning a system replacement, or living through one that keeps slipping, this episode is for you..

In This Episode, You’ll Hear

• What happens when your staff become the connection between disconnected systems

• Why a project with the right plan can still miss its go-live date several times

• How writing training materials exposed processes nobody had defined

• The real cost of a delayed-but-successful go-live

• How the five steps of CLEAR would have found the root causes and set a realistic date

.

THE FRAMEWORK — CLEAR

1. Check: Assess your current technology health across Initiative, Organization, Process, People, and Technology, and identify the root causes creating friction.

2. Link: Connect the root-cause fix to a measurable business outcome, not a feature list.

3. Establish: Prioritize improvements, define responsibilities, identify dependencies, and build a practical sequence of action.

4. Activate: Implement the roadmap while managing communication, testing, training, and support.

5. Review: Measure progress, compare it to the outcome you wanted, and keep refining until you get there.

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

Subscribe to My YouTube Channel

https://www.youtube.com/@jameskineon4185

Episode Overview

Is your team paying for software capability it never actually uses? In this episode, Jim tells the real story of a small nonprofit with fewer than 25 employees, running mostly on volunteers, whose CRM had grown far more complex than the organization needed, with training nobody could find, support that couldn't keep up, and event data that had to be reconciled by hand. Jim uses their story to walk through CLEAR, his five-step process for making any technology decision: Check, Link, Establish, Activate, and Review. This episode is for business leaders and nonprofit executives who suspect their current system has outgrown their actual needs, and want a real, step-by-step example of how to right-size it.

In This Episode, You’ll Learn

Six lessons this case study teaches about any CRM decision:

1. Right-size the software to your actual needs, not your ambitions.

2. Follow a real implementation plan — don't skip steps because the system feels smaller.

3. Clean your data before it moves, so you're working from one reconciled set of contacts.

4. Decide, on purpose, how much history you actually want to bring with you.

5. Train people for the job they do, not just the buttons in the software.

6. Match your support agreement to how fast you actually need an answer.

THE FRAMEWORK — CLEAR

1. Check: Assess your current technology health across Initiative, Organization, Process, People, and Technology, and identify the root causes creating friction.

2. Link: Connect the root-cause fix to a measurable business outcome, not a feature list.

3. Establish: Prioritize improvements, define responsibilities, identify dependencies, and build a practical sequence of action.

4. Activate: Implement the roadmap while managing communication, testing, training, and support.

5. Review: Measure progress, compare it to the outcome you wanted, and keep refining until you get there.

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

Subscribe to My YouTube Channel

https://www.youtube.com/@jameskineon4185

Episode Overview

If the person who runs your financial system disappeared tomorrow, would your business still function? In this episode, Jim Kineon shares a true story from a company he worked with in the World Trade Center that had just finished replacing its financial and supply chain management systems the week of September 11th, 2001. Their technology backup worked perfectly, but no one had documented who could approve an invoice or release a vendor payment if the usual person wasn’t there, and it took months to get the business running smoothly again. Jim breaks down what this means for any business running financial or supply chain systems today, and offers a simple test for finding out how exposed your own organization really is. This episode is for any leader who has never asked what happens to their approval process the day the one person who knows it isn’t in the room.

In This Episode, You’ll Learn

• The real story of a financial and supply chain system that survived 9/11, and the business that struggled
• Why a technology backup and a business continuity plan are not the same thing
• What happens when an approval workflow only exists in one person’s head
• The One-Person Test, a quick way to check your own organization’s exposure
• What to document before your next system goes live
• Why organizations of every size, from 25 employees to 250, carry this same risk

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

Subscribe to My YouTube Channel

https://www.youtube.com/@jameskineon4185

Episode Overview

You picked your new accounting system. Now what?

In this episode, Jim Kineon walks through what actually has to go right — before and after go-live — for an accounting and financial reporting software implementation to succeed. Using a real case study of a mid-size manufacturer, distributor, and retailer, Jim shows how a go-live can look like nothing changed while the real business outcome takes months, or years, to show up.

Jim breaks down what to prepare before you migrate, what a real implementation can expose about your organization, how the plan changes as you grow, and what ownership looks like after the system is live.

If you've already chosen your software and you're wondering whether your organization actually knows how to implement it, this episode is for you.

In This Episode, You’ll Learn

• Why go-live is a milestone, not the actual goal, of an implementation
• The four things to prepare before you migrate: data, process, people, and support
• A real case study of a luxury goods manufacturer whose “successful” go-live still took years to pay off
• How implementation planning changes as you grow from 25, to 100, to 250 employees
• Why separating who creates, approves, pays, and reconciles matters more than people think
• What ownership looks like after go-live, and why the job isn't finished when the system turns on

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

Subscribe to My YouTube Channel

https://www.youtube.com/@jameskineon4185

Episode Overview

In this episode of End Business Tech Frustration, Jim Kineon explains how small and mid-size business leaders should evaluate accounting and financial reporting software. The episode covers what the software is supposed to do, why financial systems become more important as businesses grow, how needs change from 1–25 employees, 26–100 employees, and 101–250 employees, and what to consider when choosing accounting and financial reporting software for your business.

In This Episode, You’ll Learn

• Why accounting software is really about trusted decisions, not just bookkeeping.
• What core functionality every accounting system should provide.
• How accounting needs change as a business grows.
• What to look for in systems for 1–25, 26–100, and 101–250 employee organizations.

Why This Matters

For small and mid-size business leaders, financial reporting problems create more than accounting frustration. They affect cash decisions, hiring, pricing, payroll confidence, board reporting, grant compliance, customer billing, vendor payments, and growth planning. If the accounting system is poorly selected or poorly implemented, the business may end up with more spreadsheets, more rework, weaker controls, and less confidence in the numbers.

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

Subscribe to My YouTube Channel

https://www.youtube.com/@jameskineon4185

Episode Overview

In this episode of End Business Tech Frustration, Jim Kineon explains how small and mid-size business leaders should evaluate Supply Chain Management software. He breaks down what SCM software does, why it matters, which features to look for, how needs change by company size, and how to avoid overbuying, under-planning, or choosing a system that creates more operational friction.

In This Episode, You’ll Learn

• What SCM software actually does beyond basic inventory tracking
• Why supply chain problems are often people, process, data, and support problems
• How to evaluate SCM software for 1–25, 26–100, and 101–250 employee organizations
• Which features matter most at each stage of growth
• What questions to ask vendors to uncover limitations before signing
• Why data migration, training, support, criticality, and downtime must be part of the decision

Why This Matters

SCM software can improve purchasing, inventory accuracy, supplier coordination, order fulfillment, warehouse operations, shipping reliability, and reporting. But when the wrong system is chosen or when implementation is rushed, it can create more confusion, more workarounds, and more frustration. For small and mid-size businesses, the goal is not to buy the biggest system. The goal is to choose the right system for the actual business, the actual team, and the next stage of growth.

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

Subscribe to My YouTube Channel

https://www.youtube.com/@jameskineon4185

Episode Overview

Someone told you your business needs a CRM. And now you're drowning in options, features, and pricing pages that all say essentially the same thing. Which one is right for your team?

In this episode, Jim Kineon breaks down what a CRM actually is and what it's designed to do, and then walks through a practical framework for evaluating CRM software based on the size and maturity of your organization. Whether you have 12 employees or 200, the right CRM is not the one with the most features. It's the one that fits your team, your process, and where your business actually is right now.

In This Episode, You’ll Learn

• Why CRM selection is not a feature comparison, and what question you should actually be asking

• What a CRM is genuinely designed to do, and the difference between core and advanced functionality

• A real case study of a business that upgraded their CRM to get a complete picture of their customer including: purchases, contract agreements, marketing campaigns, billing and payment history.

• How to evaluate CRM software for a 1–25 person organization, including what to look for and what to avoid

• How CRM requirements and risks change as you grow to 26–100 and 101–250 employees

• The hidden costs of data migration, post-launch support, criticality, and what happens during downtime

• How to know if your organization is actually ready for a new CRM

Why This Matters

The best CRM is not the one with the most features. The best CRM is the one your team will actually use, can afford, and can manage without creating unnecessary complexity.

Connect With Me On LinkedIn

www.linkedin.com/in/jimkineon

Subscribe to My YouTube Channel

https://www.youtube.com/@jameskineon4185

Episode Overview

Choosing software should not begin with demos, feature lists, or vendor promises. It should begin with clarity. In this episode, Jim Kineon explains why business and nonprofit leaders need to define what they are trying to achieve before evaluating a software application. Using CRM software as an example, Jim walks through the importance of requirements, user needs, support, training, organization size, and practical business outcomes.

In This Episode, You’ll Learn

• Why software selection should begin with business outcomes
• How to create a first list of software requirements
• Why features are only one part of the evaluation process
• How user skill level affects software adoption
• Why support and training should be considered before buying
• How requirements change for organizations with 1–25, 26–100, and 101–250 employees

Why This Matters

Many small and mid-size organizations choose software while they are still unclear about the real problem they are trying to solve. That creates risk. The system may look good in a demo but fail in real use because it does not match the organization’s process, people, support needs, or size. Clear requirements help leaders make better decisions, reduce implementation risk, and choose systems that support the business instead of slowing it down.