<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Powers on Kevin Sookocheff</title>
    <link>https://sookocheff.com/tags/powers/</link>
    <description>Recent content in Powers on Kevin Sookocheff</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 10 May 2026 09:18:32 +0000</lastBuildDate>
    <atom:link href="https://sookocheff.com/tags/powers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Seven Powers of Platform Teams</title>
      <link>https://sookocheff.com/post/business/seven-powers-of-platform-teams/</link>
      <pubDate>Sun, 10 May 2026 09:18:32 +0000</pubDate>
      <guid>https://sookocheff.com/post/business/seven-powers-of-platform-teams/</guid>
      <description>&lt;p&gt;I work on Workiva’s cloud platform engineering team, where we design and
operate Kubernetes and AWS infrastructure supporting more than 300
microservices across multiple AWS regions. The platform spans networking,
observability, CI/CD, compliance, and internal developer tooling. Lately,
our team has been busy developing and codifying our strategy. I’m not
a big fan of reinventing the wheel, and neither is the rest of our team,
so we welcomed the opportunity to use existing business strategy
frameworks and methodologies as a way to get started quickly. We used the
&lt;a href=&#34;https://fs.blog/playing-to-win-how-strategy-really-works/&#34;&gt;Playing to Win
Framework&lt;/a&gt;,
and were able to flesh out a meaningful strategy focusing on things such
as reducing cognitive load for development teams and streamlining how we
report the customer impact of incidents.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
