Field notes — why gemba

Gemba means the real place. We start there — not in a dashboard.

Every engagement begins on the shop floor, in the call queue, inside the spreadsheet someone built at 11pm to patch a process the system doesn't support. That's where the answer usually is.

Principles

The principles behind every engagement.

DELIVERY FIRST

Working solutions rule.

Regardless of Agile or Waterfall, we deliver working code at every iteration or milestone. Planning is respected — we just avoid analysis paralysis.

MAKING SENSE

No FOMO.

Life's too short to waste on work that doesn't fit. We can't take every job, so we focus on the ones that actually make sense for us.

WALK, DON'T RUN

Right for the time, scaled smart.

It's tempting to sprint straight to a flashy build. We'd rather walk the process first and understand it properly before anything gets built.

FAIL AND LEARN

We don't know everything. That we know.

We'll learn whatever the project needs along the way — and share that process transparently with you, not just the polished result.

A note

I started GembaData after watching too many good data teams — and too many companies without one — get sold dashboards instead of answers. The tooling was never the hard part. Knowing which question to ask, and being willing to go find out firsthand, was.

— Founder, GembaData