Choose the edges
Decide what enters, what leaves and which dependencies remain outside your scope.
A NOTEBOOK ON
HOW THE WORK WORKS
INDEPENDENT WORKFORCE READING / ISSUE 01
A process can look simple on paper and feel tangled in practice. Read the queues, returns, measures and decisions that shape an ordinary workday.
Shift Systems Review is a practical reading room for people curious about hospital work as a system. Start with a small nonclinical example, learn what the observation can support, and keep local authority and safety requirements in view.
Notice the system
A request that leaves one desk may still be waiting to enter another. A quicker action may create more checking elsewhere. An average may hide a changing mix of work. These are useful questions to understand before proposing a solution.
Decide what enters, what leaves and which dependencies remain outside your scope.
Ask why work comes back without turning a process observation into a verdict on a colleague.
A change can help one outcome and make another harder. Keep both visible.
Try an invented model
ORIGINAL INTERACTIVE WORKBENCH
Move fictional paper cards through two office stations. Compare one-card transfers with a larger batch. See how the first completion, final completion and average can tell different stories. Use invented numbers only; no workplace or personal records are needed.
All inputs must be whole numbers. Cards: 2–12; each station: 1–30 minutes; batch: 1–6 and no larger than the card count; transfer: 0–15 minutes.
Six cards start at time zero. Station A takes 2 minutes per card, B takes 3, and each transfer takes 1 minute. A dedicated courier transfers each completed batch while A continues working. B processes cards sequentially as they arrive. With one-card transfers, completion times are 6, 9, 12, 15, 18 and 21 minutes: the mean is 13.5, using six transfers. With batches of three, completion times are 10, 13, 16, 19, 22 and 25: the mean is 17.5, using two transfers. Fewer transfers and faster completion are different goals.
For each batch, release time equals the last card’s A-finish time. Arrival at B equals the later of release time and the preceding transfer’s finish, plus transfer time. Each card finishes B at the later of its batch arrival and the preceding card’s B-finish, plus B processing time. The mean is the sum of card completion times divided by card count. A final incomplete batch transfers without waiting for extra cards.
Assumptions: one worker at each station, one separate courier, no return travel, no setup, no interruptions, no variation, no priorities, unlimited waiting space, all work available at time zero. This is an original arithmetic exercise, not a validated model of any hospital. It cannot determine staffing, clinical decisions or employee performance.
Method context: IHI’s Model for Improvement explains why change ideas need a defined aim, measures and testing. The calculations and fictional scenario here are original and are not IHI or Northwell tools. Source checked October 8, 2026. Inputs stay in this page’s memory; no submission, tool storage or URL change. Your browser may independently restore form values.
Read the collection
Original explanations, fictional examples and dated public sources. The articles are a starting point for understanding, not operating instructions for a hospital.
14 articles
See the system
A process boundary makes a workflow question answerable. Practice choosing a start and finish without mistaking a narrow view for the whole system.
Read the article : Draw the Boundary Before You Improve the ProcessSee the system
A useful process map shows waiting, choices, and return loops. Learn to map one path without quietly turning a description into a redesign.
Read the article : Map the Work That Happens Between the BoxesFlow and delay
Use a fictional two-stage card exercise to see why faster work and faster flow are different claims, and why batch size has tradeoffs.
Read the article : Why a Finished Item Can Still Be WaitingFlow and delay
Measure the boundary between two stages without mistaking a sent timestamp for usable work at the next stage.
Read the article : A Handoff Is Not Complete Just Because It Was SentFlow and delay
Repeated work can hide inside a reassuring completion total. A fictional print exercise shows how to count returns without labeling every check as waste.
Read the article : Count the Return Trip, Not Just the Finished ItemFlow and delay
A small backlog ledger explains why completed work cannot reveal all the work that arrived, and why daily totals can hide a timing mismatch.
Read the article : Demand, Capacity, and Completions Are Three Different NumbersRead the evidence
Two fictional processes share the same mean and very different waits. Learn what an average leaves out before explaining a change.
Read the article : The Average Can Stay Still While the Experience ChangesRead the evidence
A denominator, a start event, and a missing-data rule can change the result. Build a small fictional measure specification before calculating a percentage.
Read the article : Write the Definition Before You CountRead the evidence
A time-ordered chart can reveal what a before-and-after average hides. Check the measure, intervals, annotations, and comparison before deciding what it means.
Read the article : Read the Time Axis Before You Read the Improvement ClaimRead the evidence
A balancing measure asks whether an apparent gain moves effort, errors, or delay elsewhere. Start with a concrete mechanism rather than a long dashboard.
Read the article : Check What a Faster Process Might Make HarderTest and sustain
A short test still needs a clear boundary. Practice separating the learning question, allowed action, stop rule, and next decision.
Read the article : Design a Small Test That Stays Inside Its PermissionUnderstand the system
Speed at one step can hide extra checking, interruptions, and cleanup elsewhere. Examine the whole fictional sequence before calling it easier.
Read the article : A Faster Task Can Still Make the Workday HarderTest and sustain
A promising trial may depend on temporary help. Use a fictional failure drill to uncover what would need ownership, support, and review.
Read the article : Keep an Improvement Working After the Trial EndsStart with a question
A proposed board, form, or checklist is already a solution. First identify the exact decision or transition that needs to be understood.
Read the article : Choose an Improvement Question Before Choosing a FixKnow the boundaries
LIJ refers here to Long Island Jewish Medical Center. A public Northwell careers page for LIJ team members refers to career resources on myExperience. That establishes the public connection between the names; it does not establish the current contents or navigation of an employee account. The event advertised on that page is not offered here as a current opportunity.
This publication is not affiliated with, sponsored by or operated by Long Island Jewish Medical Center or Northwell Health. Subject names identify the subjects of the articles, not the publisher. This publication has no sign-in form, employee-account access or official support role. For workplace requirements, personal employment matters or urgent concerns, use the verified route supplied by your employer.
Our examples use fictional office cards, requests and work steps. They do not describe LIJ’s operations, staffing levels, compensation or performance. Read the editorial approach and privacy notice before using the publication.
Public source reviewed October 8, 2026. This is a review date, not an event date, policy effective date or employee-account test.