Bradley NormanOperations & Technology LeaderStart a conversation
Operations & Technology Leader

I build the operating systems leadership teams run on.

I turn production, margin, capacity, sales, and workflow problems into software, data systems, AI automation, and decision tools that work in the real world.

Talk about an opportunityExplore selected work
Charlotte, NC Open to the right next chapter
Current seatVP, Business Intelligence & Operations Technology
Built forService businesses with real operational complexity
Sweet spotWhere operating judgment meets product and data
Selected systems

Built close to the work.

The through-line is simple: find a consequential operating problem, make it legible, and build the system that lets people run it better.

01Operating platform

ArborPlus

An internal operating platform connecting sales, scheduling, production, reporting, customer communication, and field-service workflows at A Plus Tree.

  • Product leadership
  • Business systems
  • Data platform
  • Workflow design
Read the case note
02AI work system

Loomfield

A self-hosted mission-control system that lets different AI agents work from the same durable context, project structure, and human-controlled rules.

  • AI systems
  • Product architecture
  • Knowledge systems
  • Human-in-the-loop design
Read the case note
03Decision systems

Operations intelligence

Forecasting, capacity, backlog, pricing, margin, and production systems built around the questions leaders actually need answered.

  • Executive reporting
  • Forecasting
  • SQL & Python
  • Operational judgment
Read the case note
See the full work notes
How I work

Software is a mechanism. The outcome is the job.

I work across the line that usually separates the operator from the builder. That makes it possible to carry a problem from leadership conversation to live system without losing the business context in between.

  1. 01

    Find the real constraint

    Start with the operating room, the field handoff, or the decision that keeps breaking—not with a technology shopping list.

  2. 02

    Make the system legible

    Define the workflow, metric, ownership, and source of truth so the organization can see the same problem clearly.

  3. 03

    Build the missing layer

    Use software, data, automation, or AI where it creates leverage. Keep the solution close to the work.

  4. 04

    Run it until it holds

    Ship, observe, correct, and turn the result into a durable operating habit rather than a one-time analysis.

Field notes

Ideas from the work.

Writing about operations, product systems, practical AI, and what I am learning while building Loomfield.

On the desk

Next notes: why dashboards fail, building software from operating questions, and what AI systems need before they deserve automation.

Visit the writing desk