Arkanza Marketing — Roles & Operations

Roles & Operations System — Charter

5 menit baca

Roles & Operations System — Charter

Entry point for the Roles & Operations sub-project: turn each position’s JD into a connected operating system — JD → task breakdown → SOPs → worksheet → templates — wired into shared Knowledge and Tools, so the team has structured flow, a clean RACI, and clarity.

Point the Cowork sub-project at this same workspace folder. This vault (Marketing Knowledge Base/) stays the single source of truth. The sub-project is a focused lens (its own instructions + build discipline), not a separate KB.

1. Architecture decision (settled)

  • Overlay, don’t rebuild. Extend the existing domain vault with a role/ops layer. Rejected: reorganizing into five type-folders (fragments shared knowledge) and a fresh vault (double maintenance + drift).
  • One vault. Obsidian wikilinks only resolve inside one vault. The sub-project points at this folder; nothing moves.
  • Knowledge is atomic; artifact-type is a tag, not a folder. One node per concept, linked from many places. The five buckets (Knowledge · Tools · SOPs · Worksheet · Template) are views via tags/MOCs, not physical copies.
  • General vs per-position = shared nodes vs role-hub links. “General” content lives once in the domain folders / General indexes; each role hub links to the shared nodes it needs plus its own role-specific nodes.
  • Two format layers. Markdown nodes are the linkable source of truth; polished docx/xlsx are generated published deliverables for the team.

2. The node model

KNOWLEDGE ─┐                 ┌─ WORKSHEET (live working station)
TOOLS ─────┼──► SOP (per task) ──► produces/uses
TEMPLATE ──┘                 └─ links up to ► ROLE HUB ► JD + TASK BREAKDOWN
  • Role Hub (09_Roles_Operations/<Role>/_<Role>_Hub.md) = the MOC for one position. Links to: JD, Task Breakdown, every SOP, the Worksheet, Templates, and the shared Knowledge + Tools nodes the role uses. This is the RACI-at-a-glance page.
  • SOP links down to the Tools it uses, the Knowledge it assumes, the Worksheet it writes to, and any Template it fills. Every SOP maps to a task line in the breakdown.

3. Vault map (target)

Marketing Knowledge Base/            ← the ONE vault
  01–08_*/                           ← existing domain knowledge = "General Knowledge"
  05_Playbooks_SOPs/                 ← General SOPs live here; role SOPs cross-linked
  07_Performance_Data/               ← KPI_Definitions (single source for KPI targets)
  09_Roles_Operations/               ← NEW — this sub-project
      _Roles_System_Charter.md       (this file)
      _Roles_MOC.md                  (index of all role hubs + build status)
      _Standards/                    (acceptance specs + templates — see §5)
      Digital_Advertiser/            _DA_Hub · JD · Task_Breakdown · SOPs/ · Worksheet · Templates/
      Superoperator/
      Marketplace_Affiliate_KOL/     (Firyal & Irfan — shared JD, per-PIC notes)
      AI_Content_Creator/            (Surya)
      Marketing_Lead/                (Anton)
  10_Tools/                          ← NEW — one node per tool (Kalodata, Claude, Sheets…)
      _Tools_MOC.md
  99_Meta/_Templates/                ← existing template library (General Templates)

Published deliverables (docx JDs/SOPs, xlsx worksheets) are generated from the nodes and kept inside the vault — in each role folder or a vault-level _Published/ folder — so the project stays self-contained. The DA reference docx already live in 09_Roles_Operations/Digital_Advertiser/.

4. Conventions

Frontmatter (every node): title, type, role (or general), status, tags, created. Type tags: #type/knowledge #type/tool #type/sop #type/worksheet #type/template. Role tags: #role/da #role/superop #role/ms-kol #role/aicc #role/lead (+ #scope/general for shared nodes).

Linking rules:

  • SOP must link every Tool, Knowledge node, Worksheet, and Template it references.
  • Role Hub must link JD, Task Breakdown, all SOPs, Worksheet, Templates, and used shared nodes.
  • Shared knowledge is never copied into a role — it’s linked. If it’s used by ≥2 roles, it’s General.

5. The standard (acceptance spec per artifact)

To be finalized in the Foundation chat, each as a reusable template in _Standards/:

  • JD — matches JD_Digital_Advertiser format; role-generic; scope via “PIC yang ditugaskan”; KPI targets pull from KPI_Definitions; pending items flagged inline.
  • Task Breakdown — cadence-grouped (Harian · 2–3 Hari · Sesuai Kebutuhan · Mingguan · Bulanan); every task line maps 1:1 to an SOP; open items flagged.
  • SOP node — trigger/cadence · inputs · step-by-step · tools used · knowledge assumed · worksheet written to · template used · output/definition-of-done · escalation.
  • Worksheet — the live working station (Google Sheets): columns, validation, who fills, cadence.
  • Template — reusable blank doc/sheet (brief, log, report) the SOP fills.
  • Role Hub — the MOC wiring all of the above + RACI row for the role.

Team-facing text in Bahasa Indonesia; discussion in English.

6. Build tracker

Moved. The build tracker + role-hub index now live in a single home: _Roles_MOC (status per position, cross-project pending, and the five-bucket view). Update it — not this charter — as artifacts ship. This charter holds the architecture and standard; the MOC holds status.

7. Chat-slicing plan (context discipline)

One bounded deliverable per chat; this charter + the build tracker carry state so no chat re-derives context.

  1. Foundation (next): create 09_Roles_Operations/ + 10_Tools/ scaffold, author the _Standards/ templates + conventions, seed the Tools index. DA = worked example.
  2. Per position (finish one fully before the next):
    • a. JD + Task Breakdown + missing-scope audit
    • b. SOPs (batch if the task list is long)
    • c. Worksheet + Templates + Role Hub + Knowledge/Tools links
  3. DA is through 2a. Remaining for DA: 2b, then 2c.

Immediate next: run the Foundation chat.

Tampilan Grafik

Tautan Balik