During IDS, our leadership team constantly blames our software or manual tools for operational breakdowns. How do we uncover the root human or process issue behind technology complaints?

Question

Tyler Smith · Accepted Answer

Blaming software is the most common smoke screen in small and mid-sized businesses. It is emotionally easier to blame an application, an ERP, or a CRM than it is to admit that a seat owner lacks GWC or that the team is ignoring standard operating steps.

When a leadership team member raises a tech issue during the Identify step, the Integrator must immediately prohibit discussion about features, vendors, or new software platforms. Drill directly into human behavior and process compliance with three diagnostic questions:
- Is there a documented Core Process for this workflow, and is it being followed by all?
- Did the software fail technically, or did team members fail to enter clean, timely data into the system?
- Does the person responsible for this output have the capacity and skill to operate the current tool effectively?

In most instances, the team discovers that the software works fine, but people bypass steps, ignore required fields, or refuse to hold their direct reports accountable for data hygiene. When you peel away the technical complaints, the real issue behind the issue is almost always unclear accountability on the Accountability Chart or lack of process discipline.

Never approve a software migration or build a quarterly Rock around buying new tools until you have verified that your existing process is documented, simplified, and followed by all. Automating or digitizing a broken process only produces faster chaos.