Requirements
Define business rules, process states, roles, inputs, outputs, dependencies, and acceptance criteria in language that supports a shared understanding.
Case studies
How I bring order to complex workflows.
Conceptual case studies based on my experience and domain knowledge. They are sanitized examples, not descriptions of confidential implementations.
Manufacturing ERP
Inventory workflow
How can inventory processes be structured to provide visibility and support procurement, production, warehouse operations, and order fulfillment?
Business context
Inventory is a shared operational view. The business need is to make its movement, availability, and related decisions understandable across connected workflows.
Analysis approach
Start with the current state, identify gaps and exceptions, then describe a future-state workflow before translating it into delivery-ready requirements.
ANALYSIS PATH
- Business requirement
- Current-state analysis
- Gap analysis
- Future-state workflow
- Functional requirements
- User stories
- Acceptance criteria
- Development
- Validation
Key considerations
Inventory must be considered in relation to procurement, production, warehousing, and fulfillment—not as an isolated process.
Outcome
A clear conceptual path from operational problem to validated product behavior, without exposing proprietary details.
Procurement
Procure-to-pay workflow
A conceptual view of how a Business Analyst helps connect a purchase need to a reliable inventory update.
Purchase
requirementPurchase
requestApprovalPurchase
orderSupplierGoods
receiptInventory
update
requirementPurchase
requestApprovalPurchase
orderSupplierGoods
receiptInventory
update
Need & request
Clarify why a purchase is needed, what information initiates it, and who is accountable for the request.
Approval & order
Map decision points, required information, exceptions, and the handoff from authorization to supplier-facing work.
Receipt & inventory
Define how receipt is represented, checked, and reflected so downstream teams share an accurate operational view.
Manufacturing ERP
Production planning
A conceptual production-planning flow that brings demand, materials, manufacturing activity, and warehouse readiness into view.
Customer
demandProduction
planningMaterial
availabilityProduction
orderManufacturingQuality
checkFinished
goodsWarehouse
demandProduction
planningMaterial
availabilityProduction
orderManufacturingQuality
checkFinished
goodsWarehouse
Business requirements
What needs to be planned, by whom, and with what visibility.
Dependencies
How demand, material availability, orders, quality, and storage affect one another.
Data requirements
Information required to support decisions and process transitions.
Exceptions
Scenarios that require clarity when normal flow cannot proceed.
User roles
Responsibilities and handoffs throughout the operational journey.
Validation
Acceptance conditions that make the intended behavior testable.
Requirements design
Business requirement → user story
An interactive example of the path from an ambiguous request to a delivery-ready artifact.
BUSINESS PROBLEM
“Teams need a clearer way to understand whether required inventory is available.”
The starting point is not a feature. It is an operational need that needs context, questions, and boundaries.