Professional Documents
Culture Documents
Building An Enterprise Process Map PDF
Building An Enterprise Process Map PDF
Enterprise
Process Map
David Hamme
Building an Enterprise Process Map
Documenting a process generally results in at least a 25% gain in productivity – and often even
greater gains. Translating work effort into discrete steps reduces confusion, drives consistency of
execution, accelerates training, and usually uncovers efficiency opportunities along the way. But it
comes with a risk – the risk of improving a segment of an organization to the detriment of other
areas. We call this a localized improvement.
To eliminate the occurrence of localized improvements, our teams ALWAYS begin the process
transformation journey by creating an Enterprise Process Map (also called an Enterprise Process
Blueprint). An enterprise process map is a birds-eye pictorial view of how an organization delivers
value for a customer. In contrast to an organizational chart, it is not the view to identify the
hierarchical reporting structure (at least in most instances) but rather it is the embodiment of the
market and operational approach currently in existence for an organization. Good enterprise process
maps depict the workflows from the acquisition of raw material to the delivery of a product or service
and on through the ongoing servicing of the customer’s needs.
• Starts with the customer and identifies moments when the organization and the customer
interact on a regular basis (this is very useful for creating a cohesive and consistent customer
experience).
• Provides an end-to-end view of the processes spanning an enterprise (and even business
partners).
• Identifies how work flows through these processes to the end delivery of a solution for a
customer.
By documenting an enterprise process map, an organization reaps several immediate benefits.
You need information on how things get done. Begin by speaking with the leaders and managers of
the major areas of the company. Generally, aim for individuals at the Vice President or departmental
leader level. The aim of these interviews is to gain an understanding into all corners of the company.
To collect this information, ask each leader these questions.
• When does your team interact with the customer?
• What are the major activities of your team?
• What are the outputs your team produces?
• What are the inputs to building these deliverables?
• Who are your business partners?
Generally when asking about the major activities, a collection of processes are named. For example,
if you meet with a Supply Chain Vice President, you will probably get a list along these lines:
• Receive product from manufacturing
• Receive orders from sales
• Pick orders out of warehouse
• Stage orders for delivery
• Plan transportation routes
• Load orders onto trucks
• Deliver orders to customer locations
On an enterprise process map, it would make sense to merge these processes together and label
them “Order Delivery” or something similar. “Order Delivery” in this example is a mega process that
defines the collection of processes above. Listing the processes with the associated mega process
adds further richness to the enterprise process map.
1. From the interviews, take the identified mega processes and place them in order of their
general occurrence.
2. Identify the connection points between the mega processes and the customer facing
processes. With the mega processes identified, note their linkage to the customer-facing
processes. Draw a line to identify the flow of work products, decisions, or other information.
Use a simple label to clarify what is transferred. For example, an order might be generated
by a sales process and pushed to a manufacturing process for planning and execution. Write
“order” to show the flow of this line from sales to manufacturing.
3. Push support functions to a shared services area (Finance, Accounting, HR, Technology,
Legal, Facilities, Real Estate, Treasury, etc.). While shared services are necessary for any
organization, they serve a relatively similar function across organizations.
Share the draft with associates of all levels of the company and ask for feedback. It is this
melding of perspectives that drives the accuracy and authenticity of the end product. Follow
up if they don’t respond in a timely fashion.
As feedback rolls in, questions and differences of opinions will always surface. In order to complete
(and confirm) the process map, schedule a meeting to work through the outstanding questions and
drive to a shared perspective. On occasion, disagreements will require further investigation as to
what really occurs in the trenches of the company. Even after agreement is reached, continued
iterations will be required to keep it up to date.
When building the enterprise process map, there are several general rules to follow that will increase
its accuracy.
• Focus on the processes not the organizational structure. The goal is to build a view of
company without functional boundaries
• Avoid departmental or business unit names. Similarly, do not put owner’s names on
processes (at least not yet)
• Resist the temptation to jump to the future. Always build a current state process map before
beginning to plan a future state. A future state created prior to understanding the current
state invariably ignores critical operational elements.
Building an Enterprise Process Map
The greatest benefits of enterprise process maps come from the clarity and shared perspective it
delivers. Share it widely across all levels of your organization. Update it as the organization evolves.
In this way, the clarity gained extends through the employee ranks and into the future.
By delivering improved business understanding, faster processes, and greater business impact on strategic
planning, the SoftExpert solution allows people to work more efficiently while improving orchestration of
complex processes and supporting business goals with real-time business information.
The solution provides a powerful 100% web-based drag-and-drop design tool based on the Business Process
Model and Notation (BPMN) standard, allowing for the use of events, process and task activities, decision
gateways, swim lanes, and other features to quickly create executable processes.
Disclaimer: The content of this publication may not, in whole or in part, be copied or reproduced without prior authorization from SoftExpert Software. This
publication is provided by SoftExpert and/or its network of affiliates strictly for informational purposes, without any guarantee of any kind. The only guarantees
related to SoftExpert products and services are those contained within a contract. Some product functionalities and characteristics presented herein may be
optional or may depend on the makeup of the offer(s) acquired. The content of this material is subject to change without prior notice.