Start with the record.
Check where the information came from, when it was updated, what each row represents, and how the number was calculated.
I’m an operations professional with experience in international shipping, customer coordination, documentation, invoicing, reconciliations, and cross-functional problem-solving. I use that experience to ask practical questions of the information in front of me, while developing analytical and systems skills.
An outdated instruction, incorrect quantity, missing approval, or unclear owner can affect the customer and several downstream teams.
In export operations, I coordinated live-poultry shipment requirements, USDA documentation, customer changes, and handoffs across planning, transport, accounting, and other teams. I also worked in Customer Retention at AT&T. Supported HR with various projects. These experiences taught me to check both the record and the business consequence before recommending a next step.
The official process matters. So does understanding how information, influence, and decisions actually move through the work.
That became the foundation for these projects: organize the record, check the calculation, show what remains uncertain, and avoid claiming more than the evidence supports.
I want someone else to be able to follow how I reached an answer—and to see where the information is missing, conflicting, or still uncertain.
Check where the information came from, when it was updated, what each row represents, and how the number was calculated.
If two records disagree, show the difference instead of choosing the cleaner answer.
Sometimes the most useful result is the question that still needs an answer.
I separate the tools I use most comfortably from the ones I have used in projects, certification work, and continued practice.
Pivot tables, lookup formulas, conditional formatting, reconciliation, and structured review workbooks.
Used in self-directed projects, certification work, and guided practice with reports, customer records, and workflow concepts.
Used to help structure fictional data, troubleshoot code, and test presentation options. I chose the operational questions, checked the calculations, and set the limits on what the work claims.
Used in the portfolio for multi-table analysis, defined measures, and reconciliation checks against source totals.
A reflection on useful tools and the things we still want to learn for ourselves.
I’m interested in operations work that brings stakeholder needs, reliable systems, useful analysis, and practical automation together. The goal is to reduce repetitive work so people have more time for the conversations, decisions, and follow-through that matter most. I’m open to roles in customer operations, business operations, HR operations, CRM support, and operations analytics—remote or Huntsville-area.