Charter for conflict resolution in BPM - Revision history

Idea: /* Activation and Assimilation */

2026-09-29T19:16:11Z

Activation and Assimilation

← Older revision		Revision as of 19:16, 29 September 2026
Line 70:		Line 70:

	The historical data will prove invaluable for future pattern matching of conflict situations, and it should be captured in a manner that will encourage review and leverage later. Regular post-conflict reviews should occur to disseminate the knowledge and to build up a set of best practices within the organization.		The historical data will prove invaluable for future pattern matching of conflict situations, and it should be captured in a manner that will encourage review and leverage later. Regular post-conflict reviews should occur to disseminate the knowledge and to build up a set of best practices within the organization.


	=== People ===		=== People ===

Idea at 19:16, 29 September 2026

2026-09-29T19:16:05Z

← Older revision		Revision as of 19:16, 29 September 2026
Line 1:		Line 1:
	~~{{ntnes}}~~
	~~== Executive Summary ==~~
	A BPM program encompasses many parts of an organization, crossing functional and operational boundaries. In such a setting, conflict situations are bound to occur. These conflicts can arise between parts of the program or between the program and other organizational bodies.		A BPM program encompasses many parts of an organization, crossing functional and operational boundaries. In such a setting, conflict situations are bound to occur. These conflicts can arise between parts of the program or between the program and other organizational bodies.

Line 6:		Line 4:

	Conflict management and resolution entails identifying, assessing, and mitigating conflicts. Further, the program must incorporate lessons learned into the body of knowledge to reduce the likelihood that similar conflicts occur again.		Conflict management and resolution entails identifying, assessing, and mitigating conflicts. Further, the program must incorporate lessons learned into the body of knowledge to reduce the likelihood that similar conflicts occur again.


	== Objectives ==		== Objectives ==
	This Charter focuses on an approach for evaluating and resolving conflicts.		This Charter focuses on an approach for evaluating and resolving conflicts.


	== Scope ==		== Scope ==
Line 16:		Line 12:

	Conflict types include those internal to the BPM program and those between the program and other bodies. This Charter addresses both types and outlines a set of activities to address them.		Conflict types include those internal to the BPM program and those between the program and other bodies. This Charter addresses both types and outlines a set of activities to address them.


	== Plan ==		== Plan ==
Line 25:		Line 20:
	*Prioritization, and		*Prioritization, and
	*Activation and Assimilation.		*Activation and Assimilation.


	=== Problem Identification ===		=== Problem Identification ===
Line 42:		Line 36:

	In generating options, remember that BPM is a dynamic environment rather than a static one. An option might solve the problem for today and expedite conflict resolution. The solution will need to be revisited in the future, but at least long delays with trying to find the perfect solution are avoided.		In generating options, remember that BPM is a dynamic environment rather than a static one. An option might solve the problem for today and expedite conflict resolution. The solution will need to be revisited in the future, but at least long delays with trying to find the perfect solution are avoided.


	=== Impact Analysis ===		=== Impact Analysis ===
Line 61:		Line 54:

	Take the information gathered in this stage to the prioritization stage.		Take the information gathered in this stage to the prioritization stage.


	=== Prioritization ===		=== Prioritization ===
Line 71:		Line 63:

	In all cases, the prioritization scheme should be systematic. It should be clear how selections are made. The objectives should be clear, and the scoring system should align towards them. High frequency and high impact conflicts should be addressed first as these generally incur the highest cost if left unattended.		In all cases, the prioritization scheme should be systematic. It should be clear how selections are made. The objectives should be clear, and the scoring system should align towards them. High frequency and high impact conflicts should be addressed first as these generally incur the highest cost if left unattended.


	=== Activation and Assimilation ===		=== Activation and Assimilation ===
Line 87:		Line 78:

	As speed is typically of the essence, the recommendation is to select individuals rather than committees. While the individuals should take input from the program participants, deferring the decision to committees tends to delay and to hinder resolution options from being fully effective.		As speed is typically of the essence, the recommendation is to select individuals rather than committees. While the individuals should take input from the program participants, deferring the decision to committees tends to delay and to hinder resolution options from being fully effective.


	== Assumptions ==		== Assumptions ==
	*Sometimes a conflict arises because one party misunderstands what is expected of them. Developing a trial or light version of a feature may be all that is required in the short-term, with a chance to revisit that functionality at a later date. This includes interfaces on a roadmap, where early versions of solutions might only require an immature version of the service while later, they will require robust and redundant capabilities. Options for resolving a conflict need not be implemented and then forgotten. They can be addressed in a series of actions.		*Sometimes a conflict arises because one party misunderstands what is expected of them. Developing a trial or light version of a feature may be all that is required in the short-term, with a chance to revisit that functionality at a later date. This includes interfaces on a roadmap, where early versions of solutions might only require an immature version of the service while later, they will require robust and redundant capabilities. Options for resolving a conflict need not be implemented and then forgotten. They can be addressed in a series of actions.


	== (Anti-)Behaviors ==		== (Anti-)Behaviors ==
