I began my career in Atlanta in executive administration, working inside major corporate and professional environments including Accenture Consulting, Ernst & Young, Turner Broadcasting, and legal organizations. Those roles taught me very early that strong executive administration was never simply about calendars, correspondence, or keeping things neat.

The real work was knowing how the operation moved.

Information was rarely sitting in one convenient place. Priorities changed. Different people owned different pieces of an assignment. An executive needed someone who could understand what was being requested, determine what had to happen next, locate the right information, coordinate the right people and resources, and carry the work forward without requiring constant direction.

That became the foundation of how I work.

Corporate Operations

Over time, my work expanded across executive administration, legal environments, supply-chain operations, project coordination, entertainment, and public-program operations.

The industries changed, but I kept encountering the same underlying questions: Where does the work begin? Where does the information live? Who owns each part? What has to happen next? What is the final result we are trying to produce?

Working around infrastructure-driven professionals changed the way I looked at administration. I became interested not only in whether something was completed, but in the system responsible for completing it.

If the goal was a finished product for a client, I wanted to understand the entire route from beginning to end and then work backward. Each person had a particular responsibility. Each tool served a purpose. Each decision affected what came next. My role was often the point where those moving parts had to come together.

That was what made me effective at an executive desk. I learned how to pivot, how to find what was needed, how to work across people and tools, and how to keep an assignment moving when the path was not perfectly laid out in front of me.

A Broader Operating Environment

When I relocated to Arizona, I continued building on that experience through legal administration, project coordination, contract operations, and public-program work.

At the State Bar of Arizona, the environment required discretion, documentation control, scheduling, communication, and careful adherence to established procedures.

At Summer Hill Films, I moved into entertainment-industry project coordination and learned Chain of Title. Film distribution depended on signed releases, producer correspondence, agreements, documentation requirements, and legal-delivery milestones all being accounted for. One missing piece could prevent the larger process from moving forward.

Later, in high-volume remote public-program operations, I worked across documentation-heavy assignments requiring accuracy, independent judgment, changing priorities, and consistent follow-through.

Different industries. Same principle.

The work could only move as reliably as the structure underneath it.

The Notary Chapter

Eventually, I began thinking seriously about working for myself.

Becoming a notary made sense because it drew on skills I had already spent years developing: documentation, accuracy, confidentiality, scheduling, communication, client requirements, and follow-through.

But operating independently changed my perspective.

Inside a corporation, there is usually an established environment surrounding the work. There are departments, procedures, systems, shared tools, records, and people responsible for different pieces of the operation.

When you become the business owner, all of that responsibility moves much closer to you.

Requests arrive. Appointments have to be managed. Information has to be captured. Documents have to be maintained. Communication has to continue. Payments, records, delivery, and follow-up all have to connect.

A professional can be very good at the work itself while still carrying too much of the business personally.

I recognized that immediately because I had spent years working inside environments where administrative and operational professionals were often the people holding all of those moving pieces together.

The difference was that now I could see the opportunity to build the structure around the work itself.

The Shift to Systems

Norice Notary Solutions began with notary work, but the deeper business eventually became clear to me.

The real problem was not whether a professional knew how to perform her work.

The problem was often what surrounded it.

A request might arrive in one place. Client information might live somewhere else. Scheduling might sit in another application. Documents could be stored under naming conventions that only the owner understood. Follow-up might depend on memory. Important decisions were being made repeatedly because no operating rule had been established the first time.

The business worked because the owner knew where everything was.

I had seen versions of that throughout my career.

I had also spent my career learning how to build structure around it.

That was the turning point.

Building Norice Notary Solutions

Today, Norice Notary Solutions installs Business Operating Systems for serious founders and professionals already operating at a level that requires stronger operational infrastructure.

NNS connects four components into one operating environment:

• Business Presence

• Client Control Center

• Operations Structure

• Contact & Request Flow

The system is built around a simple operating principle: information should have a place, work should have a path, decisions that can be made once should not have to be made repeatedly, and the infrastructure carrying the business should be capable of matching the level at which the professional already operates.

My work now brings together the disciplines I have accumulated throughout my career: executive operations, workflow management, process design, documentation systems, SOP development, project coordination, digital operations, and AI-enabled methods that increase capacity and strengthen execution.

NNS did not represent a departure from my earlier career.

It was the progression of it.

How I Think About Operations

I genuinely enjoy systems.

I study how work moves, where constraints develop, how information travels, and what happens when one part of an operation cannot carry what the rest of the business is producing. That interest extends into the books and thinkers I study—from operational works such as The Goal and Critical Chain to the careers and leadership perspectives of people such as Ursula Burns and Mellody Hobson.

I am particularly interested in situations where everything has not already been figured out.

There is something compelling about entering an environment where the road has not been completely built yet. You identify the result, work backward, determine what has to connect, test the structure, and keep laying the blocks.

I sometimes think of it as building the Yellow Brick Road while you are already walking it.

Then there is that moment when the pieces finally connect. The information is where it belongs. The workflow carries the work. People know what happens next. The system begins doing what it was built to do.

That moment still fascinates me. It is the same instinct that made me effective in executive administration, project coordination, independent business ownership, and now operational infrastructure.

I want to understand how the work operates from beginning to end—and then build the structure capable of carrying it.

Professional Focus

• Executive Operations

• Workflow & Process Management

• Strategic Executive Administration

• Project Coordination

• Operational Systems

• AI-Enabled Operations

Credentials

Google Project Management Certificate
Google Data Analytics Professional Certificate
Arizona Notary Public Commission