i always use a mind mapping tool like mindmup (but any tree graphing utility will do) .
(there is the maremaid pack by @Leandro_Zubrezki and the svg-basted tool in coda by @Paul_Danyliuk. or you can use the miro pack that has a kinda mind-mapper tool.)
i map out the pages and subpages at the top level, with the tables and their columns below that and a seperate bunch of subtrees for views, dialogs and charts.
use color codes to distinguish the different objects; pages, tables, views, texts, numbers, dates, formulas, buttons, lookups etc.
this logically structured view is then easily communicated among collaborators and is included in the documentation. it then guides the building and testing process.
most mindmap tools let you collapse subtrees to show only the details you need at any one point.
its not a strict methodology (like UML or SSADM) but does impose rigor and structure on the design process.
i have used this for decades with my clients, for automating workflows in excel/vba, sheets/gas, etherium/solidity, salesforce/apex, and more recently with bubble, notion and coda.
so it has stood the tests of time very well. agile-dynamics has courses and tutorials on this, but honestly, its just common sense, not a hard science.