Tag Archives: project management

Top 10 Human-Centered Change & Innovation Articles of October 2024

Leave a reply

Top 10 Human-Centered Change & Innovation Articles of October 2024Drum roll please…

At the beginning of each month, we will profile the ten articles from the previous month that generated the most traffic to Human-Centered Change & Innovation. Did your favorite make the cut?

But enough delay, here are October’s ten most popular innovation posts:

  1. The Runaway Innovation Train — by Pete Foley
  2. How Leaders Make Employees Feel Respected — by David Burkus
  3. Innovation is Combination — by Greg Satell
  4. Why Modifying This One Question Changes Everything — by Robyn Bolton
  5. Acting on Strategy and Tactics — by Mike Shipulski
  6. Push versus Pull in the Productivity Zone — by Geoffrey A. Moore
  7. Next Generation Leadership Traits and Characteristics — by Stefan Lindegaard
  8. Humanizing Agility — by Janet Sernack
  9. Creating More Digital Value for Customers — by Howard Tiersky
  10. False Choice – Founder versus Manager — by Robyn Bolton

BONUS – Here are five more strong articles published in September that continue to resonate with people:

If you’re not familiar with Human-Centered Change & Innovation, we publish 4-7 new articles every week built around innovation and transformation insights from our roster of contributing authors and ad hoc submissions from community members. Get the articles right in your Facebook, Twitter or Linkedin feeds too!

SPECIAL BONUS – THREE DAYS ONLY: From now until 11:59PM ET on November 11, 2024 you can get the hardcover version of the SECOND EDITION of my latest bestselling book Charting Change for 40% OFF using code HARDC50. This deal won’t last long, so grab your copy while supplies last!

Accelerate your change and transformation success

Have something to contribute?

Human-Centered Change & Innovation is open to contributions from any and all innovation and transformation professionals out there (practitioners, professors, researchers, consultants, authors, etc.) who have valuable human-centered change and innovation insights to share with everyone for the greater good. If you’d like to contribute, please contact me.

P.S. Here are our Top 40 Innovation Bloggers lists from the last four years:

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Don’t Wait for the Wheels to Fall Off

Leave a reply

Don't Wait for the Wheels to Fall Off

GUEST POST from Mike Shipulski

When your most important product development project is a year behind schedule (and the schedule has been revved three times), who would you call to get the project back on track?

When the project’s unrealistic cost constraints wall of the design space where the solution resides, who would you call to open up the higher-cost design space?

When the project team has tried and failed to figure out the root cause of the problem, who would you call to get to the bottom of it?

And when you bring in the regular experts and they, too, try and fail to fix the problem, who would you call to get to the bottom of getting to the bottom of it?

When marketing won’t relax the specification and engineering doesn’t know how to meet it, who would you call to end the sword fight?

When engineering requires geometry that can only be made by a process that manufacturing doesn’t like and neither side will give ground, who would you call to converge on a solution?

When all your best practices haven’t worked, who would you call to invent a novel practice to right the ship?

When the wheels fall off, you need to know who to call.

If you have someone to call, don’t wait until the wheels fall off to call them. And if you have no one to call, call me.

Image credit: Pixabay

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

28 Things I Learned the Hard Way

1 Reply

28 Things I Learned the Hard Way

GUEST POST from Mike Shipulski

  1. If you want to have an IoT (Internet of Things) program, you’ve got to connect your products.
  2. If you want to build trust, give without getting.
  3. If you need someone with experience in manufacturing automation, hire a pro.
  4. If the engineering team wants to spend a year playing with a new technology, before the bell rings for recess ask them what solution they’ll provide and then go ask customers how much they’ll pay and how many they’ll buy.
  5. If you don’t have the resources, you don’t have a project.
  6. If you know how it will turn out, let someone else do it.
  7. If you want to make a friend, help them.
  8. If your products are not connected, you may think you have an IoT program, but you have something else.
  9. If you don’t have trust, you have just what you earned.
  10. If you hire a pro in manufacturing automation, listen to them.
  11. If Marketing has an optimistic sales forecast for the yet-to-be-launched product, go ask customers how much they’ll pay and how many they’ll buy.
  12. If you don’t have a project manager, you don’t have a project.
  13. If you know how it will turn out, teach someone else how to do it.
  14. If a friend needs help, help them.
  15. If you want to connect your products at a rate faster than you sell them, connect the products you’ve already sold.
  16. If you haven’t started building trust, you started too late.
  17. If you want to pull in the delivery date for your new manufacturing automation, instead, tell your customers you’ve pushed out the launch date.
  18. If the VP knows it’s a great idea, go ask customers how much they’ll pay and how many they’ll buy.
  19. If you can’t commercialize, you don’t have a project.
  20. If you know how it will turn out, do something else.
  21. If a friend asks you twice for help, drop what you’re doing and help them immediately.
  22. If you can’t figure out how to make money with IoT, it’s because you’re focusing on how to make money at the expense of delivering value to customers.
  23. If you don’t have trust, you don’t have much.
  24. If you don’t like extreme lead times and exorbitant capital costs, manufacturing automation is not for you.
  25. If the management team doesn’t like the idea, go ask customers how much they’ll pay and how many they’ll buy.
  26. If you’re not willing to finish a project, you shouldn’t be willing to start.
  27. If you know how it will turn out, it’s not innovation.
  28. If you see a friend that needs help, help them ask you for help.

