Continual Improvement Management difference with other processes

[Tommaso2]

Hi all,

Can you please provide a clear functional explanation to understand why someone should create an improvement initiative?

This is my understanding:

- improvement initiative: to improve something existing, implementation is not part of the process (a change can be created for this), cost analysis is not included (a demand can be created from here)

- idea: is for a new initiative, only description is available

- demand: is for a new initiative, financials/resource/value analysis is conducted

- project: is for a new initiative, goal is the execution and delivery (assessment is done in the demand phase)

- change: is a modification of an existing IT component that includes a risk assessment

Is this analysis correct? Why Improvement Initiative and Changes are different? 

Another doubt:

the strategies related to Improvement Initiatives are somehow related to Strategic Planning Workspace strategies/goals or to something else?

Many thanks!

Tommaso

[GlideFather]

Hi @Tommaso2,

I would understand it similar as you, just a few ideas:

• Project is execution of Demand,
• Ideas, Initiatives, Demands - all 3 are more analytical and not executional, so it is gathering details or preparing ground, while the Project is the real execution of some product in the end,
• Change from its definition is adding, changing, removing in something existing, I want to emphasise that the removal is sometimes being forgotten.

This is quite theoretical, each client might have different needs and policies.
 Do you have any particular question or you want to understand it from the general level?

[Dr Atul G- LNG · Accepted solution]

Hi @Tommaso2 

- improvement initiative: to improve something existing, implementation is not part of the process (a change can be created for this), cost analysis is not included (a demand can be created from here) -->

Yes, we can also say that improvements can come from existing functionality as well. For example, if there's a need to improve CSAT scores or team skills, you can leverage an Improvement Plan to address those areas.

- idea: is for a new initiative, only description is available

Yes, correct

- demand: is for a new initiative, financials/resource/value analysis is conducted and benefit too

Yes , correct

- project: is for a new initiative, goal is the execution and delivery (assessment is done in the demand phase)

Yes , correct

- change: is a modification of an existing IT component that includes a risk assessment

Is this analysis correct? Why Improvement Initiative and Changes are different? 

When we talk about Change from an IT perspective, it typically refers to a modification in the state of a Configuration Item (CI)—this is what the Change Management module focuses on.

On the other hand, when we speak about Improvement, it relates more to enhancing overall processes. For example, improving CSAT scores, team efficiency, or operational workflows.

Improvements can include:

• Creating more relevant knowledge base (KB) articles

• Adding validation checks when incidents are closed

• Identifying and implementing process-level changes

So while Change is about making a specific technical adjustment, Improvement is broader and often continuous, focused on raising service quality and performance.

Another doubt:

the strategies related to Improvement Initiatives are somehow related to Strategic Planning Workspace strategies/goals or to something else?

Atul: I don’t have a complete understanding of this yet, but I’m confident there is some linkage or connection involved.