<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title><![CDATA[StreamCore NexWave]]></title>
  <link>https://streamcorenexwave.com/</link>
  <description><![CDATA[StreamCore NexWave offers technology strategy, process redesign, and vendor evaluation consulting for Canadian organisations. Based in Toronto, serving clients since 2018.]]></description>
  <language>en</language>
  <atom:link href="https://streamcorenexwave.com/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title><![CDATA[What a technology strategy actually needs to contain]]></title>
    <link>https://streamcorenexwave.com/notes/technology-strategy-without-the-jargon.html</link>
    <guid isPermaLink="true">https://streamcorenexwave.com/notes/technology-strategy-without-the-jargon.html</guid>
    <description><![CDATA[The phrase 'technology strategy' gets used in a lot of contexts, and it means different things depending on who is using it. For some organisations, it means a list of planned software purchases. For others, it is a high-level vision statement that nobody references after the board presentation. Neither of those is particularly useful. A technology strategy that does its job is a document that helps an organisation make consistent decisions over a period of two to four years, even as circumstances change.]]></description>
    <pubDate>Sat, 18 Jul 2026 19:37:42 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[How to run a vendor evaluation that produces a defensible decision]]></title>
    <link>https://streamcorenexwave.com/notes/vendor-evaluation-process-canada.html</link>
    <guid isPermaLink="true">https://streamcorenexwave.com/notes/vendor-evaluation-process-canada.html</guid>
    <description><![CDATA[Choosing a software vendor or technology partner is one of the decisions that is hardest to reverse. A contract signed in haste, or on the basis of an impressive demonstration, can bind an organisation to a system that does not fit its actual needs for three to five years. The evaluation process is where that risk is managed, and most organisations underinvest in it.]]></description>
    <pubDate>Sun, 21 Jun 2026 10:51:35 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[Why process mapping should happen before you choose any software]]></title>
    <link>https://streamcorenexwave.com/notes/process-mapping-before-technology.html</link>
    <guid isPermaLink="true">https://streamcorenexwave.com/notes/process-mapping-before-technology.html</guid>
    <description><![CDATA[There is a sequence that produces good technology implementations, and it is not the sequence most organisations follow. The common approach is to identify a technology, select a vendor, and then figure out how to make the existing process fit the new system. The sequence that works is the reverse: map the existing process in detail, identify where it breaks down, redesign it, and then select the technology that supports the redesigned process.]]></description>
    <pubDate>Mon, 18 May 2026 11:28:21 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[Data governance for Canadian organisations: what PIPEDA requires in practice]]></title>
    <link>https://streamcorenexwave.com/notes/data-governance-pipeda-ontario.html</link>
    <guid isPermaLink="true">https://streamcorenexwave.com/notes/data-governance-pipeda-ontario.html</guid>
    <description><![CDATA[Most Canadian organisations subject to PIPEDA have taken the minimum steps: they have designated a privacy officer, they have a privacy policy on their website, and they have a process for responding to access requests. What fewer organisations have is the underlying infrastructure that makes those steps meaningful: a data inventory, documented retention schedules, access controls that are actually enforced, and a breach response procedure that has been tested.]]></description>
    <pubDate>Mon, 30 Mar 2026 20:55:41 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[Change management during a technology rollout: what actually works]]></title>
    <link>https://streamcorenexwave.com/notes/change-management-technology-rollout.html</link>
    <guid isPermaLink="true">https://streamcorenexwave.com/notes/change-management-technology-rollout.html</guid>
    <description><![CDATA[A technology implementation that staff do not adopt is not an implementation. It is an expensive parallel system that runs alongside the old way of doing things until one of them is abandoned. The adoption problem is predictable, it is well understood, and it is still the most common failure point in technology projects. The reason is that change management is usually treated as a communication exercise rather than a design exercise.]]></description>
    <pubDate>Sat, 28 Mar 2026 13:04:07 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[Post-implementation review: what to assess six months after go-live]]></title>
    <link>https://streamcorenexwave.com/notes/post-implementation-review-why-it-matters.html</link>
    <guid isPermaLink="true">https://streamcorenexwave.com/notes/post-implementation-review-why-it-matters.html</guid>
    <description><![CDATA[Most technology projects are declared complete at go-live. The project team disperses, the steering committee stops meeting, and the organisation moves on to the next initiative. Six months later, the system is in production, but whether it is delivering what was expected is a question that often goes unasked. A post-implementation review is the structured exercise that answers it.]]></description>
    <pubDate>Wed, 04 Mar 2026 10:08:26 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[When to bring in a consultant and when to hire internally instead]]></title>
    <link>https://streamcorenexwave.com/notes/when-to-hire-a-consultant-vs-internal-hire.html</link>
    <guid isPermaLink="true">https://streamcorenexwave.com/notes/when-to-hire-a-consultant-vs-internal-hire.html</guid>
    <description><![CDATA[The decision to bring in an external consultant rather than hire internally is not primarily a cost decision, though it is often framed that way. It is a question about what kind of problem the organisation is trying to solve and what kind of resource is best suited to solving it. Getting that question wrong in either direction is expensive.]]></description>
    <pubDate>Sat, 10 Jan 2026 21:07:50 GMT</pubDate>
  </item>
</channel>
</rss>
