MHZ. MIN HEIN ZAWIT MANAGER
Process

What happens when a problem lands on my desk.

Six stages I follow on factory IT and business-system work. They come from doing the work, not from a textbook, and each one links to a real case.

The six stages

  1. 01

    Understand

    Start with the business problem, not the technology.

    • Go to the floor and watch the work as it happens.
    • Talk with the people who do it, in meetings and during testing.
    • Follow how work moves from one team to the next.

    In practiceProduction team meetings showed why a tracking system gave them little back. Production tracking case study

  2. 02

    Define

    Turn what I saw into something people can act on.

    • Requirements and clear change requests.
    • Constraints, risks and who is responsible for what.
    • What success looks like for the operation.

    In practiceFactory feedback grouped into change requests for the developers. Visitor system case study

  3. 03

    Stabilize

    Keep the operation running while the real fix is prepared.

    • Find a safe temporary workaround.
    • Keep interruption to daily work as small as possible.
    • Plan from the start how the workaround will be removed.

    In practiceA temporary Microsoft 365 register kept visitor registration running for about a month. Visitor system case study

  4. 04

    Deliver

    Coordinate the people and the work.

    • Coordinate developers, vendors and the group IT team.
    • Configuration, data preparation and testing.
    • Training and go-live support for users.

    In practiceA new factory’s cabling, network and servers, fitted around construction. Factory IT set-up case study

  5. 05

    Validate

    Does it work for the operation, not only technically?

    • Test with real users and real workflows.
    • Re-test after every round of changes.
    • Give management a clear summary to decide on.

    In practiceFactory-side UAT found the gaps before the system went live. Visitor system case study

  6. 06

    Improve

    Delivery is not the end of the work.

    • Collect feedback and document what was done.
    • Monitor, back up, and test that restores work.
    • Automate where it helps; retire temporary solutions.

    In practiceDaily backups with tested restores; the temporary visitor register retired. Backup and recovery case study

How I decide

When deciding on a solution, I ask:

  1. Does it fit the operation?
  2. Can users work with it?
  3. Is it secure enough for its purpose?
  4. Can IT support it?
  5. What happens when it fails?
  6. Can it be maintained?
  7. Is temporary complexity becoming permanent?

See the stages in real work.

View case studies Contact