CUSTOMER OPERATIONS · ANALYSIS · PROCESS

I’m interested in what becomes visible when separate details are considered together.

Brooke Moss

These projects use customer records, account numbers, and process details to answer practical questions: What needs attention? What is missing? Who owns the next step?

I’m most interested in the details that are easy to dismiss on their own, but useful once the fuller picture is visible.

SELECTED WORK

Three projects showing how I organize customer information, review account risk, and clarify who needs to decide or act. Each uses clearly labeled fictional data.

01INTERACTIVE PRODUCT STUDY

In Context

The question
What is missing before the next customer decision can be made?
What I created
A practical check of what is confirmed, what is missing, and who needs to answer before a customer commitment is due.
Method
Decision preparation · matching records · source links
View case study
02SELF-DIRECTED ANALYSIS

North Star

The question
Which accounts need action, validation, or closer review?
What I created
An Excel review that shows which accounts need attention and how every total was calculated.
Method
Excel · metric definitions · data reconciliation
View case study
03INTERACTIVE SYSTEM STUDY

Who Decides?

The question
Who provides the information, who makes the decision, and who owns what happens next?
What I created
A clickable path that separates input, approval, ownership, and follow-through when several requests are moving at once.
Method
Process mapping · role clarity · workflow design
View case study
WHY I STARTED

A little distance changed what I noticed.

I’ve always been drawn to the small details that seem unrelated until they change the larger picture—and to the way people can give the same information a different meaning.

After becoming a stay-at-home mom, I spent much of my free time learning new tools and thinking back on the pain points I had accepted as part of the job in earlier roles. Time and change have a way of shifting your perspective. I kept coming back to how difficult it could be to trace a request: who contributed, who had influence, who could approve it, and who was expected to act.

An org chart is excellent at showing who reports to whom. It is not always as good at showing who actually has influence.

That became one starting point for these projects: use records and technical tools to make the connections easier to follow, while leaving room for the part no system can fully explain—the people involved.

HOW I APPROACH THE WORK

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.

01

Start with the record.

Check where the information came from, when it was updated, what each row represents, and how the number was calculated.

02

Keep contradictions visible.

If two records disagree, show the difference instead of choosing the cleaner answer.

03

Ask the missing question.

Sometimes the most useful result is the question that still needs an answer.

TECHNICAL RANGE

The tools behind the work.

MOST HANDS-ONExcel

Pivot tables, lookup formulas, conditional formatting, reconciliation, and structured review workbooks.

PROJECTS + CERTIFICATIONSPower BI · Tableau · Salesforce · HubSpot · Monday.com

Used in portfolio projects, certification work, and guided practice with reports, CRM workflows, process maps, KPIs, and customer records.

FOUNDATIONAL PRACTICESQL · Python

Basic queries and scripts, with continued practice in workflow logic and checking results.

HOW AI FITS INTO MY WORK

I use it deliberately.

Google AI Professional Certificate · Completed

I use AI to organize complex information, compare approaches, build and test interactive prototypes, and work through technical problems. I choose the question, decide what belongs, and check the source records, calculations, and claims.

AI can help sort information or point out a pattern. It cannot know what a customer meant, whether every record is complete, or why someone’s behavior changed. Those questions still require judgment and follow-up.

ABOUT + CONTACT

Curious by nature.
Practical in how I work.

I like work that involves making sense of details, asking good questions, and communicating clearly with the people involved. I’m open to remote or Huntsville-area opportunities, including full-time, part-time, contract, and project-based work.

In previous customer and operations roles, I saw how one missing detail or outdated record could create extra work for everyone involved. These projects show how I would organize and check that information using fictional data I can share publicly.