Which problems do not lead to change management process?

[win_vj]

Which problems do not lead to change management process?

Please provide some examples.

[UKVIKING]

Easy.

Problems that can not be solved
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

[rpmason]

Any problem that doesn't need a modification to the infrastructure to correct. Simple example: users call the service desk too often (choose your own number) because some reports contain the wrong information. Root cause analysis determines that the users are defining the reports incorrectly. You don't need a RFC to schedule and provide training. However, if it's an in-house application that produces the reports, the User Guide could change under an RFC (if it's a CI).

Another example would be a problem that's not worth fixing. Maybe the fix is too expensive or maybe the item is at end-of-life anyway.
_________________
Ruth Mason
USA

[Diarmid]

Plus, of course, the problems on the bypass route
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718

[frenkel]

Management should be strict, loyal and efficient.There should not be laziness and delay in management work. The information should properly classified and correct. It should not be fake and the most emphasizing should on this main thing that it should be reliable to everyone.

[Diarmid]

Is that "should be" a categorical imperative, a moral imperative, or just something which will see an ROI?
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718

[pk_]

[Diarmid]

The PM team would not make that decision. The business would. Whether that comes about after initiating a request for change or whether it never gets that far is moot.

Unless Problem Management has a very large budget it will not be in a position to sponsor a costly change. But if the costs only emerge late in the day the change process will be under-way. So, either the problem manager or the change manager may be taking the issue to the business but that is where it will be decided.

There is also a distinction to be made between plain "too expensive" and "too expensive at this time". In either case it may be correct to continue investigation seeking cheaper resolutions. You can even argue that an impossibly costly solution is not a solution at all.

Just to make things a bit less simple, the long term solution may be to replace fundamental components (architectures, infrastructures, technologies for example) so that such solutions will be cost effective in the future in a more flexible environment.
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718