Archive:Opacity leads to higher costs - Revision history

wikademia>Wikademia: moved Opacity leads to higher costs to Archive:Opacity leads to higher costs:

2009-04-26T22:41:38Z

moved Opacity leads to higher costs to Archive:Opacity leads to higher costs:

← Older revision	Revision as of 22:41, 26 April 2009
(No difference)

wikademia>Wikademia: 4 revisions

2009-04-11T05:54:28Z

4 revisions

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

wikademia>Chungw: added category

2009-04-10T21:54:02Z

added category

← Older revision		Revision as of 21:54, 10 April 2009
Line 15:		Line 15:
	\| [[Charter for alignment\|Charter for Alignment]]		\| [[Charter for alignment\|Charter for Alignment]]
	\|}		\|}


			[[Category:(Anti-)Behaviors of business process management program governance]]

wikademia>Chungw: added navigation to parent charter

2009-04-10T19:04:48Z

added navigation to parent charter

← Older revision		Revision as of 19:04, 10 April 2009
Line 11:		Line 11:
	\| [[Image:DemocracyGlobe.gif\|left\|link=Charter for bpm democracy]]		\| [[Image:DemocracyGlobe.gif\|left\|link=Charter for bpm democracy]]
	\| [[Charter for bpm democracy\|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]]
	\|}		\|}

wikademia>Chungw: added navigation to parent charter

2009-04-10T19:03:16Z

added navigation to parent charter

← Older revision		Revision as of 19:03, 10 April 2009
Line 5:		Line 5:

	IT system owners when asked for the same set of interfaces repeatedly can provide feedback that there are going to be problems with duplication of systems or solutions. Including the end-users in the evaluation of the projects can be a powerful to eliminate duplicates. They will be happier, and therefore, more productive.		IT system owners when asked for the same set of interfaces repeatedly can provide feedback that there are going to be problems with duplication of systems or solutions. Including the end-users in the evaluation of the projects can be a powerful to eliminate duplicates. They will be happier, and therefore, more productive.


			== Applies to ==
			{\|
			\| [[Image:DemocracyGlobe.gif\|left\|link=Charter for bpm democracy]]
			\| [[Charter for bpm democracy\|Charter for BPM Democracy]]
			\|}

wikademia>Chungw: Initial behavior page

2009-04-10T15:46:29Z

Initial behavior page

New page

== Summary ==
Organizations often have redundant projects concurrently active. Overlapping requirements and capabilities have multiple resources tackling the same problem and reinventing the wheel. This is usually due in part to separate business units operating with limited visibility into one another's activities. Then when the systems go-live, the users are frustrated because they have to pick from multiple systems to accomplish their jobs.

A transparent BPM society where teams can review intent, objectives, and requirements helps remove this problem. It is the programmatic equivalent of a '''Freedom of Information Act'''.

IT system owners when asked for the same set of interfaces repeatedly can provide feedback that there are going to be problems with duplication of systems or solutions. Including the end-users in the evaluation of the projects can be a powerful to eliminate duplicates. They will be happier, and therefore, more productive.