Image credit: Pixabay

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

The Hidden Cost of Waiting

1 Reply

The Hidden Cost of Waiting

GUEST POST from Mike Shipulski

If you want to do a task, but you don’t have what you need, that’s waiting for a support resource. If you need a tool, but you don’t have it, you wait for a tool. If you need someone to do the task, but you don’t have anyone, you wait for people. If you need some information to make a decision, but you don’t have it, you wait for information.

If a tool is expensive, usually you have to wait for it. The thinking goes like this – the tool is expensive, so let’s share the cost over too many projects and too many teams. Sure, less work will get done, but when we run the numbers, the tool will look less expensive because it’s used by many people. If you see a long line of people (waiting) or a signup list (people waiting at their desks), what they are waiting for is usually an expensive tool or resource. In that way, to find the cause of waiting, stand at the front of the line and look around. What you see is the cause of the waiting.

If the tool isn’t expensive, buy another one and reduce the waiting. If the tool is expensive, calculate the cost of delay. Cost of delay is commonly used with product development projects. If the project is delayed by a month, the incremental revenue from the product launch is also delayed by a month. That incremental revenue is the cost of delaying the project by a month. When the cost of delay is larger than the cost of an expensive tool, it makes sense to buy another expensive tool. But, to purchase that expensive tool requires multiple levels of approvals. So, the waiting caused by the tool results in waiting for approval for the new tool. I guess there’s a cost of delay for the approval process, but let’s not go there.

Most companies have more projects than people, and that’s why projects wait. And when projects wait, projects are late. Adding people is like getting another expensive tool. They are spread over too many projects, and too little gets done. And like with expensive tools, getting more people doesn’t come easy. New hires can be justified (more waiting in the approval queue), but that takes time to find them, hire them, and train them. Hiring temporary people is a good option, though that can seem too expensive (higher hourly rate), it requires approval, and it takes time to train them. Moving people from one project to another is often the best way because it’s quick and the training requirement is less. But, when one project gains a person, another project loses one. And that’s often the rub.

When it’s time to make an important decision and the team has to wait for missing information, the project waits. And when projects wait, projects are late. It’s difficult to see the waiting caused by missing or un-communicated information, but it can be done. The easiest to see when the information itself is a project deliverable. If a milestone review requires a formal presentation of the information, the review cannot be held without it. The delay of the milestone review (waiting) is objective evidence of missing information.

Information-based waiting is relatively easy to see when the missing information violates a precedent for decision making. For example, if the decision is always made with a defined set of data or information, and that information is missing, the precedent is violated and everyone knows the decision cannot be made. In this case, everyone’s clear why the decision cannot be made, everyone’s clear on what information is missing, and everyone’s clear on who dropped the ball.

It’s most difficult to recognize information-based waiting when the decision is new or different and requires judgment because there’s no requirement for the data and there’s no precedent to fall back on. If the information was formally requested and linked to the decision, it’s clear the information is missing and the decision will be delayed. But if it’s a new situation and there’s no agreement on what information is required for the decision, it’s almost impossible to discern if the information is missing. In this situation, it comes down to trust in the decision-maker. If you trust the decision-maker and they say there’s information missing, then there’s information missing. If you trust the decision-maker and they say there’s no information missing, they should make the decision. But if you don’t trust the decision-maker, then all bets are off.

In general, waiting is bad. And it’s helpful if you can recognize when projects are waiting. Waiting is especially bad went the delayed task is on the critical path because when the project is waiting on a task that’s on the critical path, there’s a day-for-day slip in the completion date. Hint: it’s important to know which tasks and decisions are on the critical path.

Image credit: Pexels

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Projects Don’t Go All Right or All Wrong

Leave a reply

Projects Don't Go All Right or All Wrong

GUEST POST from Howard Tiersky

What The Heck Went Right?!

Have you found yourself working on a project that’s having problems, missing deadlines, over budget and/or full of defects?

