GFE Process Walkthrough Template

Template Type: Workflow Orchestration
Source: GFE Skill System Process Definitions (/spec/processes/PROC-{CATEGORY}-{NAME}.json)
Goal: Visualize how atomic tasks sequence into cross-functional value streams.
Use with: .agent/workflows/create-process-post.md

0. SCHEMA EXTRACTION GUIDE

Before writing, extract these fields from the process JSON:

Required Fields

json

{
  "id": "PROC-REV-LEAD-TO-CASH-01",
  "name": "Lead to Cash for B2B SaaS",
  "description": "End to end flow from lead capture to cash collection...",
  "steps": [
    { "order": 1, "task_id": "M-001", "role_signature": "GFE-2.1.0", "tooling": ["hubspot"] },
    { "order": 2, "task_id": "S-001", "role_signature": "GFE-1.2.0", "tooling": ["hubspot"] },
    { "order": 3, "task_id": "F-001", "role_signature": "GFE-0.0.2", "tooling": ["zoho"] }
  ],
  "primary_kpis": ["KPI-REV-001", "KPI-CF-001"],
  "valuation_link": ["revenue", "cashflow"],
  "okrs": ["OKR-2025-Q1-01"]
}

1. Step Details (from /spec/tasks/): For each task_id in steps[]:

Extract: title, domain, level, description
Link: /blog/posts/[task-slug]

2. KPI Details (from /spec/metrics/): For each primary_kpis[]:

Extract: name, description, owner
Link: /blog/posts/[kpi-slug]

3. ValuationOps Layer: Map valuation_link array to layers (Revenue Ops, Cash Flow Ops, etc.)

1. ARTICLE STRUCTURE

Frontmatter

yaml

---
title: 'Process: [Process Name]'
slug: proc-[id-slug]
date: '[YYYY-MM-DD]T00:00:00.000Z'
description: >-
  [Process description]. Orchestrates [Count] tasks across [Domains] to drive [Valuation Impact].
author: GFE Strategy Lab
image: /images/blog/proc-[id-slug]-hero.png
alt: [Hero image description]
tags:
  - process
  - [valuation_link items]
  - orchestration
sections:
  - gfe-systems
  - processes
featured: false
aside: true
footer: true
traceability:
  valuationLayer: [primary valuation channel]
  processId: [this Process ID]
  relatedTasks: [array of task IDs from steps]
  kpiIds: [primary_kpis array]
  okrIds: [okrs array]
head:
  - - meta
    - name: robots
      content: 'index, follow'
  - - meta
    - property: 'og:title'
      content: 'Process: [Process Name]'
  - - meta
    - property: 'og:description'
      content: >-
        [Process description]
  - - meta
    - property: 'og:image'
      content: '/images/blog/proc-[id-slug]-hero.png'
  - - meta
    - property: 'og:type'
      content: 'article'
  - - script
    - type: 'application/ld+json'
    - |
      {
        "@context": "https://schema.org",
        "@type": "HowTo",
        "name": "[Process Name]",
        "description": "[Process description]",
        "step": [
          {
            "@type": "HowToStep",
            "name": "Step 1: [Task Title]",
            "position": 1,
            "url": "https://growthflowengineering.xyz/blog/posts/[task-slug]"
          },
          ...
        ]
      }
---

Section 1: Hook — The Orchestration Gap (150-200 words)

Purpose: Explain why isolated tasks fail and why this specific sequence creates value.

Template:

markdown

# Process: [Process Name]

Most organizations have capable people doing individual tasks. The failure mode isn't **competence**; it's **handoffs**.

**[Process Name]** (`[Process ID]`) is the canonical workflow for [goal]. It orchestrates [Number] tasks across [Domains] to ensure that [Input] reliably converts into [Output].

Without this process, you get [Failure Mode - e.g., "leads that never close" or "revenue that never collects"]. With it, you get [Valuation Outcome].

