{"id":138222,"date":"2026-08-06T02:31:08","date_gmt":"2026-08-06T02:31:08","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2026\/08\/06\/building-organizational-intelligence-oreilly\/"},"modified":"2026-08-06T02:32:14","modified_gmt":"2026-08-06T02:32:14","slug":"building-organizational-intelligence-oreilly","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2026\/08\/06\/building-organizational-intelligence-oreilly\/","title":{"rendered":"Building Organizational Intelligence \u2013 O\u2019Reilly"},"content":{"rendered":"

<\/a>\n<\/p>\n

\n

Introduction<\/h2>\n

Not way back, one in every of my engineering administrators got here to me with a request: His workforce appeared overloaded, and he needed to rent one other engineer. I made a decision to check a analysis assistant I had been constructing\u2014an AI agent related to our inner techniques through MCP\u2014by asking it to investigate the workforce\u2019s workload and write a hiring case.<\/p>\n

What got here again was thorough. Headcount, service possession, dash velocity, ticket backlog, and capability allocation, all of it neatly summarized. However studying via the doc, I felt the identical frustration I\u2019d felt with each AI-generated organizational report that\u2019s come throughout my desk. It informed me what was taking place<\/em> with out serving to me perceive why<\/em>, or what I ought to really do. It was organized across the knowledge quite than across the resolution. In brief, it was the form of response that\u2019s simple to agree with and troublesome to behave on.<\/p>\n

Then I added another factor to the configuration: the O\u2019Reilly Knowledgeable MCP server. I reran the identical evaluation and requested a barely totally different query: \u201cHow would the specialists on O\u2019Reilly assessment this request?\u201d<\/p>\n

As an alternative of main with headcount and ticket counts, the output now opened with a discovering: \u201cThe operational overhead drawback is structural, not a staffing deficiency.\u201d Citing the Google SRE framework\u2019s idea of operational toil<\/a>, it famous that the workforce was working at roughly 67% toil, effectively above the edge at which the SRE literature recommends structural intervention, and made particular, concrete suggestions: run a toil audit, set specific discount targets, and assign operational runbook possession. This wasn\u2019t a advice for whether or not to rent or not. It was a grounded, traceable argument for doing one thing else as a substitute.<\/p>\n

That distinction\u2014between a knowledge abstract and an expert-grounded advice\u2014is what this paper is about.<\/p>\n

What follows is a case research of how we constructed an organizational intelligence system at O\u2019Reilly, utilizing our personal platform as a core part. The strategy I describe is grounded in engineering as a result of that\u2019s the place I work, however it generalizes to any operate the place necessary data is scattered throughout a number of techniques and necessary selections require synthesizing all of it. The recipe has 4 steps: map your info hierarchy; join these techniques to an LLM through MCP and write a ability file that defines the way it ought to purpose; add the O\u2019Reilly Knowledgeable MCP as an professional assessment layer that grounds the evaluation in established frameworks; and construct a light-weight system for human-in-the-loop assessment. I\u2019ll clarify every step intimately and make the case for why the third step is the one which adjustments every part.<\/p>\n

Why organizational intelligence is getting more durable<\/h2>\n

To know the issue this strategy solves, it helps to look briefly at how engineering has modified over the previous three many years. These forces have performed out first and quickest in engineering, however as AI instruments proliferate past the engineering workforce, the underlying dynamic of extra output, extra selections, and extra scattered info is spreading to each a part of the group.<\/p>\n

Within the waterfall period of the Nineties, software program organizations ran on central plans. Every thing was specified up entrance, and leaders maintained visibility exactly as a result of all info flowed via a single coordinating doc. The plans have been brittle and sometimes fictional by the point they have been executed, however not less than everybody knew what was presupposed to be taking place.<\/p>\n

Agile changed central plans with small, autonomous groups working briefly sprints, and this solved the reliability drawback whereas making a visibility drawback. Vital selections started taking place domestically and shortly\u2014the fitting groups making the fitting calls\u2014however the info wanted to see throughout all of these selections splintered into dozens of separate instruments. Product technique lived in a single system, challenge execution in one other, code in a 3rd, and repair possession in a fourth. Extra issues obtained shipped, however the big-picture view obtained more durable to take care of.<\/p>\n

The agentic period has intensified this dynamic dramatically. Particular person engineers at this time can ship in a day what used to take a full dash workforce. The output is extraordinary, however the visibility is almost gone.<\/p>\n

\"slide11_Odewahn\"<\/figure>\n

Any effort that spans a number of groups, resembling a platform migration, a shared infrastructure change, or a reorganization, now requires monumental coordination overhead just because the knowledge decision-makers want to grasp the total image is distributed throughout too many locations. And this isn\u2019t an issue distinctive to engineering. It exists in any operate that runs on knowledge unfold throughout a number of techniques.<\/p>\n

Confronted with this visibility drawback, I needed to construct one thing I might ask big-picture questions and get synthesized solutions again shortly. Issues like:<\/p>\n