<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Nophil Consulting: Writing</title>
  <link>https://nophilconsulting.fi/writing/</link>
  <atom:link href="https://nophilconsulting.fi/writing/feed.xml" rel="self" type="application/rss+xml"/>
  <description>Notes by Nophil Anwer on running business analysis and design for Omne ERP, a manufacturing ERP. Decision records, design reviews, scope and AI in a BA and design team, with real numbers from the team&#x27;s records.</description>
  <language>en-gb</language>
  <lastBuildDate>Tue, 17 Nov 2026 09:00:00 +0200</lastBuildDate>
  <item>
    <title>Catching drift before handoff</title>
    <link>https://nophilconsulting.fi/writing/catching-drift-before-handoff/</link>
    <guid isPermaLink="true">https://nophilconsulting.fi/writing/catching-drift-before-handoff/</guid>
    <pubDate>Tue, 17 Nov 2026 09:00:00 +0200</pubDate>
    <description>Every module has three records of what it&#x27;s supposed to do: the user stories, the prototype and the spec. By handoff they rarely agree. The first full review of one OMNE module found about 175 issues between them.</description>
  </item>
  <item>
    <title>Decision, for now, or just a view?</title>
    <link>https://nophilconsulting.fi/writing/decision-for-now-or-view/</link>
    <guid isPermaLink="true">https://nophilconsulting.fi/writing/decision-for-now-or-view/</guid>
    <pubDate>Tue, 17 Nov 2026 09:00:00 +0200</pubDate>
    <description>Most meeting notes say what was decided. Very few say what kind of call it was. Since October 2026 every ruling in the Omne decision wiki says whether it&#x27;s a decision, a for-now call or just someone&#x27;s view. Here&#x27;s why I made that a rule.</description>
  </item>
  <item>
    <title>How I keep track of every decision in an ERP</title>
    <link>https://nophilconsulting.fi/work/decision-wiki/</link>
    <guid isPermaLink="true">https://nophilconsulting.fi/work/decision-wiki/</guid>
    <pubDate>Mon, 16 Nov 2026 09:00:00 +0200</pubDate>
    <description>Omne ERP&#x27;s decisions were spread across calls, Slack threads, Jira comments and specs, and nobody could keep track of all of it. So in September 2026 I built a decision wiki with Claude. It reads all of those every night and keeps one record of what was decided.</description>
  </item>
  <item>
    <title>Bringing AI into a BA and design team</title>
    <link>https://nophilconsulting.fi/work/ai-in-ba-and-design/</link>
    <guid isPermaLink="true">https://nophilconsulting.fi/work/ai-in-ba-and-design/</guid>
    <pubDate>Mon, 16 Nov 2026 09:00:00 +0200</pubDate>
    <description>I moved OMNE&#x27;s analysts and designers onto Claude, built Claude skills for their day-to-day work, and keep clear rules on when to trust what it produces. The point is fewer gaps between what got decided, designed and built.</description>
  </item>
  <item>
    <title>Running BA and design for a manufacturing ERP</title>
    <link>https://nophilconsulting.fi/work/omne-erp/</link>
    <guid isPermaLink="true">https://nophilconsulting.fi/work/omne-erp/</guid>
    <pubDate>Mon, 16 Nov 2026 09:00:00 +0200</pubDate>
    <description>I wrote the original feature set for Omne ERP, an ERP for discrete manufacturers, and I still run its business analysis and design. The numbers here come from the team&#x27;s own decision records.</description>
  </item>
</channel>
</rss>