::: tip Process Stats
- **Steps**: [Count]
- **Cross-Functional**: [List Domains, e.g., Marketing → Sales → Finance]
- **Primary KPI**: [First KPI Name]
- **Valuation Impact**: [Valuation Link]
:::

![Process visualization](/images/blog/proc-[id-slug]-hero.png)

---

Section 2: The Workflow Map (Visual)

Purpose: High-level visual of the sequence.

Template:

markdown

## The Workflow Map

```mermaid
graph LR
    %% Nodes
    start((Start))
    
    subgraph "Phase 1: [Domain 1]"
    S1[[Step 1: [Task Title]]]
    end
    
    subgraph "Phase 2: [Domain 2]"
    S2[[Step 2: [Task Title]]]
    end
    
    subgraph "Phase 3: [Domain 3]"
    S3[[Step 3: [Task Title]]]
    end
    
    end((End))

    %% Edges
    start --> S1
    S1 --> S2
    S2 --> S3
    S3 --> end

    %% Click events
    click S1 "/blog/posts/[task-slug-1]"
    click S2 "/blog/posts/[task-slug-2]"
    click S3 "/blog/posts/[task-slug-3]"

Orchestration Logic:

Step 1 ([Domain]): [Task Title]
Step 2 ([Domain]): [Task Title]
Step 3 ([Domain]): [Task Title]


---

### Section 3: Step-by-Step Walkthrough (500-800 words)

**Purpose:** Detailed breakdown of each step, focusing on **inputs, outputs, and handoffs**.

**Template:**
```markdown
## Execution Walkthrough

[For each step in `steps[]`:]

### Step [N]: [Task Title]

**Task ID:** [[Task ID]](/blog/posts/[task-slug])  
**Role:** `[role_signature]` (e.g., GFE-2.1.0)  
**Tools:** [Tooling list]

**The Work:**  
[Brief description of what happens in this step, derived from task description]

**Critical Handoff:**  
[Explain what this step produces that the NEXT step needs. E.g., "Produces a validated lead list that Sales uses in Step 2."]

::: info Deep Dive
How to execute this step: [[Task Title]](/blog/posts/[task-slug])
:::

---

Section 4: Role & Tooling Requirements (200-300 words)

Purpose: Define the "minimum viable pod" to run this process.

Template:

markdown

## Minimum Viable Pod

To run this process at scale, you need the following **Skill Signatures**:

| Role | Signature | Responsibility |
| :--- | :--- | :--- |
| **[Domain] Lead** | `GFE-[Level].x.x` | [Responsibility based on highest level task] |
| **[Domain] Operator** | `GFE-[Level].x.x` | [Responsibility based on execution tasks] |

### Tooling Stack

This process requires integration between:
- **[Tool Category 1]:** [Tools from steps]
- **[Tool Category 2]:** [Tools from steps]

*Note: GFE is tool-agnostic, but these categories are required.*

---

Section 5: Measuring Success (KPIs) (200-300 words)

Purpose: Link process execution to metric movement.

Template:

markdown

## Measuring Success

If this process is working, these KPIs will move:

[For each KPI in `primary_kpis[]`:]

### [[KPI Name]](/blog/posts/[kpi-slug])
- **Why:** [Reason this process moves this KPI]
- **Target:** [General benchmark or "Positive Trend"]

---

Section 6: ValuationOps Connection (150-200 words)

Purpose: Tie the workflow to enterprise value.

Template:

markdown

## ValuationOps Connection

This process anchors the **[ValuationOps Layer]** stack.

**The Value Chain:**
1. **Orchestration**: You connect [Domain 1] and [Domain 2] via this process.
2. **Velocity**: Cycle time decreases (e.g., Lead to Cash drops from 40 to 20 days).
3. **Efficiency**: [KPI] improves.
4. **Valuation**: [Valuation Link] becomes predictable, increasing the multiple.

