Production judgment / Creative operations / AI-aware systems

PRODUCTION SYSTEMS

Your team is good. Your system is the problem.

Most creative companies between 20 and 200 people run on a few senior people who absorb everything: every unclear decision, every orphaned task, every client question with no owner. It works until it doesn’t. That isn’t a talent problem. It’s an operating problem, and it’s fixable.

When meaning gets lost between rooms, senior people become the patch.

The failure usually happens between rooms.

Most teams can make strong work. The drag appears when pressure crosses a handoff without translation, approvals preserve optionality instead of creating consequence, and nobody is sure which version, decision, or constraint is real.

High accountability plus incomplete authority is where production stress becomes structural. Better tools do not solve that on their own.

Common failure modes
  • Vague briefs and hidden pressure
  • Notes without translation
  • Approval without consequence
  • Unclear decision rights
  • Too many live options
  • Plan/version drift
  • Tool sprawl
  • Human memory as infrastructure
  • AI without rules
  • Founder dependency

Frame, translate, decide, deliver, learn. Then prove the loop holds.

A decision system, not another checklist.

The model is simple: frame the real problem, translate pressure without losing meaning, name the decision, deliver against current conditions, and return what the team learns to the next cycle. The engagement turns that loop into a working operating rhythm.

  1. Frame
  2. Translate
  3. Decide
  4. Deliver
  5. Learn
01

Diagnose

Map how work enters, where meaning changes, who decides, and what stalls.

02

Design

Define decision rights, translation points, review gates, tooling roles, and required artifacts.

03

Install

Build the templates, gates, current-version signals, AI assists, and routines the team will actually use.

04

Verify

Pressure-test the system against live work, difficult approvals, changed conditions, and edge cases.

05

Transfer

Document the logic, train the team, and leave useful memory so the system works without me in the room.

Focused engagements for teams that need sharper decisions and stronger production machinery.

Engagements

Start with an audit. It ends with a clear decision: install, partner, or stop. No implementation is hidden inside it.

ENTRY POINT
Duration: 2 weeks

Production Systems Audit

For: founders, agency principals, and heads of production who know time is leaking but need the failure named.

A decision-rights map. A source-of-truth map. Your top five failure loops, with what each one costs. A 90-day operating plan.

Outcome: a clear view of where the system is leaking and what to fix first.

$7,500

Duration: 4–6 weeks, fixed scope

Systems Install

For: teams that already know what’s broken and have the authority to change it.

A working system, configured to your tools: intake, project and client trackers, an owner/date/blocker cadence, change-order rules, and an AI use policy with real gates. Training, then handover.

Outcome: an operating rhythm your team runs without another layer of management.

$20k–$30k

Type: monthly, 6-month minimum

Production Systems Partner

For: companies that need senior operating judgment without a full-time hire.

Operating model, producer development, portfolio cadence, senior escalation, and keeping the system honest as you grow.

Outcome: the system keeps working as the work changes, without a new daily dependency.

$5k–$10k / month. Two partners at a time.

Operator experience, published thinking, public systems, and enough pattern recognition to see the failure mode early.

Built from production scar tissue, not theory.

Led by Bill Anastas, a production and creative operations executive with 20+ years across digital, interactive, VFX, social, experiential, and campaign production for Google, Sony, Netflix, Warner Bros, Snap, FX, Philips, and more. I’ve been the person absorbing all of it. I know what it costs, and I know which parts can be designed away.

400+ artists

crewed and scheduled across simultaneous features at Imageworks

30+ campaigns

global theatrical work at Sony Pictures Interactive

20-person org

EPs, producers, and PMs unified into one practice as Head of Production at Monks

Ideas in public

Production judgment, in writing and in the ear.

I publish the thinking behind this work through essays at blog.banast.as and The Decision Layer, a short-form podcast about production, taste, technology, and the choices that make work real.

I build, not just advise. Public systems include archive, reference, listening, collection, and utility products, including ArtBellArchive, OneSheet, SecondTrack, OverBlack, and related collection sites, plus paid Mac apps like Blit and Rune.

Executive Producer at kissd; formerly Monks, Sony Pictures Interactive, INDG, AvatarLabs, hi5, BLKBX, and Imageworks. Member, Producers Guild of America.

The line matters. Improve the machine; do not become the machine.

What this is not.

  • Not embedded project management.
  • Not outsourced production support.
  • Not another standing meeting.
  • Not another dashboard nobody maintains.
  • Not AI demos. The rules that make AI safe on real client work.
  • Not replacing broken process with personal heroics.

The work is designed to improve the production system, not become the production system. Diagnose the machine, install better loops, and leave the team with artifacts they can use without me in the room. If you need a producer, hire one. I’ll help you hire the right one.

Start small enough to see clearly. Then fix the leak.

Start with an audit.

If your team is losing time to handoffs, untranslated pressure, decision latency, version drift, or status archaeology, start with a two-week audit. It’s enough to see where the system is losing time or meaning and what should change first.

Send a note with the production system that is leaking. I’ll reply with a few questions about the workflow, failure modes, decision rights, and whether an audit is the right starting point.

Los Angeles. Remote-first. Two partner engagements at a time.