<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Leadership on Jice Lavocat</title><link>https://jice.lavocat.name/tags/leadership/</link><description>Recent content in Leadership on Jice Lavocat</description><generator>Hugo</generator><language>fr-FR</language><copyright>All rights reserved - 2016</copyright><lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jice.lavocat.name/tags/leadership/index.xml" rel="self" type="application/rss+xml"/><item><title>Prioritizing Requests in a Growing Data Team (CoE)</title><link>https://jice.lavocat.name/blog/2026/prioritizing-requests-in-a-growing-data-team-coe/</link><pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate><guid>https://jice.lavocat.name/blog/2026/prioritizing-requests-in-a-growing-data-team-coe/</guid><description>&lt;p&gt;Every shared-service function goes through a similar awkward adolescence. Data, IT, marketing ops, &amp;hellip; you name it. At some point a small team is asked to do two things at once: &lt;strong&gt;build the foundations the whole company will eventually rely on&lt;/strong&gt;, and &lt;strong&gt;deliver the tasks stakeholders are assigning them &lt;em&gt;right now&lt;/em&gt;&lt;/strong&gt;. Those two things compete for the same hours, and the tension between them doesn&amp;rsquo;t resolve on its own. It has to be managed.&lt;/p&gt;</description></item></channel></rss>