::: warning Law 7: Processes → KPIs → Valuation
You cannot fix valuation directly. You fix the process, which moves the KPI, which drives the valuation.
:::

---

Section 7: Traceability Chain

Template:

markdown

## Traceability Chain

**ValuationOps Layer:** [[Layer Name]](/blog/posts/[layer-slug]) *(coming soon)*  

**Related OKRs:**
[For each OKR:]
- [[OKR ID]: [Objective]](/blog/posts/[okr-slug]) *(coming soon)*

**Component Tasks:**
[For each task in steps:]
- [[Task ID]: [Task Title]](/blog/posts/[task-slug])

---

Section 8: FAQ (5-8 Questions)

Template:

markdown

## FAQ

**Q: How long does this end-to-end process take?**  
A: [Estimate cycle time based on steps]

**Q: Can this be automated?**  
A: [Identify which steps are "Human" vs "Agent" ready]

**Q: Who owns this process?**  
A: [Role responsible for the end-to-end outcome, usually the highest level signature]

**Q: What is the most common failure point?**  
A: [Identify the riskiest handoff between steps]

---

2. WRITING GUIDELINES

Tone Strategy

Systemic & Orchestrational:

Focus on flow and handoffs, not just individual task execution.
Highlight interdependencies (e.g., "If Marketing fails Step 1, Finance cannot do Step 3").
Use terms like "upstream," "downstream," "bottleneck," "velocity."

Visuals:

The Mermaid diagram is critical. Ensure it accurately reflects the steps[] order.

3. IMAGE GENERATION

Subject Formula:

"Horizontal pipeline with distinct stages connecting [Domain 1] to [Domain 2]"
"Conveyor belt of value transformation"
"Relay race baton pass visualization"

Base Prompt:

Minimalist 3D relief illustration on off-white background. Muted teal (#1AA8A0) accent. Subject: [SUBJECT]. Composition: wide, horizontal flow, connected nodes, negative space. Typography: "[Process Name]" in clean sans, dark slate. Lighting: soft top-front. 16:9 aspect ratio.

Save To: docs/public/images/blog/proc-[id-slug]-hero.png

4. FINAL CHECKLIST

[ ] Process schema extracted
[ ] Mermaid diagram matches steps[]
[ ] All task links generated (even if 404 for now)
[ ] Role signatures aggregated
[ ] KPIs linked
[ ] Valuation logic explained
[ ] Hero image generated

End of Template

GFE Process Walkthrough Template ​

0. SCHEMA EXTRACTION GUIDE ​

Required Fields ​

Auto-Fetch Related Data ​

1. ARTICLE STRUCTURE ​

Frontmatter ​

Section 1: Hook — The Orchestration Gap (150-200 words) ​

Section 2: The Workflow Map (Visual) ​

Section 4: Role & Tooling Requirements (200-300 words) ​

Section 5: Measuring Success (KPIs) (200-300 words) ​

Section 6: ValuationOps Connection (150-200 words) ​

Section 7: Traceability Chain ​

Section 8: FAQ (5-8 Questions) ​

2. WRITING GUIDELINES ​

Tone Strategy ​

3. IMAGE GENERATION ​

4. FINAL CHECKLIST ​

GFE Process Walkthrough Template

0. SCHEMA EXTRACTION GUIDE

Required Fields

Auto-Fetch Related Data

1. ARTICLE STRUCTURE

Frontmatter

Section 1: Hook — The Orchestration Gap (150-200 words)

Section 2: The Workflow Map (Visual)

Section 4: Role & Tooling Requirements (200-300 words)

Section 5: Measuring Success (KPIs) (200-300 words)

Section 6: ValuationOps Connection (150-200 words)

Section 7: Traceability Chain

Section 8: FAQ (5-8 Questions)

2. WRITING GUIDELINES

Tone Strategy

3. IMAGE GENERATION

4. FINAL CHECKLIST