Or have you launched new products only to discover that they didn’t get the uptake you had hoped in the market?

On most such projects, at some point, someone will say “when this is all over we need to do a post-mortem” to determine what went wrong and how we avoid these kinds of problems in the future. This is certainly an important and worthwhile activity. In Agile practices, we refer to this as a “retrospective” instead of using the term “post-mortem.” We do this partly to avoid the ever so slightly negative death-related connotations of the term “post-mortem;” also because anything named in Latin tends to sound intimidating. But most importantly because we take the mindset that a retrospective should not be triggered because “there was a problem” (or death!) but rather should be part of the completion of every project (or even a phase of a project).

In fact, I recommend you don’t view the retrospective being exclusively, or even primarily about identifying “what went wrong” on a project. The first and primary focus of every retrospective is what went right. The recommended guideline is that over 75% of the time in every retrospective should be spent on what went right. Why is that?

What went right is more useful than what went wrong.

Sure, its good to understand what went wrong, but even once you’ve done that you have a lot more work to do. Just knowing what went wrong doesn’t make the next project more successful, you then need also to figure out what you will do differently to make that “wrong” thing not happen again. And then even once you have “figured that out,” the reality is you may or may not have gotten it correct. Your “fix” is not yet proven.

So, there is yet a third step to try that “fix” on another project and see if it has the desired effect. Hopefully, it does and if so, great. In fact, I heartily recommend you do take this three-step approach when looking at “what went wrong.” But, let’s contrast that with how many steps it takes to benefit from what went right. Step 1- determine what went right. Step 2- determine why that thing went right (which is usually a lot easier than finding the root cause of problems).

And once you have figured out what went right and why you just need to keep doing that thing. So it’s simpler to get future benefit from what’s right vs. what’s wrong.

Now I can hear your wheels spinning, and you may be thinking “yeah, but come on if we are already doing something right, why would we stop doing it anyway? We are already doing that thing; we aren’t going to get any “incremental value” by praising what we already know how to do! We should focus on improvements! I’d like to say, “good point,” but I can’t.

It’s a terrible point, and here is why.

This line of thinking is based on a fallacy. The fallacy is that good and beneficial practices sort of automatically perpetuate themselves. Having worked with scores of large enterprises, I have not found this to be the case. In fact, when project teams retrospect on “what went wrong,” very often the root cause of the problem was a failure to engage in practices which they have done in the past that led them to success.

There are many reasons for this – efforts to seek efficiency, change in project leadership, a desire for variation, or just old-fashioned “forgetting to do it.” That’s why it’s incredibly valuable to reinforce what went right, so we don’t forget to keep doing it, and we acknowledge the value of the practices that led to the successful outcome.

But here’s another reason to focus most of your time on “what went right.”

Talking about “what went right” makes people feel good.

Perhaps you are thinking, “Come on, this is a place of business! We don’t come here to feel good; we come here to get things done! You can feel good at home!” In reality, many studies have shown morale is a hugely important component of productivity. In one study, the Gallup organization estimated that low morale in the form of worker “disengagement” costs the US economy as much as $350 billion a year. Giving people the opportunity not just to say “good job” but really “get into” what was done right, by who and why is a huge morale booster for everybody.

And here’s one final benefit to focusing on “what’s right,” when it comes time to get to that last 25% of your retrospective where you do want to talk about “what can we do better next time,” the team is going to be a lot less defensive and a lot more open to acknowledging problems and responsibility if it’s preceded by discussion of the positive aspects of the project. Furthermore, when team members become accustomed to retrospectives being positive experiences, they are less likely to procrastinate scheduling them, less likely to find an excuse to miss them, and less likely to show up in a defensive posture. All good things.

And I’ll anticipate one final question; you may be thinking, “But what if nothing went right on the project, it was a total disaster?” Believe this; something always went right; you just aren’t seeing it. Just like something can always be improved. On super successful projects its still very valuable to consider whether there are “things that went wrong” (once you’ve thoroughly covered what went right) and even on the most messed up projects, it’s worth digging to find what went right, it might be more than you think and its working from those past aspects of success, however small, that you will build towards an even more successful future.

This article originally appeared on the Howard Tiersky blog

Image Credits: Unsplash

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Who Are the Most Important People in Your Company?

2 Replies

Who Are the Most Important People in Your Company?

GUEST POST from Mike Shipulski

When the fate of your company rests on a single project, who are the three people you’d tap to drag that pivotal project over the finish line? And to sharpen it further, ask yourself “Who do I want to lead the project that will save the company?” You now have a list of the three most important people in your company. Or, if you answered the second question, you now have the name of the most important person in your company.

