OMNINEThe leaders who could not see their most expensive problems were not the least capable people in my study. Several of them ran strong operations at some of the largest companies in the world, and they were declining a technology wave for reasons that felt, from where they sat, like discipline. That combination, real competence next to real blindness, is the puzzle my doctoral research kept handing back, and the resolution was not flattering to anyone’s assumptions, including mine. What separated the leaders who adopted from the leaders who resisted was not intelligence, and the study ruled out the other comfortable explanations too: not budget, not company size, not age (Goodwin, 2014). What separated them was recognition, the plain act of seeing a cost the organization had stopped noticing. That deserves a name, because it is the gate most owners are standing at right now without knowing it. Call it the recognition problem: the mechanism by which capable leaders lose the ability to see expensive problems in their own operations, and this piece takes it apart, the evidence for it, the process that produces it, the three specific ways a cost stays hidden, and the protocol for manufacturing recognition on purpose.
What the interviews kept showing
The study set five Fortune 500 leaders who had adopted social business platforms against five who had resisted them, with nine surrounding interviews to check the leaders’ accounts against what their people saw, and the full construction is in adopters and resisters. The resisting leaders’ defining features were absences. Three of the five could not define the technology they were declining when asked directly, with one describing physical meetings and another describing social media. More striking for this piece’s purposes, the fragmentation in their own operations, the disconnected channels and rekeyed information their people navigated every day, had become invisible to them. They were not refusing to fix a problem. They could no longer see one, and from the inside, the not seeing felt like prudence, like focus, like declining a distraction (Goodwin, 2014).
The adopting leaders inverted the picture, and the inversion is where the concept earns its name. One of the eight themes the analysis surfaced was that platform users standardize communication: the adopters had recognized a concrete communication breakdown, information scattered across too many disconnected tools, and moved because a unified system fixed that specific, felt pain. Their decision was downstream of an act of sight. Adoption, in case after case, was less about loving new technology and more about finally seeing a cost the organization had normalized, then declining to keep paying it. Recognition was the scarce act. Everything after it, evaluating tools, running pilots, was comparatively easy and comparatively common.
Normalization, the machine that hides costs
How does a capable leader lose sight of an expensive problem? The mechanism is ordinary, which is why it is universal. Repetition converts anomalies into routine. The first time a team member rebuilds a quote by hand, it is an event, discussed and escalated. The tenth time, it is a task. By the fortieth, it is simply how quoting works here, defended by the very people it costs the most. The clearest field example I have watched is Advocate Roofing, where a version migration silently broke the connection between quoting templates and the supplier’s product library, and within weeks the sales team had absorbed the full manual rebuilding of every estimate into their normal workflow. A serious failure between two systems had become furniture. The complete diagnosis is in how a roofing company stopped rebuilding every quote by hand, and the part that belongs here is the speed: weeks, not years, from breakage to invisibility.
Scale the mechanism up and the numbers get large enough to be embarrassing. The McKinsey Global Institute estimated in 2012 that the average interaction worker spent 28 percent of the workweek on email and nearly 20 percent more searching for internal information or hunting down colleagues, close to half of every week spent moving information rather than acting on it (McKinsey Global Institute, 2012). That figure described the ordinary operating condition of white collar work, sitting in plain sight of an entire generation of managers, most of whom would have told you their organizations communicated fine. The cost was enormous, measured, published, and unrecognized, which is the recognition problem operating at the scale of an economy.
The three hiding mechanisms
Normalization explains that costs disappear. It takes three more specific mechanisms to explain how they stay hidden from smart people who are looking straight at them, and naming the three is the practical core of this piece, because each one has a distinct antidote.
The first mechanism is per-movement billing: the cost is charged per incident and never aggregated anywhere. A subscription arrives as a line item twelve times a year and gets scrutinized. A ninety second rekeying event arrives thousands of times a year and appears on no report, no statement, and no agenda, because nothing in a business’s accounting is built to sum it. The same total, presented once as a single annual invoice, would trigger a decision within the week. Presented as thousands of small withdrawals, it triggers nothing, and the business ends up governed by the format of its costs rather than their size.
The second mechanism is triviality: each individual charge is too small to escalate, and escalation is the only path by which problems reach a leader’s attention. Organizations are calibrated to detect events, the crashed system, the lost account, the angry customer, and are nearly blind to erosion, the steady loss that never once crosses the threshold a single incident needs to become a conversation. Nobody has ever called a meeting about ninety seconds, so a cost that only ever arrives in ninety second pieces has structural immunity from management, regardless of what it sums to.
The third mechanism is pride: the workaround reads as diligence, so the people paying the cost defend it. Chasing the update, catching the dropped handoff, holding the whole picture in your head, every one of these is experienced as conscientiousness and praised as such, which means questioning the chore feels like questioning the team. This is the cruelest of the three mechanisms because it recruits a business’s best people as the camouflage: the more conscientious the team, the more completely the broken flow is absorbed, and the prouder everyone is of the absorption. The resisting organizations in my research displayed exactly this texture, capable people diligently carrying costs their leaders could not see, and nobody anywhere behaving badly (Goodwin, 2014).
Notice what the three mechanisms share: each is a property of how the cost presents rather than of how large it is. Change the presentation, sum the movements, escalate the erosion, reframe the pride, and the same cost becomes visible without shrinking or growing at all, which is why the cures in the next two sections are acts of formatting as much as acts of analysis. The recognition problem is not defeated by thinking harder about the same view. It is defeated by changing the view.
Why outsiders and instruments can see what owners cannot
The three mechanisms also explain the two reliable cures, and neither one is intelligence. The first is unfamiliarity. An outside eye has not undergone the normalization, so the invisible chore looks like what it is, which is most of what an outside diagnosis contributes and the reason the roofing team’s rebuilding routine looked unremarkable to everyone inside the building and unmistakable from outside it. The second is instrumentation. Measurement defeats per-movement billing by doing the aggregation the accounting never will. Written counts defeat triviality by converting erosion into an event large enough to escalate. And a well framed audit defeats pride by blaming the flow rather than the people, which frees the team to report the chores they were quietly proudest of surviving. Recognition, in other words, does not require a smarter leader. It requires a leader willing to point an instrument at their own operation, and the instinct to reach for measurement before opinion is the same one that separates a real assessment from a scored questionnaire, the anatomy laid out in inside Assess: what the first stage really measures.
Manufacturing recognition on purpose
Because the mechanisms are specific, the protocol against them can be too, and it runs in three steps that map one to one.
The first step is to aggregate. Run one week of light logging across the team, every incident of rekeying, chasing, dropping, and rebuilding, with rough minutes attached, then tally it on Friday. This is the audit built in the communication tax your business pays every day, and its entire function is to give the per-movement cost the one thing it has never had, a total.
The second step is to externalize. Trace one real transaction end to end through every system it touches, a real quote, a real booking, a real invoice, and watch where a person carries it by hand. Walking the path as an observer borrows the outsider’s unfamiliarity without hiring the outsider, and the hand carried segments you find are your operation’s versions of the rebuilt quote.
The third step is to interrogate the pride. Ask the team what they are proudest of catching, the near misses, the saves, the things that would fall apart without them, and write the answers down. Every save on that list is a flow that failed upstream and got rescued by conscientiousness, which makes the pride list a map of broken flows, volunteered cheerfully by the people who know them best. Handled with the respect it deserves, this step converts the camouflage into the reconnaissance.
Run all three and recognition stops being a trait some leaders have and becomes a practice any leader can schedule, which matches the most hopeful thing the research found: the differences between adopters and resisters were behaviors, not personalities, and behaviors move.
Where this gets challenged
If the problem were expensive, we would have noticed. That sentence is the recognition problem speaking in the first person. Noticing is precisely the faculty the three mechanisms disable, and the study’s whole point is that the failure to notice happened to demonstrably capable leaders running otherwise strong operations. The claim is not that you are careless. The claim is that per-movement billing, triviality, and pride hide costs from careful people specifically, and the honest response to the sentence is not offense but a week of logging, since the tally will settle it one way or the other with your own numbers.
A consultant naming an invisible problem is a consultant inventing one. Fair suspicion, and the protocol is built to survive it, because every step produces figures from your operation rather than mine. The audit counts your team’s minutes. The trace follows your transaction. The pride list is written in your people’s words. If the tally comes back small, you have purchased certainty for one week of light attention, and some businesses will run the numbers and rationally decide the cost is worth carrying for now, which is a legitimate outcome. The only outcome the research argues against is continuing to pay a bill no one has ever read.
Recognition without capacity is just anxiety. This one is right as far as it goes, and it is why recognition sits at the front of a sequence rather than standing alone. Seeing the cost is what my research says starts adoption, and what happens next has a structure: the named problem feeds a designed fix, the fix gets built and measured, and the whole path is walked in how an Omnine engagement runs. Recognition also pairs with a second act of sight aimed at the technology itself, since seeing the problem and understanding the tools are the two halves of the adopter profile, and the second half cascades through an organization by rules of its own, mapped in the awareness cascade.
The first act of adoption is an act of sight
Strip the technology away and the finding underneath this entire body of research is almost uncomfortably simple. The leaders who moved were the ones who saw. Not the youngest, not the richest, not the most technical, the ones who recognized a cost their organization had normalized and decided to stop paying it. Everything Omnine builds sits downstream of that act, which is why the practice begins with instruments rather than tools. Start the meter reading this week: log the week, trace one transaction, ask the pride question at Friday’s tally. And if you want a structured read on where recognition is most overdue in your operation, that act of seeing is what the Omnine AI Readiness Assessment exists to start, about three minutes to surface the lever, and the cost, you have been standing too close to notice.
References
Goodwin, M. R. (2014). A qualitative descriptive multiple-case study: Fortune 500 leaders’ social business platform adoption (Doctoral dissertation, University of Phoenix). ProQuest Dissertations Publishing (UMI No. 3648813).
McKinsey Global Institute. (2012). The social economy: Unlocking value and productivity through social technologies.