Settings

FlowHarbor community — Seoul

We onboarded Atlas Process Discovery for our procure-to-pay flow and the variant explorer surfaced six unrecorded shortcuts our shared service centre had been using for years. The steering meeting moved from debate to decision in a single session, which was a result we had not been able to manufacture for two quarters.

— Min-jae Choi , Director, Operational Excellence , Daewon Electronics (mid-market)

A short, fortnightly note from members. No sales follow-up.

Code of conduct · excerpt

Three principles. The full document is open.

  • Speak about specifics. Bring concrete cases, screenshots, or numbers. Generic praise and generic criticism slow the community down.
  • Disagree with care. Critique the argument and the artefact, not the person who shared it. Disagreement is welcome; condescension is not.
  • Share what did not work. Failure stories are more useful than success stories. The community is set up to make those safe to share.

Read the full code of conduct →

Voices · five

Specific results, named programmes

  • Each card names the FlowHarbor product or engagement that produced the result
  • Card formats vary deliberately — full attribution, platform-style with verified badge, mixed
  • At least one entry includes a constructive note rather than glowing praise
  • Testimonials reflect Korean operations programmes; identifying details are anonymised when asked

  • We onboarded Atlas Process Discovery for our procure-to-pay flow and the variant explorer surfaced six unrecorded shortcuts our shared service centre had been using for years. The steering meeting moved from debate to decision in a single session, which was a result we had not been able to manufacture for two quarters.

    Min-jae Choi Director, Operational Excellence Daewon Electronics (mid-market)

  • Conformance Lens reduced our quarterly audit walkthrough from a full week to two days. The drill-through to specific case IDs is what made it credible to the external auditor; without that, it would have been just another dashboard.

    Tae-hyung Yoon Head of Internal Audit Chungbuk Regional Bank
  • 4.8/5 verified

    The Operations Insight Dashboard forced our exec team to agree on five metrics. That argument was harder than the implementation, and more valuable than I expected. We still occasionally request a sixth slot; FlowHarbor still says no, which is the right call.

    Eun-ji Han

  • We came expecting a software pitch and left with our own internal disagreements resolved. The Process Lab format is short on slideware and long on uncomfortable conversations, which was exactly what our programme needed before signing for any platform.

    Yong-jin Bae Programme Director a domestic retailer

  • The Integration Advisory Sprint produced an estimate with low / likely / high bands. Our previous vendor gave us a single number which turned out to be the optimistic case. The honesty of the band approach paid for itself in the first project review.

    Hyun-woo Jeon Platform Owner a logistics group

Member of the month · May

Bo-ram Jung, Senior Analyst, regional manufacturer

  • Authored four community notebooks this quarter on variant cohort cleanup
  • Reviewed thirty-one pull requests on the shared event-log mapper repository
  • Hosted two open office hours for new joiners working with Korean ERP data
  • Maintained the worked-example archive for the Discovery channel
  • Published a write-up on a clustering threshold change that was wrong (and explained why)

Objection-handler FAQ · for buyers and members

Real questions, answered directly

These four questions are the ones we hear most often, in steering meetings and in member onboarding chats. The answers are the ones we actually give. We have not softened the wording for the website. If a question we have not addressed comes up repeatedly, we add it here in the next iteration; the version date is in the footer of the FAQ page.

01

Is FlowHarbor a community or a vendor pretending to be one?

It is both, and we say so on the about page. The community is open and free to join, including for people who do not buy our platform. We moderate it but we do not require participants to be customers; about a third of active members are not. This means we sometimes get critique of our own product in our own community, which is the price of running it honestly.

02

I am evaluating process mining tools. Will I be sold to here?

You will see product mentions where they are relevant to a thread, and we do publish events that include our consultants. We do not run cold outreach to community members, we do not pass member contact details to a sales team, and you can post evaluation questions about other vendors without being routed to ours.

03

What if I post something that is wrong, or asks a basic question?

That is fine. The code of conduct asks members to disagree with care and to share what did not work, including their own. Basic questions are welcome; hostile responses to them are not, and moderators remove them quickly.

04

Can my organisation use the community internally without joining the public space?

No. We do not host private mirrors. If you need a private space, that is a different kind of programme and we would point you to a Process Lab engagement or your own internal tooling. We deliberately keep the public community as one space.

See the full FAQ →