The disciplines I work across.
Eight disciplines I combine depending on what the outcome requires: four that design how the operation works—work, decisions, adoption and performance—and four that design the technology that runs it. A real problem rarely belongs to only one of them. They are lenses, not packaged offers.
01Process Architecture
Design the operation before designing the system.
I map how work actually flows—stages, owners, handoffs, decisions and exceptions—and design the target process before deciding which technology should run it.
- Lifecycle design
- Decision rights
- Ownership and handoffs
- Exception paths
Lead to customer, one lens at a time
- 01Lead qualification
Owner: Marketing
Decision
Lead belongs to an existing customerRedirected to the account team
CRM Lead scored & routed
- 02Potential customer
Owner: Sales (handoff)
Human action
Probable duplicatePaused for match review
CRM Account · prospectERP Party index lookup
- 03Opportunity
Owner: Sales
Human action
Terms outside policyFlagged into approval
CRM Opportunity & quote
- 04Commercial approval
Owner: Commercial mgmt (handoff)
Approval gate
Rejected→ back to Opportunity
CRM Approval & audit record
- 05Financial validation
Owner: Finance (handoff)
Approval gate
Missing or invalid legal data→ back to Potential customer
CRM Validation pendingERP Validation rules
- 06Customer created
Owner: ERP (handoff)
System action
Timeout — outcome unknownHeld — reconcile, then continue
CRM Number received
- 07First order
Owner: Sales (handoff)
Human action
Order exceeds credit limitHeld — credit review
CRM Order status visibleERP Sales order
- 08Active customer
Owner: Commercial mgmt (handoff)
Lifecycle state
Order cancelled before invoicing→ back to First order
CRM Lifecycle · activeERP Invoice event
02Digital Operating Model
Transformation is broader than the technology it installs.
A commercial platform changes who decides, who owns which data and how performance is governed. I design those layers together, so the organization can run what it builds—and keep changing it.
- Value streams
- Decision rights
- Governance and variation
- KPI ownership
03Change & Adoption
Go-live is where adoption starts, not where it ends.
Systems change nothing until people work differently. I design adoption into the solution—roles, incentives, enablement and the signals that show whether the process is really followed.
- Operating habits
- Roles and incentives
- Enablement on real work
- Process compliance
04Systems & CRM Architecture
Give every system one clear job, owner and boundary.
I define system boundaries, responsibilities, sources of truth, identities, contracts and failure behavior—so CRM, ERP and the platforms around them each do one job well.
- CRM architecture
- ERP interaction
- System ownership
- Integration contracts
05Data & Integrations
Decide what moves, how fast, and who owns it.
I decide which system of record owns each fact, what moves by API, event or batch, and how both sides are reconciled when they disagree—before anyone maps a field.
- Systems of record
- API and event flows
- Sync and reconciliation
- Data quality
06Automation
Automate the path, keep the judgement human.
I treat automation as process execution: which steps should run on their own, which need a person, and what happens when either of them fails.
- Workflow orchestration
- Approvals and escalation
- Exception handling
- Human-in-the-loop
TriggerManualAutomated
Opportunity marked as won
RuleManualAutomated
Does this customer need a credit review?
AutomationManualAutomated
Creation request sent to the ERP
Human decisionManualPerson decides
Finance validates the credit terms
Next stateManualAutomated
Customer ready to order
The decision stays with a person. Everything around it moves on its own.
07AI & Agentic Workflows
AI that acts in real workflows, with people in control.
Not demos: agents that read structured context, take bounded actions in systems of record, pause for human approval where it matters, and leave an audit trail.
- Structured context
- Bounded system actions
- Human approval
- Audit and guardrails
- 01Incoming emailRFQ from a distributor, three lines
- 02Classify & extractReads it with permitted context only
- 03Match entitiesCustomer matched; two of three products
- 04CRM draftDraft quote prepared—nothing committed
- 05Human reviewApprove, or send back with a reason
Awaiting human review
08Revenue Operations
One commercial operating system, measured the same way everywhere.
RevOps connects process, CRM, data, targets and measurement into one system the business can steer by—with one definition per metric and a clear line from signal to action.
- Pipeline and stage criteria
- Forecast ownership
- Management cadence
- Performance governance
Discipline landscape
Process Architecture
Current-state analysis, target-state design and process governance: stages, decision points, ownership, handoffs, approvals, exceptions and SLAs—defined before anything is automated.
ProcessOperating modelSystemsDataAutomationMeasurement- Processprimary
- Operating modelsupporting
- Systemssupporting
- Datasupporting
- Automationsupporting
- Measurementprimary
Explore Process Architecture- Approvals nobody really owns
- Handoffs that lose context
- Exceptions handled in email
- Which decision does each approval actually make—and on what evidence?
- Where does accountability transfer, and what must be true at that moment?
Process Architecture
Current-state analysis, target-state design and process governance: stages, decision points, ownership, handoffs, approvals, exceptions and SLAs—defined before anything is automated.
- Processprimary
- Operating modelsupporting
- Systemssupporting
- Datasupporting
- Automationsupporting
- Measurementprimary
- Approvals nobody really owns
- Handoffs that lose context
- Exceptions handled in email
- Which decision does each approval actually make—and on what evidence?
- Where does accountability transfer, and what must be true at that moment?
- 01Process
Which stages, decisions and exceptions does the outcome require?
Stage & decision model - 02Operating model
Who owns each stage, decision and handoff?
Decision-rights matrix - 03Systems
Which system acts at each step—and which one is authoritative?
Process-to-system map - 04Data
Which information is required, and who may create or change it?
Data ownership matrix - 05Automation
Which work is deterministic enough to automate, and where must a person decide?
Automation boundary - 06Measurement
How do we know the operation works—and who acts on the signal?
KPI ownership model
The obvious requirement is only the first layer.
I make the assumptions underneath a request visible before they become expensive system behavior—whether the request is about a process, a system or data.
“We need an approval process.”
Add an approval step to the flow.
4 of 12 questions surfaced
An approval without a named decision becomes a formality people learn to click through.