Stupidity In Management

I learned this distinction the hard way while reviewing business decisions after problems had already become expensive. Early reviews often focused on the visible error: the wrong order, the missed follow-up, or the poor hire. A better question produced better answers: “What happened before, and what changed afterward?” That question forms the basis of the Foolishness Signal Map, the method used here. It works because it examines repeated behavior, not personality. It gives you a record to act on instead of a label to throw at someone.

The Foolishness Signal Map

The Foolishness Signal Map separates an isolated mistake from a recurring pattern by checking four signals: repetition, warning, response, and spread. One error does not prove a management problem. Repeated errors, ignored warnings, weak correction, and damage spreading to other work create a much stronger signal.

Use the map in this order:

1. Record the event. Write the date, decision, cost, and immediate result. “The team undercharged a Saturday emergency call by $180” gives you something useful. “Pricing was careless” does not. 2. Check repetition. Search the previous 30 to 60 days for similar decisions. Look at invoices, schedules, customer complaints, stock records, and staff messages. Repetition shows whether the event stands alone. 3. Identify the warning. Ask what information was available before the decision. A missing supplier quote, an ignored calendar conflict, or a previous complaint counts as a warning only if someone could reasonably have seen it. 4. Measure the response. Record what changed after the problem. Did the person correct the price sheet, ask for help, or repeat the same choice? Response separates a teachable mistake from stubborn poor judgment. 5. Trace the spread. Check whether the decision affected cash, customers, staff workload, or your time. A $50 error that forces three hours of rework signals more than its price alone. 6. Choose the smallest effective action. Fix a rule, coach a person, add an approval step, or change responsibility. Match the response to the pattern rather than the emotion of the moment.

A useful original measure is the Three-Event Rule: do not call a behavior a management pattern until you find three comparable events, unless one event creates immediate danger, legal exposure, or a serious cash threat. Three events do not make the judgment automatic, but they force you to compare evidence. For example, one missed stock order may reflect unusual pressure. Three missed orders in six weeks, each after the inventory warning fell below the reorder point, demand a management response.

The second measure is the Correction Test. After the first event, state the needed change in writing and set a deadline. If the person makes the change, the problem may be limited. If the person agrees but repeats the behavior, the signal strengthens. If the person hides the event or blames others, treat that response as part of the pattern. A business cannot improve when its records protect pride instead of showing facts.

Do not confuse a bad result with bad judgment. A technician can follow the correct diagnostic process and still meet an unusual fault. A manager can make a sound hiring decision that fails because the applicant misrepresented experience. Your map asks whether the decision made sense with the information available at the time. That protects capable people from punishment and directs attention toward choices they could control.

Applying the Map to a Growing Service Business

Consider a heating and cooling company with eight employees, $92,000 in monthly sales, and a growing service area. The owner notices that emergency jobs often produce little cash despite strong demand.

1. Record the first event. On March 4, a technician quotes an emergency repair at $240 without checking the current parts price of $165. Labor and travel leave the job $40 short of break-even. The owner records the invoice, parts cost, and margin. 2. Search for repetition. On March 8 and March 16, two other emergency jobs show the same problem. The owner reviews 30 days of invoices and finds six underpriced jobs, costing about $780 in lost gross profit. 3. Find the warning. The pricing sheet, stored in the shared drive, shows updated parts costs. The team also received a text message on February 28 telling technicians to check the sheet before quoting emergency work. 4. Run the Correction Test. On March 18, the owner holds a 20-minute meeting, demonstrates the quote process, and requires every emergency quote above $500 to receive a second check for the next two weeks. 5. Measure the next results. During the following 14 days, technicians complete 19 emergency jobs. All quotes use the updated parts prices, and the company recovers an estimated $1,140 in gross profit compared with the earlier pricing pattern. 6. Trace the spread. The owner discovers that the office team also copied old prices into three customer estimates. The problem was not one careless technician; the business lacked one controlled pricing source. The owner removes the old file, names one current sheet, and adds a weekly price review. 7. Set the response. The owner coaches the team, changes the pricing process, and reviews the next 20 emergency invoices. No warning signs justify firing anyone. The evidence points to a weak system reinforced by repeated checking failures.

The expected outcome is not simply better pricing. The owner now knows how to investigate future problems without guessing. The Foolishness Signal Map showed repetition, an ignored warning, a measurable correction, and spread across roles. That combination justified a process change rather than a personal attack.

Quick checklist

• Record the event with a date, decision, cost, and result. - Compare at least 30 days of similar work. - Identify information available before the decision. - Write one correction and set a deadline. - Review the next 10 to 20 comparable events. - Check whether the problem spread to cash, customers, staff, or your time. - Choose coaching, a rule change, approval, reassignment, or discipline based on the evidence.

Use the checklist within 48 hours of a serious error. Waiting several months allows memory, excuses, and incomplete records to replace facts.

Mistakes That Distort the Signal

Treating every mistake as stupidity

A new employee may make one wrong entry while learning your software. Calling that person foolish creates fear and encourages concealment. Apply the Three-Event Rule unless the error creates immediate danger or major financial exposure.

Do this: Record the event, explain the correct action, and review the next five similar tasks.

Not this: Remove responsibility after one error or announce that someone “always gets things wrong.”

Counting results without examining the decision

A job can lose money even when the manager followed the available information. Conversely, a profitable job can result from a reckless decision that happened to work. Judge the process, warnings, and response, not luck.

Do this: Ask what the person knew, what they checked, and what choice made sense at that moment.

Not this: Praise every profitable gamble or punish every disappointing outcome.

Ignoring the owner’s role

Owners often call staff foolish for repeating a process the owner designed. If the price sheet has three versions, no one owns updates, and urgent work bypasses review, the business helped create the pattern.

Do this: Map the conditions around the decision, then fix unclear tools, authority, or deadlines before blaming an individual.

Not this: Add another warning message to a broken process and expect behavior to change.

The practical task now is simple: choose one recurring problem from the past 60 days and complete a Foolishness Signal Map for it. Record the event, find comparable cases, identify the warning, run the Correction Test, and measure the spread. You may discover a person who needs firmer accountability, a process that needs repair, or an owner habit that keeps inviting the same poor judgment. That distinction is the first step toward managing growth without allowing foolishness to become the company’s normal way of working.

End of chapter one. 39 more chapters and about 72,900 words in the full book.