Amanda Harris Advisory

AMANDA HARRIS ADVISORY

Make the way work happens work better.

When updates need chasing, handoffs get lost, and capable people keep working around their tools, it’s time to look at the system.

Explore how I can help Take the free diagnostic
People.Process.Technology.

Connected by design.

AHA / 01A better rhythm for
the way work gets done.
Operating system design for modern teams.Find a useful place to begin

SOUND FAMILIAR?

01

The answer exists.
Finding it takes work.

02

The report is ready.
The next action isn’t.

03

The tools are there.
The work still needs chasing.

01 / WAYS TO WORK TOGETHER

Start where the
work gets stuck.

You may need a clearer view of the whole system, or help with one recurring problem. Choose the starting point that fits the work in front of you.

01 OPERATING SYSTEM AUDIT

See what’s slowing
the work.

A focused look at how information, ownership, workflows, and tools fit together—and where to direct your effort next.

  • 01 A current-state operating picture
  • 02 A maturity assessment and priority findings
  • 03 A 90-day improvement roadmap

A good starting point when the same problems keep resurfacing, and you need to understand what’s causing them before investing in changes.

Discuss an Audit Read about Operating System Audit
THE OPERATING PICTUREFIELDNOTES / 01

Look at the
connections.

  1. 01Information

    Where does it live?

  2. 02Ownership

    Who carries it forward?

  3. 03Workflow

    Where does it stall?

  4. 04Technology

    What supports the work?

  5. 05Governance

    How does it stay useful?

Find the friction.
Decide what deserves attention.

The questions behind a more useful operating picture.

02 REPORTING-TO-ACTION PILOT

Turn reporting
into follow-through.

Make one recurring report easier to prepare and act on, with clear decisions, named owners, and agreed next steps.

Give the next step an owner.

Start with one team and one reporting workflow. Together, we’ll clarify what the report supports, how actions are captured, and who keeps the work moving.

  • 01 A redesigned reporting flow
  • 02 One improved report and connected action register
  • 03 An operating guide, owner training, and pilot review

Useful when reporting creates updates, but decisions and actions still need chasing. AI can be part of the solution where it earns its place.

Explore the pilot Read about Reporting-to-Action Pilot

ONE REPORT. A CLEARER RESPONSE.

Illustrative workflow
WEEKLY OPERATIONS REVIEW01
SIGNAL TO REVIEW

Delivery date
changed.

The update triggers a defined next step.

Connected to an owner and a review point

NEXT ACTIONAssigned

Confirm the revised commitment.

Owner
Operations lead
Review point
Next operating review
Recorded in
Shared action register

The report, the response, and the responsibility are connected.

Example only. The actual workflow is designed around your team.

One team.One workflow.A practical place to start.

THE FREE OPERATING SYSTEM DIAGNOSTIC

Take a closer look
at your everyday work.

Reflect on what happens in your team today. See your five-part profile and a practical starting recommendation.

25questions
5areas of work
1place to begin
Find my starting point

Free. No email required. Your answers stay in this page.

YOUR OPERATING PICTURE

See the whole system.

Illustrative profile. Your results reflect your own answers; the diagnostic is a starting point for reflection.

02 / THE BROADER PRACTICE

Build on the
right foundation.

As the problem becomes clearer, the work can expand into design, implementation, or ongoing improvement. Each engagement has its own agreed scope.

03Operating System BlueprintDesign how the work should run.

Turn a clear understanding of the problem into a practical future-state design. Define the workflows, information, ownership, governance, and tool roles the team needs.

  • Future-state workflow architecture
  • Information and governance design
  • Automation and AI opportunities
  • An implementation roadmap
Discuss a Blueprint Read about Operating System Blueprint
04TeamOS BuildPut the design into daily use.

Implement an agreed operating environment that people can use and maintain. The build reflects your tools, access, and the capabilities needed for the work.

  • Configured workflows and collaboration structures
  • Agreed reporting and knowledge systems
  • Ownership and operating guidance
  • Handoff and adoption support
Explore a TeamOS Build Read about TeamOS Build
05AI in the FlowGive AI a useful role in the work.

Find where AI or automation can help a real workflow: interpreting information, preparing an output, routing a request, or supporting a decision. Start with the task and the people responsible for it.

  • A focused workflow and opportunity review
  • A practical use case and review process
  • An agreed pilot or implementation scope
  • Measures for effort, quality, and adoption
