Optimizing Mixpanel Events for User Tracking: Best Practices

First-timer Mixpanel user here. We're in beginning steps with the Data Tracking plan. We first created several events per page - as we were seeing things from the perspective of needing to see every step through a multi-page enrollment process, field-by-field (yes, we need that level of detail). But after completion, it seems like it might be easier to create more 'generic' events, like "Input_blurred" to capture any event where a field is entered and de-focused, or "button_triggered" – like given in a Mixpanel page's example. Then we'd attach properties of page_name, page_url, form_name, etcetera so we can still see the user's path through pages, and where they might have dropped, or hit an error. My question is a two-parter: Is this feasible, or over-simplifying events. And will we have any problems stitching together a user's experience? Does Mixpanel have built-in tools that present that with a few filters - like if I wanted to quickly see a user flow through pages, with drop-off? Or, is there a heavy lift in finding and presenting that information? 🎫