The most important person in your company is the person that drags the most important projects over the finish line. Full stop.

When the project is on the line, the CEO doesn’t matter; the General Manager doesn’t matter; the Business Leader doesn’t matter. The person that matters most is the Project Manager. And the second and third most important people are the two people that the Project Manager relies on.

Don’t believe that? Well, take a bite of this. If the project fails, the product doesn’t sell. And if the product doesn’t sell, the revenue doesn’t come. And if the revenue doesn’t come, it’s game over. Regardless of how hard the CEO pulls, the product doesn’t launch, the revenue doesn’t come, and the company dies. Regardless of how angry the GM gets, without a product launch, there’s no revenue, and it’s lights out. And regardless of the Business Leader’s cajoling, the project doesn’t cross the finish line unless the Project Manager makes it happen.

The CEO can’t launch the product. The GM can’t launch the product. The Business Leader can’t launch the product. Stop for a minute and let that sink in. Now, go back to those three sentences and read them out loud. No, really, read them out loud. I’ll wait.

When the wheels fall off a project, the CEO can’t put them back on. Only a special Project Manager can do that.

There are tools for project management, there are degrees in project management, and there are certifications for project management. But all that is meaningless because project management is alchemy.

Degrees don’t matter. What matters is that you’ve taken over a poorly run project, turned it on its head, and dragged it across the line. What matters is you’ve run a project that was poorly defined, poorly staffed, and poorly funded and brought it home kicking and screaming. What matters is you’ve landed a project successfully when two of three engines were on fire. (Belly landings count.) What matters is that you vehemently dismiss the continuous improvement community on the grounds there can be no best practice for a project that creates something that’s new to the world. What matters is that you can feel the critical path in your chest. What matters is that you’ve sprinted toward the scariest projects and people followed you. And what matters most is they’ll follow you again.

Project Managers have won the hearts and minds of the project team.

The Project manager knows what the team needs and provides it before the team needs it. And when an unplanned need arises, like it always does, the project manager begs, borrows, and steals to secure what the team needs. And when they can’t get what’s needed, they apologize to the team, re-plan the project, reset the completion date, and deliver the bad news to those that don’t want to hear it.

If the General Manager says the project will be done in three months and the Project Manager thinks otherwise, put your money on the Project Manager.

Project Managers aren’t at the top of the org chart, but we punch above our weight. We’ve earned the trust and respect of most everyone. We aren’t liked by everyone, but we’re trusted by all. And we’re not always understood, but everyone knows our intentions are good. And when we ask for help, people drop what they’re doing and pitch in. In fact, they line up to help. They line up because we’ve gone out of our way to help them over the last decade. And they line up to help because we’ve put it on the table.

Whether it’s IoT, Digital Strategy, Industry 4.0, top-line growth, recurring revenue, new business models, or happier customers, it’s all about the projects. None of this is possible without projects. And the keystone of successful projects? You guessed it. Project Managers.

Image credit: Unsplash

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

You Don’t Win By Completing the Most Tasks

1 Reply

You Don't Win By Completing the Most Tasks

GUEST POST from Mike Shipulski

If you have too much to do, that means you have more tasks than time. And because time is limited, the only way out is to change how you think about your task list.

If you have too many tasks, you haven’t yet decided which tasks are important and which are less important. Until you rank tasks by importance, you’ll think you have too many.

When you have more tasks than you can handle, you don’t. You can handle what you can handle. No problem there. What you have are expectations that are out of line with the reality of what one person can get done in a day. What you can get done is what you can get done. Then end. The thing to understand about task lists is they don’t give a damn about work content. They are perfectly happy to get longer when new tasks are added, regardless of your capacity to get them done. That’s just how it goes with task lists. Why do you think it’s okay to judge yourself negatively for a growing task list?

Just because a task is on a task list doesn’t mean it must get done. A task list is just a tool to keep track of tasks, nothing more. A task list helps you assess which tasks are most important so you can work on the right one until it’s time to go home.

Here are some tips on how to handle your tasks.

Identify your top three most important tasks and work on the most important one until it’s complete.

When the most important task is complete, move each task one step closer to the top and work on the most important one until it’s complete.

If you’re not willing to finish a task, don’t start it. (Think switching cost.)

Don’t start a task before finishing one. (No partial for a half-done task.)

The fastest way to complete a task is to simply remove it from the list. (Full credit for deleting a task of low importance.)

Complete the tasks you can complete and leave the rest. (And no self-judgment or guilt.)

It’s not about completing the most tasks. It’s about completing the most important ones.

Image credit: Unsplash

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Spotting a Good Leader

Leave a reply

Spotting a Good Leader