Line 106:		Line 95:

	A structure for conflict resolution provides more than the means to solve a specific conflict situation. It also allows the lessons learned to be assimilated back into the program's collective knowledge. That collective experience can help either to avoid the conflicts entirely or to minimize their impact should they occur again in the future.		A structure for conflict resolution provides more than the means to solve a specific conflict situation. It also allows the lessons learned to be assimilated back into the program's collective knowledge. That collective experience can help either to avoid the conflicts entirely or to minimize their impact should they occur again in the future.


	== Lesson exercises ==		== Lesson exercises ==


	[[Category:Charters for business process management program governance]]		[[Category:Charters for business process management program governance]]

wikademia>Eme: moved Archive:Charter for conflict resolution to Charter for conflict resolution in BPM

2010-11-22T15:48:22Z

moved Archive:Charter for conflict resolution to Charter for conflict resolution in BPM

← Older revision	Revision as of 15:48, 22 November 2010
(No difference)

wikademia>Wikademia: moved Charter for conflict resolution to Archive:Charter for conflict resolution

2009-06-12T08:15:06Z

moved Charter for conflict resolution to Archive:Charter for conflict resolution

← Older revision	Revision as of 08:15, 12 June 2009
(No difference)

wikademia>Wikademia at 04:37, 27 April 2009

2009-04-27T04:37:41Z

@@ Line 1: / Line 1: @@
 {{ntnes}}
 == Executive Summary ==
 A BPM program encompasses many parts of an organization, crossing functional and operational boundaries.  In such a setting, conflict situations are bound to occur.  These conflicts can arise between parts of the program or between the program and other organizational bodies.

wikademia>Wikademia at 04:32, 27 April 2009

2009-04-27T04:32:23Z

← Older revision		Revision as of 04:32, 27 April 2009
Line 22:		Line 22:
	\| [[A charters glossary\|A Charters Glossary]]		\| [[A charters glossary\|A Charters Glossary]]
	\|}		\|}
			{{ntnes}}

	== Executive Summary ==		== Executive Summary ==

wikademia>Wikademia: 5 revisions

2009-04-11T05:54:20Z

5 revisions

← Older revision	Revision as of 05:54, 11 April 2009
(No difference)

wikademia>Chungw: added category

2009-04-10T21:37:12Z

added category

← Older revision		Revision as of 21:37, 10 April 2009
Line 133:		Line 133:

	== Lesson exercises ==		== Lesson exercises ==


			[[Category:Charters for business process management program governance]]

wikademia>Chungw: capitalized aliases for links

2009-04-10T21:25:48Z

capitalized aliases for links

← Older revision		Revision as of 21:25, 10 April 2009
Line 120:		Line 120:

	=== Behaviors ===		=== Behaviors ===
	*[[Internal dependencies - simultaneous upgrades]]		*[[Internal dependencies - simultaneous upgrades\|Internal Dependencies - Simultaneous Upgrades]]

	=== Anti-behaviors ===		=== Anti-behaviors ===
	*[[External dependencies - the five-year plan]]		*[[External dependencies - the five-year plan\|External Dependencies - The Five-Year Plan]]
	*[[Internal dependencies - identifying shared assets]]		*[[Internal dependencies - identifying shared assets\|Internal Dependencies - Identifying Shared Assets]]


	== Conclusions ==		== Conclusions ==

wikademia>Chungw: added navigation to other charters

2009-04-10T18:55:51Z

added navigation to other charters

← Older revision		Revision as of 18:55, 10 April 2009
Line 1:		Line 1:
			== Related lessons ==
			{\|
			\| [[Image:Charters.gif\|left\|link=The charters for bpm program governance - an overview]]
			\| [[The charters for bpm program governance - an overview\|The Charters for BPM Program Governance - An Overview]]
			\|-
			\| [[Image:Engine.gif\|left\|link=Charter for the bpm engine]]
			\| [[Charter for the bpm engine\|Charter for the BPM Engine]]
			\|-
			\| [[Image:DemocracyGlobe.gif\|left\|link=Charter for bpm democracy]]
			\| [[Charter for bpm democracy\|Charter for BPM Democracy]]
			\|-
			\| [[Image:Alignment.gif\|left\|link=Charter for alignment]]
			\| [[Charter for alignment\|Charter for Alignment]]
			\|-
			\| [[Image:Resolution.gif\|left\|link=Charter for conflict resolution]]
			\| [[Charter for conflict resolution\|Charter for Conflict Resolution]]
			\|-
			\| [[Image:Investment.gif\|left\|link=Charter for bpm investment]]
			\| [[Charter for bpm investment\|Charter for BPM Investment]]
			\|-
			\|
			\| [[A charters glossary\|A Charters Glossary]]
			\|}


	== Executive Summary ==		== Executive Summary ==
	A BPM program encompasses many parts of an organization, crossing functional and operational boundaries. In such a setting, conflict situations are bound to occur. These conflicts can arise between parts of the program or between the program and other organizational bodies.		A BPM program encompasses many parts of an organization, crossing functional and operational boundaries. In such a setting, conflict situations are bound to occur. These conflicts can arise between parts of the program or between the program and other organizational bodies.