{"id":37,"date":"2026-08-01T13:23:17","date_gmt":"2026-08-01T13:23:17","guid":{"rendered":"https:\/\/prequake.ai\/resources\/?p=37"},"modified":"2026-08-01T14:33:16","modified_gmt":"2026-08-01T14:33:16","slug":"the-friction-ledger-why-vague-findings-arent-findings","status":"publish","type":"post","link":"https:\/\/prequake.ai\/resources\/the-friction-ledger-why-vague-findings-arent-findings\/","title":{"rendered":"The Friction Ledger: Why Vague Findings Aren&#8217;t Findings"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Most diagnostic reports end with a findings section that reads like this: &#8220;communication needs improvement.&#8221; &#8220;Change fatigue is present in some teams.&#8221; &#8220;Leadership alignment could be strengthened.&#8221; Every sentence is true. None of them are useful, because none of them can actually be acted on by anyone \u2014 they don&#8217;t say who, what, or what to do about it Monday morning.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A finding that can&#8217;t be assigned to an owner isn&#8217;t a finding yet. It&#8217;s an observation waiting to become one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What makes something a finding, not an observation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Four things turn a vague theme into something a real organization can act on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>It&#8217;s specific enough to be wrong.<\/strong> &#8220;Communication needs improvement&#8221; can&#8217;t be disproven \u2014 there&#8217;s no version of a rollout where that sentence wouldn&#8217;t apply. &#8220;The logistics team wasn&#8217;t told the new system would change their escalation path&#8221; can be checked, and either is or isn&#8217;t true.<\/li>\n\n\n\n<li><strong>It names who it affects.<\/strong> Not &#8220;some employees&#8221; \u2014 which team, which location, which shift. A finding that applies to everyone equally usually isn&#8217;t a finding, it&#8217;s a restatement of the fact that change is hard.<\/li>\n\n\n\n<li><strong>It has a proposed owner.<\/strong> Not a name \u2014 a role. &#8220;Ops Lead&#8221; or &#8220;IT Director,&#8221; not a person, since the point is accountability by function, not by individual. A risk with no proposed owner reliably becomes nobody&#8217;s problem.<\/li>\n\n\n\n<li><strong>It has a next action, not a recommendation.<\/strong> &#8220;Improve communication&#8221; is a recommendation. &#8220;Publish the new escalation path and confirm it in the next team stand-up&#8221; is an action \u2014 someone can actually finish it and report back that it&#8217;s done.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Why the vague version is so tempting to write<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Generic findings are safer to write and harder to be wrong about. &#8220;Communication needs improvement&#8221; is true of almost every organization at almost every point in time \u2014 which is exactly the problem. A report that could have been written before a single interview happened isn&#8217;t adding information; it&#8217;s adding pages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Specific findings carry real risk for whoever writes them: they can be checked, disagreed with, and shown to be incomplete. That risk is also what makes them worth reading. A steering committee that&#8217;s seen a dozen &#8220;communication needs improvement&#8221; slides in past reviews has learned to skim past that sentence. A named risk with a named owner and a specific action gets read differently, because it&#8217;s the first version that could actually be wrong \u2014 and being checkable is what makes something credible.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ranked by prevalence, not by how interesting it is to write about<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The other discipline a real risk register needs: ordering by how often something actually came up across real conversations, not by severity as judged after the fact or by which finding makes the best story. A friction mentioned by one person in an offhand comment and a friction independently raised by a third of an affected team are not the same weight of evidence, even if the first one sounds more dramatic when quoted. Prevalence is what turns &#8220;someone said this once&#8221; into &#8220;this is a pattern,&#8221; and that distinction is most of what separates a risk register worth acting on from a collection of anecdotes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The test for any finding before it ships<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before a finding goes in front of a sponsor, it should survive one question: could someone read this on a Monday morning and know what to do by Tuesday? If the honest answer is &#8220;not really, it&#8217;s more of a theme,&#8221; it isn&#8217;t done yet \u2014 it&#8217;s still an observation, and it needs to get more specific before it earns a place in the report.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most diagnostic reports end with a findings section that reads like this: &#8220;communication needs improvement.&#8221; &#8220;Change fatigue is present in some teams.&#8221; &#8220;Leadership alignment could be\u2026<\/p>\n","protected":false},"author":1,"featured_media":38,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-37","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-frameworks"],"_links":{"self":[{"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/posts\/37","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/comments?post=37"}],"version-history":[{"count":1,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/posts\/37\/revisions"}],"predecessor-version":[{"id":39,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/posts\/37\/revisions\/39"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/media\/38"}],"wp:attachment":[{"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/media?parent=37"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/categories?post=37"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/tags?post=37"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}