Service Line

Consulting / Process Review

Consulting / Process Review Service Line

One-liner. Audit, redesign, or formalize a client's (or the factory's own) process — not build a talent, not catalog architecture, but improve how work is done.

When to use this line

  • "Document our mandate creation process so we can find the bottleneck" → as-is process map
  • "Design a lifecycle for client requests" → REQ-CONS-006 pattern
  • "Audit our cadenassage workflow for safety compliance gaps" → REQ-CONS-004 pattern
  • "Map the end-to-end factory process and find improvement levers" → REQ-CONS-007 pattern
  • "Evaluate whether TradingAgents would fit our consulting practice" → REQ-CONS-003 pattern

Do not use this line for: documenting tech architecture (→ EA), building a talent that automates the process (→ Talent Factory Build — usually a follow-on to Consulting).

Inputs

/request-create --service=consulting collects:

  1. Client + sponsor
  2. Process or topic in scope (one sentence)
  3. Pain points or driving question
  4. Stakeholders + interview availability
  5. As-is artifacts (existing diagrams, docs, recordings, meeting notes)
  6. Expected output type (audit memo, lifecycle design, decision memo, etc.)
  7. Decision-makers + timeline
  8. AC + DoD

Standard production process

1. Kickoff brief         (process/YYYY-MM-DD-kickoff-brief-{stakeholder}.md)
   ↓
2. As-is capture          (interviews, doc review, observation)
   ↓
3. Diagnostic             (pain points, drivers, leaks)
   ↓
4. To-be design           (lifecycle / process / decision memo)
   ↓
5. Decision recommendation  (write TFD if structural)
   ↓
6. Handoff + adoption plan

Deliverables

Varies by request type, but always includes:

  • process/ — kickoff brief, interview notes, decision logs
  • output/ — final memo (HTML preferred per feedback_documentation-format)
  • request.md — frontmatter status, AC, DoD checked

Common output formats:

  • As-is map — process diagram + bottleneck analysis
  • Decision memo — options, criteria, recommendation (may spawn a TFD)
  • Lifecycle design — diagram + stage definitions + AC/DoD per stage (REQ-CONS-006 reference)
  • Audit report — finding-by-finding with severity + recommendation

Acceptance Criteria + DoD

Per-request, drafted in request.md before work starts (per feedback_document-before-shipping-standards).

Publishing target

Mixed. Three patterns:

  • Client-facing memo → JCT portail (HTML livrable)
  • Internal-only methodology work → factory intranet under /processes or /standards
  • Decision memos → company/decisions/TFD-NNN + linked from the request

Worked examples

Request Type Status
REQ-CONS-001 — R&D video eval dashboard UX UX consulting Done
REQ-CONS-002 — EA design for approved initiatives Architecture consulting Active
REQ-CONS-003 — Evaluate TradingAgents Tool eval Done
REQ-CONS-004 — STM electrician safety cadenassage process Process audit Pipeline B live
REQ-CONS-006 — Client request & feedback intake lifecycle Lifecycle design Active (this one)
REQ-CONS-007 — End-to-end factory process audit Internal audit Active

Lead role

Philippe — Process Consultant. Owns kickoff, capture, design, recommendation. Collaborates with role-specific specialists per topic (Camille for intake, Marcel for methodology, Riley for R&D scope).

Source-of-truth links

  • Department: departments/consulting/
  • Active queue: departments/consulting/requests/
  • Lifecycle reference: REQ-CONS-006

Status

Most active service line by volume. 7 REQ-CONS requests shipped or in flight.