Using this template, you can take any problem and put it through the meat-grinder of ORCA. You'll gather your research, go noun-foraging, define and consolidate your objects, connect them with a system model and a nested-object matrix, and then bring your objects into a CTA matrix. Finally, you'll finish defining your objects' structure by brainstorming attributes.
Next, you'll take your new system through the Requirements round of ORCA, clearly defining your objects as well as the roles and ownership of them in the system. You'll take your objects' relationships through My Cat Saving Fire Department, defining mechanics and cardinality, sorting and filtering, and dependencies. You will define the why and when of CTAs, and you'll outline the values, conditional logic, permissions, and formatting requirements of your system's attributes.
Next is the Prioritization round. You'll eliminate, combine, and downgrade metadata. You'll force rank nested objects and CTAs, offloading or de-prioritizing nice-to-have functionality.
This session could take anywhere from an hours to days. But at then end, you'll have a ton more clarity on the scope and complexity of the problem you are trying to solve, and, most likely, a massive parking lot of questions and answers.
Remember! The ORCA process is four rounds — one round of Discovery, Requirements, and Prioritization just scratches the surface. If you are interested in diving deeper, consider the OOUX Masterclass.