Internal Applications Department System

Department needs arrive as a card in “Request” describing the problem, not a ready-made solution: which process is struggling, who suffers from it, and how much time it costs. The card moves to “Analysis,” where the analyst sits with the requesting department, understands the process as it actually is, and writes requirements and acceptance criteria on the card. After approval it moves to “Build,” where developers work on it in phased deliveries; then “Testing,” where users from the requesting department itself try it and their notes are logged; then “Launch” when it's ready for all employees. The journey doesn't end at launch: the card moves to “Adoption” to track employee usage and train them on the tool, then “Measurement” to document its actual impact on the process it was built for.

Chat is for developers' daily coordination and urgent requirements questions with requesting departments. The Forum documents engineering decisions, major requirements debates, and post-launch reviews — so design choices and their rationale stay understandable to whoever joins the team later, and the same discussions aren't repeated every time.

The applications manager receives requests, ranks their priorities, and approves their entry into “Build”; the analyst accompanies the card from “Analysis” through “Testing” acceptance with the requesting department; and developers execute and address feedback. “Measurement” results return to the applications manager to decide: develop the tool with a second phase, keep it as is, or officially retire it if it went unused.