Consider a standardized interface with customers and partners
Reijers, H., & Liman Mansar, S. (2005). Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4) All sources
category: External Environment class: Rules for External Parties frameworkAspect: External perspective: organizational/resource
Every exchange with customers, suppliers or partners is an opportunity for misunderstanding. Free-form letters, e-mails with attachments in varying formats and phone calls lead to incomplete applications, missing data and information that has to be interpreted, re-keyed and clarified. This pattern proposes replacing such unstructured exchanges with a standardised interface: a fixed form, a structured portal, an agreed message format or an API.
The concept underlying this heuristic suggests that employing a standardized interface can reduce the likelihood of errors, incomplete submissions, unclear communications, and so forth.
The interfacing heuristic can be regarded as a particular interpretation of the integration heuristic.
Where Integration links your process directly with a partner’s process, interfacing settles for a common, agreed format at the boundary, which is easier to establish with many partners at once.
A good standardised interface does more than fix a layout. It defines which information is mandatory, validates entries when they are captured and uses a vocabulary both sides understand. In this way it moves part of the checking to the moment of submission, which links the pattern to Control relocation, and it reduces the clarification contacts addressed by Reduce touchpoints.
■ This pattern ■ Baseline
A standardized interface may result in fewer errors (quality), faster processing (time), and less rework (cost).
The ratings show moderate improvements in quality, time and cost. Quality rises because mandatory fields and validation prevent incomplete or ambiguous input; time drops because clarification loops and manual interpretation disappear; cost falls as rework and re-keying decrease, although designing and maintaining the interface and onboarding partners require investment. Flexibility is neutral: a fixed format handles expected cases efficiently but cannot easily capture unusual requests, so a controlled fallback channel for exceptions is often useful.
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: processes that receive many documents or requests from external parties through unstructured channels. Location: the start of the process and activities that follow receipt from an external party, such as Request missing information or Clarify with customer. Attributes: input channel (e-mail, paper, portal, EDI), share of cases with clarification loops per channel, manual field changes after capture, waiting time for external responses. Constraints: few partners or low volumes; partners unable or unwilling to adopt the standard; highly individual requests that a fixed format cannot capture.
Foundational free Patterns
Elevate physical constraints by applying new technology
Consider the division of a general activity into two or more alternative activities
Assign a responsible individual for handling each case type
Let workers perform as many steps as possible for single cases
Consider automating activities
Automate for environmental impact
Implement automation in a sustainable way
Buffer external information and subscribe to updates
Combine small activities into composite activities
Collect similar work items and work in batches
Constraint-based task assignment
Allocate tasks considering business process execution constraints