As continuous improvement is the name of the game, our product team is constantly adding new features to KaiNexus that allow our customers to map their workflows, with increasing efficiency, to the platform. This can result in instances that can look wildly different from one another, despite the fact that some customers share a similar methodology. A few months ago, we rolled out our Customer roundtable series that sought to bridge the gap not only between our customers, but also between what each of them has configured in their instance, and what they may not even know they could do. For the first quarter of the new year, we kicked off this series with a walkthrough of tips and tricks used to develop impressive templates and workflows.
The players in this edition of the roundtable series involved KaiNexus champions from organizations of different sizes and in some cases, industries. Our participants included Kreg Tool, Nebraska Methodist Health Systems, and Our Lady of the Lake Regional Medical Center. Read on for highlights from the hour-long session.
Starting off the session, was a certification workflow that is currently being piloted over at Kreg Tool. At Kreg Tool, they are seeking to build a “network of problem solvers,” through the use of their CIA certification program. In previous years, ensuring each participant of the program is attending each session and completing the action items required a lot of effort tracking people down. Using KaiNexus, Kreg Tool has started implementing a templated workflow that puts the tracking effort onto the individual to complete the items and request sign off. Incorporating milestones, and badges, they are able to see at a glance which assignments need to be approved, and where each employee is on their certification journey. And each time a new user goes through certification, the template just needs to be copied, rather than recreated each time, saving tons of time for the facilitators.
For users who may not be involved in piloting certifications, Kreg Tool has another workflow. Their users are encouraged to “pull the Andon” and initiate an A3 problem-solving cycle. The digital version of this previously paper-based form was designed to look very similar, however, having it in KaiNexus makes it easier to track the status of current Andons, request sign off to ensure elimination of the root cause, and it results in a much smoother communication process. The template creation is streamlined to only include the planning phase upon submission, making it incredibly easy for users to begin the problem-solving cycle. The “Do,” “Check,” and “Act,” phases are introduced later as a series of questions to ensure the process is clear and easy to follow.
Our Lady of the Lake Regional Medical Center
At Our Lady of the Lake Regional Medical Center, our champions use a similar method, with a very different format for their Problem-Solving Storyboards. These storyboards are used as an introduction to problem-solving that each user must complete. Using the custom layout functionality, users are able to add images and KaiNexus charts directly into their workflows with one click. In addition, they are able to track their action plan, as well as the benefit/Impact, all be managed from within the template.
Closing out our roundtable were a few workflows from our friends over at Nebraska Methodist Health Systems. Because all of their quality projects have to be run through an A3, NMHS has developed a more traditional A3 template that includes a plan of action, metrics, and leadership signoff upon close. Using the new compact header to save space, NMHS is able to print their A3s and post them on their daily visual management boards for anyone who is looking for information on problem-solving work that is occurring.
Finally, we closed the roundtable with a discussion of a template used to capture meeting minutes. Since meetings are happening around projects that are being managed in KaiNexus, the team over at NMHS developed a simple template used to capture date, time, location and attendees that are nested under the parent project. Anyone who is on the project team of the parent will get a notification when a new set of meeting minutes were added to the project, and are able to ask questions about anything they may have missed in the comments. Creating this workflow as a project type allows for action items from the meeting to be included as nested improvements and tasks. This lets their users keep track of what needs to be done for the project to move forward, and at the start of the following meeting, action items are reviewed.
Concluding another roundtable, I am personally excited by the ideas that were shared, and the introductions made. We think of our customers as a family, and we love when our family gets together. This won’t be the last time, so keep an eye out for that invite next quarter!