<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Analyst Harbor]]></title><description><![CDATA[Where Business Analysts Learn, Connect, and Grow Together]]></description><link>https://www.analystharbor.online</link><image><url>https://substackcdn.com/image/fetch/$s_!J-A7!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb4a2b8c2-6ae7-4d50-b832-deec8050d6aa_1024x1024.png</url><title>Analyst Harbor</title><link>https://www.analystharbor.online</link></image><generator>Substack</generator><lastBuildDate>Mon, 16 Nov 2026 23:47:03 GMT</lastBuildDate><atom:link href="https://www.analystharbor.online/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Lucia & Miloš]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[analystharbor@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[analystharbor@substack.com]]></itunes:email><itunes:name><![CDATA[Lucia & Miloš]]></itunes:name></itunes:owner><itunes:author><![CDATA[Lucia & Miloš]]></itunes:author><googleplay:owner><![CDATA[analystharbor@substack.com]]></googleplay:owner><googleplay:email><![CDATA[analystharbor@substack.com]]></googleplay:email><googleplay:author><![CDATA[Lucia & Miloš]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[The Business Has Vibe-Coded an App. Now What?]]></title><description><![CDATA[How business analysts can turn an AI-built prototype into clear requirements without mistaking it for a production solution.]]></description><link>https://www.analystharbor.online/p/the-business-has-vibe-coded-an-app</link><guid isPermaLink="false">https://www.analystharbor.online/p/the-business-has-vibe-coded-an-app</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Tue, 10 Nov 2026 09:28:27 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!NU6U!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>AI is everywhere, and sooner or later, someone from the business will come with an application they built themselves.</p><div class="paywall-jump" data-component-name="PaywallToDOM"></div><p>They will open it, click through several screens, and say:</p><p><strong>&#8220;This is exactly what we need. It is much better than what we have now, and I built it in two evenings.&#8221; </strong></p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!NU6U!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!NU6U!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!NU6U!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!NU6U!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!NU6U!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!NU6U!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png" width="1456" height="971" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/c81fee8c-2ec4-4808-803f-546387230109_1536x1024.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:971,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1340424,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/223798469?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!NU6U!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!NU6U!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!NU6U!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!NU6U!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc81fee8c-2ec4-4808-803f-546387230109_1536x1024.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>How should you, as a business analyst, approach this kind of statement?</p><p>First, recognize it for what it is: a business request expressed in a new form. It is not a complete specification, <strong>but it is an interactive expression of what the business believes it needs.</strong></p><p>A few years ago, the same person might have brought you an email, an Excel file, or a collection of hand-drawn screens. Today, AI allows people with limited technical experience to turn their ideas into something they can actually demonstrate. And that is great.</p><p>Today, in this article, I am not going to discuss security, architecture, code quality, or application maintenance. Those topics are important, but they deserve a separate conversation.</p><p>Instead, we will look at a vibe-coded application from the perspective of a business analyst:</p><ul><li><p>How should you examine it?</p></li><li><p>What information can you extract from it?</p></li><li><p>Which questions should you ask?</p></li><li><p>What analysis outputs should you produce?</p></li></ul><p>I believe, for a business analyst, it can be an extremely valuable source of information, as I said earlier, it is <strong>an interactive expression of business requirements.</strong></p><h2>Era of New Requirements Documents</h2><p>I remember when business users were expected to write down their business goals, needs, and requirements.</p><p>Perhaps this still happens in some organizations :)</p><p>The problem was that many business users found it difficult to describe an application or feature that did not yet exist. They understood their daily work and the problem they were trying to solve, but they did not necessarily know how to translate that knowledge into structured requirements.</p><p>A business analyst would receive statements such as:</p><ul><li><p>We need a better overview.</p></li><li><p>The current process takes too long.</p></li><li><p>Users should receive a notification.</p></li><li><p>The system should be easier to use.</p></li><li><p>And my personal favorite: the system must be faster! :)</p></li></ul><p>All these statements may be true, but they leave many questions unanswered.</p><p>Faster in what way? Should the page load faster? Should the user complete the process faster? Should the system make decisions faster?</p><p>A vague requirement can easily send an entire team in the wrong direction.</p><p>A vibe-coded application changes the conversation. Instead of only telling you what they imagine, the business can show you. You can see the screens, follow the process, click the buttons, and observe how they expect the application to behave. The prototype is not a complete requirements document, but it contains requirements. </p><p><strong>Your job as a business analyst is to know how to read them.</strong></p><p>Do not examine the application randomly. Read it in four passes and in this order.</p><h1>1. Understand the General Idea</h1><p>Begin with the purpose of the application.</p><p>Do not start by discussing buttons, colours, or individual fields. First, understand why the application exists.</p><p>Ask:</p><ul><li><p>What problem were you trying to solve?</p></li><li><p>Who experiences this problem?</p></li><li><p>Who is the primary user?</p></li><li><p>What is difficult about the current process?</p></li><li><p>What should improve if this application is introduced?</p></li><li><p>What outcome do you expect?</p></li><li><p>How will we know that the solution is successful?</p></li><li><p>Which part of the prototype is essential?</p></li><li><p>Which parts were added only because the AI suggested them?</p></li><li><p>If this prototype disappeared tomorrow, what business need would still remain?</p></li></ul><p>Imagine that the prototype contains a dashboard of unpaid invoices.</p><p>The real business need may not be &#8220;a dashboard.&#8221; The actual need may be to reduce the time employees spend identifying overdue payments and following up with customers.</p><p>The dashboard is one possible solution. The underlying problem is more important.</p><p>At the end of this step, you should understand:</p><ul><li><p>The business problem</p></li><li><p>The target users</p></li><li><p>The desired outcome</p></li><li><p>The expected business value</p></li><li><p>The success measures</p></li><li><p>The initial scope</p></li></ul><p>If you cannot explain the purpose of the application in two or three sentences, you are not ready to move to the next step.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Upgrade&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">This post has bonus content for paid subscribers. Upgrade to get full access.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Upgrade"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h1>2. Follow the Process Flow</h1><p>Do you understand the general idea? Do you know which problem you are trying to solve?</p><p>Good. Now you may start clicking the buttons.</p><p>Ask the business user to demonstrate the process from beginning to end. Do not focus only on what appears on each screen. Follow the story of the process.</p><p>Ask:</p><ul><li><p>What triggers the process?</p></li><li><p>Who performs the first action?</p></li><li><p>What information does the user need before starting?</p></li><li><p>Which information must be entered?</p></li><li><p>Where does the data come from?</p></li><li><p>Which decisions are made during the process?</p></li><li><p>Who makes those decisions?</p></li><li><p>What happens automatically?</p></li><li><p>Does anyone need to approve the request?</p></li><li><p>What is the final output?</p></li><li><p>Who receives the output?</p></li><li><p>When is the process considered complete?</p></li></ul><p>Vibe-coded applications usually demonstrate the <strong>happy path</strong> very well. Every field is completed correctly, all required information is available, and nothing unexpected happens.</p><p>Real processes are rarely that cooperative.</p><p>Continue asking:</p><ul><li><p>What happens when required information is missing?</p></li><li><p>What happens when the user enters incorrect information?</p></li><li><p>What happens when a request is rejected?</p></li><li><p>Can the user return to a previous step?</p></li><li><p>Can the process be cancelled?</p></li><li><p>What happens when an external system is unavailable?</p></li><li><p>Which errors can occur?</p></li><li><p>Who needs to know about those errors?</p></li><li><p>How does the user recover and continue?</p></li><li><p>Are there different flows for different users or situations?</p></li></ul><p>At the end of this step, you should have enough information to create a process map containing:</p><ul><li><p>The process trigger</p></li><li><p>Actors and responsibilities</p></li><li><p>Activities and decisions</p></li><li><p>Inputs and outputs</p></li><li><p>The happy path</p></li><li><p>Alternative paths</p></li><li><p>Exception paths</p></li><li><p>The process end</p></li></ul><p>The prototype gives you the visible flow. Your analysis must uncover the complete one.</p><h1>3. Examine the Design and User Interface</h1><p>You understand the purpose. You have followed the process. Now step back and look at the screens themselves.</p><p>The prototype shows how the business imagines the application should look. This is useful because screen design often reveals priorities that never appear in written requirements.</p><p>Ask:</p><ul><li><p>What information must the user see immediately?</p></li><li><p>Why is this information important?</p></li><li><p>Which information is essential and which is only nice to have?</p></li><li><p>Why are these fields grouped together?</p></li><li><p>Does the order of the fields follow the real working process?</p></li><li><p>Which fields are mandatory, and why?</p></li><li><p>Which fields should be editable?</p></li><li><p>Which values should be calculated automatically?</p></li><li><p>Does the user need to see all this information at the same time?</p></li><li><p>Why is this action represented by a button?</p></li><li><p>Does the colour communicate a business meaning?</p></li><li><p>Was this layout chosen deliberately, or did the AI simply generate it?</p></li><li><p>Will users complete this process on a computer, tablet, or mobile phone?</p></li><li><p>Does every user need the same screen?</p></li></ul><p>If a button is red, do not immediately document that the button must be red. Ask whether red communicates danger, rejection, or urgency, or whether it was simply the colour selected by the AI.</p><p>The goal is not to reproduce every pixel. The goal is to understand what users need to see, know, and do.</p><p>At the end of this step, you should be able to distinguish between:</p><ul><li><p>Mandatory interface requirements</p></li><li><p>User preferences</p></li><li><p>Visual priorities</p></li><li><p>Information hierarchy</p></li><li><p>Prototype design choices that do not need to be preserved</p></li></ul><p>Depending on the project, your output may be an annotated prototype, a wireframe, or a set of clear interface requirements.</p><h1>4. Listen to the Business Language</h1><p>Finally, pay close attention to field names, buttons, statuses, and other labels.</p><p>This is particularly important in industries such as aviation, banking, healthcare, and insurance, where terminology has precise meanings. A field must often use the language people already understand. Otherwise, you can spend months having unnecessary discussions about words.</p><p>Ask:</p><ul><li><p>Are these the terms employees use in their daily work?</p></li><li><p>Do these terms have agreed definitions?</p></li><li><p>Does <strong>Customer</strong> mean the same thing as <strong>Client</strong>?</p></li><li><p>Is the different wording intentional, or is it a mistake?</p></li><li><p>What does each status mean?</p></li><li><p>What causes a record to move from one status to another?</p></li><li><p>Can a record move backwards?</p></li><li><p>Do different departments use different terms for the same thing?</p></li><li><p>Are any abbreviations unclear?</p></li><li><p>Do any labels have regulatory or contractual meanings?</p></li><li><p>Are the same terms used in existing systems and reports?</p></li><li><p>Could a user misunderstand any of the buttons or instructions?</p></li></ul><p>If the application contains the statuses <strong>Approved</strong>, <strong>Completed</strong>, and <strong>Closed</strong>, do not assume their meaning is obvious.</p><p>What exactly has been approved? When is something completed? Who closes it? Can it be reopened?</p><p>Labels may look like a small detail, but inconsistent language often reveals unclear business concepts.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Practical business analysis knowledge takes time to research, test, and write. If this article helped you, consider becoming a paid subscriber. </p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>5. Now Look at What Is Missing</h2><p>So far, you have analyzed what is visible.</p><p>Now you need to analyze what is absent.</p><p>A vibe-coded application shows what the business user was thinking about while creating it. It may also reveal what they were not thinking about.</p><p>Ask:</p><ul><li><p>Are all user roles represented?</p></li><li><p>Who is allowed to view, create, edit, approve, or delete information?</p></li><li><p>Are approval limits defined?</p></li><li><p>Who owns the data?</p></li><li><p>Where does the data come from?</p></li><li><p>Which other systems must be integrated?</p></li><li><p>Which actions must be recorded for audit purposes?</p></li><li><p>Which reports will be required?</p></li><li><p>Are all calculations and business rules defined?</p></li><li><p>What happens when the process fails?</p></li><li><p>Who receives notifications?</p></li><li><p>Who will own the application after launch?</p></li><li><p>Who will support the users?</p></li><li><p>Which assumptions did the business make while building the prototype?</p></li><li><p>Which scenarios were never considered?</p></li></ul><p>This does not make the prototype bad. It simply means that it is a starting point.</p><p>A prototype is often the happy path wearing a nice shirt.</p><p>The business analyst must uncover everything happening behind it.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!TP-f!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!TP-f!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png 424w, https://substackcdn.com/image/fetch/$s_!TP-f!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png 848w, https://substackcdn.com/image/fetch/$s_!TP-f!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!TP-f!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!TP-f!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png" width="1024" height="1536" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/e4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1536,&quot;width&quot;:1024,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1571848,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/223798469?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!TP-f!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png 424w, https://substackcdn.com/image/fetch/$s_!TP-f!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png 848w, https://substackcdn.com/image/fetch/$s_!TP-f!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!TP-f!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe4ecf410-6524-4c2a-b618-785ceb7f12cd_1024x1536.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><h1>Next, How the Analysis Should Flow</h1><p>First, please do not turn the first demonstration into a three-hour interrogation. :) Let the business user show you what they created and explain why they created it.</p><p>A practical analysis flow can look like this:</p><h3>Step 1: Watch the Initial Demonstration</h3><p>Let the business user present the application without constant interruption.</p><p>Listen to the story they are telling. Notice which features they are excited about and which problems they mention repeatedly.</p><h3>Step 2: Confirm the Purpose</h3><p>Repeat the business problem and expected outcome in your own words.</p><p>Ask the business user to confirm whether you understood them correctly before examining the details.</p><h3>Step 3: Walk Through the Four Analysis Areas</h3><p>Review the application again, this time focusing on:</p><ol><li><p>The general idea</p></li><li><p>The process flow</p></li><li><p>The design and interface</p></li><li><p>The labels and business language</p></li></ol><p>Capture assumptions, missing scenarios, and unresolved questions as you proceed.</p><h3>Step 4: Create the Analysis Outputs</h3><p>Translate what you learned into structured analysis outputs and get answers from section 5.</p><p>Do not simply document what the prototype does. Document what the business needs, which rules must apply, and which questions still remain unanswered.</p><h3>Step 5: Conduct a Playback Session</h3><p>Return to the business and explain:</p><ul><li><p>What you understood</p></li><li><p>What you believe the business needs</p></li><li><p>Which parts of the prototype represent confirmed requirements</p></li><li><p>Which parts are only design preferliererences</p></li><li><p>Which assumptions require validation</p></li><li><p>Which scenarios are missing</p></li><li><p>Which decisions still need to be made</p></li></ul><p>The purpose of the playback is not to present a beautiful document. It is to confirm that everyone has the same understanding.</p><h3>Step 6: Move to Solution Assessment</h3><p>Only after the business intent and requirements have been validated should the prototype move into technical assessment and solution design.</p><p>This is where the team determines what can be reused, what must be redesigned, and what is required before any production implementation can be considered.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!sJg9!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!sJg9!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png 424w, https://substackcdn.com/image/fetch/$s_!sJg9!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png 848w, https://substackcdn.com/image/fetch/$s_!sJg9!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!sJg9!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!sJg9!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png" width="1024" height="1536" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1536,&quot;width&quot;:1024,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1653490,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/223798469?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!sJg9!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png 424w, https://substackcdn.com/image/fetch/$s_!sJg9!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png 848w, https://substackcdn.com/image/fetch/$s_!sJg9!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!sJg9!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9da91e71-1e3d-41bb-afeb-36da27c405e1_1024x1536.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><h1>What Should the Final Output Look Like?</h1><p>The exact outputs will depend on the size and complexity of the initiative.</p><p>A small internal tool may need only lightweight documentation. A business-critical application will require more detail.</p><p><strong>At minimum</strong>, your analysis should produce:</p><ul><li><p>A short initiative brief describing the problem, users, value, scope, and success measures</p></li><li><p>A process map covering the happy path, alternative paths, and exceptions</p></li><li><p>A list of actors, roles, and responsibilities</p></li><li><p>Annotated screens, wireframes, or interface requirements</p></li><li><p>A glossary of agreed business terms</p></li><li><p>Business rules and calculations</p></li><li><p>Data requirements and sources</p></li><li><p>Integration requirements</p></li><li><p>User stories or functional requirements</p></li><li><p>Acceptance criteria</p></li><li><p>A list of assumptions</p></li><li><p>A list of open questions and decisions</p></li><li><p>A list of missing scenarios</p></li></ul><p>You do not need to create a cemetery of documents that nobody will ever read.</p><p>The important point is that your final documentation must describe the validated business need, not simply copy the behaviour of the prototype. </p><p>A vibe-coded application may be one of the best presentations a business user can give to a business analyst.</p><p>It makes an abstract idea visible. </p><p></p>]]></content:encoded></item><item><title><![CDATA[Ayushi Malviya: From QA to Business Analysis]]></title><description><![CDATA[Requirements, priorities, AI, and growth through the eyes of a practising business analyst]]></description><link>https://www.analystharbor.online/p/ayushi-malviya-from-qa-to-business</link><guid isPermaLink="false">https://www.analystharbor.online/p/ayushi-malviya-from-qa-to-business</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Tue, 13 Oct 2026 10:20:33 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!xdI8!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Business analysis is not only about writing requirements or managing a backlog. It is about creating clarity, asking the right questions, validating what you have understood, and helping business and technical teams move in the same direction.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!xdI8!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!xdI8!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!xdI8!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!xdI8!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!xdI8!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!xdI8!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png" width="1456" height="971" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:971,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1496269,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/219069281?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!xdI8!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!xdI8!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!xdI8!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!xdI8!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F646dc35e-0947-4bdb-a51b-b3cf314809f8_1536x1024.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>For <strong><a href="https://www.linkedin.com/in/ayushi-malviya93/">Ayushi Malviya</a></strong>, that journey began in credit risk and quality assurance. Working with data, validation, requirements, and automation gradually brought her closer to the business analyst role.</p><p>In this interview, Ayushi shares how she organises her day, protects important decisions from being lost, validates requirements, and uses AI without allowing it to replace professional judgement.</p><p>This conversation is part of the <strong>Analyst Harbor interview series</strong>, where we speak with practising business analysts about their careers, working methods, tools, and lessons learned. Our goal is to give junior analysts an honest and practical view of how business analysis works in real projects.</p><h2>From Credit Risk and QA to Business Analysis</h2><p><strong>1. How did you become a business analyst, and what attracted you to this profession?</strong></p><p>I started my career in credit risk and quality assurance, where I worked closely with requirements, data validation, and automation.</p><p>Over time, I realised that I enjoyed bridging the gap between business needs and technical solutions. The business analyst role attracted me because it combines problem-solving, communication, and analytical thinking. It allows me to help organisations deliver value while reducing risk.</p><h2>Organising the Work</h2><p><strong>2. How do you organise your working day and set priorities when you have meetings, analysis work, and several different tasks to manage?</strong></p><p>I begin by reviewing my calendar and task list. I then prioritise my work based on urgency, dependencies, and stakeholder impact.</p><p>Critical meetings and deliverables come first, followed by analysis work that requires concentration. I also block out time for focused work to avoid constant context switching.</p><p><strong>3. Which tools do you use most frequently, and how does each of them support your work?</strong></p><ul><li><p><strong>Jira and Confluence</strong> for backlog management, user stories, and documentation.</p></li><li><p><strong>SQL and Excel</strong> for data validation and analysis.</p></li><li><p><strong>Visio and Figma</strong> for process flows and wireframes.</p></li><li><p><strong>Power BI</strong> for dashboards and reporting.</p></li></ul><p>Together, these tools help me capture requirements, analyse data, visualise processes, and communicate clearly with stakeholders.</p><p><strong>4. How do you take notes during meetings and ensure that important requirements, decisions, and action items are not lost?</strong></p><p>I use structured templates in OneNote or Confluence to capture decisions, action items, and their owners.</p><p>Immediately after the meeting, I summarise the key points and share them with stakeholders to confirm that my understanding is accurate. This also gives everyone an opportunity to correct or clarify anything that may have been misunderstood.</p><p><strong>5. How do you make sure that you have correctly understood the business requirements before you document them or propose a solution?</strong></p><p>I validate my understanding through stakeholder workshops, playback sessions, and clarifying questions.</p><p>I restate the requirements in simple terms and confirm them with business users. This helps ensure that everyone is aligned before I begin documenting the requirements or proposing a solution.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Enjoying this Interview? Independent interviews and practical articles take time to prepare. If Analyst Harbor helps you grow, consider becoming a paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Using AI Without Losing Professional Judgement</h2><p><strong>6. How do you currently use AI in your work? Which activities does it help you with the most?</strong></p><p>AI helps me summarise meeting notes, prepare initial drafts of user stories, create process flows, and analyse large datasets more quickly.</p><p>It reduces manual effort and speeds up documentation, giving me more time to focus on analysis and communication.</p><p><strong>7. Can you share a specific example of a task that AI helped you complete faster or to a higher standard?</strong></p><p>During a mobile application project for gold loans, I used AI to create structured user stories from stakeholder discussions.</p><p>This saved several hours of manual writing and helped maintain consistency across the backlog items.</p><p><strong>8. How do you verify the accuracy of AI-generated outputs?</strong></p><p>I cross-check AI-generated outputs against source data, business rules, and stakeholder feedback.</p><p>I treat AI as a tool for creating an initial draft, not as a final authority. Everything must be reviewed and validated before it is used.</p><p><strong>9. Are there situations in which you prefer not to rely on AI?</strong></p><p>Yes, particularly when I am working with sensitive data, regulatory requirements, or complex stakeholder negotiations.</p><p>In these situations, human judgement, professional experience, and domain expertise are essential.</p><p><strong>10. Does your organisation have rules for using AI and handling confidential or internal information? How do these rules affect your work?</strong></p><p>Yes, we have clear guidelines. AI tools cannot be used with confidential client data or proprietary information.</p><p>These rules help protect data and ensure compliance. I therefore use AI mainly for generic activities, such as preparing documentation drafts, creating analysis templates, and supporting knowledge sharing.</p><h2>What Comes Next?</h2><p><strong>11. Which tool, organisational method, or AI-related skill would you like to improve next, and what would you recommend to other junior business analysts?</strong></p><p>I would like to deepen my expertise in <strong>process automation and AI-driven analytics</strong>.</p><p>For junior business analysts, I recommend mastering the fundamentals first: clear documentation, effective stakeholder communication, and structured analysis.</p><p>Once these foundations are in place, AI tools can gradually be introduced to improve efficiency. AI can make the work faster, but it cannot replace a solid understanding of business analysis.</p><h2>What We Can Learn from Ayushi</h2><p>Ayushi&#8217;s answers show that effective business analysis is not defined by one tool, template, or methodology. It comes from a disciplined way of working: prioritising carefully, confirming what you have understood, documenting decisions, protecting sensitive information, and continuing to learn.</p><p>AI may change how some tasks are completed, but the foundations remain the same. Business analysts still need to create clarity, connect people, challenge assumptions, and ensure that the proposed solution addresses the real business need.</p><h2>Who Should We Interview Next?</h2><p>Do you know an interesting business analyst whose work deserves more attention?</p><p>Perhaps they have an unusual career journey, a practical way of solving problems, or valuable lessons that could help other analysts grow.</p><p><strong>Let us know! :)</strong></p><p>Leave their name in the comments or send us a message with a link to their profile. We are always looking for analysts who deserve the chance to share their experience with the Analyst Harbor community.</p>]]></content:encoded></item><item><title><![CDATA[Harbor Short #004: The Hidden Cost of Workarounds]]></title><description><![CDATA[What looks like a simple solution today may become an expensive problem tomorrow.]]></description><link>https://www.analystharbor.online/p/harbor-short-004-the-hidden-cost</link><guid isPermaLink="false">https://www.analystharbor.online/p/harbor-short-004-the-hidden-cost</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Tue, 06 Oct 2026 10:47:43 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!Emoj!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!Emoj!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!Emoj!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!Emoj!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!Emoj!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!Emoj!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!Emoj!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png" width="1456" height="971" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:971,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1430960,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/215500570?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!Emoj!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!Emoj!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!Emoj!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!Emoj!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb799b948-1b80-4d9f-aed5-65aefb1079e0_1536x1024.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Today&#8217;s story will sound familiar to almost every one of you :)</p><p>You have finished the project. The processes are working, the customer is happy with the result, and there are no major incidents. For a moment, the world seems like a good place.</p><p>But one thing is quietly spoiling this perfect picture.</p><p><strong>A workaround!</strong></p><p>I am sure you have heard this word many times during your career. A workaround often looks harmless. It solves an immediate problem, keeps the process moving, and helps everyone get through the day.</p><p>But <strong>every workaround has a hidden cost</strong>&#8212;and sometimes that cost is much higher than anyone expected.</p><p>Today, I want to explain why.</p><h2>A Simple Example: Processing Customer Discounts</h2><p>Imagine an order system that cannot handle a specific type of customer discount. This is actually a very common example.</p><p>Every Friday, someone exports the affected orders, adjusts the amounts in Excel, and sends the corrected file to finance.</p><p>It takes about two hours a week. Nothing dramatic.</p><p>But two hours a week adds up to roughly 100 hours a year.</p><p>And that is only the regular work. It does not include explaining the process to a colleague, investigating a mistake, or finding someone to cover during a holiday.</p><p>Now imagine the number of orders doubles.</p><p><strong>The system limitation has become a recurring operational cost.</strong></p><p>That does not automatically mean the company should build a new feature. A system change may cost more than the workaround.</p><p>But &#8220;we can do it manually&#8221; is not enough information to make that decision. </p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption"><strong>Did you find this Harbor Short useful?</strong>Consider becoming a paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>What does the workaround really cost?</h2><p>The most <strong>visible cost</strong> is the time spent doing it.</p><p>Other <strong>hidden costs</strong> are easier to miss:</p><ul><li><p>Checking and correcting the results.</p></li><li><p>Waiting for a particular person to become available.</p></li><li><p>Delaying the next step in the process.</p></li><li><p>Training someone to cover the task.</p></li><li><p>Handling errors that reach customers.</p></li><li><p>Giving up other work that the same person could have done.</p></li></ul><p>A workaround can also create dependency on knowledge that exists only in someone&#8217;s head.</p><p>&#8220;It&#8217;s easy, Anna knows how to do it.&#8221;</p><p>Great. What happens when Anna is away?</p><h2>10 Questions a Business Analyst Should Ask Before Introducing a Workaround</h2><ol><li><p>What problem does the workaround solve?</p></li><li><p>Who performs it, and how often?</p></li><li><p>How much time does it take, including checks and corrections?</p></li><li><p>How often does it fail, and what happens when it does?</p></li><li><p>Does it delay customers or other teams?</p></li><li><p>Can someone else perform it when the usual person is unavailable?</p></li><li><p>What happens if the business volume doubles?</p></li><li><p>Could we remove or simplify the underlying business requirement?</p></li><li><p>How does the ongoing cost compare with the cost of changing the system?</p></li><li><p>If we keep the workaround, when should we review that decision?</p></li></ol><h2>The key lesson</h2><p>Not every workaround needs to be automated.</p><p>For a rare exception, a manual process may be the best business choice. For a frequent activity, it may be much more expensive than it appears.</p><p><strong>The important thing is to make that choice consciously.</strong></p><p>A good business analyst does not ask only whether a process works. They also ask what it takes to keep it working and whether that still makes sense.</p>]]></content:encoded></item><item><title><![CDATA[Harbor Shorts Are Growing]]></title><description><![CDATA[Short practical lessons, hands-on exercises, and monthly discussions for junior business analysts.]]></description><link>https://www.analystharbor.online/p/harbor-shorts-are-growing</link><guid isPermaLink="false">https://www.analystharbor.online/p/harbor-shorts-are-growing</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Thu, 01 Oct 2026 10:43:58 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!xuVz!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!xuVz!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!xuVz!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!xuVz!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!xuVz!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!xuVz!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!xuVz!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png" width="1456" height="819" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:819,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1958893,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/217115714?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!xuVz!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!xuVz!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!xuVz!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!xuVz!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F42bf5246-7828-4a6e-abdf-a4346058c513_1672x941.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>A few weeks ago, we started publishing <strong>Harbor Shorts</strong>.</p><p>We introduced the idea in <a href="https://www.analystharbor.online/p/harbor-shorts-a-new-concept-arrives">our first article</a>, but the goal was simple: to give junior business analysts practical knowledge they rarely receive during training courses and to keep each lesson short and easy to understand.</p><p>The response has been amazing. Thank you! </p><p>Many of you have told us that the Shorts helped you understand a problem or recognize a mistake you had made yourself. And that is completely fine. It happened to all of us. The only difference is that experienced analysts have already made more mistakes and had more time to learn from them.</p><p>Now, we want to make Harbor Shorts even more practical.</p><h2>From reading to practising</h2><p>Starting next week, every Harbor Short will include a practical exercise based on the topic of the article.</p><p>At the end of each Short, you will receive a business scenario and a task to complete. You will then have two working days to prepare your answer. On Thursday evening, we will publish our suggested solution.</p><p>We call it as <strong>suggested solution</strong> because business analysis rarely has only one correct answer. Your approach may be different from ours and still work perfectly well. </p><p>The goal is to help you practise how to think, not simply copy an answer.</p><blockquote><h2>Learn from Experienced Business Analysts for Less Than $10 a Month</h2><p>Formal business analysis courses can cost thousands of dollars. For less than $10 a month, you can learn from experienced professionals through practical lessons, real-world exercises, suggested solutions, and monthly discussions.</p><p>Become a paid subscriber, develop your skills with us, and support the creation of more practical content for junior business analysts.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.analystharbor.online/subscribe?"><span>Subscribe now</span></a></p></blockquote><h2>Bonus: Join our monthly discussion</h2><p>At the end of each month, we will also host an online call for our subscribers.</p><p>We will review all the Harbor Shorts published that month, discuss the exercises, explain why we chose particular outputs, and explore other possible approaches. You can ask questions, share your solution, or simply join the conversation.</p><p>Bring coffee, tea, or whatever you like, and spend some time with us solving real business analysis problems.</p><p><strong>Read the lesson. Try the exercise. Compare your answer. Join the discussion.</strong></p><p>We look forward to learning with you :)</p>]]></content:encoded></item><item><title><![CDATA[Harbor Short #003: Before Your Best People Walk Away]]></title><description><![CDATA[A simple rejection brought me back to what our community had already revealed about why business analysts leave.]]></description><link>https://www.analystharbor.online/p/harbor-short-003-before-your-best</link><guid isPermaLink="false">https://www.analystharbor.online/p/harbor-short-003-before-your-best</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Tue, 29 Sep 2026 10:58:55 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!-FfT!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>We do a <em>lot</em> of interviews at Analyst Harbor, juniors, seniors, business analysts, business architects&#8230; basically anyone who has ever said the words: <em>&#8220;It depends.&#8221;</em> :)</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!-FfT!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!-FfT!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!-FfT!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!-FfT!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!-FfT!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!-FfT!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png" width="1456" height="819" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:819,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1029890,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/187766476?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!-FfT!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!-FfT!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!-FfT!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!-FfT!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9b9365c1-fa7c-467e-bc4b-3a2e1b1a3d7d_1672x941.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>And I genuinely love it. Not because interviews look good on a content calendar (they do), but because people are honest. They talk about what&#8217;s changing, what&#8217;s painful, what AI is doing to our work, and what still matters when everything around us feels like it&#8217;s on &#8220;fast forward&#8221;.</p><p>Recently I reached out to one of my connections and asked (gently, politely, with my best &#8220;networking voice&#8221;) if he&#8217;d be open to an interview.</p><p><strong>He declined.</strong></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Analyst Harbor is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>No long explanation. Just one sentence:</p><blockquote><p>&#8220;You already wrote an article about that.&#8221;<em> - <a href="https://www.analystharbor.online/publish/post/174638592?back=%2Fpublish%2Fposts%2Fdrafts">Why Business Analysts Leave: Insights from Our Community</a></em></p></blockquote><p>Whether you are the one making the rules or the one following them, take a few minutes to read this piece. It may help you avoid costly mistakes and protect what is most valuable in any organization&#8230; its PEOPLE.</p>]]></content:encoded></item><item><title><![CDATA[We Built the API on Assumptions: The Real Reason Our Integration Failed]]></title><description><![CDATA[What a failed integration taught us about assumptions, API contracts, and the true cost of ambiguity.]]></description><link>https://www.analystharbor.online/p/we-built-the-api-on-assumptions-the</link><guid isPermaLink="false">https://www.analystharbor.online/p/we-built-the-api-on-assumptions-the</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Tue, 22 Sep 2026 10:30:41 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!dMVx!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Recently, one of my integration projects was closed after a difficult month of trying to bring it to life :(</p><p>The team worked hard. </p><p>We held meetings, clarified requirements, made changes, tested different scenarios, and kept trying to move the project forward. Yet despite all that effort, we could not prepare and deploy the integration in the way the business users expected it to work.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!dMVx!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!dMVx!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!dMVx!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!dMVx!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!dMVx!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!dMVx!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png" width="1456" height="819" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/a2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:819,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1011806,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/188789158?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!dMVx!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!dMVx!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!dMVx!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!dMVx!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa2cc36ce-5faa-4e5c-b2bc-453dca285d14_1672x941.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>The reason was painfully simple:</p><h4><strong>We had never reached a shared agreement on what the API integration was actually supposed to do.</strong></h4><p>We had discussed systems, fields, endpoints, and technical possibilities. </p><p>People had assumptions. </p><p>People also believed that other people shared those assumptions.</p><p>They did not.</p><p>By the time the differences became visible, code had already been written, time had been spent, and every clarification created another round of changes. We were no longer refining one solution. We were trying to reconcile several different ideas of what the solution should have been.</p><p>This article is not about blaming developers, business users, or anyone else involved. It is about examining the mistake and turning it into something useful that we all as a community can lear. </p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!Ffno!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!Ffno!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png 424w, https://substackcdn.com/image/fetch/$s_!Ffno!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png 848w, https://substackcdn.com/image/fetch/$s_!Ffno!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png 1272w, https://substackcdn.com/image/fetch/$s_!Ffno!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!Ffno!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png" width="1456" height="1352" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/f4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1352,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:2887368,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/188789158?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!Ffno!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png 424w, https://substackcdn.com/image/fetch/$s_!Ffno!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png 848w, https://substackcdn.com/image/fetch/$s_!Ffno!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png 1272w, https://substackcdn.com/image/fetch/$s_!Ffno!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4b56b24-85af-4be0-bc69-3d179d3752bb_1982x1840.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a><figcaption class="image-caption">An API Is Not Just a Technical Connection</figcaption></figure></div><p>So, what should we have agreed before development began?</p><h2>An API Is Not Just a Technical Connection</h2><p>When someone says, &#8220;We need to connect System A with System B,&#8221; the request sounds straightforward.</p><p>System A sends data. System B receives it. Done.</p><p>Except that this sentence tells us almost nothing about the behaviour the business needs.</p><ul><li><p>Which event should start the exchange?</p></li><li><p>What information should be sent?</p></li><li><p>Which system owns each piece of data?&#8230; this turned out to be a major problem for our project.</p></li><li><p>Should the receiving system create a new record or update an existing one?</p></li><li><p>What happens when a mandatory value is missing?</p></li><li><p>What happens when the same request is sent twice?</p></li><li><p>What happens when one system is temporarily unavailable?</p></li><li><p>Who needs to know when the integration fails?</p></li><li><p>How will the business confirm that the data is complete and correct?</p></li></ul><p>These are not minor technical details. </p><h4><strong>They are business decisions.</strong></h4><p>An API is more than a pipe between two systems. It is an agreement about how those systems will behave together. If that agreement exists only in separate conversations, assumptions, or people&#8217;s heads, the team does not yet have a requirement. It has several competing interpretations.</p><p>That was our problem. </p><p>We moved too quickly from a business idea to technical implementation.</p><h2>The Most Dangerous Word in an Integration Project: &#8220;Sync&#8221;</h2><p>Consider a simple requirement:</p><blockquote><p>Flight data should be synchronised from System A to System B.</p></blockquote><p>Everyone may nod. The sentence sounds clear. But ask five more questions and the agreement can disappear immediately.</p><p>Does &#8220;synchronised&#8221; mean:</p><ul><li><p>updating every field or only selected fields?</p></li><li><p>sending changes immediately or in scheduled batches?</p></li><li><p>transferring all or only those with a particular status?</p></li><li><p>overwriting only values already changed in System B?</p></li><li><p>what if System B accepts the request but fails before completing the update?</p></li><li><p>and  I could go on and on&#8230;</p></li></ul><p>The original requirement did not answer any of these questions.</p><p>And yet someone will have to answer them before the integration can work. </p><p>If the business does not make those decisions, developers will make reasonable assumptions so they can continue building. QA will later test against another interpretation. And business users will assess the result against the process they imagined.</p><h2>What We Should Have Done Before Writing Code</h2><p>The solution is not a 100-page specification. It is a series of focused agreements, made in the right order and recorded clearly enough to build and test.</p><h3>1. Start with the business outcome</h3><p>Before discussing endpoints or payloads, the team should be able to answer one question:</p><p><strong>What business outcome is this integration expected to create?</strong></p><p>&#8220;Connect the two systems&#8221; is not an outcome. Neither is &#8220;automate the process.&#8221;</p><p>A useful outcome sounds more like this:</p><blockquote><p>When a customer is approved in System A, an account must be created in System B without manual re-entry, so the operations team can begin service within ten minutes.</p></blockquote><p>Now we know the trigger, the systems involved, the intended result, the user who benefits, and an important timing expectation.</p><p>At this stage, also define what is outside the scope. </p><p>If the integration creates customers but does not update them later, say so. If historical records will not be migrated, record that decision. Clear exclusions are just as valuable as clear requirements.</p><p><strong>Output:</strong> a short initiative brief containing the objective, scope, stakeholders, consumers, constraints, and success measures.</p><h3>2. Map the end-to-end business flow</h3><p>An endpoint does not exist in isolation. Something happens before it is called, and something must happen after it responds.</p><p>Map the complete flow from the first business event to the final visible outcome. Include the human steps, not only the system interactions.</p><p>For each step, confirm:</p><ul><li><p>who or what initiates it;</p></li><li><p>what information is required;</p></li><li><p>which system performs the action;</p></li><li><p>who owns the result;</p></li><li><p>how success becomes visible to the user;</p></li><li><p>what the user does if it fails.</p></li></ul><p>This is often where hidden disagreements emerge. </p><p>One team thinks approval triggers the integration; another thinks it happens after a scheduled job. One team expects an automatic retry; another expects a person to correct the record and submit it again.</p><p><strong>Output:</strong> an end-to-end process map with numbered steps, systems, actors, decision points, and failure paths.</p><h3>3. Agree on the meaning and ownership of data</h3><p>Fields with the same name do not necessarily have the same meaning.</p><p>One system&#8217;s &#8220;active customer&#8221; may mean a signed contract. In another system, it may mean that the customer has completed onboarding. A field called &#8220;STATUS&#8221; can contain technically compatible values while representing completely different business states.</p><p>Create a shared glossary and a field-level mapping. For every important value, agree on:</p><ul><li><p>its business definition;</p></li><li><p>its source system;</p></li><li><p>its owner;</p></li><li><p>its format and allowed values;</p></li><li><p>whether it is mandatory;</p></li><li><p>any transformation applied during transfer;</p></li><li><p>what should happen when it is missing or invalid.</p></li></ul><p>Do not allow the mapping exercise to become a purely technical comparison of column names. </p><p>The critical question is not &#8220;Can we send this field?&#8221; It is &#8220;Will the receiving system understand it in the same way?&#8221;</p><p><strong>Output:</strong> a domain glossary and data-mapping document with ownership and transformation rules.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Analyst Harbor is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3>4. Turn expectations into explicit business rules</h3><p>&#8220;Only valid customers should be transferred&#8221; is not precise enough. What makes a customer valid? Which values are required? Who approves an exception?</p><p>A testable rule might say:</p><blockquote><p>A customer may be sent to System B only when the approval status is &#8220;APPROVED&#8221; and the registration number, legal name, billing country, and billing email are populated.</p></blockquote><p>Now the team can implement it.</p><p>Give important rules an identifier and record the business owner who approved them. This makes later discussions much easier. Instead of debating what someone remembers from a meeting, the team can review the decision that was actually made.</p><p><strong>Output:</strong> a lightweight business-rule catalogue.</p><h3>5. Design the unhappy paths before the happy path is approved</h3><p>Most teams are comfortable discussing success. A valid request is sent, the receiving system accepts it, and the record appears in the right place.</p><p>But integrations are defined by what happens when that sequence breaks.</p><p>Discuss at least these scenarios:</p><ul><li><p>required data is missing;</p></li><li><p>the user is not authorised;</p></li><li><p>the same request is received more than once;</p></li><li><p>the receiving system is unavailable;</p></li><li><p>the request times out and the sender does not know whether it succeeded;</p></li><li><p>part of the transaction succeeds and part fails;</p></li><li><p>the receiving system rejects a value;</p></li><li><p>data is accepted but produces the wrong business state;</p></li><li><p>a corrected record must be submitted again.</p></li></ul><p>For every meaningful failure, decide:</p><ol><li><p>What response will the sending system receive?</p></li><li><p>Will the request be retried automatically?</p></li><li><p>Could a retry create a duplicate?</p></li><li><p>Will a business user see the failure?</p></li><li><p>Who is responsible for resolving it?</p></li><li><p>How can the team confirm that the final state is correct?</p></li></ol><h4>If QA is the first team to ask these questions, the project has already waited too long.</h4><p><strong>Output:</strong> a scenario and exception map covering success, validation failures, technical failures, retries, and recovery.</p><h3>6. Write requirements that can become acceptation tests</h3><p>Every requirement entering development should have a clear pass-or-fail condition.</p><p>Avoid phrases such as:</p><ul><li><p>&#8220;The integration should be fast.&#8221; (a side note: I see this requirement all the time, and I still have no idea what &#8220;fast&#8221; actually means. Fast like an Arabian horse? A cheetah? A project manager five minutes before a deadline? :))</p></li><li><p>&#8220;Errors should be handled correctly.&#8221;</p></li><li><p>&#8220;The systems should remain synchronised.&#8221;</p></li><li><p>&#8220;Duplicate records should be avoided.&#8221;</p></li></ul><p>They express a sensible intention, but they cannot be implemented or accepted consistently.</p><p>Instead, write the expected behaviour in observable terms:</p><blockquote><p>When an approved customer is received with a registration number that already exists in System B, the API must update the existing record and return its identifier. It must not create a second customer record.</p></blockquote><p>This tells the developer what to build, the tester what to verify, and the business owner what to approve.</p><p><strong>Output:</strong> functional requirements with acceptance criteria and examples.</p><h3>7. Turn the agreed behaviour into an API contract</h3><p>Only now is the team ready to finalise the technical contract.</p><p>For each API endpoint, the contract should define:</p><ul><li><p>its business purpose and consumer;</p></li><li><p>method, path, and version;</p></li><li><p>required headers;</p></li><li><p>request fields, formats, and validation constraints;</p></li><li><p>successful response;</p></li><li><p>error responses and their meanings;</p></li><li><p>authentication and authorisation;</p></li><li><p>duplicate and retry behaviour;</p></li><li><p>performance expectations;</p></li><li><p>logging, audit, and trace identifiers;</p></li><li><p>data sensitivity and security requirements.</p></li></ul><p>OpenAPI or another machine-readable specification is extremely useful here. It creates a common reference for development, testing, documentation, and consumer teams.</p><p>But an API specification cannot invent the missing business decisions. If it is written before the rules are agreed, it is a technical draft&#8212;not yet a reliable contract.</p><p><strong>Output:</strong> an approved API specification supported by the business rules and scenarios behind it.</p><h3>8. Connect every decision to a test</h3><p>A simple chain should be visible throughout the project:</p><p><strong>Business outcome &#8594; business rule &#8594; functional requirement &#8594; API behaviour &#8594; test case</strong></p><p>This traceability is not paperwork for its own sake. </p><p>Without traceability, every change becomes a new investigation. With it, impact analysis becomes much faster and less political.</p><p><strong>Output:</strong> a lean traceability matrix maintained throughout delivery.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!q_5j!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!q_5j!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg 424w, https://substackcdn.com/image/fetch/$s_!q_5j!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg 848w, https://substackcdn.com/image/fetch/$s_!q_5j!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg 1272w, https://substackcdn.com/image/fetch/$s_!q_5j!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!q_5j!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg" width="1456" height="1820" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1820,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:7877,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/svg+xml&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/188789158?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!q_5j!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg 424w, https://substackcdn.com/image/fetch/$s_!q_5j!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg 848w, https://substackcdn.com/image/fetch/$s_!q_5j!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg 1272w, https://substackcdn.com/image/fetch/$s_!q_5j!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F21dc2f36-9b9d-4034-8bf1-fee2739d4cb4_1080x1350.svg 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><h2>TEST: The Sentence Every Team Should Complete</h2><p>Before development starts, ask the product owner, business analyst, developer, and tester to complete this sentence together:</p><blockquote><p>When <strong>[business event]</strong> happens in <strong>[source system]</strong>, the integration sends <strong>[specific information]</strong> to <strong>[target system]</strong>. The target system validates <strong>[rules]</strong> and then <strong>[creates/updates/rejects]</strong> the record. On success, <strong>[visible outcome]</strong> happens. On failure, <strong>[recovery and ownership]</strong> applies.</p></blockquote><p>If the team cannot complete this sentence without disagreement, the integration is not ready to be built.</p><p>Did the test go well? Congratulations! </p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Analyst Harbor is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>But you&#8217;re still only halfway there.</strong> Before implementation begins, run this 20-minute review to make absolutely sure everyone on the team agrees on what the integration is supposed to do.</p><h2>A 20-Minute Review That Can Save Weeks</h2><h3>Minutes 1&#8211;5: Purpose and trigger</h3><p>Confirm why the endpoint exists, who or what calls it, and which business event triggers it.</p><h3>Minutes 6&#8211;10: Data and rules</h3><p>Walk through the request and response. Challenge mandatory fields, allowed values, ownership, transformations, and validation rules.</p><h3>Minutes 11&#8211;15: Failure and recovery</h3><p>Review duplicates, timeouts, retries, partial failures, error messages, and manual intervention. Confirm who owns each recovery action.</p><h3>Minutes 16&#8211;20: Acceptance</h3><p>Link each important behaviour to an acceptance criterion or test. Confirm how the business will recognise that the integration works&#8212;not merely that the endpoint returned a successful status code.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!3YFv!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!3YFv!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png 424w, https://substackcdn.com/image/fetch/$s_!3YFv!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png 848w, https://substackcdn.com/image/fetch/$s_!3YFv!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png 1272w, https://substackcdn.com/image/fetch/$s_!3YFv!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!3YFv!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png" width="1080" height="1350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1350,&quot;width&quot;:1080,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:211223,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/188789158?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!3YFv!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png 424w, https://substackcdn.com/image/fetch/$s_!3YFv!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png 848w, https://substackcdn.com/image/fetch/$s_!3YFv!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png 1272w, https://substackcdn.com/image/fetch/$s_!3YFv!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86245728-fcc2-4cdc-92e1-234b385e62cf_1080x1350.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><h2>5 Warning Signs That an API Project Is Not Ready</h2><h3>1. The requirement is only &#8220;connect the systems&#8221;</h3><p>The connection is the mechanism, not the business outcome.</p><h3>2. The team is designing endpoints before agreeing on rules</h3><p>The structure may look correct while the behaviour remains undefined.</p><h3>3. Success is documented, but failure is left for later</h3><p>Error handling, retries, and recovery are part of the product&#8212;not technical cleanup.</p><h3>4. Different teams use the same words without a shared glossary</h3><p>Matching field names can hide conflicting meanings.</p><h3>5. Business users will see the integration for the first time during acceptance testing</h3><p>Acceptance testing should confirm agreed behaviour. It should not be the first moment when the expected behaviour is discovered.</p><h2>Two Perspectives from the Authors</h2><h3>Lucia&#8217;s perspective</h3><p>For me, the biggest lesson from this project is that hard work cannot compensate for a lack of agreement. I watched my team work their asses off and still get nowhere.</p><p>Next time, I would not begin by asking the team to describe the endpoint. I would bring the business owner, system owners, developer, and QA together and ask them to walk through the entire process&#8212;from the first business event to the final visible result.</p><p>I would stop whenever someone used words such as &#8220;sync,&#8221; &#8220;automatically,&#8221; &#8220;valid,&#8221; &#8220;failed,&#8221; or &#8220;updated&#8221; and ask what they meant in observable, testable behaviour. I would document the decisions, not only the discussion, and ask everyone to explain the integration back to the group in their own words.</p><p>It would require more time at the beginning. But it would save far more time, money, and frustration at the end.</p><h3>Milos&#8217;s perspective</h3><p>From my perspective, a reliable API is defined as much by its failures as by its successful responses.</p><p>The happy path is usually easy to describe. The real questions begin when data is missing, a request is duplicated, a system times out, or only part of a transaction succeeds. If error behaviour, retries, recovery, and ownership are not agreed in advance, the API may work technically while still failing the business.</p><p>This is especially important in regulated environments, where predictable behaviour, traceability, and auditability are essential. Documentation does not need to be extensive, but the contract must be clear enough that developers, testers, support teams, and business users all interpret it in the same way.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Help Us Keep Analyst Harbor Going</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Our Conclusion</h2><p>Good business analysis does not mean producing a library of documents that nobody reads. It means creating enough shared understanding to remove dangerous assumptions.</p><p>One clear page that answers the right questions is more valuable than fifty pages copied from a template. However, &#8220;lightweight&#8221; must never become an excuse for leaving essential decisions undocumented.</p><p>The most expensive integration problems rarely begin with bad code. They begin with reasonable people holding different interpretations of what the code is supposed to do.</p><p>Before development starts, ask everyone involved to explain what should happen before, during, and after the API call, including what happens when something goes wrong.</p><p>If their answers differ, you have found the most valuable work on the project.</p><p>And it is much cheaper to do that work today than after another month of trying to bring the wrong solution to life.</p><p><em>Have you worked on an integration where everyone believed they agreed&#8212;until testing proved otherwise? Share the lesson with the Analyst Harbor community. Your experience may help another analyst ask the right question before the first line of code is written.</em></p>]]></content:encoded></item><item><title><![CDATA[Harbor Short #002: The One Thing Every Process Map Needs]]></title><description><![CDATA[Numbering transforms a process map from a picture into a practical working document.]]></description><link>https://www.analystharbor.online/p/harbor-short-002-the-one-thing-every</link><guid isPermaLink="false">https://www.analystharbor.online/p/harbor-short-002-the-one-thing-every</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Tue, 15 Sep 2026 10:45:51 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!BlKU!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I have to admit that I love process maps :). Creating a clear and understandable one can be surprisingly difficult, but once you master this skill, it will help you enormously as a business analyst.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!BlKU!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!BlKU!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!BlKU!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!BlKU!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!BlKU!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!BlKU!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png" width="1456" height="971" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:971,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1501638,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/214150186?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!BlKU!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!BlKU!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!BlKU!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!BlKU!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F604c567f-77c8-4b9a-8dc3-3cbccd341d50_1536x1024.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Today, I am not going to explain how to create a process map from beginning to end. That deserves a separate article. Instead, I want to focus on one simple detail that junior analysts often overlook.</p><p>They study the methodology, learn the correct notation, select the right shapes, and connect everything properly. Then they send me a process map that looks perfectly fine at first glance &#8230; but one important feature is usually missing:</p><p><strong>Unique reference number.</strong></p><p>It may sound obvious, but numbering transforms a process map from a picture into a practical working document.</p><p>Imagine that you need to discuss the map with a colleague or link one of its steps to more detailed documentation. Without numbers, you might say:</p><blockquote><p>&#8220;The email address must be mandatory in the personal information step.&#8221;</p></blockquote><p>A numbered step makes the requirement much clearer:</p><blockquote><p>&#8220;In Step 6 &#8211; Enter Personal Information, the email address must be mandatory.&#8221;</p></blockquote><p><strong>Now everyone knows exactly which part of the process you are referring to.</strong></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Support More Harbor Shorts. Become a paid subscriber and help us keep writing them. Thank you for your support.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Step numbers also allow you to connect your process map to:</p><ul><li><p>detailed requirements and business rules,</p></li><li><p>user stories and development tasks,</p></li><li><p>meeting notes and decisions,</p></li><li><p>test cases,</p></li><li><p>supporting documentation,</p></li><li><p>and future change requests.</p></li></ul><p>You can use simple numbers such as <strong>1, 2, 3</strong>, or identifiers such as <strong>S01, S02, S03</strong>. For processes with multiple branches, you can use identifiers such as <strong>S04A</strong> and <strong>S04B</strong>. The format is less important than consistency.</p><p>So, next time before sending your process map to team, ask yourself one simple question:</p><p><strong>Can everyone refer to any step without pointing at the screen?</strong></p><p>A process map is not only something people look at. It is something the team must be able to discuss, document, test, and maintain.</p>]]></content:encoded></item><item><title><![CDATA[Harbor Short #001: Estimated vs. Actual: Why Your System Must Keep Both]]></title><description><![CDATA[A simple lesson in understanding what was expected, what actually happened, and why the difference matters.]]></description><link>https://www.analystharbor.online/p/harbor-short-001-estimated-vs-actual</link><guid isPermaLink="false">https://www.analystharbor.online/p/harbor-short-001-estimated-vs-actual</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Tue, 08 Sep 2026 10:45:38 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!kRH5!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><span>A few weeks ago, I finished a project that was demanding for the entire team. During the project, I assigned what I thought was a simple task to a junior business analyst: working with estimated and actual values.</span></p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!kRH5!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!kRH5!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!kRH5!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!kRH5!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!kRH5!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!kRH5!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png" width="1456" height="819" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:819,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1984173,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/213897332?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!kRH5!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!kRH5!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!kRH5!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!kRH5!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F82055dbd-80a4-4387-b49d-73601a5a99be_1672x941.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><span>I assumed the difference was obvious. It wasn&#8217;t&#8212;and I spent far longer explaining it than I expected.</span></p><p><span>It reminded me that concepts that appear obvious after years of experience may not be obvious when you are just starting out. More importantly, if this distinction is misunderstood, it can have a serious impact on the system and the business.</span></p><p><span>So, this is my first short note for Analyst Harbor.</span></p><p><span>The main message is simple: </span><strong><span>never treat an estimated value as an actual value. Never overwrite one with the other. You usually need both.</span></strong></p><h2><span>A simple example</span></h2><p><span>Imagine you are waiting for your partner and children at Prague Airport.</span></p><p><span>Their estimated time of arrival is 1:00 p.m. However, the flight is delayed, and they finally arrive at 7:00 p.m. The actual time of arrival is therefore 7:00 p.m.</span></p><p><strong>What is the difference between these two values?</strong></p><p><span>Six hours of waiting&#8212;and possibly six additional hours of airport parking  :D</span></p><p><span>If the system replaces the estimated arrival time with the actual arrival time, you will know when the flight arrived, but you will lose the original expectation. </span><strong><span>Without both values, you cannot calculate the delay, explain the additional cost, or assess how accurate the estimate was.</span></strong></p><p><span>The same principle applies to costs, quantities, revenue, working hours, delivery dates, and many other types of business data.</span></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Analyst Harbor is a reader-supported publication. To receive new posts and support our work, consider becoming a paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2><span>Questions a business analyst should ask</span></h2><p><span>When working with estimated and actual values, always ask these questions:</span></p><ol><li><p><span>What exactly does the estimated value represent?</span></p></li><li><p><span>When is the estimate created, and who creates or approves it?</span></p></li><li><p><span>Can the estimate be updated?</span></p></li><li><p><span>If it changes, should the original estimate or its previous versions be preserved?</span></p></li><li><p><span>When does the actual value become available?</span></p></li><li><p><span>Where does the actual value come from?</span></p></li><li><p><span>Can the actual value be corrected later&#8212;for example, after receiving a corrected invoice?</span></p></li><li><p><span>What should the system display before the actual value is available?</span></p></li><li><p><span>How should users distinguish between the estimated and actual values?</span></p></li><li><p><span>Which value should be used in each report? in calculation?  business decision?</span></p></li><li><p><span>Does the business need to see or calculate the difference between the estimate and the actual value?</span></p></li></ol><h2><span>The key lesson</span></h2><p><span>Estimated and actual values are not two versions of the same number. They answer two different questions:</span></p><ul><li><p><strong><span>Estimated value:</span></strong><span> What do we currently expect?</span></p></li><li><p><strong><span>Actual value:</span></strong><span> What really happened?</span></p></li></ul><p><span>A good business analyst does not ask only what data must be stored. They also ask what the data represents, when it becomes valid, where it comes from, whether it can change, and how it will be used.</span></p>]]></content:encoded></item><item><title><![CDATA[Harbor Shorts: A New Concept Arrives at Analyst Harbor]]></title><description><![CDATA[Harbor Shorts will give you practical knowledge, useful insights, and lessons you can apply in your everyday work.]]></description><link>https://www.analystharbor.online/p/harbor-shorts-a-new-concept-arrives</link><guid isPermaLink="false">https://www.analystharbor.online/p/harbor-shorts-a-new-concept-arrives</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Mon, 07 Sep 2026 10:55:33 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!tFkR!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Over the past few years, we have published many in-depth articles packed with knowledge. However, explaining a specific business analysis topic often requires several pages and to be honest, junior analysts can easily get lost in so much information.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!tFkR!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!tFkR!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!tFkR!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!tFkR!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!tFkR!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!tFkR!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png" width="1456" height="971" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/aed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:971,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1310853,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/213978606?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!tFkR!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!tFkR!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!tFkR!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!tFkR!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faed8bd1c-3de6-4d8f-819e-e6da18a8fca0_1536x1024.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>We felt we needed a different approach. </p><p>One that would help junior analysts understand important concepts and patterns more easily. That is why we created a new format called <strong>Harbor Shorts</strong>.</p><p>Harbor Shorts are crafted as one-page articles. Each article gets straight to the point and focuses on one specific topic.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.analystharbor.online/subscribe?"><span>Subscribe now</span></a></p><p>The ideas behind these articles come from our own experience as business analysts, as well as from our work with junior colleagues whom we regularly coach and whose work we review.</p><p>We hope Harbor Shorts will give you lessons you can apply in your everyday work.</p><p>Stay tuned! </p><p>The first Harbor Short arrives tomorrow :)</p>]]></content:encoded></item><item><title><![CDATA[Business Analysis Certifications That Actually Pay Off]]></title><description><![CDATA[How to choose the right business analysis certification and turn it into real career growth]]></description><link>https://www.analystharbor.online/p/business-analysis-certifications</link><guid isPermaLink="false">https://www.analystharbor.online/p/business-analysis-certifications</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Wed, 20 May 2026 10:45:39 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!NBGk!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!NBGk!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!NBGk!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!NBGk!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!NBGk!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!NBGk!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!NBGk!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png" width="1456" height="971" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:971,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:2236010,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/195067015?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!NBGk!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!NBGk!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!NBGk!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!NBGk!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F47dcc963-8d57-4bf9-a9a0-ab7bc45d6105_1536x1024.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Business analysis certifications can be valuable, but only when they are tied to the role you want next.</p><p>A certification can strengthen credibility, improve job prospects, build confidence, and support stronger earning potential. For experienced analysts, credentials such as CBAP can be especially useful because they help signal senior-level capability.</p><p>But the real value does not come from passing an exam. It comes from choosing the right certification for your level, using the preparation process to improve how you work, and continuing to build on it after the exam.</p><h1>Why certifications matter</h1><p>A good BA certification can help in three ways.</p><p><strong>First,</strong> it gives employers and stakeholders a clearer signal of your capability.</p><p><strong>Second,</strong> it helps you speak about your work more confidently and more professionally.</p><p><strong>Third,</strong> it can improve your market position. Certified professionals often report better career satisfaction, stronger visibility in hiring, and better compensation than non-certified peers in similar roles.</p><h2>The biggest mistake people make</h2><p>The most common mistake is treating certification as the finish line.</p><p>Passing the exam is useful, but the badge alone will not transform your career. The value becomes much higher when certification helps you do better stakeholder work, define requirements more clearly, support decisions better, and position yourself for the next role.</p><div class="preformatted-block" data-component-name="PreformattedTextBlockToDOM"><label class="hide-text" contenteditable="false">Text within this block will maintain its original spacing when published</label><pre class="text">A better mindset is this: <em><strong>certification is not decoration. It is leverage.</strong></em></pre></div><h2>Start with the role you want next</h2><p>Before choosing any certification, ask yourself one practical question.</p><p><strong>What role am I trying to move into next?</strong></p><p>That matters more than choosing the most impressive-sounding credential.</p><p>If you are early in your career, an entry-level certification may give you better return than jumping straight to a senior-level option.</p><p>If you already have substantial BA experience, a senior certification such as CBAP may be the better choice because it helps prove maturity, depth, and readiness for advancement.</p><h1>Common business analysis certifications</h1><p>Here are the certifications most people come across when planning a BA career.</p><h5>ECBA</h5><p>A strong entry-level certification for beginners, junior analysts, and career changers. It is best when you want structure, foundational knowledge, and a first recognized credential.</p><h5>CCBA</h5><p>A good mid-level option for analysts who already have hands-on experience and want to show they can apply BA practices consistently.</p><h5>CBAP</h5><p>The best-known senior-level BA certification. It is designed for experienced professionals and is often the strongest option when you want to signal senior capability, improve credibility, and support career progression.</p><h5>PMI-PBA</h5><p>A useful option if your work sits close to project management, delivery governance, or PMO-style environments. It can be a good fit for analysts working in project-heavy organizations.</p><h5>AAC</h5><p>A certification for analysts working in agile environments. It is useful if your work is strongly connected to agile delivery, product collaboration, and iterative requirement work.</p><h5>CBDA</h5><p>A good choice if your BA role is becoming more data-driven. It suits analysts who work with analytics, decision support, and business data interpretation.</p><h5>BCS Foundation in Business Analysis</h5><p>A well-known option in the UK and Europe, especially for people who want a structured introduction to business analysis.</p><h5>CPRE</h5><p>A strong certification path for people whose work is heavily focused on requirements engineering rather than broader business analysis.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!XSi_!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!XSi_!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png 424w, https://substackcdn.com/image/fetch/$s_!XSi_!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png 848w, https://substackcdn.com/image/fetch/$s_!XSi_!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!XSi_!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!XSi_!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png" width="1024" height="1536" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1536,&quot;width&quot;:1024,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1318024,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/195067015?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!XSi_!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png 424w, https://substackcdn.com/image/fetch/$s_!XSi_!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png 848w, https://substackcdn.com/image/fetch/$s_!XSi_!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!XSi_!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb37f6b55-7901-4399-ac12-714929dac1bd_1024x1536.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><h1>Which certification should you pick</h1><p>A simple rule helps here.</p><p>Choose the certification that matches both your current level and your next realistic move.</p><h4>Pick ECBA or a similar foundation-level certification if:</h4><ul><li><p>You are new to business analysis.</p></li><li><p>You are moving into BA from another role.</p></li><li><p>You want a recognized credential that helps you learn the basics and talk about your work with more confidence.</p></li></ul><h4>Pick CCBA or a similar mid-level certification if:</h4><ul><li><p>You already have real BA experience.</p></li><li><p>You want to prove consistency and strengthen your profile for broader responsibility.</p></li><li><p>You are aiming for stronger BA roles but are not yet at the senior-most level.</p></li></ul><h4>Pick CBAP if:</h4><ul><li><p>You already have substantial business analysis experience.</p></li><li><p>You want to demonstrate senior-level capability.</p></li><li><p>You are aiming for lead BA, principal BA, consulting, or more strategic roles.</p></li><li><p>You want a credential that improves credibility in promotion or hiring conversations.</p></li></ul><h4>When CBAP makes the most sense</h4><p>CBAP is most valuable when you already have enough experience to make the certification believable and useful.</p><p>At that stage, it can help validate your track record, strengthen your professional reputation, and position you for more senior opportunities. It is especially useful when you want your experience to be understood in a clear, market-recognized way.</p><p>For experienced analysts, that is where CBAP often delivers the strongest return.</p><h1>How to get the most value from certification</h1><p>The best return comes from doing three things well.</p><h3>1. Study to improve your real work</h3><p>Do not prepare only to pass the exam. Use the learning to sharpen stakeholder analysis, requirement quality, facilitation, and decision support.</p><h3>2. Apply the ideas on the job</h3><p>This is where certification becomes real.</p><p>For example, if you are studying BABOK-aligned practices, use them in real stakeholder work. Build a better stakeholder map. Improve your workshop structure. Write clearer scenarios and acceptance criteria. Support business cases more clearly.</p><h3>3. Keep building after the exam</h3><p>A certification is more valuable when it stays active and becomes part of your long-term professional development.</p><p>That might mean continuing your learning, mentoring others, improving your BA toolkit, or using the credential to reposition yourself for the next role.</p><h2>A practical decision guide</h2><p>Use this quick filter.</p><p>Choose certification if it matches your experience, supports your next step, and helps you improve real work.</p><p>Delay it if you are picking it only because it sounds impressive or because you expect the badge alone to change your career.</p><h2>Final thought</h2><p>Business analysis certifications are worth most when they are treated as an investment, not a trophy.</p><p>If you are early in your career, choose a certification that helps you build foundations.</p><p>If you already have substantial experience, CBAP can be a strong option for proving senior capability and supporting advancement.</p><p>In both cases, the pattern is the same.</p><p>Pick the certification that fits your level.</p>]]></content:encoded></item><item><title><![CDATA[The Modern BA: Skills That Matter Now]]></title><description><![CDATA[The most valuable analysts in 2026 will be the ones who can connect stakeholders, data, and decisions.]]></description><link>https://www.analystharbor.online/p/the-modern-ba-skills-that-matter</link><guid isPermaLink="false">https://www.analystharbor.online/p/the-modern-ba-skills-that-matter</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Fri, 15 May 2026 18:08:52 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/195267261/d3fd6eb829a98bda3358f014d28fa467.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Being a strong BA in 2026 is no longer just about gathering requirements. </p><p>This episode breaks down how the role is shifting toward decision support, sharper communication, data fluency, and responsible use of AI.</p>]]></content:encoded></item><item><title><![CDATA[The BA Skills Map for 2026: From Requirements Gathering to Strategic Influence]]></title><description><![CDATA[The real skills business analysts need in 2026, from stakeholder leadership to AI literacy]]></description><link>https://www.analystharbor.online/p/the-ba-skills-map-for-2026-from-requirements</link><guid isPermaLink="false">https://www.analystharbor.online/p/the-ba-skills-map-for-2026-from-requirements</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Wed, 13 May 2026 10:46:02 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!ReLe!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!ReLe!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!ReLe!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!ReLe!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!ReLe!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!ReLe!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!ReLe!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png" width="1456" height="971" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:971,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:2171492,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/188805378?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!ReLe!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!ReLe!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!ReLe!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!ReLe!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36e6dc86-60db-43bc-aaf0-52ede48de264_1536x1024.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Open any business analyst job posting today and you will find the same list.</p><div class="pullquote"><p>Requirements gathering. Stakeholder management. Agile. SQL. Power BI. Communication skills. Ability to work in a fast-paced environment.</p></div><p>In 2026, business analysis is moving beyond documentation and requirement capture. The role is becoming more strategic, more judgment-based, and more closely tied to decision quality. </p><p>AI is changing how work gets done. Data is no longer optional. And the analysts who stand out are the ones who can connect business goals, stakeholder needs, and operational reality with far more precision than before.</p><p>The gap between what job descriptions say and what strong BA work actually requires is now too large to ignore.</p><h1>Why the role is changing</h1><p>The biggest shift is simple: analysts are spending less time producing raw material and more time interpreting it.</p><p>AI tools can already support note-taking, summarisation, draft requirements, and first-pass analysis. That does not make the BA obsolete. It makes weak analysis easier to automate and strong analysis more valuable.</p><p>As repetitive tasks become easier to delegate, the analyst&#8217;s value moves upward. The real work becomes deciding what matters, identifying what is missing, spotting risk early, and helping teams make better decisions with incomplete information.</p><p>That changes the profile of a strong BA.</p><p>It is no longer enough to collect requirements and document them neatly. Analysts are increasingly expected to facilitate decisions, translate data into business meaning, and challenge unclear thinking before it becomes expensive.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Enjoying Analyst Harbor? Subscribe for practical BA articles on strategy, AI, and delivery</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>Lucia&#8217;s view:</strong> the most important shift is not technical. It is the rising value of judgment. Good analysts do not just record what stakeholders say. They test it, clarify it, and identify what is still unresolved. In practice, that means knowing when a requirement is incomplete, when a risk is being ignored, and when a team is moving forward on assumptions instead of evidence.</p><p><strong>Milos&#8217;s view:</strong> the role is also becoming more structurally demanding. In technical and regulated environments, the BA now operates closer to contracts, rules, data structures, and control logic than many organisations realise. The analyst who is only comfortable with workshops and user stories will increasingly struggle if they cannot also read specifications, understand system impacts, and ask sharper questions about how a decision is actually made.</p><h3>3 forces driving the change</h3><p><strong>AI is entering the requirement space.</strong> Systems that make decisions algorithmically &#8212; credit scoring models, fraud detection engines, clinical decision support tools &#8212; now need requirements just like any other system. But writing requirements for a model is not the same as writing requirements for a rule. The inputs, the failure modes, and the audit obligations are different. Most BA methodologies have not caught up.</p><p><strong>Regulation is becoming a technical discipline.</strong> DORA, NIS2, PSD3, AI Act, GDPR enforcement. Regulatory change used to mean updating a policy document. Now it means tracing the impact across APIs, data models, audit logs, and operational processes &#8212; and documenting that trace in a way that satisfies both a project manager and a regulator. This is BA work, and it requires a different kind of fluency than it did five years ago.</p><p><strong>The line between BA and data is dissolving.</strong> Not because BAs are becoming data scientists, but because the questions stakeholders are asking now &#8212; &#8220;why did this model decline that customer?&#8221;, &#8220;what does our data actually say about this process?&#8221; &#8212; cannot be answered without someone who can move between business language and data structure. That person is increasingly the BA.</p><h1>The Skills That Actually Matter in 2026</h1><p>The strongest BA skill set in 2026 is not a random collection of tools. It is a layered capability.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!kQ1u!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!kQ1u!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png 424w, https://substackcdn.com/image/fetch/$s_!kQ1u!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png 848w, https://substackcdn.com/image/fetch/$s_!kQ1u!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png 1272w, https://substackcdn.com/image/fetch/$s_!kQ1u!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!kQ1u!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png" width="818" height="760" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/ee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:760,&quot;width&quot;:818,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:801646,&quot;alt&quot;:&quot;&quot;,&quot;title&quot;:&quot;&quot;,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/188805378?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" title="" srcset="https://substackcdn.com/image/fetch/$s_!kQ1u!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png 424w, https://substackcdn.com/image/fetch/$s_!kQ1u!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png 848w, https://substackcdn.com/image/fetch/$s_!kQ1u!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png 1272w, https://substackcdn.com/image/fetch/$s_!kQ1u!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fee9b6d52-8dbf-4752-a4ee-bf9f1ec6ba17_818x760.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><p>Some skills remain foundational. Some are rising fast. And some have become key differentiators precisely because most people still underestimate them.</p><h3>The Foundation: Still Non-Negotiable</h3><p>Requirements elicitation, process modeling, stakeholder facilitation, and written communication remain the core of the role. These are not going away. If anything, they matter more &#8212; because the environments in which BAs operate have become more complex, and the cost of ambiguity has risen.</p><p>What has changed is the bar. &#8220;Can write a user story&#8221; is no longer sufficient. The expectation is that a BA can write requirements that are precise enough to be tested, traceable to a business rule, and resilient to a change request three sprints later. That is a higher standard than most job descriptions capture.</p><h3>The Genuinely New Skills</h3><p><strong>AI requirements literacy.</strong> This is the most underspecified skill in the market right now. Writing requirements for systems where an algorithm makes the decision requires understanding what the model needs as input, what it cannot be asked to guarantee, how failure should be defined and detected, and what the audit trail must capture. In regulated industries, this is not optional &#8212; it is the difference between a compliant system and a finding.</p><p>This does not mean BAs need to understand model architecture. It means they need to understand enough about how models behave to ask the right questions, define the right acceptance criteria, and push back when &#8220;the model decides&#8221; is offered as a substitute for a requirement.</p><p><strong>Regulatory translation.</strong> The ability to read a regulatory text &#8212; a directive, a technical standard, an EBA guideline &#8212; and identify its operational implications for a specific system or process. Not as a compliance officer would, but as an analyst would: which business rules change, which data fields are affected, which API behaviors need to be documented or modified, which tests need to be added.</p><p>This skill is rare. Most BAs either defer entirely to legal and compliance teams, or try to interpret regulation without sufficient context. The analysts who can sit in the middle &#8212; who can have a productive conversation with both the compliance officer and the developer &#8212; are consistently the ones who move projects forward when regulatory requirements land.</p><p>A honest note on scope: regulatory translation is a critical skill in banking, financial services, healthcare, energy, and any environment where external regulation directly shapes system behavior. If you work in e-commerce, SaaS, or internal IT projects without significant compliance exposure, this is useful context but not a daily priority. The distinction matters &#8212; a skills map that tells everyone they need everything is not a skills map, it is a wish list.</p><p><strong>Contract thinking.</strong> The ability to specify behavior &#8212; not just describe it. This applies to API contracts, data exchange agreements, and system integration points. A requirement that says &#8220;the system should return customer data&#8221; is not a contract. A requirement that defines the schema, the error codes, the latency expectations, the retry behavior, and the data sensitivity classification &#8212; that is a contract. The shift from description to specification is one of the most important transitions a BA can make.</p><h3>The Underrated Differentiators</h3><p><strong>Domain depth.</strong> Generic BA skills travel. Domain knowledge is where leverage concentrates. A BA who understands how a payment settlement works, or how a clinical trial is structured, or how an energy trading desk operates &#8212; that person can ask better questions, spot missing requirements earlier, and challenge technical decisions that look correct on paper but are wrong in context.</p><p>Domain knowledge cannot be acquired from a course. It accumulates from time spent in an industry, asking questions, and building mental models of how things actually work. It is slow to develop and difficult to replicate. That makes it one of the most durable competitive advantages available to an analyst.</p><p><strong>Structured writing.</strong> Not &#8220;good communication skills&#8221; in the generic sense &#8212; but the ability to write a requirement, a business rule, or a specification in language that is unambiguous, complete, and testable. This is a craft. It requires practice, feedback, and deliberate attention to precision. It is also, based on the quality of requirements that actually circulate in most organisations, genuinely rare.</p><p><strong>Change detection.</strong> The ability to recognize when a scope change has occurred &#8212; even when no one has announced it &#8212; and surface it explicitly before it becomes a defect. This is partly analytical skill and partly organisational awareness. It is the difference between a BA who processes information and one who governs it.</p><h2>What This Looks Like in Practice</h2><p>Consider two business analysts working on the same type of project &#8212; implementing a new fraud detection system in a financial institution.</p><p>The first analyst gathers requirements from the fraud team, documents the happy path, writes user stories, and hands them to development. The system ships. Three months later, a compliance review identifies that the model&#8217;s decision logic cannot be reconstructed from the audit log. The fix requires a significant rework of the logging architecture.</p><p>The second analyst starts by asking a different set of questions. What does the regulator require in terms of explainability? What must the audit log capture for each decision? How should the model&#8217;s output be represented in requirements &#8212; as a rule, as a threshold, or as a probability band? What happens when the model is retrained &#8212; does the requirement change? The compliance review finds no gaps. The audit log was designed correctly from the start.</p><p>The difference is not technical skill. It is the frame through which requirements are approached.</p><h3>What to Prioritize First When Choosing a New Business Analyst</h3><p>For analysts building their 2026 skill stack, the smartest sequence is not to chase every trend at once.</p><p>A practical order looks like this:</p><ul><li><p>First, strengthen stakeholder communication and facilitation.</p></li><li><p>Then improve requirements analysis and solution thinking.</p></li><li><p>After that, build basic data literacy and SQL confidence.</p></li><li><p>Next, develop AI and automation awareness.</p></li><li><p>Then deepen domain knowledge in your target industry.</p></li><li><p>Finally, improve storytelling and executive reporting.</p></li></ul><p>That order matters because influence comes before tools.</p><h1>Final thouths &amp; the honest summary</h1><p><strong>Lucia&#8217;s closing view:</strong> the skills that will define the next generation of senior BAs are not technical &#8212; they are judgement-based. Knowing when a requirement is complete. Knowing when a stakeholder&#8217;s stated need differs from their actual need. Knowing when a project is heading toward rework and intervening early. These are not certifiable skills, but they are learnable &#8212; and they are what separates analysts who are managed from analysts who lead.</p><p><strong>Milos&#8217;s closing view:</strong> in regulated and technical environments, the BA who cannot read a contract &#8212; whether that contract is an API specification, a regulatory text, or a data processing agreement &#8212; is operating with a significant blind spot. The work increasingly lives at the intersection of business intent and technical precision, and analysts who are comfortable only on one side of that line will find their scope narrowing as the role evolves.</p><p><strong>The skills </strong>that make a BA genuinely effective in 2026 <strong>are not dramatically different</strong> from what they have always been &#8212; clarity of thought, precision of language, understanding of context. <strong>What has changed is the environment</strong> in which those skills are applied.</p><p>AI, regulation, and technical integration have raised the complexity of the problems BAs are asked to solve. The analysts who will thrive are the ones who extend their foundational skills into these new domains &#8212; not by becoming experts in everything, but by developing enough fluency to ask the right questions and recognise when they are getting incomplete answers.</p><p></p>]]></content:encoded></item><item><title><![CDATA[Regulatory Change Never Waits]]></title><description><![CDATA[How junior business analysts can stay ahead of regulatory change without creating more chaos]]></description><link>https://www.analystharbor.online/p/regulatory-change-never-waits</link><guid isPermaLink="false">https://www.analystharbor.online/p/regulatory-change-never-waits</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Thu, 30 Apr 2026 10:45:49 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!BNGX!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In the last article, we looked at a simple six step framework for handling regulatory requirements without drowning in paperwork. The big idea was straightforward: good analysis in a regulated environment is not about writing more documents. It is about making change clearer, safer, and easier to deliver.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!BNGX!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!BNGX!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!BNGX!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!BNGX!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!BNGX!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!BNGX!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png" width="1456" height="971" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:971,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:2815405,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/194826735?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!BNGX!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!BNGX!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!BNGX!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!BNGX!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2c502d64-e7cc-4258-984d-56b2b78c177a_1536x1024.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Now it is time for the next part of the story.</p><p>Because even the best framework has one awkward little problem.</p><p>It works beautifully once you know which regulation or obligation you are dealing with. But in real life, that is rarely the hard part. The hard part is spotting what is coming early enough to do something sensible about it.</p><p>A lot of junior business analysts imagine regulation like a train timetable. One rule arrives, the team deals with it, everyone takes a breath, and then the next one shows up politely a few months later.</p><p>Real life is less polite.</p><p>Regulatory change behaves more like a crowded airport conveyor belt. One suitcase arrives, then three more, then one odd shaped bag no one recognizes, and then suddenly someone says, &#8220;By the way, that first suitcase also belongs to two other teams.&#8221;</p><p>That is why business analysts in banking and insurance need more than requirement writing skills. They also need a simple way to watch the regulatory pipeline, understand what matters, and prepare the team before the pressure starts.</p><p>In this article, we will look at what the never ending regulatory pipeline means for your work, how to track change without reading everything ever published, what new regulation means for requirements, and the four mistakes that create the most avoidable rework.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption"> We break down difficult topics into simple, useful ideas you can actually apply in your day to day work</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h1>The Regulatory Pipeline Is Never Empty</h1><p>The six step framework from the previous article assumes that you already know which obligations apply. In practice, that is rarely the case for long.</p><p>The regulatory landscape is never still. New rules arrive in waves. Existing rules get updated. Guidance appears later and changes how the original text should be understood. One new obligation can also create a ripple effect across systems, controls, and requirements that the team thought were already settled.</p><p>For a BA in banking or insurance, part of the job is knowing what is coming before it lands in the middle of your project plan.</p><p><strong>Right now in the European Union, two big changes are especially important.</strong></p><p>One is DORA, the Digital Operational Resilience Act. It has been in force since January 2025 and is changing how institutions deal with ICT risk, third party providers, vendor contracts, and incident reporting. If your project touches a cloud provider, an external platform, or any important third party system, DORA is probably already part of the picture.</p><p>The second is PSD3 together with the Payment Services Regulation, often called PSR. Political agreement was reached in November 2025, with formal publication expected in mid 2026 and a transposition period of around 18 to 24 months after that. For any BA working in payments, this is not distant future material. It is already something to watch closely. Fraud liability, open banking interfaces, and strong customer authentication are all areas where requirements will likely need to be updated before the deadline arrives.</p><p>The impact is practical, not theoretical.</p><p>A transaction threshold that looked fine under PSD2 may need to be reviewed under PSR.</p><p>A vendor contract that looked acceptable last year may need new clauses because of DORA.</p><p>The earlier a BA sees that coming, the easier and cheaper the change is to manage.</p><h1>How to track the regulatory pipeline without reading everything</h1><p>The good news is that you do not need to read every regulation from page one to page three hundred and fifty seven.</p><p>You just need a simple monitoring habit and a clear idea of where the early signals appear.</p><p><strong>For EU wide regulation, the main sources are usually the European Banking Authority, EIOPA for insurance, and ESMA for financial markets.</strong> These organizations often publish consultation papers, draft standards, and supporting materials long before the final compliance deadline arrives.</p><p>That matters because reading a consultation paper is not legal work. It is early requirement discovery.</p><p>It gives you a first look at what may change, which parts of the business might be affected, and where future delivery work is likely to appear.</p><p>For national implementation, the key source is your local regulator or supervisor. That might be the FCA in the UK, BaFin in Germany, or the CNB in the Czech Republic. National authorities often add practical guidance that sits on top of the EU text. And very often, that is where the operational detail becomes much clearer.</p><p>Assign one person to do a monthly regulatory scan for the three or four regulators most relevant to your domain.</p><p>The output does not need to be a giant report. A<strong> one page summary</strong> is enough.</p><p>That summary should answer three things:</p><ol><li><p>What is coming</p></li><li><p>When it is likely to matter</p></li><li><p>Which systems, controls, or requirements it could affect</p></li></ol><p>That summary can then go into the backlog as a flagged item. Not an active delivery item yet, but something visible and tracked until the regulation is final enough to act on properly.</p><p>This is one of those habits that looks small and saves a huge amount of confusion later.</p><h1>What a regulatory change means for your requirements</h1><p>When a new regulation appears, your first job is not to design the solution.</p><p>Your first job is to understand the impact.</p><ul><li><p>Which rules in your rule catalogue are affected</p></li><li><p>Which requirements refer to those rules</p></li><li><p>Which systems implement them</p></li><li><p>Which controls, reports, or manual activities also depend on them</p></li></ul><p>This is exactly why traceability matters so much.</p><p>In the previous article, <em><strong>Step 5 focused</strong></em> on connecting obligations, rules, requirements, tests, and evidence. That may feel like extra work when everything is calm. But the moment a new regulation appears, it starts paying for itself.</p><p>If your requirements are connected to rules, and those rules are connected to regulatory obligations, you can work out the impact of change in hours instead of weeks.</p><p>That is a big difference.</p><p>Take DORA as an example.</p><p>DORA requires financial entities to maintain a register of contractual arrangements with ICT third party providers.</p><p>For a BA, that is not just a legal sentence to admire from a distance.</p><p>It becomes a practical requirement question.</p><ul><li><p>Which system or process will capture vendor data</p></li><li><p>Who keeps that data current</p></li><li><p>What fields are mandatory</p></li><li><p>How do you prove the data is complete</p></li><li><p>How quickly can it be produced if a regulator asks for it</p></li></ul><p>That is the real job of analysis in a regulated environment. You take an obligation and turn it into something testable, buildable, and operationally useful before the deadline arrives.</p><h1>The Four Mistakes That Cause Most Avoidable Rework</h1><p>After working across regulated delivery programs, the same failure patterns show up again and again. They are not usually dramatic at the start. In fact, they often look like small shortcuts. But later, they create expensive rework.</p><h3>1. Treating compliance as a final gate instead of a design partner</h3><p>One of the most common mistakes is bringing compliance in too late.</p><p>If compliance reviews the requirements for the first time when the release is almost ready, they can still find problems, but by then the team has very little room left to fix them properly.</p><p>That is not a review. That is a rescue mission.</p><p><strong>Bring compliance in from the start</strong>, ideally when the objective and obligations are first being discussed. Early input is almost always cheaper and more useful than late correction.</p><h3>2. Writing requirements without capturing control intent</h3><p>A requirement that says, &#8220;the system shall process the transaction,&#8221; sounds complete until somebody asks, &#8220;And what control is supposed to happen around that?&#8221;</p><p>That is where <strong>weak requirements start to show</strong>.</p><p>A more useful requirement explains not only the action, but also the control behaviour that matters.</p><p>For example, a transaction might need an audit event when an amount crosses a threshold. Or it might require manual review when screening is incomplete. Without that control intent, the requirement may describe activity, but not the risk handling behind it.</p><p>And in regulated work, that missing piece matters a lot.</p><h3>3. Shipping changes without evidence mapping</h3><p>Teams often know what changed. That part is usually visible.</p><p>What is less visible is whether the team knows what was tested, what evidence was produced, and where that evidence lives.</p><p>That gap becomes painful very quickly during audits, reviews, or post incident investigations.</p><p><strong>It is not enough to say the control was tested</strong>. You need to know how, where, and with what result.</p><p>Evidence mapping may sound dull, but it is one of the quiet things that makes regulated delivery much more manageable.</p><h3>4. Updating the implementation but not the requirement version</h3><p>This one causes more trouble than many teams expect.</p><p>A developer fixes behaviour during the sprint. The code is updated. The team is happy. Everyone moves on.</p><p>But the <strong>requirement never gets updated</strong>.</p><p>Now the implementation says one thing and the requirement says another. The traceability chain breaks, and from that point on, confusion spreads very easily.</p><p>Auditors do not follow the code first. They follow the chain of requirement, decision, approval, test, and evidence.</p><p>If one link is out of date, confidence drops fast.</p><h2>The Small Template That Prevents Big Problems, Impact Assessment Template</h2><p>For every medium or high impact change, capture the essentials before sign off.</p><p>Keep it compact. Keep it useful.</p><p>Your impact assessment should include:</p><ol><li><p>Change ID, owner, and target release</p></li><li><p>Impact class such as regulatory, customer, or operational</p></li><li><p>Affected rules, controls, requirements, and systems</p></li><li><p>Compliance decision owner and sign off requirement</p></li><li><p>Linked tests and evidence location</p></li><li><p>Go or no go decision with rollback trigger</p></li></ol><p>This does <strong>not need to become a massive template</strong>, it just needs to give the team enough structure to <strong>make good decisions</strong> and <strong>keep the audit </strong>trail intact.</p><h2>AI Can Support the Decision. It Should Not Own It</h2><p>AI tools are becoming more common in regulated delivery teams. They can help with drafting, analysis, summarising, and decision support. That makes them useful, but it also means they need to be treated carefully.</p><p>A simple principle helps here.</p><p>If AI output can influence a customer outcome, treat it like any other controlled requirement.</p><p>That means <strong>asking practical</strong> questions.</p><ul><li><p>What part of the output must be explainable to compliance or audit</p></li><li><p>What data is allowed to be used</p></li><li><p>What data is stored and for how long</p></li><li><p>When is human review mandatory</p></li><li><p>How are model changes versioned, approved, and rolled back</p></li></ul><p>A <strong>good example</strong> is a claims fraud model.</p><p>If the model returns a score of 0.85 or above, it may be sensible to route the case to manual review.</p><p>What it should not do is automatically reject a customer claim with no human involvement.</p><p>The model can inform the decision.</p><p>A person should still make the decision.</p><p>That is a useful rule of thumb for junior BAs. Whenever AI enters a regulated process, <strong>ask where human judgment must remain in the loop</strong> and how that control will be expressed in requirements.</p><h2>Final thoughts</h2><p>The regulatory pipeline is never empty. That is not a temporary problem. It is simply part of the environment.</p><p>For a business analyst, that means the job is not only about understanding today&#8217;s obligations. It is also about spotting tomorrow&#8217;s changes early enough to prepare the team properly.</p><p>You do not need to become a lawyer.</p><p>You do not need to read every document ever published.</p><p>But you do need a habit for monitoring what is coming, a simple way to assess impact, and enough structure to connect obligations to requirements before the pressure arrives.</p><p>That is where the real value sits.</p>]]></content:encoded></item><item><title><![CDATA[Six Practical Steps for Handling Legal and Regulatory Requirements Without the Bureaucracy ]]></title><description><![CDATA[A Junior BA Guide to Regulatory Change in Six Steps]]></description><link>https://www.analystharbor.online/p/six-practical-steps-for-handling</link><guid isPermaLink="false">https://www.analystharbor.online/p/six-practical-steps-for-handling</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Fri, 24 Apr 2026 10:53:45 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/194805562/64d4c03c7c24ee01aa27e6ebbdb7711c.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In this episode, we walk through a simple six step framework that helps business analysts handle regulatory requirements in a clear and practical way.</p><p>You will learn how to move from legal language to testable requirements without adding unnecessary bureaucracy.</p><p>Happy listening, and may your requirements stay clear and your stakeholders calm.</p>]]></content:encoded></item><item><title><![CDATA[Six Steps to Handle Regulatory Requirements Without Drowning in Paperwork]]></title><description><![CDATA[A simple framework for junior business analysts in banking and insurance]]></description><link>https://www.analystharbor.online/p/six-steps-to-handle-regulatory-requirements</link><guid isPermaLink="false">https://www.analystharbor.online/p/six-steps-to-handle-regulatory-requirements</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Thu, 23 Apr 2026 10:45:43 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!lvk0!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!lvk0!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!lvk0!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png 424w, https://substackcdn.com/image/fetch/$s_!lvk0!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png 848w, https://substackcdn.com/image/fetch/$s_!lvk0!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png 1272w, https://substackcdn.com/image/fetch/$s_!lvk0!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!lvk0!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png" width="1456" height="1336" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1336,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:4414427,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/188785663?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!lvk0!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png 424w, https://substackcdn.com/image/fetch/$s_!lvk0!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png 848w, https://substackcdn.com/image/fetch/$s_!lvk0!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png 1272w, https://substackcdn.com/image/fetch/$s_!lvk0!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10c25122-04ca-46a2-8e52-71398a4da0f0_2034x1866.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>One Monday morning, a junior analyst walked into a meeting feeling very proud. He had updated one tiny number in a rule. Just one. A harmless little threshold change.</p><p>By Tuesday, Compliance was asking questions, Operations had found three broken cases, QA looked like they had aged five years overnight, and someone from Risk said, &#8220;This is why I do not sleep well.&#8221;</p><p>The analyst stared at the screen and said, &#8220;But it was only one number.&#8221;</p><p>That is the funny thing about regulatory change. It never arrives alone. It comes with cousins, neighbours, and a suitcase full of consequences.</p><p>If you work as a business analyst in banking or insurance, this will feel familiar. Regulatory changes often look small at first. But if you handle them loosely, they become slow, messy, and expensive very quickly.</p><p>The good news is this: you do not need a mountain of documents to manage them well. You need a simple way to think, ask the right questions, and keep the team aligned.</p><p>Today, I want to share a practical six step framework to help you handle regulatory requirements with more confidence and a lot less bureaucracy.</p><h1><strong>What business analyst should do in regulatory change</strong></h1><p>When a regulatory change lands on your desk, your job is not just to write requirements. Your job is to make the change clear enough that nobody has to guess what it means.</p><p>In regulated industries, guessing is dangerous. A missing detail is not just a bug waiting to happen. It can become a customer issue, an audit problem, a release delay, or a costly fix after go live.</p><p>That is why the business analyst plays such an important role here. You should focus on three things.</p><ol><li><p><strong>Clarity</strong></p></li></ol><p>Take unclear policy language and turn it into something the team can actually use. Legal or compliance text is often broad and formal. Engineers, testers, and operations teams need something precise.</p><ol start="2"><li><p><strong>Traceability</strong></p></li></ol><p>You should be able to show how one thing connects to another. Why does this rule exist? Which requirement supports it? Which test proves it works? This matters a lot when questions come later.</p><ol start="3"><li><p><strong>Controlled change</strong></p></li></ol><p>A regulatory update can affect several teams at once. Product, Compliance, Risk, Engineering, QA, and Operations all need to see the same picture early.</p><p>In many product teams, unclear requirements create extra work. In regulated teams, unclear requirements create risk.</p><p>That is the big difference.</p><p>In a less regulated setting, the team may say, &#8220;We will fix it next sprint.&#8221; In banking or insurance, the same problem can trigger an incident, an audit finding trust me, you really do not want to do that).</p><p>So what should a junior BA remember?</p><ol><li><p><strong>What is changing</strong></p></li><li><p><strong>Why it is changing</strong></p></li><li><p><strong>What rule or obligation sits behind it</strong></p></li><li><p><strong>What could go wrong if it is misunderstood</strong></p></li><li><p><strong>How the team will prove the change works</strong></p></li></ol><p>That is where good BA work becomes visible. Not in the number of pages written, but in the number of surprises avoided.</p><h1><strong>What stakeholder expect in regulators changes</strong></h1><p>Stakeholders usually do not ask for &#8220;better requirements.&#8221; They ask for outcomes and usually want to know this:</p><ol><li><p>Are we reducing risk or just moving it somewhere else</p></li><li><p>Can we deliver this change without chaos before release</p></li><li><p>Can we explain our decisions if an audit happens</p></li><li><p>Do people understand the trade offs before they become problems</p></li></ol><p>That means your work as a BA should help answer those questions.</p><p>A stakeholder does not care that your document is beautifully formatted if the team still does not know what to build.</p><p>What they do care about is whether the change is clear, testable, and connected to the real obligation behind it.</p><p>Even simple tracking can make BA quality more visible. For example, a team can look at:</p><ol><li><p>How many incidents came from unclear requirements</p></li><li><p>How many important changes went ahead without full traceability</p></li><li><p>How many audit issues were linked to missing controls or vague requirements</p></li><li><p>How long it took to move a change from request to release readiness</p></li></ol><p>These are much more useful than counting pages, meetings, or templates.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">If this kind of practical BA advice is useful for you, subscribe to Analyst Harbor for more simple frameworks, real examples, and lessons that help junior analysts grow faster.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h1><strong>6 steps framework</strong></h1><p>The six steps below are designed to keep things lean. They give you structure, but they do not bury the team in paperwork.</p><div class="paywall-jump" data-component-name="PaywallToDOM"></div><h2><strong>Step 1: Define the objective and the obligations</strong></h2><p>Start with one clear objective.</p><p>What exactly is the change trying to achieve?</p><p>Then identify the obligations connected to it. These might come from regulation, internal policy, compliance guidance, or risk controls.</p><p>Do this before people jump into solution mode. If the team starts designing too early, they may build something clever that solves the wrong problem.</p><p>Output: a short BRD style note with scope, constraints, assumptions, and owners.</p><h2><strong>Step 2: Convert policy into explicit, testable rules</strong></h2><p>Policy language is rarely written in a way that delivery teams can use directly.</p><p>Your job is to translate it into plain, testable rules.</p><p>For example:</p><p>If a transfer is above 10,000 EUR, enhanced due diligence must be completed before processing.</p><p>That is much easier for a team to work with than a paragraph full of policy wording.</p><p>When you write rules, keep them specific. One rule should describe one clear expectation.</p><p>Output: a numbered rule list that can be reviewed and tested.</p><h2><strong>Step 3: Model controls and exception paths before build begins</strong></h2><p>Teams naturally focus on the main path. But regulated processes often fail in the messy parts.</p><p>Think about cases like:</p><ol><li><p>Invalid input</p></li><li><p>Missing data</p></li><li><p>Duplicate requests</p></li><li><p>Sanctions match</p></li><li><p>Timeout from an external service</p></li><li><p>Manual review needed</p></li></ol><p>These are the moments where control gaps appear.</p><p>A junior BA can add huge value by asking, &#8220;What happens if this goes wrong?&#8221; before development starts.</p><p>Output: a process map that shows the main flow and the exception paths.</p><h2><strong>Step 4: Write functional requirements in condition and outcome format</strong></h2><p>A requirement should help the team understand when something happens and what the system must do.</p><p>That makes it easier for engineers to implement and easier for QA to test.</p><p>For example:</p><p>If screening stays pending for more than 30 seconds, the system returns REVIEW PENDING and creates an audit event.</p><p>This style removes guesswork. It gives the team a condition and an expected result.</p><p>When writing requirements, ask yourself:</p><ol><li><p>Is this specific enough to build</p></li><li><p>Is this specific enough to test</p></li><li><p>Would two different people read it and understand the same thing</p></li></ol><p>If the answer is no, rewrite it.</p><p>Output: a requirement set with clear pass or fail logic.</p><h2><strong>Step 5: Build traceability before coding starts</strong></h2><p>Traceability sounds scary at first, but it is really just a chain of logic.</p><p>You want to connect:</p><ul><li><p>Objective</p></li><li><p>Rule</p></li><li><p>Requirement</p></li><li><p>Test</p></li><li><p>Evidence</p></li></ul><p>This makes life easier later. If someone asks why a requirement exists, you can show it. If an auditor asks how the rule was tested, you can show that too.</p><p>Traceability also helps with impact analysis. If one rule changes, you can quickly see which requirements and tests are affected.</p><p>Output: a simple traceability matrix.</p><h2><strong>Step 6: Govern change continuously</strong></h2><p>Not every change needs the same level of control.</p><p>Some changes are low impact. Some are high risk and need closer review.</p><p>That is why it helps to classify change requests. A simple low, medium, high approach is often enough.</p><p>For higher impact changes, make sure the team agrees on:</p><ol><li><p>Who must review and sign off</p></li><li><p>What evidence is needed before release</p></li><li><p>What rollback condition exists if something goes wrong</p></li></ol><p>This keeps governance practical. It is not about slowing people down. It is about making sure the right eyes are on the right changes.</p><p>Output: a change log that stays with the release and records decisions clearly.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!ooYo!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10f253c2-07a7-4732-9920-89b21340f33f_2752x1507.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!ooYo!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10f253c2-07a7-4732-9920-89b21340f33f_2752x1507.png 424w, https://substackcdn.com/image/fetch/$s_!ooYo!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10f253c2-07a7-4732-9920-89b21340f33f_2752x1507.png 848w, https://substackcdn.com/image/fetch/$s_!ooYo!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10f253c2-07a7-4732-9920-89b21340f33f_2752x1507.png 1272w, https://substackcdn.com/image/fetch/$s_!ooYo!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10f253c2-07a7-4732-9920-89b21340f33f_2752x1507.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!ooYo!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10f253c2-07a7-4732-9920-89b21340f33f_2752x1507.png" width="2752" height="1507" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/10f253c2-07a7-4732-9920-89b21340f33f_2752x1507.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1507,&quot;width&quot;:2752,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:5788832,&quot;alt&quot;:&quot;A 6-step framework for regulatory requirements&quot;,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/188785663?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F083a9c81-773b-4c13-8355-7ea3c96cd8cb_2752x1536.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="A 6-step framework for regulatory requirements" title="A 6-step framework for regulatory requirements" srcset="https://substackcdn.com/image/fetch/$s_!ooYo!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10f253c2-07a7-4732-9920-89b21340f33f_2752x1507.png 424w, https://substackcdn.com/image/fetch/$s_!ooYo!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10f253c2-07a7-4732-9920-89b21340f33f_2752x1507.png 848w, https://substackcdn.com/image/fetch/$s_!ooYo!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10f253c2-07a7-4732-9920-89b21340f33f_2752x1507.png 1272w, https://substackcdn.com/image/fetch/$s_!ooYo!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10f253c2-07a7-4732-9920-89b21340f33f_2752x1507.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><h1><strong>Final thoughts</strong></h1><p>In banking and insurance, requirement work is not about producing paperwork for its own sake. It is about helping teams deliver safely, clearly, and with fewer nasty surprises.</p><p>In the next article, we will go deeper into the mistakes that often make regulatory change harder than it needs to be. We will also share a compact template created especially for legal and regulatory requirements, to help you stay clear, structured, and practical. Stay tuned! </p>]]></content:encoded></item><item><title><![CDATA[Why Business Analyst Training Fails — And the Framework That Fixes It]]></title><description><![CDATA[Analyst Harbor Onboarding Framework]]></description><link>https://www.analystharbor.online/p/why-business-analyst-training-fails</link><guid isPermaLink="false">https://www.analystharbor.online/p/why-business-analyst-training-fails</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Thu, 12 Mar 2026 11:31:57 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/190703183/c0d299e73ebc2af1c986429872a79ee9.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Most companies teach analysts step by step, beginning with tools, then assigning tasks, and eventually giving them projects.</p><p>At <strong>Analyst Harbor</strong>, we do the opposite.</p><p>In this episode, we introduce the <strong>Analyst Harbor Onboarding Framework</strong> &#8212; a new way to train analysts by focusing on <strong>how they think, not just what they do</strong>.</p><p>You&#8217;ll learn why great analysts:</p><ul><li><p>prioritize <strong>human cognition over tools</strong></p></li><li><p>rely on <strong>cheat sheets instead of theory</strong></p></li><li><p>solve problems using <strong>frameworks</strong></p></li><li><p>design <strong>architecture before analysis</strong></p></li><li><p>work quietly and <strong>deliver clear results</strong></p></li><li><p>treat <strong>documentation as the real product</strong></p></li></ul><p>Because in the age of AI, the best analysts aren&#8217;t the ones writing the most SQL or prompts.</p><p>They&#8217;re the ones who can <strong>structure problems clearly.</strong></p><p><strong>Enjoy the episode.</strong></p>]]></content:encoded></item><item><title><![CDATA[Deep Dive: Why AI Puts Bad Analysts on Steroids ]]></title><description><![CDATA[Why your BA skills matter more than ever! The 3 Major Mistakes Junior Analysts Make When Working With AI.]]></description><link>https://www.analystharbor.online/p/deep-dive-why-ai-puts-bad-analysts</link><guid isPermaLink="false">https://www.analystharbor.online/p/deep-dive-why-ai-puts-bad-analysts</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Thu, 05 Feb 2026 11:17:50 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/186757963/a3f64d416c02c58a2cdf20de39769434.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Every industry feels AI&#8217;s gravitational pull.<br>It won&#8217;t replace you &#8212; it will amplify you.<br>Great analysts get faster.<br>Weak inputs get dangerous &#8212; on steroids.<br>Stay on the right side of the equation.</p><p>This episode shows how to stay on the right side of that equation.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!HWrP!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb924701d-c528-4549-ae63-833263a97b06_2752x1536.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!HWrP!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb924701d-c528-4549-ae63-833263a97b06_2752x1536.png 424w, https://substackcdn.com/image/fetch/$s_!HWrP!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb924701d-c528-4549-ae63-833263a97b06_2752x1536.png 848w, https://substackcdn.com/image/fetch/$s_!HWrP!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb924701d-c528-4549-ae63-833263a97b06_2752x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!HWrP!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb924701d-c528-4549-ae63-833263a97b06_2752x1536.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!HWrP!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb924701d-c528-4549-ae63-833263a97b06_2752x1536.png" width="1456" height="813" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b924701d-c528-4549-ae63-833263a97b06_2752x1536.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:813,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:6620627,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/186757963?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb924701d-c528-4549-ae63-833263a97b06_2752x1536.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!HWrP!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb924701d-c528-4549-ae63-833263a97b06_2752x1536.png 424w, https://substackcdn.com/image/fetch/$s_!HWrP!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb924701d-c528-4549-ae63-833263a97b06_2752x1536.png 848w, https://substackcdn.com/image/fetch/$s_!HWrP!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb924701d-c528-4549-ae63-833263a97b06_2752x1536.png 1272w, https://substackcdn.com/image/fetch/$s_!HWrP!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb924701d-c528-4549-ae63-833263a97b06_2752x1536.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><p></p>]]></content:encoded></item><item><title><![CDATA[Why Business Analysts Leave: Insights from Our Community]]></title><description><![CDATA[What 300+ Business Analysts Told Me About Why They Really Leave]]></description><link>https://www.analystharbor.online/p/why-business-analysts-leave-insights</link><guid isPermaLink="false">https://www.analystharbor.online/p/why-business-analysts-leave-insights</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Mon, 02 Feb 2026 07:30:52 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!-4xV!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!-4xV!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!-4xV!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic 424w, https://substackcdn.com/image/fetch/$s_!-4xV!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic 848w, https://substackcdn.com/image/fetch/$s_!-4xV!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic 1272w, https://substackcdn.com/image/fetch/$s_!-4xV!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!-4xV!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic" width="1408" height="768" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:768,&quot;width&quot;:1408,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:351220,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/heic&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/174638592?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!-4xV!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic 424w, https://substackcdn.com/image/fetch/$s_!-4xV!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic 848w, https://substackcdn.com/image/fetch/$s_!-4xV!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic 1272w, https://substackcdn.com/image/fetch/$s_!-4xV!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1bc1a290-6a11-471b-b698-c4f7f4304ad4_1408x768.heic 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Recently, I had a profound conversation with a friend who, after five years, is considering leaving the company she&#8217;s been working for. This conversation struck a chord with me and inspired today&#8217;s article. </p><p>I want to explore why business analysts really leave&#8212;their projects, their bosses, their companies.</p><p>While my focus is on business analysts, these insights are relevant far beyond our profession and can be generalized to many other roles.</p><p>The depth of our discussion made me reflect on this question from multiple angles, and I realized that understanding why talented BAs walk away is crucial for organizations that want to retain their best people. </p><p>This led me to conduct research within our business analyst community to gather real experiences and perspectives.</p><p>Today, I&#8217;m sharing what I discovered.</p><h2>Question 1: Why Do Business Analysts Leave?</h2><p>The responses from our community revealed seven distinct patterns that drive business analysts to seek opportunities elsewhere. </p><p>Here&#8217;s what the data shows:</p><h3>1. Role Ambiguity / Reduction to Documentation Provider (68%)</h3><p>The most common complaint among departing BAs is being misunderstood. Many organizations view business analysts as &#8220;writers of specs&#8221; rather than active creators of business value. </p><p>The analyst becomes relegated to documentation duties, remaining outside critical decision-making processes even though their insights and deliverables are fundamental to project success. </p><p>When your role is reduced to &#8220;just document what we&#8217;ve already decided,&#8221; it&#8217;s no wonder talented analysts look elsewhere.</p><h3>2. Limited Influence on Decisions (62%)</h3><p>Even when analysts deliver well-researched recommendations backed by data and stakeholder insights, they often find themselves without the authority or platform to effectively influence what actually gets implemented. </p><p>They become executors rather than partners in the solution. </p><p>This disconnect between responsibility and influence creates frustration&#8212;you&#8217;re accountable for the analysis, but powerless to act on it.</p><h3>3. Pressure on Speed and Compromises in Quality (57%)</h3><p>Frequent requirement changes, unrealistic deadlines, and unclear expectations force analysts into an impossible position: sacrifice depth of analysis or cut corners on specification detail. </p><p>Neither option feels right. </p><p>This constant pressure to deliver &#8220;fast enough&#8221; rather than &#8220;good enough&#8221; erodes professional pride and creates a sense that quality simply doesn&#8217;t matter to the organization.</p><h3>4. Overload and Risk of Burnout (54%)</h3><p>Constant work under pressure.</p><p>Inability to disconnect and rest.</p><p>Taking on multiple roles simultaneously&#8212;analyst, project coordinator, tester, documentation specialist&#8212;all of this leads to exhaustion. </p><p>The result is inevitable.</p><p>Fatigue, loss of motivation, and ultimately, departure. </p><p>Burnout doesn&#8217;t happen overnight, but when it arrives, it&#8217;s often too late to recover the relationship with the employer.</p><h3>5. Lack of Recognition and Visibility (48%)</h3><p>When analysts don&#8217;t feel that leadership sees or values their work, they lose the sense that their effort matters. </p><p>Good analysis often prevents problems that never happen&#8212;which means the value is invisible. </p><p>Without visible feedback, appreciation, or acknowledgment, motivation gradually fades. People need to know their contributions make a difference.</p><h3>6. Career Stagnation and Limited Growth Opportunities (45%)</h3><p>They master their current role and then find themselves at a &#8220;dead end&#8221; with nowhere to grow. </p><p>When learning stops, engagement follows soon after.</p><h3>7. Weak Managerial Support (41%)</h3><p>A manager who doesn&#8217;t understand the BA domain, fails to negotiate removal of obstacles, or doesn&#8217;t provide meaningful feedback weakens both trust and psychological safety within the team. </p><p>When your manager can&#8217;t advocate for you, doesn&#8217;t protect your time, or can&#8217;t articulate the value you bring, you&#8217;re left to fight battles alone. </p><p>Eventually, that becomes exhausting.</p><h2>Question 2: What Do Business Analysts Expect from Themselves?</h2><p>Understanding why analysts leave is only half the story. </p><p>The other half lies in understanding what drives them. </p><p>When I asked our community about their personal expectations, a clear picture emerged of what motivates BAs to stay engaged and committed.</p><h3>1. Growth and Development (76%)</h3><p>Business analysts are lifelong learners by nature. </p><p>They expect continuous growth.</p><p>When they stop learning, they start looking for their next opportunity. </p><p>Growth isn&#8217;t a nice-to-have; it&#8217;s oxygen for a BA&#8217;s career.</p><h3>2. Meaning and Impact (71%)</h3><p>BAs don&#8217;t just want to produce deliverables.</p><p>They want those deliverables to matter. </p><p>Documents that sit unused on a shelf represent wasted potential. </p><p>Analysts want to see the thread from their work to tangible business results.</p><h3>3. Professionalism and Quality (69%)</h3><p>They expect to deliver work they can be proud of.</p><p>Being forced to cut corners or deliver &#8220;good enough for now&#8221; solutions due to external pressure conflicts with their internal sense of craftsmanship. </p><p>Quality matters.</p><h3>4. Autonomy and Responsibility (64%)</h3><p>They don&#8217;t want to be micromanaged.</p><p>Forced into rigid templates that don&#8217;t fit the situation. </p><p>With autonomy comes responsibility, and BAs are ready to own both.</p><h3>5. Respect and Recognition (58%)</h3><p>Analysts expect to be taken seriously as specialists with valuable expertise. </p><p>Respect isn&#8217;t about ego&#8212;it&#8217;s about being treated as a strategic partner rather than an administrative function.</p><h3>6. Work-Life Balance (52%)</h3><p>BAs expect reasonable boundaries that allow for regeneration and life outside work. </p><p>They&#8217;re willing to work hard and occasionally put in extra hours during critical periods. </p><p>Chronic overload isn&#8217;t sustainable. </p><p>Space to rest, reflect, and recharge isn&#8217;t a luxury&#8212;it&#8217;s necessary for sustained high performance.</p><h3>7. A Clear Career Path (47%)</h3><p>Analysts want to know where they can go next. </p><p>A visible path forward&#8212;even if it&#8217;s not perfectly linear&#8212;provides direction and motivation.</p><h2>Question 3: What Do Business Analysts Expect from Their Managers and Leadership?</h2><p>If self-expectations form the internal compass for BAs, then management expectations form the external environment that either enables or constrains their success. </p><p>When I asked what analysts need from their leaders, ten clear themes emerged&#8212;and together, they paint a picture of leadership that either retains talent or drives it away.</p><h3>1. Clarity of Goals and Expectations (82%)</h3><p>Analysts need to know the purpose of their tasks.</p><p>How success will be measured.</p><p>Vague directives like &#8220;just document the requirements&#8221; or &#8220;figure out what they need&#8221; without clear objectives create confusion and wasted effort. </p><p>Clear goals aren&#8217;t about control&#8212;they&#8217;re about alignment and focus.</p><h3>2. Constructive and Regular Feedback (78%)</h3><p>BAs want feedback that goes beyond pointing out mistakes. </p><p>They need direction for improvement.</p><p> Insight into blind spots.  </p><p>Regular feedback&#8212;not just annual reviews&#8212;helps analysts course-correct quickly and grow continuously. </p><p>Silence is often interpreted as indifference.</p><h3>3. Support for Growth and Mentoring (74%)</h3><p>Strong managers delegating challenging assignments.</p><p>When managers actively cultivate their team&#8217;s capabilities, they signal that growth matters. </p><p>When they don&#8217;t, talented people find mentors elsewhere&#8212;often at a new company.</p><h3>4. Trust and Freedom to Make Decisions (71%)</h3><p>Micromanagement kills motivation. </p><p>Analysts expect their managers to give them responsibility and trust them to execute. </p><p>This doesn&#8217;t mean abdication&#8212;it means delegating authority alongside accountability. </p><p>When managers constantly second-guess or override professional judgment, they communicate that the analyst&#8217;s expertise doesn&#8217;t matter.</p><h3>5. Removing Obstacles and Advocating for the Team (69%)</h3><p>When the team hits limits the manager&#8217;s job is to intervene at higher levels. </p><p>BAs can&#8217;t fight every battle themselves.</p><p>They need leaders.</p><p>They need shield from unnecessary organizational friction.</p><h3>6. Visibility for the Team with Stakeholders (66%)</h3><p>Managers should ensure that BA work is heard by business decision-makers and that credit flows to the right people. </p><p>When leaders take analyst insights into executive meetings and amplify their voices with stakeholders, they create opportunities and recognition. </p><p>When they don&#8217;t, good work dies in obscurity.</p><h3>7. Appreciation and Recognition (63%)</h3><p>Both public and private acknowledgment matter. </p><p>Celebrating wins.</p><p>Sharing successes across the organization</p><p>Or simply saying &#8220;thank you&#8221; for exceptional work fuel motivation. </p><p>Recognition doesn&#8217;t cost anything, yet its absence costs everything&#8212;particularly top talent who have options.</p><h3>8. Empathy and a Human Approach (61%)</h3><p>Great managers recognize the limits of their people. </p><p>They prevent burnout by monitoring workload.</p><p>Empathy isn&#8217;t soft management; it&#8217;s sustainable management.</p><h3>9. Psychological Safety (58%)</h3><p>Analysts need to work in an environment where they can raise uncertainties.</p><p>When teams lack psychological safety people keep their heads down. </p><p>Trust is built through how leaders respond when things go wrong.</p><h3>10. Connecting Work with Vision and Meaning (55%)</h3><p>BAs want to understand how their work connects to broader company goals and strategy. </p><p>When managers consistently link daily tasks to organizational vision, they provide context and purpose. </p><p>Without this connection, work feels meaningful&#8212;and meaning is what keeps talented people engaged long-term.</p><h2>&#8230; so, what This Means for You</h2><h3><strong>For Managers and Leaders:</strong> </h3><p>Retention isn&#8217;t a mystery. </p><p>Almost every factor that drives BAs away is within your control:</p><p>how you define their role, </p><p>whether they have real influence, </p><p>the quality standards you uphold under pressure, </p><p>how workload is managed, </p><p>and whether growth is possible. </p><p>Most of these changes don&#8217;t require massive budgets or restructuring; they require intentionality, consistency, and genuine respect for the BA profession.</p><h3><strong>For Business Analysts</strong></h3><p>If you&#8217;re considering your options, this research validates what you already feel. </p><p>Your expectations aren&#8217;t unreasonable. </p><p>Wanting to grow, make an impact, maintain quality, and be respected isn&#8217;t asking too much&#8212;it&#8217;s the minimum conditions needed to do excellent work. </p><p>If your current environment can&#8217;t provide these conditions, sometimes the best decision is to find an organization that values what you bring.</p><h2>Final Thoughts</h2><p>My friend&#8217;s conversation about leaving after five years wasn&#8217;t really about salary or a better title elsewhere. It was about the accumulated weight of unmet expectations&#8212;the feeling that her best work wasn&#8217;t valued. Her growth had stalled. The gap between what she could contribute and what she was allowed to contribute had grown too large.</p><p>She&#8217;s not alone. The data shows that thousands of talented business analysts face the same calculation every year.</p><p>Organizations that understand this will keep their best people. Those that don&#8217;t will keep wondering why their talented analysts keep walking out the door.</p><p>The choice is clear. </p><p>The path forward is clear. </p><p>The only question is whether leadership will take it seriously before it&#8217;s too late.</p><p><strong>What&#8217;s your experience? Have you left a BA role for reasons similar to what we&#8217;ve discussed here? Or if you&#8217;re a manager, what strategies have worked to keep your BA team engaged and growing? Share your thoughts in the comments below.</strong></p>]]></content:encoded></item><item><title><![CDATA[Top 3 AI Mistakes Junior Business Analysts Make (and How to Avoid Them)]]></title><description><![CDATA[Real project lessons on AI, requirements quality, impact analysis, and meeting documentation]]></description><link>https://www.analystharbor.online/p/top-3-ai-mistakes-junior-business</link><guid isPermaLink="false">https://www.analystharbor.online/p/top-3-ai-mistakes-junior-business</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Tue, 20 Jan 2026 11:44:28 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!ie73!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!ie73!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!ie73!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic 424w, https://substackcdn.com/image/fetch/$s_!ie73!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic 848w, https://substackcdn.com/image/fetch/$s_!ie73!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic 1272w, https://substackcdn.com/image/fetch/$s_!ie73!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!ie73!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic" width="1456" height="794" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/a8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:794,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1236194,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/heic&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/184572707?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!ie73!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic 424w, https://substackcdn.com/image/fetch/$s_!ie73!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic 848w, https://substackcdn.com/image/fetch/$s_!ie73!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic 1272w, https://substackcdn.com/image/fetch/$s_!ie73!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8cee7be-6c05-4f2c-a6fc-5e7c7d8b983d_2816x1536.heic 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>I genuinely love working with junior business analysts. </p><p>There is something refreshing about their curiosity, energy, and willingness to learn. </p><p>Recently, I had the pleasure of working closely with a group of junior analysts during a training program called &#8220;<a href="https://www.blok37.cz/lihen/">Lihen</a>&#8221;. Watching their progress reinforced an important truth: growth is not only about experience, but about <strong>how fast you learn and how well you adapt</strong>.</p><p>AI has become a powerful part of that journey. </p><p>Used correctly, it can accelerate learning and productivity. </p><p>Used incorrectly, it can slow you down &#8212; or even damage trust with developers and stakeholders.</p><p>Based on my recent experience, here are <strong>three common mistakes junior business analysts make when working with AI</strong>.</p><h2>1. Vague Requirements and Too Much Information</h2><p>Generating text with AI is one of the easiest things in the world. </p><p>But for a business analyst, this can quickly become dangerous.</p><p>During training, I noticed that many junior analysts rely heavily on AI-generated outputs and copy them almost verbatim into requirements. The result is long, repetitive descriptions that say the same thing in slightly different ways.</p><p>Developers then have to read through a wall of text just to understand a very simple requirement.</p><h3>Example</h3><p><strong>AI-generated requirement (problematic):</strong></p><blockquote><p>The system should allow the user to enter a value into a field which represents the customer reference. This reference is important for identifying the customer and should be visible to the user in the interface. The field should allow input and be displayed accordingly so that users can recognize the customer reference.</p></blockquote><p><strong>Improved BA requirement:</strong></p><blockquote><p>Add a mandatory &#8220;Customer Reference&#8221; text field to the user profile screen. </p><p>The field must be editable and visible to all users with role XXX.</p></blockquote><p><strong>Short. Clear. Actionable.</strong></p><p>During training, I always emphasized one rule: </p><h1><strong>AI output is a draft, not a final deliverable</strong>.</h1><p>After executing a prompt, you must review, simplify, and refine the text. If the result is too vague, too broad, or too verbose, either:</p><ul><li><p>run a more specific prompt, or</p></li><li><p>manually edit the output.</p></li></ul><p>The goal is simple: <strong>clear requirements, as short as possible</strong>.<br>Nobody wants to read a small novel just to implement a new field on one screen with no significant logic behind it.</p><h2>2. Not Understanding (or Not Documenting) the Context</h2><p>Another common mistake is not fully understanding &#8212; or not clearly documenting &#8212; the context of the problem.</p><p>A business analyst&#8217;s job is not just to write down what the business user says. Your role is to <strong>analyze, challenge, and anticipate impact</strong>.</p><p>Many junior analysts skip proper impact analysis. They focus only on the immediate request and forget to consider:</p><ul><li><p>reporting impacts,</p></li><li><p>legal or compliance constraints,</p></li><li><p>dependencies with other systems,</p></li><li><p>effects on other users or departments.</p></li></ul><h3>Example</h3><p>A business user says:</p><blockquote><p>&#8220;We need to hide this field from the user screen.&#8221;</p></blockquote><p>A junior analyst writes the requirement exactly as stated.</p><p>A more mature BA approach would ask:</p><ul><li><p>Is this field used in reports?</p></li><li><p>Is it required for audits or legal purposes?</p></li><li><p>Is it still needed by another department?</p></li><li><p>What happens to historical data?</p></li></ul><p><strong>Context matters.</strong></p><p>Before stakeholder interviews, always think in terms of <strong>impact analysis</strong> (or even run an AI prompt for it):</p><ul><li><p>Who is affected?</p></li><li><p>Which systems are touched?</p></li><li><p>What could break?</p></li></ul><p>If something is unclear, plan follow-ups <em>before</em> meeting developers. The worst situation is when a developer asks a simple question and the answer is:</p><blockquote><p>&#8220;I don&#8217;t know, I need to ask.&#8221;</p></blockquote><p>One core part of the BA role is <strong>anticipation</strong>. You are expected to predict questions, not react to them.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">We share real project examples, practical BA techniques, and honest lessons from the field.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>3. Poor Documentation (Especially Meeting Minutes)</h2><p>Documentation is not limited to formal specifications. </p><p><strong>Meeting minutes are documentation too.</strong></p><p>One recurring issue &#8212; not only in training but in real projects &#8212; is that meeting minutes are either:</p><ul><li><p>not written at all, or</p></li><li><p>far too long and useless.</p></li></ul><p>It&#8217;s very common that two people leave the same meeting with two completely different understandings. That&#8217;s why sending out meeting minutes is essential. <strong>Meeting minutes are critical for capturing agreements, decisions, and outcomes &#8212; and later in the development lifecycle they often explain </strong><em><strong>why</strong></em><strong> a certain decision was made.</strong></p><p>This context becomes extremely valuable weeks or months later, when someone challenges a requirement and nobody remembers the original reasoning.</p><p>Today, AI tools can automatically generate meeting minutes, which is great. But automation does not remove responsibility.</p><h3>Example</h3><p><strong>Bad meeting minutes:</strong></p><ul><li><p>three pages of discussion</p></li><li><p>repeated arguments</p></li><li><p>no clear decisions</p></li><li><p>no next steps</p></li></ul><p><strong>Good meeting minutes:</strong></p><ul><li><p>Decision: Field X will be removed from Screen Y</p></li><li><p>Agreement: Finance confirmed there is no reporting dependency</p></li><li><p>Risk: Audit impact to be validated</p></li><li><p>Next step: BA to follow up with Compliance by Friday</p></li></ul><p>Sometimes <strong>one sentence is enough</strong> if it captures the essence of the meeting.</p><p>If you use AI for meeting minutes, make sure you are not sending out the next <em>Harry Potter</em> novel. </p><p>Minutes must be short and straight to the point &#8212; no unnecessary filler, no <strong>&#8220;bullshitting around&#8221;</strong> because someone didn&#8217;t know the answer.</p><h2>Final Thoughts: How Junior Business Analysts Can Use AI the Right Way</h2><p>AI is becoming a standard tool for business analysts &#8212; but tools alone do not make you better at your job. The difference between a junior and a strong business analyst is not whether AI is used, but <strong>how</strong> it is used.</p><p>The most common mistakes junior business analysts make with AI are:</p><ul><li><p>producing vague, overly long requirements,</p></li><li><p>missing context and impact across systems and teams,</p></li><li><p>and neglecting clear, concise documentation such as meeting minutes.</p></li></ul><p>These issues are not technical problems. They are <strong>business analysis fundamentals</strong> &#8212; and AI only amplifies them, for better or worse.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">If you are a junior business analyst looking to grow faster, <strong>subscribe to Analyst Harbor</strong>.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p>]]></content:encoded></item><item><title><![CDATA[Smarter Days: My Business Analyst AI Routine]]></title><description><![CDATA[How small habits create big impact in the era of AI-assisted business analysis]]></description><link>https://www.analystharbor.online/p/smarter-days-my-business-analyst</link><guid isPermaLink="false">https://www.analystharbor.online/p/smarter-days-my-business-analyst</guid><dc:creator><![CDATA[Lucia & Miloš]]></dc:creator><pubDate>Tue, 07 Oct 2025 10:45:26 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!_aQN!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>It was early spring, the sun was setting, and I suddenly realized the day was ending &#8212; yet I was nowhere near finishing my work. That&#8217;s when it hit me: most of my time had slipped away on tasks that added little real value. Hours spent rewriting meeting notes, summarizing Jira tickets, or tweaking documentation. </p><p>That frustration is what led me to experiment with AI in my daily routine. And the results were clear: fewer hours wasted, more energy left for collaboration, and problem-solving.</p><p>I had been exploring the world of AI and its role in supporting business analysts more broadly &#8212; which I covered in a previous  <a href="https://www.analystharbor.online/publish/post/161796312?back=%2Fpublish%2Fposts%2Fscheduled">article exploring AI&#8217;s broader role in business analysis.</a> </p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!_aQN!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!_aQN!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic 424w, https://substackcdn.com/image/fetch/$s_!_aQN!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic 848w, https://substackcdn.com/image/fetch/$s_!_aQN!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic 1272w, https://substackcdn.com/image/fetch/$s_!_aQN!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!_aQN!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic" width="1456" height="870" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:870,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:290871,&quot;alt&quot;:&quot;&quot;,&quot;title&quot;:null,&quot;type&quot;:&quot;image/heic&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.analystharbor.online/i/172322492?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" title="" srcset="https://substackcdn.com/image/fetch/$s_!_aQN!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic 424w, https://substackcdn.com/image/fetch/$s_!_aQN!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic 848w, https://substackcdn.com/image/fetch/$s_!_aQN!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic 1272w, https://substackcdn.com/image/fetch/$s_!_aQN!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a40c88d-d2a3-4748-8cbb-56367679b86b_1534x917.heic 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Today, let&#8217;s zoom in on the <strong>day-to-day workflow</strong> &#8212; practical ways to make your routine smarter, lighter, and more impactful.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Subscribe to get more AI playbooks for BAs straight to your inbox</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>How Use AI Throughout the Day</h2><p>AI doesn&#8217;t need to overhaul your workflow &#8212; it works best when it slips into small, repeatable habits. Here&#8217;s what a typical BA day can look like with AI support:</p><p>&#127749; <strong>Morning Kickoff</strong></p><ul><li><p>Summarize Jira/Confluence issues</p></li><li><p>Highlight deadlines and blockers</p></li><li><p>Replace 30 minutes of review with a 5-minute scan</p></li></ul><p>&#128209; <strong>Before Meetings</strong></p><ul><li><p>Auto-draft agendas</p></li><li><p>Surface recurring themes in feedback</p></li><li><p>Generate quick diagrams to steer discussion</p></li></ul><p>&#128483;&#65039; <strong>During Meetings</strong></p><ul><li><p>Capture decisions with Otter.ai or Zoom AI Companion</p></li><li><p>Auto-generate action items in real time</p></li><li><p>Stay present instead of drowning in notes</p></li></ul><p>&#128221; <strong>Mid-Day Focus</strong></p><ul><li><p>Refine requirements with ChatGPT</p></li><li><p>Prompt for missing edge cases</p></li><li><p>Generate acceptance criteria instantly</p></li></ul><p>&#127769; <strong>End-of-Day Wrap-Up</strong></p><ul><li><p>Summarize progress and completed tasks</p></li><li><p>Update documentation automatically</p></li><li><p>Close the day with clarity and alignment</p></li></ul><p>These micro-routines evolve into your <strong>personal AI playbook</strong> &#8212; less typing, more thinking.</p><h2>Prompt Patterns for Key Use Cases</h2><p>Tools are only as powerful as the prompts we give them. For business analysts, prompts can act like reusable templates: shortcuts that deliver structured, high-quality outputs in seconds.</p><p>Here are a few practical ones to add to your toolkit:</p><ul><li><p><strong>Backlog Review</strong><br><em>&#8220;Given effort and business value, prioritize these items with reasoning.&#8221;</em></p></li><li><p><strong>Risk Identification</strong><br><em>&#8220;Act as a risk analyst. Identify risks by category and assess severity.&#8221;</em></p></li><li><p><strong>Requirement Critique</strong><br><em>&#8220;Review this user story for clarity. Suggest improvements and add acceptance criteria.&#8221;</em></p></li><li><p><strong>Decision Tables</strong><br><em>&#8220;Create a table showing outcomes based on inputs A, B, and C. Ensure no combination is </em></p></li></ul><h2>Tools and Integrations</h2><p>Habits and prompts are the foundation &#8212; but they become even more powerful when combined with the right tools. AI is no longer something you open in a separate tab; it&#8217;s built directly into the platforms we already use every day.</p><p>Here are a few examples you can use. The AI space is evolving quickly, so this list is not exhaustive &#8212; just a source of inspiration. And if I missed a tool or practice you find really useful, feel free to share it in the comments.</p><p>&#9999;&#65039; <strong>Discovery &amp; Documentation</strong></p><ul><li><p>Jira / Confluence + Atlassian Intelligence</p></li><li><p>Figma / FigJam AI</p></li><li><p>Miro AI</p></li><li><p>Notion AI</p></li><li><p>ChatGPT / Claude / Jasper</p></li></ul><p>&#128202; <strong>Analysis &amp; Visualization</strong></p><ul><li><p>Productboard</p></li><li><p>Amplitude / Mixpanel</p></li><li><p>Mermaid / Lucidchart + GPT</p></li></ul><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.analystharbor.online/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Analyst Harbor is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Security &amp; Ethics for AI in BA Practice</h2><p>With all these possibilities, it&#8217;s tempting to push full speed ahead. Right? &#128578;</p><p>But AI doesn&#8217;t just boost productivity &#8212; it changes how information flows. And with that shift comes responsibility.</p><p>Here are some key guidelines for safe and ethical use:</p><ul><li><p><strong>Minimize sensitive data exposure</strong> &#8211; never put personal data into public models</p></li><li><p><strong>Use enterprise AI platforms</strong> &#8211; e.g., ChatGPT Enterprise, Azure OpenAI, Confluence AI</p></li><li><p><strong>Validate outputs</strong> &#8211; AI can be wrong or biased, always double-check</p></li><li><p><strong>Stay transparent</strong> &#8211; let teams know what content was AI-assisted</p></li><li><p><strong>Comply with regulations</strong> &#8211; be GDPR-aware, follow internal policies</p></li></ul><p>At the end of the day, <strong>trust is the BA&#8217;s currency. </strong></p><p>Protect it.</p><h2>Final Thoughts: Connecting to the Bigger Picture</h2><p>AI is not a silver bullet. </p><p>It works best when layered onto <strong>collaborative modeling</strong> (see <em><a href="https://www.analystharbor.online/p/collaborative-modeling-turning-complexity">Article 1</a></em>) and <strong>continuous discovery cycles</strong> (see <em><a href="https://www.analystharbor.online/p/continuous-product-discovery-from">Article 2</a></em>). Together, they form the foundation for turning conversations, sticky notes, and experiments into structured, testable documentation.</p><p>This is how we link discovery to delivery, and how we scale insights without losing nuance.</p><p>The future of business analysis isn&#8217;t about doing more &#8212; it&#8217;s about doing better. By adopting AI as a daily companion, we can shift our energy from low-value admin work to what truly matters: shaping strategy, building alignment, and guiding outcomes.</p><p>&#128073; <strong>Start today. Pick one AI habit, test it this week, and see how it reshapes your workflow. Share.</strong></p>]]></content:encoded></item></channel></rss>