System Analyst Artifacts and Tools for Capturing "Not Knowing"

What should a systems analyst do when a regulator delays the regulatory framework for months, requirements shift constantly, and code is needed yesterday? Traditional approaches fail inside a "black box," leading to endless refactoring and missed deadlines.

In such environments, an analyst's goal is not to guess the future, but to quantify current "unknowns," isolate risks at the architectural level, and shield the team from chaos.

This talk breaks down a real-world case study of development under extreme uncertainty. You will learn how the "Granite & Sand" model splits requirements into stable and volatile blocks. We will dissect four artifacts that turn chaos into a measurable backlog: Unknown Inventory, Assumption Register, Decision Backlog, and Delta Map. Expect only battle-tested templates to help your team maintain pace when the rules are rewritten on the fly.