Find a useful AI starting point Read about AI in the Flow
06Operating OptimizationKeep the system working as work changes.

Keep improving the operating environment after it is in use. Review friction, adoption, and changing needs, then make deliberate adjustments with the team.

  • An agreed improvement and review cadence
  • Prioritized workflow refinements
  • Governance and adoption support
  • Measurement and next-step recommendations
Explore ongoing support Read about Operating Optimization

You don’t need to buy every stage. We’ll choose the engagement that fits your situation.

03 / THE SIGNAL METHOD

A method for
making work work.

A practical framework for understanding the system, connecting its parts, and learning from what happens in use.

  1. S01

    Surface

    Make the current way of working visible. Follow the information, decisions, and workarounds.

  2. I02

    Integrate

    Connect the people, processes, tools, and information that need to work together.

  3. G03

    Govern

    Clarify ownership, decision rights, standards, and the source of truth.

  4. N04

    Notify

    Get relevant information to the right person at the point it becomes useful.

  5. A05

    Activate

    Connect information to a decision, a next action, and someone accountable.

  6. L06

    Learn

    Measure what changes. Refine the system around what the team learns.

04 / MEET AMANDA

A practical partner
in the messy middle.

Amanda Harris, founder of Amanda Harris Advisory
AMANDA HARRISFounder & advisor

I build the operating systems, governance, and capabilities that turn strategy into measurable execution.

When priorities, processes, tools, and responsibilities become tangled, I trace how the work actually happens, clarify ownership and decisions, and design a more connected way forward.

I’ve built governance, led cross-functional programs, improved processes, and helped teams develop new capabilities. I bring that experience to the work we do together.

We’ll start with your context: what’s happening, what you’ve already tried, and what improvement would actually mean for your team.

MBAPMPPMO-CPSix Sigma Green Belt
Connect with me on LinkedIn

05 / NOTES FROM THE WORK

Good questions.
Practical moves.

A few ways to look at familiar problems before choosing what to change.

01 / WORKFLOW

Before you automate the handoff

Take one recent request. Identify who sent it, what the next person needed, and how they knew it was ready.

Read the practical move

Write down the trigger, the required information, the receiving owner, and the point when responsibility changes. Ask both people to review it. If they describe different processes, resolve that difference before automating anything.

Build a clearer cross-functional handoff

02 / VISIBILITY

A dashboard needs a decision

A report can be accurate and still leave the team unsure what to do. Start with the decision it should support.

Read the practical move

Choose one recurring report. For each metric, ask: Who uses this? What decision does it inform? What action follows a change? Agree on those answers and a review cadence before adding another visual.

Make the dashboard useful

03 / PRACTICAL AI

Choose the work before the tool

A useful AI experiment begins with a specific task and a way to judge whether the result helps.

Read the practical move

Pick a repeated task with clear inputs and a reviewable output. Record the current effort and quality. Define what information can be used, who checks the output, and when the experiment should stop. Compare the result with the original process.

Design a reviewed AI pilot

Explore Insights & Amanda’s Angle

BEFORE WE START

A few useful
answers.

Where should I start?

The free Diagnostic can help you identify questions to investigate. Choose an Audit when the causes and priorities need a closer look. The Reporting-to-Action Pilot is a focused starting point when one recurring report and its follow-through need attention.

Will you help implement the changes?

Yes. I lead the diagnosis and design, and I implement the parts we agree I can support. The scope reflects your tools, access, and needs. If your internal team or a specialist needs to be involved, we agree those roles up front.

Do we need new tools or AI?

We’ll first look at how your current tools and processes support the work. A clearer handoff or better use of an existing system may be the right change. AI is an option when it improves the task and can be used responsibly.

How are scope and fees agreed?

We start with the problem, the people involved, and the outcome you want. Then we agree on deliverables, responsibilities, timing, and fees before the engagement begins.

What does the Diagnostic tell me?

It reflects your own assessment of five parts of your operating environment. It helps identify questions to investigate. It doesn’t benchmark your organization against others or replace a detailed review.

LET’S FIND A STARTING POINT

What’s harder
than it needs to be?

Tell me what’s getting stuck, who’s involved, and what better would look like. We can start there.

Connect with Amanda on LinkedIn

A FEW NOTES BEFORE WE TALK

Put the problem into words.

Use these prompts to prepare a brief you can bring to the conversation.

For your own use. Downloading doesn’t send an inquiry.