GUEST POST from Mike Shipulski

When the team can get things done without the leader, that’s the sign of a good leader.

If the organization bypasses the leader and goes directly to the subject matter experts, that’s because the leader trusts the subject matter experts.

When subject matter experts are trusted, they do amazing work. Good leaders know that.

When a team leader tells you they made a mistake and take full responsibility for it, they make it safe for you to do the same.

When the team can write a good monthly report while the team leader is on vacation, that’s good for the company and the people who can write a good report on their own.

Good leaders know that they make mistakes and know you will too. And, they’re okay with all that.

When a leader won’t tell you what to do, it’s because she believes in you and knows you’re the best person to figure it out.

When a leader says “I don’t know.” they make it safe for team members to do the same.

When a team leader defers to you, that leader knows the limits of their knowledge and yours.

When a leader responds to your question with a question, the leader is helping you answer your question so you can answer it next time on your own.

Good leaders know that sometimes good people don’t know the answer. And they’re okay with that.

When a leader is comfortable with you reaching out to their boss without their knowledge it’s because that leader has told you the truth over the last several years.

Good leaders don’t celebrate failure, they celebrate learning.

When a leader asks you to use your best judgment, that’s a compliment.

When leaders show their emotions in front of you, it demonstrates that they trust you.

Judge a leader by the performance of people on their team.

Image credit: Pexels

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

From Sticky Notes to Digital Transformation

1 Reply

How to Properly Leverage Kanban Boards

From Sticky Notes to Digital Transformation

GUEST POST from Dainora Jociute

Whether it’s a bunch of sticky notes on an office wall or a clever digital tool with color-coded boxes, most of us are familiar with the ingenious concept of a Kanban board.

Perhaps that’s not the name you use. Maybe for you and your team, it’s Trello or simply a whiteboard, yet at the very core of it all, hides a little neat Japanese invention that sparks joy – Kanban.

It is not exactly a new concept, however over the years Kanban remains largely unchanged and its popularity unwavering. In this article, I will try to take a deeper look at what it is and how to make it work for you.

A Short History of Kanban

The word Kanban translated from Japanese means sign or signboard. Back in the day, and I am talking way back – 17th century – that was exactly what Kanban was. It was a signboard signaling to passersby what services or products a business offered.

In a more recent chapter of history, in the wake of the Second World War, the Japanese automotive manufacturer Toyota was in a pickle. The company struggled to make any profit, and they realized that something must be done. This is where Taiichi Ohno, the so-called founding father of Kanban comes into the picture.

A budding industrial engineer, Ohno was sent to the US to scout and gather inspiration for improving manufacturing back at the Toyota plant. The revelation hit Ohno in the most inconspicuous place – a grocery store. He noticed that some supermarkets stocked their shelves based only on customer demand. Customers would pull products they need off a shelf, and the store would restock them only once it was gone, avoiding unnecessary overloading of the shelves with excess products in advance. This system ensured that the store only sold products with real demand.

This pull approach (on that a little later) clearly reduced waste: it saved the time wasted on restocking, resources spent on overproduction, produce thrown out, and much more. Aiming to eliminate waste without sacrificing production back at the Toyota plant, Ohno introduced the pull system in the shape of paper cards that he later named Kanban.

Each Kanban card contained a clear description of each step in the production line, be it the number of materials needed or a particular task of the production chain to be done. It controlled amounts of production ensuring that only what is needed will be created. These cards moved systematically along the whole manufacturing process and guided what must be done throughout the journey. It became a simple yet ingenious tool for managing the whole manufacturing process ensuring that no waste will be created along the way.

Later down the line, other brilliant minds realized that the same approach can be applied to other industries too, not just manufacturing.

One of the key figures responsible for this adaptation was David J. Anderson. He is known for adapting Kanban principles from their origins in manufacturing to knowledge work, particularly software development and project management.

Although there were other prominent advocates of Kanban in software development, Anderson’s 2010 book on Kanban gained significant popularity, leading him to gain widespread recognition as one of the main proponents of the Kanban we all know today.

What is Kanban?

With all that said, it is time to go into more detail about what Kanban actually is.

In the simplest words, Kanban is a visual tool, a signboard for mapping and tracking planned work, work in progress, and work done.

Kanban is a visual tool for mapping and tracking planned work, work in progress, and work done.

While Toyota mainly used the original Kanban system to track inventory in their manufacturing processes, today’s Kanban can be applied to a much broader range of work areas.

Today, Kanban is widely used in knowledge work to visualize and map the value stream. It helps teams and individuals self-organize and minimizes the need for constant supervision.

