Rent-a-Process-Manager

Rent-a-Process-Manager is a fractional process-owner engagement — turning ambiguous workflows into documented, measured, and optimizable systems. The prerequisite for any serious automation effort, and the function that most organizations underfund until something breaks.

  flowchart LR
    A[Discover<br/>interviews + mining] --> B[Model<br/>BPMN 2.0]
    B --> C[Measure<br/>cycle / errors / rework]
    C --> D[Optimize<br/>backlog]
    D --> E{"Automation-ready?"}
    E -->|Yes| F[Automation handoff]
    E -->|No| D

When this fits

• You have decided to automate something and discovered that nobody can describe the current process consistently. Three people draw three different flow diagrams.
• You have grown to the point where tribal knowledge no longer scales. New hires take six months to figure out how things work, and key processes still rely on one person remembering.
• You are preparing for a certification audit (ISO 9001, ISO 27001 process clauses, SOC 2) and need documented processes that auditors will accept and people will actually follow.
• You are integrating an acquisition and need to reconcile two sets of processes into one.
• A process has visibly broken — customer complaints, rework, missed SLAs — and you need someone to take it apart, understand it, and put it back together.

What this role covers

• Process discovery. Sit with the people doing the work, not just the ones who manage them. Map what actually happens, including the workarounds.
• BPMN 2.0 modeling. Capture the process in standard notation that survives the conversation and can be reused for training, audit, and automation design.
• Process measurement. Define the handful of metrics that actually matter (cycle time, error rate, rework loops) and instrument them. Avoid the metrics-theater trap.
• Optimization. Identify and prioritize improvement opportunities: handoffs that lose information, controls that add no value, decision points that nobody is empowered to make.
• Automation readiness. Determine which steps are candidates for automation (RPA, workflow engines, integration scripts) and which are not. Many “automate this” requests fail because the process is not automation-ready.
• Process governance. Establish ownership — every process has a named owner who is accountable for changes — and a cadence for review.
• Training material. Turn the documented process into the onboarding material that new hires actually use.

Method notes

• BPMN 2.0 first. A common notation that engineers, operations, and business stakeholders can read with light training. Vendor-neutral.
• Process mining where applicable. If transactional systems are available (ERP, CRM, ticketing), process mining gives an evidence base that complements interview-based discovery — what actually happens versus what people say happens.
• No “process for its own sake.” A documented process that nobody follows is worse than no documentation: it creates false confidence and audit risk. We refuse to produce shelf-decoration.

What you get

• Process inventory — a real list of the processes that matter, with ownership and priority.
• BPMN model library for the in-scope processes, version controlled, refresh-able.
• Optimization backlog — a ranked list of concrete improvements with estimated effort and business impact.
• Automation candidate list — clearly distinguishing “ready to automate now” from “needs process work first”.
• A governance proposal — who owns processes going forward, what review cadence, what change process.

What sets this apart

• Business + technical view in the same head. Process work that ignores the underlying systems produces models that look nice and cannot be implemented. Process work that only looks at systems produces automation that encodes broken handoffs faster.
• Operator pragmatism. We have run operations. We will not propose a process that cannot survive a Friday afternoon under load.
• Audit-defensible documentation. Output is structured enough to satisfy an auditor without being so heavy that nobody updates it.
• No vendor capture. No referral relationships with RPA, workflow-engine, or process-mining vendors. We recommend what fits.

Why this matters at the CEO level

• 💰 Operating margin tax. Process inefficiency is a direct margin tax. Most organizations operate with 15–30 % of work activity that adds no customer value — pure rework, handoff loss, and shadow workarounds.
• 🤖 Automation success depends on it. Roughly 70 % of automation projects fail. They almost always fail on process design, not on the automation tooling. Process discipline is the prerequisite, not the follow-up.
• 📋 Compliance and certification. ISO 9001, ISO 27001 process clauses, SOC 2 — they all require documented processes. The process documentation is the audit material. Without it, certification is unaffordable.
• 🎓 Onboarding cost. New-hire time-to-productivity is a direct function of process documentation quality. Sloppy process documentation means 6 months of partial productivity per hire; clean process documentation means 6 weeks.
• 🤝 M&A integration depends on it. Integration of an acquired entity requires reconciling two process landscapes. Done well, synergies materialize; done badly, the acquired entity runs as a permanent silo.

Engagement format

• Typical duration. 3 to 12 months, scoped per process-area.
• Cadence. 2 to 5 days per month, plus workshop weeks (typically 1 week per quarter for stakeholder workshops).
• Onboarding. First 3 weeks focused on discovery — interviews, current-state walkthroughs, transactional-data sampling.
• Pricing. Fixed monthly retainer plus workshop-week pricing. Optimization implementation work can extend into a Development engagement.

Reach out and we will scope what process-management coverage your organization actually needs.