<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MBA on Chris Reddington</title><link>https://chrisreddington.com/tags/mba/</link><description>Recent content in MBA on Chris Reddington</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Wed, 11 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chrisreddington.com/tags/mba/index.xml" rel="self" type="application/rss+xml"/><item><title>How does Developer Relations (DevRel) create value? What 13 interviews revealed.</title><link>https://chrisreddington.com/blog/devrel-value-creation/</link><pubDate>Wed, 11 Mar 2026 00:00:00 +0000</pubDate><guid>https://chrisreddington.com/blog/devrel-value-creation/</guid><description>&lt;p&gt;What does value creation in Developer Relations actually look like?&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m not asking what DevRel &lt;em&gt;does&lt;/em&gt;, as there&amp;rsquo;s plenty of descriptions of DevRel activities out there. Nor what it &lt;em&gt;should&lt;/em&gt; do, as there&amp;rsquo;s no shortage of opinion there either. But what does value creation (the specific mechanism by which a DevRel team contributes something meaningful to its organisation and its developer community) actually look like in practice?&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve spent a large part of my career in and around Developer Relations, so I&amp;rsquo;ve been thinking about this question for a while. Back in 2024, I decided to stop thinking about it and actually research it.&lt;/p&gt;</description></item></channel></rss>