<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Governance on Christa Burger</title><link>https://christaburger.com/tags/ai-governance/</link><description>Recent content in AI Governance on Christa Burger</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 07 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://christaburger.com/tags/ai-governance/index.xml" rel="self" type="application/rss+xml"/><item><title>Post 6 of 5: How the Quest Layer Actually Works</title><link>https://christaburger.com/blog/quest-guide-how-it-works/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/quest-guide-how-it-works/</guid><description>&lt;p&gt;&lt;em&gt;Bonus post in the series: The Quest Guide Era — Why Enterprise Work Needs More Than Dashboards&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;At some point, every good metaphor has to come down from the clouds and pass through an operating model. This is inconvenient, because the clouds are very pretty and the airships have excellent lighting, but eventually someone reasonable will ask, &amp;ldquo;Okay, charming, but how does this actually work?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;And they should ask that. If the quest layer is going to be more than a beautiful idea, it has to connect to the real machinery of work: objectives, teams, owners, evidence, decisions, risks, progress, and outcomes. Otherwise we have not built an operating model. We have built a screensaver with ambitions.&lt;/p&gt;</description></item><item><title>Corporate Work Is Already a Quest. We Just Keep Calling It Alignment.</title><link>https://christaburger.com/blog/quest-guide-alignment/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/quest-guide-alignment/</guid><description>&lt;p&gt;&lt;em&gt;2 of 5 in the series: The Quest Guide Era — Why Enterprise Work Needs More Than Dashboards&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Corporate work is already a quest.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s just a bit difficult to tie together because &amp;ldquo;quest&amp;rdquo; sounds unserious, while &amp;ldquo;cross-functional strategic alignment initiative&amp;rdquo; sounds like something that will get you a promotion.&lt;/p&gt;
&lt;p&gt;But structurally, the quest metaphor is much closer to reality — because if you have never observed that Q4 is every end-of-season boss battle, you aren&amp;rsquo;t using your creativity enough.&lt;/p&gt;</description></item><item><title>Enterprise Work Has Outgrown the Dashboard</title><link>https://christaburger.com/blog/quest-guide-dashboard/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/quest-guide-dashboard/</guid><description>&lt;p&gt;&lt;em&gt;1 of 5 in the series: The Quest Guide Era — Why Enterprise Work Needs More Than Dashboards&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I love a good dashboard. Truly. I am not here to drag the humble dashboard into the street and accuse it of crimes against humanity, partly because dashboards are useful and partly because humanity has committed far stranger crimes with pivot tables.&lt;/p&gt;
&lt;p&gt;Dashboards serve a real purpose. Boards need them. Executives need them. Oversight groups need a point-in-time readout that says, &amp;ldquo;Here is where things stood when we gathered the data, checked the colors, assembled the slide, and sent it around for review.&amp;rdquo; That is not nothing. A clean dashboard can be clarifying, especially when the alternative is six people describing the same initiative in slightly different shades of corporate fog.&lt;/p&gt;</description></item><item><title>If We Need a Quest Guide, We Must Already Be on a Quest</title><link>https://christaburger.com/blog/quest-guide-on-a-quest/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/quest-guide-on-a-quest/</guid><description>&lt;p&gt;&lt;em&gt;3 of 5 in the series: The Quest Guide Era — Why Enterprise Work Needs More Than Dashboards&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I have been noodling on this idea with my own team: if modern enterprise work needs a quest guide, then we probably have to admit we are already on a quest.&lt;/p&gt;
&lt;p&gt;Which is inconvenient, because &amp;ldquo;quest&amp;rdquo; sounds much less corporate than &amp;ldquo;strategic cross-functional execution framework.&amp;rdquo; Unfortunately, it is also more accurate.&lt;/p&gt;
&lt;p&gt;A quest has an objective. It also has uncertainty. You know what you are trying to achieve, but you do not always know the route, the blockers, the allies, the dependencies, the approvals, or the decisions you will meet along the way.&lt;/p&gt;</description></item><item><title>The Flight Crews Need a Control Tower</title><link>https://christaburger.com/blog/quest-guide-control-tower/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/quest-guide-control-tower/</guid><description>&lt;p&gt;&lt;em&gt;4 of 5 in the series: The Quest Guide Era — Why Enterprise Work Needs More Than Dashboards&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;If teams are working through quests, then AI cannot just be another enthusiastic productivity machine producing artifacts in the corner.&lt;/p&gt;
&lt;p&gt;I say that with affection. I love a useful AI assistant. I love a draft. I love a calendar summary first thing in the morning.&lt;/p&gt;
&lt;p&gt;But if AI only helps us produce more words, tickets, notes, updates, and summaries, we have not solved the coordination problem.&lt;/p&gt;</description></item><item><title>The Future of Enterprise Software May Be in the Quest Layer</title><link>https://christaburger.com/blog/quest-guide-quest-layer/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/quest-guide-quest-layer/</guid><description>&lt;p&gt;&lt;em&gt;5 of 5 in the series: The Quest Guide Era — Why Enterprise Work Needs More Than Dashboards&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;At some point in this whole thought experiment, I realized I was no longer just talking about dashboards.&lt;/p&gt;
&lt;p&gt;That is how these things go. You begin with a perfectly reasonable complaint about status reporting, take one small conceptual step toward quest guides, add a Control Tower, involve several airships, and suddenly you are staring at the ceiling thinking, &amp;ldquo;Wait. Is the next generation of enterprise software actually a custom operating world?&amp;rdquo;&lt;/p&gt;</description></item><item><title>My AI Maturity Ladder: From Chat to Choreography</title><link>https://christaburger.com/blog/my-ai-maturity-ladder-chat-to-choreography/</link><pubDate>Wed, 24 Jun 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/my-ai-maturity-ladder-chat-to-choreography/</guid><description>&lt;p&gt;Here is how I currently think about AI maturity:&lt;/p&gt;
&lt;h2 id="1-chat"&gt;1. Chat&lt;/h2&gt;
&lt;p&gt;Ask questions, get answers.&lt;/p&gt;
&lt;h2 id="2-templates"&gt;2. Templates&lt;/h2&gt;
&lt;p&gt;Reuse prompts for common work.&lt;/p&gt;
&lt;h2 id="3-workflows"&gt;3. Workflows&lt;/h2&gt;
&lt;p&gt;Connect steps into repeatable processes.&lt;/p&gt;
&lt;h2 id="4-roles"&gt;4. Roles&lt;/h2&gt;
&lt;p&gt;Different AI functions do different jobs.&lt;/p&gt;
&lt;h2 id="5-governance"&gt;5. Governance&lt;/h2&gt;
&lt;p&gt;Add review, evidence, escalation, and accountability.&lt;/p&gt;
&lt;h2 id="6-choreography"&gt;6. Choreography&lt;/h2&gt;
&lt;p&gt;Intelligence moves through the organization in designed patterns.&lt;/p&gt;
&lt;p&gt;Most people are somewhere between 1 and 3.&lt;/p&gt;
&lt;p&gt;That is not bad.&lt;/p&gt;
&lt;p&gt;But it explains why results still feel inconsistent.&lt;/p&gt;</description></item><item><title>Prompting Is Not the Endgame of AI</title><link>https://christaburger.com/blog/prompting-is-not-the-endgame/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/prompting-is-not-the-endgame/</guid><description>&lt;p&gt;Prompting is useful.&lt;/p&gt;
&lt;p&gt;For your phone AI app.&lt;/p&gt;
&lt;p&gt;Prompting is not the endgame.&lt;/p&gt;
&lt;p&gt;After a few years of experimenting with AI, I think the real maturity curve is &lt;strong&gt;choreography&lt;/strong&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How does work enter the system?&lt;/li&gt;
&lt;li&gt;Who gathers context?&lt;/li&gt;
&lt;li&gt;Who summarizes?&lt;/li&gt;
&lt;li&gt;Who checks risk?&lt;/li&gt;
&lt;li&gt;Who drafts?&lt;/li&gt;
&lt;li&gt;Who reviews?&lt;/li&gt;
&lt;li&gt;Who approves?&lt;/li&gt;
&lt;li&gt;Where does the evidence go?&lt;/li&gt;
&lt;li&gt;What happens next time?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That is a different conversation.&lt;/p&gt;
&lt;p&gt;Prompting is asking better questions.&lt;/p&gt;
&lt;p&gt;Choreography is designing how intelligence moves.&lt;/p&gt;</description></item><item><title>Unnamed Work Becomes Weather</title><link>https://christaburger.com/blog/unnamed-work-becomes-weather/</link><pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/unnamed-work-becomes-weather/</guid><description>&lt;p&gt;Unnamed work becomes weather.&lt;/p&gt;
&lt;p&gt;It just happens.&lt;/p&gt;
&lt;p&gt;People feel it. People complain about it. People plan around it. Nobody owns it.&lt;/p&gt;
&lt;p&gt;This is true in teams, households, operations, governance, and AI workflows.&lt;/p&gt;
&lt;p&gt;The first act of control is often &lt;strong&gt;naming&lt;/strong&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Name the recurring burden&lt;/li&gt;
&lt;li&gt;Name the decision point&lt;/li&gt;
&lt;li&gt;Name the review&lt;/li&gt;
&lt;li&gt;Name the handoff&lt;/li&gt;
&lt;li&gt;Name the risk&lt;/li&gt;
&lt;li&gt;Name the evidence trail&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Once something has a name, it can have an owner.&lt;/p&gt;</description></item><item><title>Give AI a Job Description Before Giving It Access</title><link>https://christaburger.com/blog/give-ai-a-job-description-before-access/</link><pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/give-ai-a-job-description-before-access/</guid><description>&lt;p&gt;Before giving AI more access, give it a job description.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What is it responsible for?&lt;/li&gt;
&lt;li&gt;What should it ignore?&lt;/li&gt;
&lt;li&gt;What does good output look like?&lt;/li&gt;
&lt;li&gt;What tools can it use?&lt;/li&gt;
&lt;li&gt;When should it escalate?&lt;/li&gt;
&lt;li&gt;What should it never decide?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This sounds obvious.&lt;/p&gt;
&lt;p&gt;It is apparently not.&lt;/p&gt;
&lt;p&gt;People will give AI access to meaningful workflows with less role clarity than they would give an intern named Brayden who starts Monday and says &amp;ldquo;for sure&amp;rdquo; too much.&lt;/p&gt;</description></item><item><title>Not Every AI Should Be the Same AI</title><link>https://christaburger.com/blog/not-every-ai-should-be-the-same-ai/</link><pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/not-every-ai-should-be-the-same-ai/</guid><description>&lt;p&gt;I used to put too much into one AI conversation.&lt;/p&gt;
&lt;p&gt;Strategy. Drafting. Summarizing. Planning. Debugging. Content ideas. Household systems. Possibly plant identification.&lt;/p&gt;
&lt;p&gt;A perfectly normal range of human concerns.&lt;/p&gt;
&lt;p&gt;Eventually, I realized the issue was not the model.&lt;/p&gt;
&lt;p&gt;It was the lack of role clarity.&lt;/p&gt;
&lt;p&gt;Human teams have roles for a reason:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Strategist&lt;/li&gt;
&lt;li&gt;Analyst&lt;/li&gt;
&lt;li&gt;Operator&lt;/li&gt;
&lt;li&gt;Reviewer&lt;/li&gt;
&lt;li&gt;Auditor&lt;/li&gt;
&lt;li&gt;Assistant&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;AI needs the same distinction.&lt;/p&gt;
&lt;p&gt;Some AI functions should explore. Some should execute. Some should check. Some should preserve context. Some should challenge assumptions. Some should produce clean artifacts.&lt;/p&gt;</description></item><item><title>Accountability Should Not Require Archaeology</title><link>https://christaburger.com/blog/accountability-should-not-require-archaeology/</link><pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/accountability-should-not-require-archaeology/</guid><description>&lt;p&gt;If accountability requires archaeology, the system is under-designed.&lt;/p&gt;
&lt;p&gt;People should not need to dig through inboxes, Slack threads, meeting notes, and the memory of whoever was least distracted at the time.&lt;/p&gt;
&lt;p&gt;That is not a process.&lt;/p&gt;
&lt;p&gt;That is a scavenger hunt with legal exposure.&lt;/p&gt;
&lt;p&gt;AI should make this better.&lt;/p&gt;
&lt;p&gt;Every meaningful AI-assisted workflow should be able to answer:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What did it do?&lt;/li&gt;
&lt;li&gt;What inputs did it use?&lt;/li&gt;
&lt;li&gt;What changed?&lt;/li&gt;
&lt;li&gt;What did it recommend?&lt;/li&gt;
&lt;li&gt;What did a human approve?&lt;/li&gt;
&lt;li&gt;Where is the evidence?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This is not just a security or compliance concern.&lt;/p&gt;</description></item><item><title>"I Think We Talked About This" Is Not a Control</title><link>https://christaburger.com/blog/i-think-we-talked-about-this-is-not-a-control/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/i-think-we-talked-about-this-is-not-a-control/</guid><description>&lt;p&gt;The worst time to document a decision is after something goes wrong.&lt;/p&gt;
&lt;p&gt;Everyone is calm. Everyone remembers clearly. No one is searching email for &amp;ldquo;final_final_ACTUAL_USE_THIS_ONE_v7.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Obviously.&lt;/p&gt;
&lt;p&gt;AI can help us stop doing this.&lt;/p&gt;
&lt;p&gt;It can capture decisions as they happen:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What was known?&lt;/li&gt;
&lt;li&gt;What was decided?&lt;/li&gt;
&lt;li&gt;Who decided it?&lt;/li&gt;
&lt;li&gt;What changed later?&lt;/li&gt;
&lt;li&gt;What evidence existed at the time?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That is incredibly valuable.&lt;/p&gt;
&lt;p&gt;But only if we design for it.&lt;/p&gt;
&lt;p&gt;Otherwise AI just helps us create more outputs with less traceability.&lt;/p&gt;</description></item><item><title>Set It and Forget It Is a Trap in AI Automation</title><link>https://christaburger.com/blog/set-it-and-forget-it-ai-automation/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/set-it-and-forget-it-ai-automation/</guid><description>&lt;p&gt;&amp;ldquo;Set it and forget it&amp;rdquo; is not how most useful automation works.&lt;/p&gt;
&lt;p&gt;It is how rot gets a login.&lt;/p&gt;
&lt;p&gt;Systems without maintenance atrophy with time.&lt;/p&gt;
&lt;p&gt;The better model is not forgetting.&lt;/p&gt;
&lt;p&gt;It is &lt;strong&gt;rhythm&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What runs daily?&lt;/li&gt;
&lt;li&gt;What runs weekly?&lt;/li&gt;
&lt;li&gt;What runs when triggered?&lt;/li&gt;
&lt;li&gt;What needs human review?&lt;/li&gt;
&lt;li&gt;What gets summarized?&lt;/li&gt;
&lt;li&gt;What gets escalated?&lt;/li&gt;
&lt;li&gt;What gets archived?&lt;/li&gt;
&lt;li&gt;Do you have something auditing it all?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;AI systems need cadence because real life has cadence.&lt;/p&gt;</description></item><item><title>Heroics Are Usually a Design Problem</title><link>https://christaburger.com/blog/heroics-are-a-design-problem/</link><pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/heroics-are-a-design-problem/</guid><description>&lt;p&gt;I used to be more impressed by heroic effort.&lt;/p&gt;
&lt;p&gt;The late-night push. The last-minute save. The frantic deck rescue. The spreadsheet that emerges from the ashes wearing a tiny cape.&lt;/p&gt;
&lt;p&gt;Now I mostly see heroics as a signal: a broken system relying on the goodwill of one person — or their insecurities — to keep functioning.&lt;/p&gt;
&lt;p&gt;Sometimes heroics are necessary. Workloads can fluctuate wildly.&lt;/p&gt;
&lt;p&gt;But that is also a lazy acceptance.&lt;/p&gt;</description></item><item><title>Human-in-the-Loop AI Is Not Enough</title><link>https://christaburger.com/blog/human-in-the-loop-is-not-enough/</link><pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/human-in-the-loop-is-not-enough/</guid><description>&lt;p&gt;&amp;ldquo;Human in the loop&amp;rdquo; has become one of those phrases we say to make everyone feel better.&lt;/p&gt;
&lt;p&gt;Like &amp;ldquo;cross-functional alignment.&amp;rdquo; Or &amp;ldquo;quick sync.&amp;rdquo; Or &amp;ldquo;this should be straightforward.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The issue is not whether a human is somewhere in the loop.&lt;/p&gt;
&lt;p&gt;The issue is whether the human is in the &lt;strong&gt;right place&lt;/strong&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Before the AI acts?&lt;/li&gt;
&lt;li&gt;After it drafts?&lt;/li&gt;
&lt;li&gt;When risk is detected?&lt;/li&gt;
&lt;li&gt;When money is involved?&lt;/li&gt;
&lt;li&gt;When customer trust is at stake?&lt;/li&gt;
&lt;li&gt;When a decision needs authority?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That matters.&lt;/p&gt;</description></item><item><title>AI Should Prepare Decisions, Not Replace Human Judgment</title><link>https://christaburger.com/blog/ai-should-prepare-decisions-not-replace-judgment/</link><pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/ai-should-prepare-decisions-not-replace-judgment/</guid><description>&lt;p&gt;Most leaders are not lacking judgment.&lt;/p&gt;
&lt;p&gt;They are lacking clean inputs. Good context. Sometimes, a general curiosity to understand.&lt;/p&gt;
&lt;p&gt;AI can fix two of those things.&lt;/p&gt;
&lt;p&gt;By the time a decision reaches a senior leader, it is often wrapped in six emails, three Slack threads, a deck, two side conversations, a deadline that is now their problem, and the risk of it all dumped into their lap.&lt;/p&gt;
&lt;p&gt;From there, what happens next is highly dependent on the leader and their risk tolerance.&lt;/p&gt;</description></item><item><title>Why Metaphor Matters in AI System Design</title><link>https://christaburger.com/blog/metaphor-as-ai-architecture/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/metaphor-as-ai-architecture/</guid><description>&lt;p&gt;We often think metaphor is something that explains a system after the fact.&lt;/p&gt;
&lt;p&gt;Now I think metaphor is often how you know what you are building.&lt;/p&gt;
&lt;p&gt;This has been especially true with AI because AI systems get abstract very quickly.&lt;/p&gt;
&lt;p&gt;You start with, &amp;ldquo;I need help managing recurring work.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Three hours later, you are still wrestling with what that means, trying to identify recurring work in your own life for realsies this time, and maybe even falling into a therapy session with chat about why you are like this.&lt;/p&gt;</description></item><item><title>The AI Moment Is Now — Are You Navigating It or Reacting to It?</title><link>https://christaburger.com/blog/the-ai-moment-is-now/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/the-ai-moment-is-now/</guid><description>&lt;p&gt;Every generation faces a moment when the world reorganizes itself around a new force. We are in that moment now.&lt;/p&gt;
&lt;p&gt;Artificial intelligence is not a tool you adopt or ignore. It is a shift in the fundamental infrastructure of how organizations think, decide, communicate, and operate. The question is not whether to engage — it&amp;rsquo;s whether you&amp;rsquo;ll engage with intention or simply react as it reshapes everything around you.&lt;/p&gt;
&lt;h2 id="the-trap-most-organizations-fall-into"&gt;The trap most organizations fall into&lt;/h2&gt;
&lt;p&gt;The most common mistake I see is treating AI adoption as a technology project. Leadership hands it to IT. IT implements a tool. The tool either works or doesn&amp;rsquo;t. The organization declares itself &amp;ldquo;doing AI.&amp;rdquo;&lt;/p&gt;</description></item><item><title>What AI Governance Actually Means (And Why Most Organizations Get It Wrong)</title><link>https://christaburger.com/blog/what-ai-governance-actually-means/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/what-ai-governance-actually-means/</guid><description>&lt;p&gt;When most organizations hear &amp;ldquo;AI governance,&amp;rdquo; they think one of two things: a policy document nobody reads, or a legal team saying no to everything.&lt;/p&gt;
&lt;p&gt;Neither is governance. Both are avoidance.&lt;/p&gt;
&lt;p&gt;Real AI governance is the architecture through which an organization makes decisions about AI — consistently, accountably, and in alignment with its values. It answers three fundamental questions:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Who decides?&lt;/strong&gt; When an AI system affects employees, customers, or communities — who has authority over that decision? Who can challenge it? Who is accountable when it goes wrong?&lt;/p&gt;</description></item></channel></rss>