<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ron McKay on Medium]]></title>
        <description><![CDATA[Stories by Ron McKay on Medium]]></description>
        <link>https://medium.com/@oldmanrunning?source=rss-7c7ab4a5fe36------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*QQy93Jqh8OHWjjxk.jpeg</url>
            <title>Stories by Ron McKay on Medium</title>
            <link>https://medium.com/@oldmanrunning?source=rss-7c7ab4a5fe36------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:31:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oldmanrunning/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AI Loves Problem-Rich Environments]]></title>
            <link>https://medium.com/@oldmanrunning/ai-loves-problem-rich-environments-51990600ad4d?source=rss-7c7ab4a5fe36------2</link>
            <guid isPermaLink="false">https://medium.com/p/51990600ad4d</guid>
            <category><![CDATA[data-platforms]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[value-creation]]></category>
            <dc:creator><![CDATA[Ron McKay]]></dc:creator>
            <pubDate>Mon, 01 Jul 2024 10:16:24 GMT</pubDate>
            <atom:updated>2024-07-01T10:16:24.375Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*By_QCXFuA6PVwEwB" /></figure><h3>tl;dr — AI models are tools, but like all tools, their value lay only in problem-specific applications.</h3><p><em>Part 3 of #x series discussing the use of Intelligent Data platforms and Artificial Intelligence systems.</em></p><p>AI models are tools, but like all tools, their value lay only in problem-specific applications.</p><p>The enterprises who seemed to have the greatest success with their AI projects are those starting their funnel with numerous potential problems across a variety of business functions where AI could be applied. This is because, like all good innovation portfolios, AI efforts should be a funnel of projects. When striving for AI value, efforts should first start with idea generation around the art of the possible. These ideas should then be filtered through questions of data availability. Those with suitable data sources should then be considered for their potential value to the organization. This inevitable filtering of new AI opportunities will ultimately reduce to a handful of plausible projects, meaning that the top of the funnel requires a lot of potential problems or opportunities.</p><p>Initial conversations around the application of AI should be far more design thinking than machine learning. Before a single bit of data is cleaned or a single line of code written, efforts should be undertaken to identify the feasibility, data availability, and potential value of any project. In this approach, far greater value and likelihood of success is possible when building POCs or MVPs.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/ai-loves-problem-rich-environments-ron-mckay-bz3mc/?trackingId=HHRfK7NqQXqhxe0efrzRww%3D%3D"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51990600ad4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Criticality of the AI Translator]]></title>
            <link>https://medium.com/@oldmanrunning/criticality-of-the-ai-translator-5d88ade5c07e?source=rss-7c7ab4a5fe36------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d88ade5c07e</guid>
            <category><![CDATA[value-creation]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[data-platforms]]></category>
            <dc:creator><![CDATA[Ron McKay]]></dc:creator>
            <pubDate>Mon, 01 Jul 2024 10:15:11 GMT</pubDate>
            <atom:updated>2024-07-01T10:15:11.065Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/621/0*TTBCujn0r74XvkVx" /></figure><h3>tl;dr — Focus in needed in AI initiatives between leadership’s strategy and developers’ implementation.</h3><p><em>Part 2 of #x series discussing the use of Intelligent Data platforms and Artificial Intelligence systems.</em></p><p>Though change management may bottleneck some of AI projects, the other challenge and a common source of failure for AI projects is the lack of a sort of AI translator role: an interpreter of strategic vision, evangelizer of AI value, and architect of AI models and approaches. This person could be a strategically-minded developer who evolves into a higher calling or a business leader with a penchant and curiosity for learning about tech. Their origin is far less important than their function. The translator acts as a go-between for the technical and strategic, constantly swapping hats to ensure that both sides are well considered and, as change inevitably happens over the course of a project, that people on both sides of the wall are aligned and bought-into the project outcome and value.</p><p>The implication: I witness many organizations recognize this role and have matured into people with this as a role title. If you can’t identify this person in your organization, there is a chance it could be you, or no one. Many people informally and unwittingly play this role, however, there is tremendous value in making the role explicit. By doing so, both sides have someone to hold accountable and be accountable to. This role is most important upfront, when filtering a long list of potential projects down by jointly weighing the feasibility and viability of a project. However, the role retains value over time as a project evolves to ensure alignment with all stakeholders.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/criticality-ai-translator-ron-mckay-wamdc/?trackingId=HHRfK7NqQXqhxe0efrzRww%3D%3D"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d88ade5c07e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Not Everyone is Allowed to Play]]></title>
            <link>https://medium.com/@oldmanrunning/not-everyone-is-allowed-to-play-5a60e049367e?source=rss-7c7ab4a5fe36------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a60e049367e</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[governance-and-tech]]></category>
            <category><![CDATA[responsible-ai]]></category>
            <category><![CDATA[data-platforms]]></category>
            <dc:creator><![CDATA[Ron McKay]]></dc:creator>
            <pubDate>Mon, 01 Jul 2024 10:10:19 GMT</pubDate>
            <atom:updated>2024-07-01T10:10:19.457Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*3XxhVFPAW1qqwGSy" /></figure><h3>tl;dr — do we need a sign around all of our data and AI tools that reads: ‘danger lurks here’?</h3><p><em>Part 1 of #x series discussing the use of Intelligent Data platforms and Artificial Intelligence systems.</em></p><p>Risks associated with centralized data structures necessitate a barrier to entry for who gets to work with them. Particularly for more mature organizations that have centralized their data, processes, and tools, users of these systems have the potential to, at best, waste valuable time playing with models that have no business value, and at worst, cause irreparable damage to datasets that can set the organization back. While some of these challenges can be prevented through appropriate permissioning, ultimately the solution to this problem is that of good judgement. Technically minded people need to develop good business judgement in order to know how to use their time effectively. Business minded people need to develop good technical judgement to know how to respect the complexity of such systems and play within their own capabilities.</p><p>Perhaps a need for having badges or certifications required before anyone can access certain datasets or tools. Ultimately, this is a question of education surrounding people who play with data and AI, however, with technologies, tools, and approaches constantly evolving, the education becomes less about specific skills and knowledge, and more about instilling a sense of good judgement and responsibility around use.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/everyone-allowed-play-ron-mckay-dwkec/?trackingId=HHRfK7NqQXqhxe0efrzRww%3D%3D"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a60e049367e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>