Start with the process, not the symptom.
A number is only as clear as the workflow that produced it. Map the workflow and the number becomes useful.
I'm an accounting professional working in higher-education finance and operations, and currently doing an MBA at Cal State Long Beach. Most of my day-to-day lives in close cycles, reconciliations, and reporting. It's the work that keeps an organization honest about itself.
Over time the part I've cared about most has shifted. I'm less interested in producing one more report than in understanding the system that produces it: where data loses fidelity, which decisions get made on evidence, and which ones get made on habit.
I'd rather understand the report than write a longer one.
That's the angle I'm bringing into analytics, BI, and AI-enabled workflows. Not as a developer, and not as a finance person trying to look technical. Just as someone who has lived inside the day-to-day these tools are supposed to improve.
The CPA and CGFM sit underneath all of it. What I'm building toward is straightforward: a practice that pairs solid finance fundamentals with practical analytics and good judgment about where new tools actually help.
Outside of work, I play a lot of video games and read about how good businesses actually run. The messy operational details, not the brochure version. Same curiosity as the day job, lower stakes.
Not slogans. Just orientations that tend to make the work go better.
A number is only as clear as the workflow that produced it. Map the workflow and the number becomes useful.
Getting the numbers right is the floor. The harder, more useful work is making a finding obvious to someone whose job isn't to read finance.
Repeatable, rules-based work belongs in tools. Decisions belong with people. The interesting design problem is the boundary.
MBA modules, analytics practice, AI experiments. Same instinct. Keep updating the model of how the work actually runs.
A short running list. The shape of where attention goes when it's free.