EOS Module 04

Process That Elevates Work: Core Processes Under an American System Filter

Learn · Diagnose

1 · Learn
Slide deck
Open the deck
2 · Diagnose
One question at a time
Start the diagnostic
3 · Next
No EOS agentic packaged kit available. Start a kit build, or a Fit conversation.

PDF hosted on the source library; open/download if the embedded view does not load in your browser. Download / open PDF

Joshua Konkle · Operator

Posture: American System / Hamiltonian filter on native EOS tools. Not a claim that standard EOS practice is Hamiltonian.

1. Diagnostic Checklist

Use with leadership or alone. Prefer facts over aspirations. Complete in the guided checklist (Yes / Partially / No + short note). No essay required.

Process as documented and followed

[ ] Core processes are identified, documented simply, and actually followed — not only posted once and ignored.
[ ] Level 10 uses process clarity when something breaks (not only “try harder” or “hire faster”).

Elevation vs. pure elimination

[ ] Process improvement aims to elevate work into higher-skill design, maintenance, or system roles — not only to cut hours or headcount.
[ ] Team can state the Elevator logic: when the dedicated operator role disappeared, value moved into design, controls, and upkeep — not into “cheaper operators forever.”

Failure mode (process that rents weakness)

[ ] Failure mode check: No core process is designed so that critical steps only work with permanent short-cycle temporary or visa labor coverage.
[ ] Where short-cycle temporary or visa labor appears, it is labeled bridge, not permanent process design.

One-line hand-offs

[ ] At least one process fix points at a capacity metric (Module 3) or a seat family (Module 5) — this companion does not redesign Scorecard or People.
[ ] Process Rocks (if any) stay owned in the Rocks system (Module 2).

Anchors

[ ] Team can state: we either design processes that build lasting capability or we design processes that depend on rented capacity.
[ ] Posture: Operating in the United States is not workforce-neutral. Seat design either builds lasting productive capacity or rents weakness.

Diagnostic result (one line): Biggest gap — undocumented process, improvement that only cuts hours, critical steps that depend on permanent short-cycle temporary or visa labor coverage, or Level 10 that never uses process in IDS?

2. 90-Day Outline (Free Execution Scaffold)

This is a starting outline, not a full managed engagement. Paid implementation support (e.g. 90-Day Sovereign Capacity Sprint) sits behind deeper facilitation and cross-module integration.

Days 1–30 — Diagnose

Action	Output
Name 1–2 core processes that touch critical delivery or knowledge	Process list
Map where steps depend on short-cycle temporary or visa labor coverage	Bridge vs permanent labels
Failure mode: Flag any critical step that only works as permanent short-cycle temporary or visa labor design	Explicit risk list
Note whether recent “improvements” elevated skill or only removed hours	Elevation vs cut notes

Days 31–60 — Redesign

Action	Output
Document one core process simply (followable, not a binder)	One-page process
Redesign one step so work elevates (skill, knowledge retention) rather than only shrinks	Before/after step
Remove or time-box any permanent short-cycle temporary or visa labor assumption on a critical step	Design choice noted
One-line link to a capacity metric or seat family	Hand-off note only

Days 61–90 — Execute & Embed

Action	Output
Run the documented process in live work; IDS breaks in Level 10	Follow-through notes
Keep the elevated step and bridge-only short-cycle temporary or visa labor coverage for next quarter	Locked process choice
Hand off measurement to Scorecard (Module 3) and seats to People (Module 5)	Short hand-off list

Success check at day 90: One core process is documented and followed; at least one step elevates work rather than only cutting hours; no critical step remains on unchallenged permanent short-cycle temporary or visa labor design — so process builds lasting productive capacity rather than rents weakness.

3. Soft Cross-Reference (BMC)

BMC Module 4 (Value Streams / Lean under a Hamiltonian filter) applies the same elevation lens in value-stream language. Preferred path for teams new to the filter: free BMC series first, then EOS. Teams already running EOS may start here and use BMC diagnostics alongside — no mandatory sequence.

4. What This Companion Is / Is Not

Is	Is not
Free diagnostic + 90-day scaffold (guided checklist compatible)	Full lean program or Scorecard/People rewrite
Process-centered under a Hamiltonian filter	A rewrite of EOS or a claim that EOS = American System
Funnel toward paid execution support if useful	Required purchase to use the checklist

Joshua Konkle · Operator · @7SwanSwimming · 512-423-5448 · joshua@digitalknowledge.net

Fit conversation