However, it takes a bit of time to reach that harmonious sync with your team and squeeze the full value from the board. There are key things in the process that should be known before kicking one off, so let’s break the Kanban down.

Kanban, the Pull System

Now, you read it in this article and most likely you heard it before: Kanban is based on the pull process. But what does that entail?

In Kanban, the concept of “pull” means that tasks or projects are pulled into the process based on the team’s skills, readiness, and capabilities. Similarly, to the pull that Ohno observed in American grocery stores, in Kanban, you take action when there is a need and capability. This approach ensures that tasks are not imposed on individuals who might not have the time but are instead taken up by those who are more likely to complete them.

This enhances efficiency and effectiveness, prevents bottlenecks, increases the completion rate, and prevents waste. In the end, by pulling tasks based on readiness, the team can maintain a sustainable workflow and deliver outcomes within the expected timeframe.

Elements of the Kanban Board

When it comes to Kanban, the true beauty hides in its simplicity, and here, less is truly more. All you need is just a few elements to have a working Kanban board:

  • Column: an element indicating the stage of the process (most commonly to be done, doing, and done.
  • Card: an element visually representing a work item. This is where you write what has to be done, when, how, and who is responsible for it.
  • Work-in-progress (WIP): a number indicating the number of tasks in the respective column. Having a WIP limit set for each “active” column helps with workload management.
  • Swimlane: horizontal lines that split the columns, used to indicate the team responsible for the tasks, urgency, or just differentiate other relevant categories. The swimlanes are particularly useful for larger projects that involve multiple departments.
  • Commitment point: a step in the process that signals when a task is ready to be taken to the next step of the development process. For example, when a team member selects a task from the backlog and moves it to the next column, the task crosses the commitment point. This means that the responsible person is committed to completing the task to the best of their knowledge.

Kanban Board

Kanban Board


In addition, it is worth knowing the following definitions:

  • Cycle time: This is the time need to complete a work item or progress a card from the backlog to the done column. Cycle time starts from the moment the work item crosses the very first commitment point and ends at the moment the work item is completed. It measures the actual time spent working on a task and is an essential metric for understanding how long it takes to complete individual items within the workflow.
  • Lead time: It is the total time taken for a work item to move through the entire workflow, starting from the moment it is requested or initiated until it is completed and delivered to the customer. It includes not only the time spent actively working on the task (cycle time) but also any waiting time or delays while the task is in progress or in queues.

Cycle time measures the actual time spent working on a task.

Lead time measures the whole time spent on a task, both active work time and inactive waiting time.

These elements, paired with a clear process policy are all you need for the Kanban process to work.

How to Make Your Kanban Work

So, while the elements of Kanban are simple and straightforward, the success of the Kanban process and results heavily depend on the implementation of policies and effective communication practices.

There are a few of those that should be set in place before you start your Kanban initiative:

  • Process policies. Essentially, this is a set of rules, guidelines, and agreements that will define how work needed to be done will be executed by the team. Having policies set before you start managing projects with Kanban will ensure that the team knows how to handle different types of tasks, and how to tackle possible issues along the way, it will assist in prioritization of work. Process policies act as the standard of your Kanban process.
  • Commitment. Tasks should not cross commitment points because a member was bored or had extra time on their hands. Goals and expectations for each task should be communicated clearly. Assigning a responsible department or team for certain tasks helps to keep track and ensure that tasks remain in competent hands.
  • Defined workflow. This refers to the specific stages (columns) through which work items move as they progress from initiation to completion. By defining your workflow in Kanban, you create a clear and visible representation of how work progresses through your process. This allows everyone to have a shared understanding of every step involved and the sequence of work.
  • Limited WIP. It is a crucial aspect in reducing the cycle time for each project. By placing a cap on the number of tasks in progress, teams can allocate their capabilities and resources more effectively, avoiding the inefficiencies of multitasking. Having a smaller number of WIPs enables rapid identification of bottlenecks and prevents overburdening the team.
  • Feedback. It helps to make iterative adjustments to optimize workflow, catalyzes learning, and promotes a culture of continuous improvement. Feedback in the Kanban process can be provided in many different ways, for example, daily stand-up meetings or code reviews done after the work item moves to a respective column (i.e. from doing to testing).

Benefits of Using the Kanban Method

Kanban is flexible, easy to use, and quick to master and there are plenty of benefits of using the method. To name a few: 

  • Workflow visualization. Visualization allows transparency, immediate feedback and real-time updates. And Kanban is an excellent way to visually represent and manage workflow, no matter how simple or complicated it is. By visually breaking down the process into small steps and putting it on a board, you can get a great view of who is working on which tasks and the overall progress of your project.
  • Improved communication and collaboration. The possibility to see everyone’s progress with each task and who is responsible for what fosters more transparent communication. Regular meetings and check-ins on the board allow teams to provide feedback and leave comments. Knowing who is responsible for certain tasks improves collaboration by making it easy to give feedback or suggestion.
  • Bottleneck identification. By leveraging the visual nature of Kanban, teams can proactively identify and address bottlenecks in the workflow. This helps optimize the flow of work, reduce delays, and increase efficiency and productivity.
  • Reduced waste and increased productivity. Kanban allows gathering information about the processes quickly and changes might be made on the spot eliminating time for rework needed. Visualizing work and identifying bottlenecks enable streamlined processes, while work-in-progress limits prevent overload, leading to faster task completion.
  • Continuous improvement. All the best aspects of Kanban culminate in Continuous Improvement. It is the most significant benefit of using Kanban in project management. With a clear and visual representation of the workflow, teams can easily identify areas in need of improvement and address issues quickly. By making incremental changes based on real-time feedback, teams can enhance their workflow, deliver higher-quality outputs, and be more responsive to customer needs.

    The transparency provided by Kanban fosters a culture of ongoing optimization, making it an amazing tool for driving continuous improvement.

From Sticky Notes to a Digital System

Some years back, I worked in a company where we used a real, physical Kanban board. And I don’t mean a whiteboard, I mean a full wall, covered from top to bottom in sticky notes (big organization, big team, and a huge process). And part of me loved it.

We all worked like busy bees, with our individual tasks, tied to a common goal. Kanban was the place where everything fell into place.

Every morning we would hover over that wall, with a cup of coffee in our hands, checking where those stickies are traveling. It was a whole story unfolding in front of our eyes.

People with Sticky Notes

However, everyone agreed that tracking each sticky note took a big bite of our mornings.

Was the task I worked on approved by legal and moved to the next stage, or was it sent back to be reworked?

That’s why I see the digitalization of Kanban as a blessing. It makes things easier to track and increases readability, which reduces waste.

Also, think about the analytics and reporting. Our manager used to take pictures of the wall and show them during the Monday team meetings. Zooming and deciphering individual handwriting… yeah, not the best. Luckily, digital tools save us from this burden.

Pros and Cons of Digital Kanban Board

There are some obvious benefits of a digital Kanban board:

  • Remote collaboration. Digital Kanban provides coherent communication and coordination among distributed teams. The team can access the Kanban board from anywhere, enabling real-time updates, tracking, and smooth communication. This fosters a sense of unity and efficiency, even when team members are geographically dispersed, ensuring that projects move forward cohesively and productively.
  • Security. Digital Kanban tools often provide encryption and secure data storage, protecting sensitive information from unauthorized access, and in case of unexpected issues, you can often rely on automatic data back-ups and easy data recovery. Finally, such tools eliminate the risks of post-it falling off, being removed without a trace or simply getting damaged. In addition, it allows you to keep all the possible sensitive data hidden away from the curious eyes of office visitors.
  • Automation. Most of the tools come with certain automation features. For example, notifications and email reminders ensure that Kanban stays active, deadlines are not forgotten, or finished tasks progress automatically. All relevant data is just a few clicks away, and integration with other relevant tools makes reporting and process improvement much easier.
  • Document management. Most digital tools provide one safe and easy-to-access place to gather information, supporting files, and leave comments and feedback by the team.
  • Customization. Most of the tools allow flexible customization, you can adapt the Kanban to your unique workflow, limit WIPs, add swimlanes, or add additional columns. As a secondary bonus, customization gives a chance to create a visually appealing board or a board that perfectly fits your brand.

However, as with most tools, there is no one right way. Digital Kanban tools has some disadvantages too:

  • Lack of communication. Digital tools allow us to check information when we want, from wherever it is comfortable for us, meaning that we can finish the whole process barely ever meeting our team.

    So, without a physical board, people might end up working in isolation. While it might sound like a dream for an introvert, in the grander scheme of things, lack of communication might cause an array of issues like misunderstandings, misalignment, delayed issue resolution, and others.
  • Unfiltered input. The digital board might open the gate to idea dumping. While shooting as many shots as possible can be a good thing in a brainstorming session, only planned and discussed tasks should end up on a Kanban board to ensure that planned projects are finished efficiently.
  • Dependency on third-party vendors. Using digital tools means relying on third-party vendors, and if the vendor faces issues or discontinues the product, it could disrupt the team’s workflow.

With that said, if you will look deeper into the pros and cons of digital vs physical, you might find a lot of contradicting information. Some articles might argue that digital tools can be time-consuming, requiring people to navigate additional applications, while others claim that physically going to a board might take extra time. 

Similarly, some articles highlight concerns about communication issues and working in silos, whereas others praise digital tools for facilitating communication, especially among remote teams. The contrasting viewpoints can lead to different interpretations and opinions on the impact of digital tools in the workplace.

So, physical, or digital? As predictable as my answer will sound – it all depends on your unique way of working.

Going Digital

There are a lot of tools that could be used as a digital Kanban board. From the good old Excel to a dedicated digital Kanban tool such as Kanbanize, you have plenty to choose from. However, such tools are not necessarily equal to one another. If you were to take the digital route, here are some points worth considering before committing: 

  • Integration: i.e.: does the tool work with systems and other tools you already use?
  • Visualization: i.e.: does the allow easy visualization of the workflow?
  • Customization: i.e.: can you change and add elements as columns, WIPs, etc?
  • Automation: i.e.: are you able to get reminders, or do finished tasks move automatically to the next column?
  • Analytics: i.e.: can you extract data on cycle time or lead time?
  • Ease of use: i.e.: how steep is the learning curve?
  • Price: i.e.: does additional features, like the number of users, or analytics cost extra?

Conclusion

Kanban has come a long way from its inception as a simple manufacturing process management tool to the project management tool that it is today. And while Kanban is often associated with development, software, Lean, Agile, and Scrum… do not get tricked. Kanban can be used to manage wide-ranging projects with multiple stakeholders and at the same time, it can be used to help with organizing and managing personal projects.

As discussed earlier, it is obvious that the simplicity, flexibility, ease of deployment, and effectiveness in visualizing workflows, promoting collaboration, and continuously improving processes make Kanban an attractive tool for a variety of industries. It brings a myriad of benefits such as the reduction of bottlenecks, enhanced productivity and efficiency, improved communication and so much more. So, it is a no-brainer when it comes to giving Kanban a shot.

As to why it remains mostly unchanged, the good old rule of if it ain’t broke, don’t fix it applies here perfectly. From the 1940s to 2023, from automotive manufacturing to software development, Kanban has been and still is a simple tool that simply works.

Image credits: Viima, Unsplash

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Why Not Now?

Leave a reply

Why Not Now?

GUEST POST from Mike Shipulski

If you are anxious, you’re worried about what might happen. You’re living in the future. If you are sad or angry, you’re reacting to what happened. You’re living in the past. Nothing can be accomplished when living in the past because the die is cast. And nothing can be accomplished when living in the future because it’s all in your head. The only time we have is now.

The only time to start is now. Even if your project is a short one, you’re in a day-for-day slip with your completion date for every day you don’t start. And this is doubly true for long projects. If you’re living in the past, you block yourself from starting because the last project was difficult, you didn’t have the resources or it didn’t come out as expected, and you want to protect yourself from a rerun. If you’re living in the past, you block yourself from starting because you don’t know how it will turn out, you don’t have all the answers, you don’t have sufficient resources, and you don’t know what you don’t know. Acknowledge the problems with the past and potential problems with the future, and start anyway.

Starting starts with starting.

The only time to say something is now. If you’re living in the past, you block yourself from saying something controversial or thought-provoking because you remember how it went the last time someone did that. If you’re living in the future, you prevent yourself from saying something radical because, well, you weren’t paying attention and missed your opportunity to change history. Acknowledge that there may be some blowback for your insightful comments, live in the now and say them anyway. And live in the now so you can pay attention and use your sharp wit to create the future.

If you don’t say something, nothing is ever said.

The only time to help is now. Living in the past, you block yourself from understanding the significance of the situation because you see it through old lenses. Living in the future, you block yourself from helping because you worry if the helping will help or worry the helping will get in the way of your future commitments. If someone needs help, help them now. They will understand that the outcome is uncertain, and they’re okay with that. In fact, they will be happy you recognized their troubling situation and made time to check in with them. When you live in the now, people appreciate it. The time to help is now.

When no one helps, no one is helped.

When you find yourself living in the past, close your eyes, recognize your anger or sadness, and focus on your breath for ten seconds. And if that doesn’t work, put your hand on your chest and do it again. And if that doesn’t work, tell yourself your sadness is temporary and do it again. This is a fail-safe way to bring yourself into the now. Then, sitting in the now, start that project, say what must be said, and help people.

And when you find yourself living in the future, close your eyes, recognize your anxiety, and focus on your breath for ten seconds. And if that doesn’t work, put your hand on your chest and do it again. And if that doesn’t work, tell yourself your anxiety is temporary and repeat. This will bring you into the now. Then, sitting in the now, start that project, say what must be said, and help people.

The only time to shape the future is now.

Image credit: Pixabay

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.