<?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/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Strategy · Jared Lynskey</title>
    <link>https://jared.lynskey.co.nz/en/tags/strategy/</link>
    <description>Short stories of value on software engineering and engineering leadership — performance reviews, hiring and scaling teams, CI/CD, DevOps monitoring and agentic AI. Written from Seoul.</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© 2026 Jared Lynskey</copyright>
    <lastBuildDate>Wed, 28 Oct 2026 00:00:00 +1300</lastBuildDate>
    <atom:link href="https://jared.lynskey.co.nz/en/tags/strategy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Proactive Communication at Work: Tell People Before They Ask</title>
      <link>https://jared.lynskey.co.nz/en/posts/2023/2023-09-23-reactive-vs-proactive-communication/</link>
      <guid isPermaLink="true">https://jared.lynskey.co.nz/en/posts/2023/2023-09-23-reactive-vs-proactive-communication/</guid>
      <pubDate>Thu, 21 Sep 2023 11:30:03 +0000</pubDate>
      <dc:creator>Jared Lynskey</dc:creator>
      <category>CTO</category>
      <category>Project Management</category>
      <category>Communication</category>
      <category>Strategy</category>
      <description>Proactive communication means raising the delay, the risk or the bad news before anyone has to ask; reactive communication waits for the question. The people who do well on teams aren&#39;t always the most talented, they&#39;re the ones who communicate first. I learned it by waiting too long on a project that was falling behind.</description>
      <content:encoded><![CDATA[<p>Proactive communication means telling people what they need to know before they have to ask: the deadline that&rsquo;s slipping, the change that will affect them, the risk you&rsquo;ve spotted. Reactive communication waits for the question and then answers it. Every team needs both, but most of us default to reactive, and the cost turns up later as surprises. This is how I learned that the hard way, the situations where I now speak up first, and when just responding is still the right call.</p>
<p>I was leading a project that was falling behind. I knew the architecture had problems. I knew we&rsquo;d miss the deadline. But I kept waiting for someone to ask about it.</p>
<p>They finally did, three weeks later. By then it was a disaster.</p>
<p>Here&rsquo;s what I learned: if you wait for people to ask what&rsquo;s happening, they&rsquo;ll assume everything is fine until it isn&rsquo;t. Then they&rsquo;ll wonder why you didn&rsquo;t tell them sooner.</p>

<h2 class="relative group">The Problem with Only Responding
    <div id="the-problem-with-only-responding" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-problem-with-only-responding" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Most people communicate by responding. Someone emails, you reply. Someone asks for an update, you give one. Someone reports a bug, you fix it.</p>
<p>This feels efficient. You&rsquo;re never wasting anyone&rsquo;s time with unnecessary information.</p>
<p>But you&rsquo;re also training everyone around you that they need to chase you for information. Your manager has to ask how the project is going. Other teams have to check if your changes will affect them. Leadership has to dig to find out if there are any risks.</p>
<p>Good engineers I&rsquo;ve worked with get stuck here. They build great systems but nobody knows about them until something breaks. They solve hard problems but only after someone complains first.</p>
<p>I watched a senior developer spend two weeks refactoring a critical payment system. Beautiful code. Cut processing time in half. Nobody knew about it until six months later when someone stumbled across it while debugging something else. All that work, invisible.</p>
<p>Meanwhile, another engineer on the same team would send short updates whenever they shipped anything: &ldquo;Reduced API latency by 200ms, here&rsquo;s how.&rdquo; Five sentences, maybe a chart. Everyone knew what they were doing. Guess who got promoted?</p>
<p>The difference wasn&rsquo;t skill. It was communication timing.</p>

<h2 class="relative group">What Actually Happens When You Don&rsquo;t Communicate
    <div id="what-actually-happens-when-you-dont-communicate" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-actually-happens-when-you-dont-communicate" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Let me be specific about what &ldquo;waiting to be asked&rdquo; looks like in practice.</p>
<p>You&rsquo;re three days into a task you estimated at two days. You know you&rsquo;ll need another three days. Do you say something now, or wait until the standup tomorrow when someone asks?</p>
<p>If you wait, here&rsquo;s what happens: your manager built their plan assuming you&rsquo;d be done today. The QA team scheduled testing for tomorrow. The product manager told the customer it ships Friday. Now everyone scrambles to adjust because you didn&rsquo;t take 30 seconds to say &ldquo;This is taking longer than expected.&rdquo;</p>
<p>Or this: you&rsquo;re changing how authentication works. You know the mobile app makes assumptions about the token format. Do you message the mobile team now, or wait to see if they notice?</p>
<p>If you wait, they deploy their app next week. It breaks in production. They spend hours debugging. Eventually they find your change. Now you&rsquo;re the person who broke production without warning anyone.</p>
<p>This stuff happens constantly. And it&rsquo;s always because someone knew something and didn&rsquo;t say it.</p>

<h2 class="relative group">What to Do Instead
    <div id="what-to-do-instead" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-to-do-instead" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Tell people things before they ask. Not everything, just what they need to know.</p>
<p>Here are the situations where I&rsquo;ve learned to speak up first:</p>
<p><strong>When timelines slip.</strong> You estimated five days, it&rsquo;s been three, and you&rsquo;re maybe 30% done. Send a message now. &ldquo;This is taking longer than I thought. Now looking at 8-10 days instead of 5. Want me to cut scope or push the deadline?&rdquo;</p>
<p>Don&rsquo;t wait for the standup. Don&rsquo;t wait for someone to ask. The moment you know, tell them.</p>
<p><strong>When you make technical decisions.</strong> You chose Postgres over MySQL. You went with REST instead of GraphQL. You added a new required field to the API.</p>
<p>These decisions seem local when you make them, but someone else is depending on them. Send a quick note: &ldquo;Heads up, changing the user endpoint to require email validation. Goes live Thursday. Let me know if this breaks anything for you.&rdquo;</p>
<p><strong>When you spot risks.</strong> The database is growing faster than expected. The API is getting slower under load. The new feature works but the code is messy and will be hard to maintain.</p>
<p>Don&rsquo;t wait for it to become a problem. Flag it while there&rsquo;s time to fix it: &ldquo;Noticed the response time creeping up on the search endpoint. Not urgent yet, but we should probably look at adding caching in the next sprint.&rdquo;</p>
<p><strong>Regular updates.</strong> I send a Friday email to my stakeholders. Takes 10 minutes. Three bullets: what shipped this week, what&rsquo;s next week, anything I&rsquo;m concerned about.</p>
<p>Most weeks it&rsquo;s boring. That&rsquo;s the point. Boring means no surprises. And when something does come up, they already know the context because I&rsquo;ve been keeping them in the loop.</p>
<p>On a project with more than a couple of audiences, I write down who gets which update, how often and from whom, in a one-page <a href="https://jared.lynskey.co.nz/en/posts/2023/2023-06-02-project-frameworks-for-future-cto/" >project communication plan</a>.</p>

<h2 class="relative group">Why People Don&rsquo;t Do This
    <div id="why-people-dont-do-this" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-people-dont-do-this" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>I&rsquo;ve heard all the excuses because I&rsquo;ve used most of them myself.</p>
<p>&ldquo;I don&rsquo;t want to bother people.&rdquo; You&rsquo;re not bothering them. You&rsquo;re saving them from having to bother you. Your manager would much rather read a two-sentence update than schedule a meeting to ask you what&rsquo;s happening.</p>
<p>&ldquo;What if I&rsquo;m wrong?&rdquo; Then you send a follow-up. &ldquo;Update: that thing I said would take 8 days only took 6, we&rsquo;re back on track.&rdquo; Nobody gets mad at good news.</p>
<p>&ldquo;I don&rsquo;t want to look like I don&rsquo;t know what I&rsquo;m doing.&rdquo; Here&rsquo;s the thing: missing a deadline without warning makes you look like you don&rsquo;t know what you&rsquo;re doing. Flagging a delay early makes you look like someone who manages risks.</p>
<p>&ldquo;I&rsquo;m too busy.&rdquo; You&rsquo;re not too busy to send a three-sentence email. And if you think you are, you&rsquo;re definitely too busy to deal with the mess that happens when you don&rsquo;t.</p>
<p>The real reason people don&rsquo;t communicate early is because it feels uncomfortable. It&rsquo;s easier to stay quiet and hope things work out. But hope isn&rsquo;t a plan, and quiet isn&rsquo;t professional.</p>

<h2 class="relative group">When to Just Respond
    <div id="when-to-just-respond" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#when-to-just-respond" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>You can&rsquo;t tell people everything ahead of time. Some situations need immediate response, not advance warning.</p>
<p>During an outage, fix it first. Send updates about what you&rsquo;re doing, but don&rsquo;t wait to write the perfect post-mortem before you stop the bleeding.</p>
<p>When someone&rsquo;s blocked on your code review, just review it. They don&rsquo;t need your weekly update, they need you to unblock them in the next hour.</p>
<p>When there&rsquo;s an urgent question in Slack, answer it. Don&rsquo;t make them wait for your Friday summary.</p>
<p>The pattern: be reactive when someone needs something right now. Be proactive about everything else.</p>

<h2 class="relative group">What This Looks Like in Practice
    <div id="what-this-looks-like-in-practice" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-this-looks-like-in-practice" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Here&rsquo;s what changed when I started doing this consistently:</p>
<p>Fewer meetings. When people already know what&rsquo;s happening, they don&rsquo;t schedule meetings to find out. My calendar went from 25+ hours of meetings a week to maybe 15.</p>
<p>Fewer surprises. When you warn people about problems early, they stop feeling like problems and start feeling like things you&rsquo;re managing. Nobody panics about a risk you flagged two weeks ago.</p>
<p>More trust. This was the biggest one. When you consistently tell people what&rsquo;s happening without them having to ask, they start trusting you to handle things. Which means they give you more responsibility and more interesting work.</p>
<p>The promotion I mentioned earlier? Part of it was doing good work. But the bigger part was making sure the right people knew about the good work without having to dig for it.</p>

<h2 class="relative group">How to Start
    <div id="how-to-start" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#how-to-start" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Pick one thing you&rsquo;re working on this week. Before anyone asks about it, send a short update.</p>
<p>Could be to your manager: &ldquo;Making good progress on the API refactor. About halfway done, on track for end of week.&rdquo;</p>
<p>Could be to another team: &ldquo;Just changed how we&rsquo;re handling user sessions. Shouldn&rsquo;t affect you, but let me know if you see weird auth behavior.&rdquo;</p>
<p>Could be to your team: &ldquo;Fixed that bug in production. Root cause was a race condition in the cache layer. Added a test so it won&rsquo;t happen again.&rdquo;</p>
<p>Two or three sentences. Hit send.</p>
<p>See what happens. Usually one of two things:</p>
<ol>
<li>They appreciate it and you feel less anxious because you&rsquo;re not sitting on information</li>
<li>They don&rsquo;t respond, which is fine because they know now and you don&rsquo;t have to worry about it</li>
</ol>
<p>Do this a few times and it becomes automatic. You finish something, you tell the relevant people. You spot a problem, you flag it. You make a decision, you share it.</p>
<p>After a few weeks, people stop asking you what&rsquo;s happening because they already know. And that&rsquo;s when things get easier.</p>
]]></content:encoded>
      <media:content url="https://jared.lynskey.co.nz/en/posts/2023/2023-09-23-reactive-vs-proactive-communication/featured.jpeg" medium="image" type="image/jpeg" />
    </item>
    <item>
      <title>Coopetition: Should Your Startup Coexist or Compete?</title>
      <link>https://jared.lynskey.co.nz/en/posts/2023/2023-04-12-coexisting-stategy/</link>
      <guid isPermaLink="true">https://jared.lynskey.co.nz/en/posts/2023/2023-04-12-coexisting-stategy/</guid>
      <pubDate>Wed, 12 Apr 2023 00:30:03 +0000</pubDate>
      <dc:creator>Jared Lynskey</dc:creator>
      <category>Coexisting</category>
      <category>Competing</category>
      <category>Startups</category>
      <category>Community</category>
      <category>Coopetition</category>
      <category>Strategy</category>
      <description>What coopetition means, a few well-known business examples, and how a startup building on big platforms can tell when to stop coexisting with them and start competing.</description>
      <content:encoded><![CDATA[<p>Coopetition means cooperating with a competitor where your interests overlap while competing with them everywhere else. The term was popularised by Adam Brandenburger and Barry Nalebuff&rsquo;s 1996 book <em>Co-opetition</em>, which applies game theory to business and makes the point that the same company can be your competitor in one respect and your partner in another.</p>
<p>I think about this a fair bit at work, since I&rsquo;m building a community app that lives in the shadow of much bigger social platforms: do you build on top of the giants, or compete with them? Both can work. The interesting question is when to switch.</p>

<h4 class="relative group">Coopetition examples
    <div id="coopetition-examples" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#coopetition-examples" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p>The well-known examples are all big companies. Samsung makes many of the OLED screens in iPhones while selling Galaxy phones against them. Netflix moved its streaming systems onto Amazon Web Services, finishing in 2016, while competing with Amazon&rsquo;s own Prime Video for the same evenings on the sofa. Google pays Apple to be the default search engine in Safari, and Android goes after the same phone buyers as the iPhone. In each case both sides decided the shared slice was worth more than keeping the rival at arm&rsquo;s length.</p>
<p>A startup&rsquo;s version is smaller and more lopsided. You cooperate with a platform because you need its users, and you compete with it for their attention. Early on it&rsquo;s almost all cooperation; the question is when to start leaning the other way.</p>

<h4 class="relative group">Why coexisting first makes sense
    <div id="why-coexisting-first-makes-sense" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-coexisting-first-makes-sense" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p>Early on, while you&rsquo;re still hunting for product-market fit, riding the big platforms is usually the right call. Operating inside an ecosystem that already has users teaches you what people actually want. Integrations with popular platforms give you distribution you couldn&rsquo;t buy. And you can carve out a niche instead of fighting a giant head-on. PayPal started as a payment option for eBay users, and half the successful apps you can name began as add-ons for Shopify or Slack.</p>

<h4 class="relative group">Knowing when to compete
    <div id="knowing-when-to-compete" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#knowing-when-to-compete" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p>The shift comes later, once you understand your users better than the platform does. Instagram is the classic case — a photo-filter app that grew into a social platform in its own right. The signs I&rsquo;d look for: you&rsquo;ve built genuine domain expertise or technology of your own, and you can see from user behaviour that people want something the incumbents don&rsquo;t offer. If neither is true yet, competing is just picking a fight you&rsquo;ll lose.</p>

<h4 class="relative group">What this looks like for a community app
    <div id="what-this-looks-like-for-a-community-app" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-this-looks-like-for-a-community-app" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p>For a community product, coexisting mostly means integration work, and it&rsquo;s less glamorous than it sounds. Social sign-on, so joining doesn&rsquo;t require yet another account. Easy sharing of community content out to people&rsquo;s social feeds — that&rsquo;s your marketing budget right there. Notifications when someone gets a mention or shout-out on another platform, embeds and widgets so partners can put community features on their own sites, and API hook-ups with complementary services. On the non-technical side, collaborations with influencers who already live on the big platforms, and campaigns that run across several platforms at once, tend to do more for engagement than anything you build in-house.</p>
<p>None of this is binary, which is rather the point of coopetition. Most startups start by coexisting and drift toward competing as they grow — the trick is noticing when you&rsquo;ve quietly earned the right to make that shift.</p>
]]></content:encoded>
      <media:content url="https://jared.lynskey.co.nz/en/posts/2023/2023-04-12-coexisting-stategy/featured.jpeg" medium="image" type="image/jpeg" />
    </item>
  </channel>
</rss>
