What is the goal of a Requirements Gathering Workshop?

• A. Start the design of the metadata structure in OneStream.
• B. Establish an understanding of what the system is expected to do when it is live.
• C. Determine how the client wants to set up their Workflow.
• D. Validate the security roles for data access.

Answer: (B)

Understanding what the system should do when it goes live is the main aim of a Requirements Gathering Workshop. This session brings stakeholders together to clearly articulate business goals, the functions the system must support, data and interface needs, and how success will be measured. By focusing on end-to-end behavior in production, everyone aligns on what the system is expected to deliver and how users will interact with it, which sets the foundation for scope and priorities. In a OneStream project, this means capturing requirements for planning and consolidation processes, data sources, metadata needs, rules, approvals, and reporting so the subsequent design and configuration stay aligned with real business needs.

Other activities, like designing the metadata structure, deciding how workflows should be set up, or validating security roles, are typically handled in later stages after the essential requirements and scope have been established. Those steps translate the gathered needs into concrete design, configuration, and security plans.