My name is Ariel Klontz, and I have been working at LeanKit for the past few months as an intern alongside Andy Hoover on the Customer Documentation team.
When I first started here, I was nervous about how much work I could really accomplish on a part-time basis; but working at LeanKit opened my eyes to a whole new way to manage work. Working in a virtual Kanban board showed me how powerful our tool is — it keeps our entire team on the same page, even when the pages are constantly turning. I don’t have to wait to be told what to do. I can see what work I need to accomplish by glancing at our board, and I have the tools to move forward with it.
Today I’ll share how LeanKit helps our team systematically update our Knowledge Base based on product updates and customer feedback, so customers always have the latest information about our product. I’ll also explain how using a virtual Kanban board enables everyone — even part-time interns — to add real value.
Whether you just built your first Kanban board or you’re a Kanban expert, it’s always smart to deepen or refresh your Kanban knowledge by reading the work of leading influencers.
Hana here, from Product Marketing at LeanKit. One of my main roles is as a liaison between our Product and Marketing teams, ensuring that feature releases are communicated effectively with you, our customers.
I was recently asked to name my favorite LeanKit feature, and to be honest with you, that’s a bit like picking a favorite child. I decided to begin with LeanKit’s Subscribe to a Card feature, because it’s had a tremendous impact on the way I manage cross-departmental work.
Choosing a Kanban App
Kanban apps are increasingly adopted by enterprises looking for ways to optimize workflow processes and accelerate value delivery. While teams may start out using a physical Kanban board, the need to streamline communication between distributed and cross-functional teams quickly prompts most teams to adopt a Kanban app.
My name is Andy Hoover and I manage our Customer Support operations here at LeanKit. I spend my time making sure our amazing team of support agents has the tools, training and processes in place to help our customers with any questions or problems they run into when using LeanKit.
In this post, I’ll explain how LeanKit’s support agents use LeanKit integrations to automate part of the ticket escalation process and ensure quick, accurate resolutions for our customers.
The Kanban technique emerged in the late 1940s as Toyota’s reimagined approach to manufacturing and engineering. The system’s highly visual nature allowed teams to communicate more easily on what work needed to be done and when. It also standardized cues and refined processes, which helped to reduce waste and maximize value.
The application of Kanban to knowledge work — influenced not only by the Toyota Production System but also by Lean systems thinking — began as early as 2005. Kanban’s core principles are the same in industries like software development and human resource management as they are in manufacturing: visualize your work, make your policies explicit, limit your work in process, focus on flow, and practice continuous improvement.
Here are five of our most popular Kanban resources to help you get started with your team.
In this three-part series on Kanban for DevOps, Dominica DeGrandis, Director of Training and Coaching at LeanKit, explains three key reasons why IT Ops teams and those implementing a DevOps value chain use a lean flow approach to product development. If you’re just jumping in to this series, check out part one and part two.
Reason #3: People responsible for product support have a voice during product development.
Accountability with no authority sucks. To be responsible for keeping production running smoothly — but have no voice in the changes rolling into production — sucks energy, sucks morale, sucks cash. And that sucking noise means organizational health is heading south.