Blog

Editorial illustration of a BA at an airport-style checkpoint identifying several differently disguised entrants as the same recurring person, symbolising the same requirement re-entering a project in different forms.

The Same Requirement Keeps Coming Back in a Different Shape

A requirement you thought was closed keeps coming back as a new ticket, a clarification, or a change request, and nobody clocks that it is the same need. That is a signal, not bad luck. Here is how to resolve the requirement once at need, decision, and acceptance level, give it a traceable home, and catch the next reappearance before it costs you.

Overloaded head chef at a red OWNER station while a BA redirects most kitchen work through PROXY and DEFAULT lanes, illustrating a project bottleneck caused by single-point decision dependency.

The Business Owner Is Never Available and the Project Is Paying for It

Your project keeps stalling because every decision, clarification, and sign-off waits on one business owner who is rarely free. The fix is not chasing harder. It is reducing the dependency: triage what genuinely needs them, route the rest through proxies and documented defaults, and make the cost of waiting visible so the sponsor owns it as a project risk.

Business analyst adjusts a focus lens over a process map, bringing three relevant wait points into sharp focus while other branches remain muted outside the useful mapping boundary.

Process Mapping for BAs: How to Use It Without Getting Lost in the Detail

Process maps have a habit of ballooning until nobody reads them, or pulling you so deep into one branch you lose the whole process. The fix is to map at a deliberate level of detail: decide the one question the map must answer, map the happy path first, add only the exceptions that matter, and stop there. A practical guide for BAs who want maps that stay useful.

A business analyst inspects a questionable relay handoff while a runner approaches a newly collapsed hurdle after the decision was signed off.

Your Project Keeps Reopening Decisions That Were Already Signed Off

Decisions get signed off, then reopened weeks later after delivery has already built on them. The cause is rarely stakeholders changing their mind. It is usually sign-off collected on a document rather than a decision, from people without real authority, with the trade-off invisible and nothing recorded. Here is how to diagnose it and what to do before the next approval.