Steelworth
OPERATING PRACTICES

A business that runs on a rhythm, not on heroics.

Before any technology, a business needs a cadence of reviews, one set of numbers, and a named owner for each. This is what we install first, and what everything else stands on.

THE OPERATING RHYTHM

Four loops, from this morning to next year.

Each loop looks at its own numbers and makes its own decisions. Problems move up only when the loop below cannot solve them.

  1. 1

    Start every day at the board

    Daily management

    A short stand-up in front of yesterday's numbers. What missed, who owns it today, and what needs help from above.

  2. 2

    Clear the week's problems once a week

    Weekly operations review

    The problems the daily board could not fix. Capacity for next week, the risks in front of it, and the decisions the team needs.

  3. 3

    Compare the plan to what happened

    Monthly business review

    Plan against actual, one page per area. The three numbers that moved, why they moved, and who owns the fix. Decisions are written down with a name and a date.

  4. 4

    Agree one number for the months ahead

    Sales and operations planning

    Demand, supply and money on one plan, three to eighteen months out. Sales, operations and finance leave the room with the same number.

  5. Every problem has a meeting where it gets decided. Every meeting has a number it looks at.

THE DAILY MANAGEMENT SYSTEM

Inside the daily loop.

The daily board is where the rhythm is won or lost. Five parts make it a system rather than a meeting.

  • 01

    The board

    Yesterday's numbers against the target, in green and red, on a wall where the team works. No login, no report, no waiting.

  • 02

    The stand-up

    Same time, same place, standing, short. Three questions: what missed, who owns it today, what needs help from above.

  • 03

    The tiers

    Team boards feed an area board, which feeds a site board, all before lunch. A problem the team cannot fix reaches someone who can the same day.

  • 04

    Leader standard work

    Leaders have a written routine too: the boards they visit, the checks they make, the questions they ask. The system runs when the leader is away.

  • 05

    The problem sheet

    Anything red for more than a day gets one sheet: the problem, the cause, the fix, the check, one owner. It stays on the board until the check passes.

Improvements erode without this. The daily system is what keeps a fix fixed.

DATA-DRIVEN DECISIONS

Self-service data works in this order.

Dashboards are the last step, not the first. Most businesses we meet have the dashboards and are missing the three steps before them.

Where most businesses we meet stand: the dashboards exist, the definitions and the owners do not.

  • 01

    One definition per number

    Every number the business runs on has a written name, a formula, a source, and the date it was last checked. Two people who look it up get the same answer.

  • 02

    One owner per number

    The owner is the person who explains the number in the monthly review, not the person who built the report. If nobody can be named, the number is not ready to run the business.

  • 03

    Access in tiers

    Everyone sees the curated views. Analysts work in the governed datasets underneath. Engineers hold the raw sources. Each tier can trace its numbers to the one below.

  • 04

    A decision log

    What was decided, from which number, by whom. Next month's review opens by checking whether last month's decisions did what they were meant to.

LEAN BUSINESS PRACTICES

The habits that keep the rhythm honest.

None of these is a project. Each is a habit the cadence above depends on, and each one has a page or a service behind it.

  • Standard work

    The one best way to do a task, written down, and followed until someone improves it. Without it there is nothing to measure against.

    Process Excellence & Operations
  • Visual management

    The board on the wall shows the state of the work without a meeting. Green means on plan. Red means a name and a next step.

    The Process Maturity Model
  • The four gates before technology

    Eliminate the steps nobody needs. Simplify what is left. Standardize it. Only then automate it.

    The ESSA principle
  • Problem solving on one page

    The problem, the cause, the fix and the check, on one sheet, owned by one person, reviewed at the board.

    The two-week diagnostic
WHERE AI COMES IN

AI reads the same numbers the reviews do.

If a number has no definition and no owner, an automated system cannot use it either. The cadence and the data practice are the foundation the pyramid stands on. Once they hold, the layers above them pay for themselves.

Continue