An Analyst Starts Alone

In practice

Amira is a business analyst at a city housing office. Nobody has asked her to change how she works. Her next assignment is a change to how rent assistance is renewed each year. Before she writes a requirement, she lists the things the change touches: the Application, the Household, the Renewal Notice and the Assistance Award. The Award is the one whose mistakes reach families, so she makes it the thing she will define first. She sketches a map with four zones on one page and keeps it on her desk. In the first planning meeting, someone says the renewal resets the case. She asks, with real curiosity, what exactly is in a case here. Three answers come back, and the team realizes that case has meant both the Household's file and the Award itself. She writes both meanings down. She drafts three cards for the riskiest behaviors: create a renewed Award, generate the Renewal Notice, and log a change in income. When she uses the office's approved AI tool, she pastes her short definition of an Award and the card template first, and asks for draft test scenarios for one card at a time. The tool proposes a field for a landlord's rating that nobody had mentioned, and she deletes it. At the end of the month, a colleague asks why her change notes caught a report that would have counted renewals twice.