---
title: How we work · Maps, decisions and quarterly cycles · Zero Fog
description: How Zero Fog maps process, data, systems, people and culture one unit at a time, then turns it into decisions in quarterly execution cycles.
image: https://www.zero-fog.com/hubfs/zf-share-how-we-work.png
---

[![Zero Fog](https://www.zero-fog.com/hubfs/Zero-fog-site/zero-fog-logo.png)](https://www.zero-fog.com/?hsLang=en)

[How we work](https://www.zero-fog.com/how-we-work?hsLang=en) [Situations](https://www.zero-fog.com/situations?hsLang=en) [Selected work](https://www.zero-fog.com/reference-cases?hsLang=en) [Perspectives](https://www.zero-fog.com/insights?hsLang=en) [About](https://www.zero-fog.com/about?hsLang=en) [Talk to us](https://www.zero-fog.com/contact?hsLang=en)

01 How we work

# See it clearly. Decide. Move.

Quarterly execution cycles of about 12 weeks, each ending with a decision.

ABOUT 12 WEEKS EACH · ONE CYCLE AT A TIMECycle 1 · ClarityHow does the work really run?Readout · decideCycle 2 · MomentumWhat do we change first?Readout · decideFurther cycles, if usefulEach one scoped and agreedMap each unitIntegrate what recursAgree and act

The discipline

## Strategic orientation, practiced with discipline.

See the whole system, find what binds, sequence, decide, and make it last. The same discipline has produced lasting results in very different environments, and it is what the AI era demands most.

 PACE AND COMPLEXITY OF THE ENVIRONMENTIntegrationP&C insurer6:1 mismatch → threevalue streamsExecution at scaleBroker-dealer−80% compliance cycle;AUM 2× in 3 yrsIntelligenceBrokerage~60% less manualoverheadVelocityStrategy firm6 weeks → 1.5 minutesNow: the AI eraYour next decisionOrientation before thetoolTHE DISCIPLINE · CONSTANT ACROSS EVERY ENGAGEMENTSee the whole systemFind what bindsSequenceDecideSustain

In a faster environment

## AI raises the pace. Orientation decides whether it pays.

Starting from the tool

1Pick an AI use case

2Pilot it in one team

3Hope the process around it adapts

4Scale what demos well

Starting from orientation

1Map how work and decisions really run

2Find the constraint that binds

3Place AI and automation where the map shows they pay

4Sequence it so the change lasts

Five lenses

## Process, data, systems, people and culture, on one flow.

Process

Steps, handoffs, waits, rework

Data

Where it's created, re-keyed, lost

Systems

What each step runs in, or doesn't

People

Roles, capacity, key people

Culture

Habits, workarounds, norms

 IntakeSet upDeliverReviewBillCloseProcessSteps, handoffs, waits, rework7 handoffs~5 day loopDataWhere it's created, re-keyed, lostkeyed 3×in a spreadsheetSystemsWhat each step runs in, or doesn'temail + ticketprinted review2 billing toolsPeopleRoles, capacity, key peopleone approver1 person knows itCultureHabits, workarounds, normsleader's own wayworkaround winsescalate by email

Anatomy of a map

## Every step, system, wait and finding, with what it affects.

12

steps

11

handoffs

3 + email, paper

systems in play

~10 days

waiting

5

findings

ClientUnit leaderTeamOperationsshared serviceFinanceshared serviceITshared serviceA1A2A3A4A5Request arrivesphone / emailCapturesdetailsemailRe-keys detailsintake formChecks andclearscore systemGo ahead?Prepares termsown templateSets up accountbilling systemGrants accessby ticketDelivers workdocument systemReviews outputprinted copyInvoicesbilling systemPayscheck / online~3 days~2 days~5 daysA1 Details keyed 3 times, in 2 systemsClient · VelocityA2 Terms differ by leaderAudit · ClientA3 Setup by ticket, in 2 systemsCost · VelocityA4 Paper review adds ~5 daysVelocity · ClientA5 One person approves adjustmentsAudit · Financial

Manual re-entryWork waits in loopsControls depend on peopleSame task, done differentlySteps a system could take

Illustrative map of one unit. Shared services sit in the green lanes. Amber tags mark manual tools; amber pills mark where work waits.

Inside a cycle

## One unit at a time, with its leader. Shared services once.

 ONE QUARTERLY EXECUTION CYCLE · WEEKS123456789101112MobilizePilot unitwith its leaderUnit 2same frameUnit 3Shared servicestalked to onceIntegrate and read out

Integrate

## What recurs across units becomes a shared recommendation.

1 · MAP EACH UNIT2 · INTEGRATE WHAT RECURS3 · AGREE AND ACTUnit A · pilotA1A2A3A4A5Unit BB1B2B3B4B5Unit CC1C2C3C4Manual re-entry3 units · A1, B1, C1Work waits in loops2 units · A4, B2Controls depend on people3 units · A5, B4, C4Same task, done differently3 units · A2, B3, C2Steps a system could take3 units · A3, B5, C3R1 · Capture onceOne record feeds every systemR2 · Move reviews into the systemOn screen, with turnaround standardsR3 · Centralize controlsTwo-person approval, evidencedR4 · Shared standardsAdapted by each unitR5 · Automate routine stepsUsing systems already in place

What's specific to a unit stays with its leader. What recurs is a candidate to standardize, centralize or automate.

Decide

## Every cycle ends in a decision, and starts the next one sharper.

01

Frame

What is really being decided, and what must be true for it to be right.

02

Options

Two or three paths, with the trade-offs laid out, not one answer.

03

Sequence

What has to move first, so the rest moves faster.

04

Decide

Readouts are decision meetings with leadership, led by the founder.

 Framethe decisionMapthe evidenceShape2–3 optionsSequencewhat moves firstDecideat the readoutActwith ownersMeasurewhat changedEvery cycleends in a decisionand starts the next one sharper

Working principles

### Founder-led

Every scope, session and readout.

### Vendor-neutral

No reselling, no vendor fees; affiliations disclosed.

### Confidential

Agreement first; no client files needed.

### Yours to keep

You own every map, standard and roadmap.

Talk to us

## Tell us the decision in front of you.

[Talk to us](https://www.zero-fog.com/contact?hsLang=en)

[![Zero Fog](https://www.zero-fog.com/hubfs/Zero-fog-site/Transparent%20Logo_white%20logo%20side.png)](https://www.zero-fog.com/?hsLang=en)

Founder-led advisory for consequential decisions.

Site

[How we work](https://www.zero-fog.com/how-we-work?hsLang=en)  
[Situations](https://www.zero-fog.com/situations?hsLang=en)  
[Selected work](https://www.zero-fog.com/reference-cases?hsLang=en)  
[Perspectives](https://www.zero-fog.com/insights?hsLang=en)  
[About](https://www.zero-fog.com/about?hsLang=en)

More

[Partners](https://www.zero-fog.com/partners?hsLang=en)  
[Rejoyce](https://www.rejoyce.ai)  
[Talk to us](https://www.zero-fog.com/contact?hsLang=en)

Contact

hello@zero-fog.com

 © 2026 Zero Fog, LLC. All rights reserved. · Massachusetts, USA

[Privacy](https://www.zero-fog.com/privacy?hsLang=en) · [Terms](https://www.zero-fog.com/terms?hsLang=en) · [LinkedIn](https://www.linkedin.com/company/zero-fog)

```json
{
  "@context" : "https://schema.org",
  "@type" : "Service",
  "description" : "Engagements of about 12 weeks per cycle that map process, data, systems, people and culture one unit at a time, integrate what recurs, and end in a leadership decision.",
  "name" : "Quarterly execution cycles",
  "provider" : {
    "@id" : "https://www.zero-fog.com/#org"
  },
  "serviceType" : "Strategy and transformation advisory",
  "url" : "https://www.zero-fog.com/how-we-work"
}
```