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 with a 2017-08-09_1206.png. Some common examples of Improvement types used by our clients 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 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 to or requested of anyone in the organization. 

  • 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 Improvement to which they have access.

  • Collaborator – A Collaborator is part of the team working to implement the Improvement, but is not directly responsible for it.

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

    • Draft - This is an optional status. If the Author of an Improvement decides not to submit it yet after some information has been entered, they can save it as a draft. No one else will be able to access the draft, even if the direct link is provided.

    • New - The Improvement has been submitted but has not yet been assigned.

    • Planned - This is an optional status. It is intended for Improvements that are sure 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 active 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 Assigner's approval is required for the Resolution.

    • Completed - The Resolution has been submitted and approved by the Assigner (if required).

    • 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.

  • Authored Date – The date on which the Improvement was originally submitted.

  • Active Date – The date on which the Improvement was assigned and transitioned from "New" to "Active."

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

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

  • Comments – People 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 or local file addresses that are saved as part of the Improvement. They can be used to associate a specific web page, online document, or even a local 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