B.HaymanalıPyAI Öğren

Station 1 of 6

Process development · Optimization · Mild overthinking

All the motion.None of the waste.— Berkkan Haymanalı, process development & optimization engineer

Obsessed with how work flows. Every workflow is a machine quietly losing time — I find where it leaks, rebuild it, and make a spreadsheet slightly too excited about the result.

Optimizing since birth
24 yrs
Tabs open per root cause
37
Meetings that should be emails
0
Scroll to optimize

02The spaghetti

Straight linesare earned.

  1. Request in
  2. Validate
  3. Approve
  4. Order
  5. Receive
  6. Inspect
  7. Close

Steps 23 → 7 · Lead time 11 days → 4.3 days · −61%

Illustrative purchase-request flow. Names changed. Mehmet Bey knows.

Removed · 16

  • 02Print, sign, scan, email
  • 04Wait for Mehmet Bey to finish lunch
  • 05Forward to Steve, who forwards it back
  • 06Update the Excel nobody owns
  • 08Re-approval by the approver's approver
  • 09Reply-all: “Looping in Ayşe”
  • 10Meeting to schedule the meeting
  • 11Sign-off from Klaus (on holiday)
  • 13Double entry: ERP and the notebook
  • 14budget_FINAL_final_v3.xlsx
  • 15Ask Hüseyin Abi, who “knows the system”
  • 16Fax. Yes, a fax.
  • 18Kevin's “quick sync” (52 min)
  • 19Copy-paste from PDF
  • 21Wait for the Monday batch run
  • 22Status update on the status update

Station 01 · Packaging plant

Line changeover, resequenced

Changeover steps were reordered and every preparation task moved ahead of the stop. The manual reset became a repeatable routine.

−42%

Changeover time · one coffee saved

Before
38 min
After
22 min

Station 02 · E-commerce

Return triage, redesigned

The decision tree collapsed into a single checkpoint, and a rule engine now routes standard returns without a human touch.

−64%

Handling time · patience preserved

Before
11 min
After
4 min

Station 03 · Textile

Production schedule, rebalanced

Pattern transitions on the looms were balanced against takt time and the bottleneck station's load was redistributed.

+18%

Output per shift · loom less dramatic

Before
912 m
After
1,076 m

Station 04 · Side project

Learning Python, de-installed

Plenty of beginners lose their first Python session to installers and PATH errors. The route was rebuilt: Python runs in the browser, and 96 Turkish lessons — from print() to machine learning — are checked against real Python.

Try it

0

Installs to start · PATH errors retired

Before
Install day
After
One browser tab

03Work

Before. After. Proof.

04Method

Measure first.Then delete.

  1. Map
  2. Measure
  3. Rebuild
  4. Lock

  1. 01 — Map

    First, draw the spaghetti.

    Inputs, handoffs and waiting points — including the mysterious Excel file nobody owns.

  2. 02 — Measure

    If it wasn't timed, it was a feeling.

    Every stage gets a baseline before someone says, “It usually feels faster.”

  3. 03 — Rebuild

    Delete steps. Not lunch breaks.

    Work is removed — not squeezed into a shorter window with motivational posters.

  4. 04 — Standardize

    If it lives only in my head, it is not a system.

    The gain is standardized, tied to a metric and checked before the spreadsheet becomes folklore.

05About

I was probably optimizing my crib layout

I am 24, which technically gives me 24 years of process experience. Apparently, lining up toy cars by cycle time was an early warning. I now apply that same energy to real workflows — with fewer crayons and significantly more spreadsheets.

ToolkitWIP 6/6
  • Lean
  • Six Sigma
  • SMED
  • OEE
  • Kaizen
  • Value Stream Mapping

SORTED BY: frequency of use

Technical diagram of an improved process flow: stages connected by nodes and arrows

06Contact

Send me your slowest process.

Work order #0001PRIORITY: HIGHREQUESTED BY: YOU