← Consulting Services

Service details

What each level of support includes and how to get started.

Start here

Request a Fit Call

A conversation of up to 60 minutes to understand what is happening and determine the right kind of support.

Request a fit call →
The fit call is for understanding and scoping the work. It does not include a full workflow review or written recommendations.

What we’ll work through

  1. Describe the challengeDescribe the operational issue, project, or decision you are facing—for example, a traffic process that is creating rework, a system change that is falling behind, or a new program launch with unresolved workflow questions.
  2. Walk through the current workflowWalk through how the work is handled today: who does each step, which systems or spreadsheets are involved, where information comes from, and where delays or errors occur.
  3. Define a successful outcomeClarify what a successful outcome would look like, such as cleaner handoffs, fewer manual steps, more reliable logs, or a launch plan the team can follow.
  4. Find the right level of supportIdentify whether the issue can be addressed in a focused working session, needs a broader workflow assessment, or calls for hands-on project support.
  5. Agree on the next stepAgree on a practical next step and what information would be needed to scope it.

Focused working session

Focused Working Session

One 60-minute virtual session to work through a single, defined question or problem. This is suited to a client who can explain the issue and provide enough background to discuss it productively.

Book a consultation →
Please note: The Focused Working Session does not include extensive document review, system access, software development, migration execution, or a full assessment. Those can be scoped separately.

What we’ll work through

  1. Prepare for the sessionBefore the session, the client provides a short description of the issue and relevant background, such as a process outline, sample schedule, system notes, or a description of how information currently moves.
  2. Map the process or decisionDuring the session, map the specific process or decision under discussion: the steps, people or teams involved, systems used, required inputs, and expected outputs.
  3. Examine the defined problemExamine a defined problem—for example, where a scheduling handoff is breaking down, why changes are not reaching the right team, or what needs to be considered before moving a workflow into a new system.
  4. Discuss practical optionsDiscuss practical options, tradeoffs, dependencies, and immediate actions the client can take.
  5. Receive a written recapAfterward, receive a brief written recap with the issue discussed, recommendations, and suggested next steps.

Structured review

Broadcast Workflow Assessment

A structured review of an agreed operational workflow or area. This is suited to a problem that crosses teams, systems, or multiple steps and needs more than a single-session discussion.

Request Assessment session
The assessment identifies and prioritizes improvements. Executing those improvements or conducting expanded technical analysis can be scoped separately.

What we’ll work through

  1. Define the area to reviewDefine the area to review—for example, program acquisition through scheduling and traffic setup; commercial inventory from order entry to log reconciliation; metadata from source through distribution; or a system migration affecting daily operations.
  2. Review how the work movesReview how the work moves today, including steps, handoffs, approvals, deadlines, exceptions, and the people or teams responsible.
  3. Examine relevant materialsExamine relevant materials agreed in advance, such as process documents, workflow diagrams, sample logs or schedules, issue lists, and system or data requirements.
  4. Identify delays and operational risksIdentify where duplicate entry, unclear ownership, late information, manual workarounds, data mismatches, or missing controls create delays or operational risk.
  5. Trace dependenciesTrace dependencies between teams and systems, including what information must be accurate and available before the next step can proceed.
  6. Receive the written assessmentDeliver a written assessment that summarizes the current workflow, key findings, risks or gaps, and prioritized recommendations.
  7. Review findings and next stepsReview the findings with the client and discuss suggested next steps, owners, and areas that may require a separate implementation scope.

Ongoing or project-based support

Implementation and Advisory

Hands-on support for an agreed project or operational need, from planning through rollout or ongoing operations. The work is defined in a custom proposal.

Depending on the engagement, support may include:

Request Advisory session

What we’ll work through

  1. Workflow and project planningWorkflow and project planning: define workstreams, milestones, owners, dependencies, decision points, and readiness criteria.
  2. System implementation or migrationSystem implementation or migration: organize operational requirements, coordinate teams and vendors, track configuration or data issues, and help prepare for cutover.
  3. Testing and validationTesting and validation: build or review test scenarios; check representative schedules, logs, inventory, program data, or metadata; document defects; and coordinate retesting.

Explore other support options

Not sure where to start?

Describe what is happening and we’ll identify a practical next step.

Ask a question →