Powered by Temper

Improvement terms

  • Improvements – Suggestions, ideas, and observations entered by users into the KaiNexus system. Improvements benefit the organization in some way, whether by improving finances, quality, safety, or satisfaction. Improvements are identified by a light bulb icon. Examples include: Opportunities for Improvement, Ideas, Just-Do-Its, A3, PDCAs, etc.


  • Author – The person or people who initially had the idea and/or submitted the Improvement.


  • Assigner – This is the person who assigned someone to be responsible for an Improvement. They will stay informed about the Improvement’s progress, and they may be responsible for approving the Improvement’s Resolution before it is completed.


  • Responsible – This is the person who is tasked with evaluating, implementing, and managing an Improvement through to completion.


  • Task – Improvements can be broken down into smaller action items called Tasks. These can be assigned or requested of anyone in the organization. Due date reminders are included in the digest email.


  • Follower – This is a person who has no direct responsibility for an Improvement, but is kept aware of any updates via the digest email. Any user can follow any visible Improvements.


  • Collaborator – A Collaborator is part of the team working to implement the Improvement. This person is kept in the loop via the digest email.


  • Status – The status of an Improvement indicates how far along in the implementation process it is.

    • New - When an Improvement is initially entered into the system.

    • Planned - This is an optional status. It is intended for Improvements that will be done at a future date.

    • Active - This status is given once someone is assigned to be responsible for the Improvement.

    • Overdue -  This status is given if the Improvement is not completed before its due date.

    • Resolution Submitted - The Resolution has been submitted and is pending review by the assigner. This Status is only used if the Responsible has submitted the Resolution to the Assigner.

    • Completed - Once the Resolution is submitted and approved (if required) it changes to Completed.

    • Deferred - This is an optional status for Improvements that have been  evaluated, but no decision about whether or not to implement them has been made.

    • Draft -  This is an optional status. Before an Improvement’s submission, the Author can choose to save it as a draft if they are not ready to submit the Improvement.  

  • Authored Date – When the Improvement is initially submitted.


  • Active Date – The date when the Improvement is assigned and goes from New to Active.


  • Due Date – The date by which the Improvement is to be completed.


  • Completed Date – The date on which the Resolution is accepted.


  • Improvement Comments – Users can log updates and communicate with other users by entering comments on Improvements, Projects, and Tasks. Comments are noted in the digest email, and can optionally be sent out in individual emails.


  • Timeline – This audit trail keeps track of every significant event that happens on a Task.


  • Attachments – Files that are saved as part of the Improvement so that all information about the work being done is stored in a single location. They can be used to store everything from images, spreadsheets, project charters, and links to secure documents. All the basic file types are supported.


  • Links - Web addresses that are saved as part of the Improvement. They can be used to associate a specific web page or even an online document with an Improvement or Project.


  • Resolution – Each Improvement is resolved when the Responsible person answers a series of brief questions about how the Improvement was implemented and quantifies the benefits. Once filled out, Resolutions may need to be validated by the Improvement’s Assigner, depending on the option selected during its creation.


  • Impact – The result, whether qualitative or quantitative, of implementing an Improvement. The impact of each Improvement is captured upon its completion, and KaiNexus calculates the cumulative impact of all Improvements across the organization.

 

Have more questions? Submit a request