Manage Collins by outcomes, not task volume
2026-07-14 · Recommended operating plan · Collins is part-time at about 20 hours/week
Objective
Give Collins clear ownership without turning Akash into a full-time task manager.
Why it matters
Collins should remove build work from Akash and make client launch repeatable.
Akash needs to
Lock one priority and pause the conflicting Day-1 pile — 5 minutes.
If ignored
A 20-hour week gets split across five lanes; nothing reaches a tested handback.
Lock one six-week priority: client onboarding and campaign launch needs you
- Primary project: P-1377 — automate client onboarding and campaign launch by August 23.
- Capacity: 15 hours/week on the active work package, 3 hours/week on one bounded creative pilot, 2 hours/week on reporting, QA, and handoff.
- Work in progress: one major work package at a time. Collins may finish early and pull the next package; he does not start three packages halfway.
- Park for now: the orphaned Day-1 newsletter, carousel, B-roll look-lock, ad-pack, and split-test tasks. Reintroduce one creative pilot only after Friday's onboarding proof.
★ Recommended: tell Collins, “Your primary outcome is the onboarding runner. Finish the current proof before pulling another build. Creative work is one four-hour pilot per week until the runner is stable.”
Run one board and one communication rhythm no action
| When | What happens | Akash's job | Collins's job |
|---|---|---|---|
| Monday | One work package becomes Active. | Set the outcome, deadline, boundaries, and acceptance check. | Confirm the plan, risks, and first proof point. |
| Daily | 20-minute check-in during the ramp; 4 PM Slack report. | Unblock or re-aim. Do not add side quests in chat. | Post shipped links, proof, blocker, Akash ask, and tomorrow's first move. |
| Friday | Demo and accept/reject the package. | Say accepted, needs fixes, or cut. Give one reason. | Demo the real artifact and tests; update the board. |
| After week 2 | Reduce meetings to Monday/Wednesday/Friday if reports are clean. | Protect sales time. | Escalate after 30 blocked minutes with a Loom and exact ask. |
Use only five states
- Queued — not started.
- Active — the one major package in progress.
- Blocked — exact missing input, owner, and unblock step are named.
- Review — proof is linked; Akash can accept or reject.
- Done — Akash accepted it against the written completion check.
Use this work-package contract every time no action
- Outcome: one sentence describing what exists when finished.
- Deadline: one date, fixed when assigned.
- Inputs: links, access, examples, and the person who supplies each.
- Boundaries: what Collins may change; what remains Akash-only.
- Definition of done: observable checks, not “work on” language.
- Proof: artifact link, test result, screenshots/read-back, rollback, and a five-minute-or-shorter Loom.
Acceptance rule: no proof link means not done. A build that works once but cannot be rerun or undone is not done.
Delegate these work packages next, in this order no action
| Order | Work package | Due | Definition of done |
|---|---|---|---|
| 0 | Finish setup and confirm the work clock | Jul 14 | Collins has Slack, GitHub, read-only brain, GHL test, and Meta read access by invite/seat; the meeting time is written in both time zones; his first Slack report lists every green/red access item and his first deliverable. |
| 1 | Shadow one manual onboarding | Jul 17 | One current-state map shows every input, click, owner, output, handoff, and likely failure; a ranked automation backlog and test plan are attached; Collins gives a ≤5-minute walkthrough; no production automation is changed. |
| 2 | Build the validated client manifest | Jul 22 | Signed-and-paid client facts become one validated record; missing fields fail clearly; duplicate search runs first; two reruns create no duplicate client, task, or workspace; test values are read back and compared; rollback is written. |
| 3 | Automate the GHL setup in test | Jul 31 | The correct location/snapshot, client facts, bot fields, calendar, stages, and safeguards are configured; read-back shows no blanks, placeholders, broken merge fields, or cross-client data; every outside change is logged with an undo step. |
| 4 | Prove the lead and booking path | Aug 5 | A test to Akash's phone ending 5477 produces exactly one contact, one scripted reply, one owner, one booked call, and one next action; STOP/DND/quiet hours work; cancellation suppresses later messages; browser/CAPI events are visible without duplicate conversion count. |
| 5 | Stage the first campaign Paused | Aug 12 | Correct offer, market, creative, copy, destination, tracking, naming, consent, geography, and exclusions pass QA; mobile previews and lead routing are proven; every Meta object remains Paused; a one-screen launch brief gives Akash the proposed budget, proof, and rollback. |
| 6 | Run the first real client handoff and hand back the system | Aug 23 | The full runner passes twice in test with zero duplicates; Akash separately approves real access and spend; the live client has a launch proof pack and six-week scorecard; the runbook, failure modes, owners, rollback steps, manual touches, onboarding time, and next improvement plan are complete. |
Keep creative work small until the onboarding proof is accepted no action
- One four-hour pilot per week: never “run the whole content machine” alongside the main build.
- First pilot: map the seven creative lanes and produce one reusable B-roll-based sample in three chosen formats.
- Done means: source/rights recorded; editable source and final files linked; template/repeatability note exists; mobile QA passes; cost and minutes per asset are recorded; nothing is published or given spend without Akash's gate.
- Automation rule: Collins may edit manually. Automate only after the same format repeats enough that setup time will be recovered.
Measure whether delegation is actually working reference only
| Measure | Healthy signal | Bad signal |
|---|---|---|
| Weekly acceptance | One package accepted most Fridays. | Many “almost done” items and no demo. |
| Rework | One fix pass or less after review. | Same acceptance miss repeats. |
| Blocked time | Blockers surfaced within 30 minutes; Akash answers within one business day. | Collins waits silently or Akash becomes the hidden bottleneck. |
| Akash time removed | Manual onboarding touches and build hours fall each week. | Collins's work creates more review/admin than it removes. |
| Proof quality | Another builder can rerun and undo the work. | Only Collins knows how it works. |
Why the existing board needs cleanup reference only
- The current Builder Board still says the daily production machine is Collins's first card and places onboarding later.
- The newer, assigned job packet says automated client onboarding and campaign launch is Collins's first job.
- The live brain contains several Jul 14 Collins tasks with no project attached, while the six onboarding packages are correctly attached to P-1377.
- Older content publish-pack tasks remain open even though the role was refocused.
Do not manage around this conflict verbally. Once Akash locks the priority, update the board and task ownership so Collins sees one truth.
Sources checked reference only
- Assigned onboarding and campaign-launch job packet.
- Collins's first-six-weeks start plan.
- Current Builder Board.
- Brain project P-1377 and its six Collins-owned work packages, read 2026-07-14.
- July 13 Collins/Akash onboarding meeting transcript stored in the brain.
Permanent home:
01-Projects/St_Pierre_Digital/Recruiting/Collins-Onboarding/collins-delegation-management-plan-2026-07-14.html · Owner: Akash · Operator: Collins · Primary project: P-1377.