Category Archives: Management

An Innovation Rant: Just Because You Can Doesn’t Mean You Should

1 Reply

An Innovation Rant: Just Because You Can Doesn’t Mean You Should

GUEST POST from Robyn Bolton

Why are people so concerned about, afraid of, or resistant to new things?

Innovation, by its very nature, is good. It is something new that creates value.

Naturally, the answer has nothing to do with innovation.

It has everything to do with how we experience it.

And innovation without humanity is a very bad experience.

Over the last several weeks, I’ve heard so many stories of inhuman innovation that I have said, “I hate innovation” more than once.

Of course, I don’t mean that (I would be at an extraordinary career crossroads if I did). What I mean is that I hate the choices we make about how to use innovation.

Just because AI can filter resumes doesn’t mean you should remove humans from the process.

Years ago, I oversaw recruiting for a small consulting firm of about 50 people. I was a full-time project manager, but given our size, everyone was expected to pitch in and take on extra responsibilities. Because of our founder, we received more resumes than most firms our size, so I usually spent 2 to 3 hours a week reviewing them and responding to applicants. It was usually boring, sometimes hilarious, and always essential because of our people-based business.

Would I have loved to have an AI system sort through the resumes for me? Absolutely!

Would we have missed out on incredible talent because they weren’t out “type?” Absolutely!

AI judges a resume based on keywords and other factors you program in. This probably means that it filters out people who worked in multiple industries, aren’t following a traditional career path, or don’t have the right degree.

This also means that you are not accessing people who bring a new perspective to your business, who can make the non-obvious connections that drive innovation and growth, and who bring unique skills and experiences to your team and its ideas.

If you permit AI to find all your talent, pretty soon, the only talent you’ll have is AI.

Just because you can ghost people doesn’t mean you should.

Rejection sucks. When you reject someone, and they take it well, you still feel a bit icky and sad. When they don’t take it well, as one of my colleagues said when viewing a response from a candidate who did not take the decision well, “I feel like I was just assaulted by a bag of feathers. I’m not hurt. I’m just shocked.”

So, I understand ghosting feels like the better option. It’s not. At best, it’s lazy, and at worst, it’s selfish. Especially if you’re a big company using AI to screen resumes.

It’s not hard to add a function that triggers a standard rejection email when the AI filters someone out. It’s not that hard to have a pre-programmed email that can quickly be clicked and sent when a human makes a decision.

The Golden Rule – do unto others as you would have done unto you – doesn’t apply to AI. It does apply to you.

Just because you can stack bots on bots doesn’t mean you should.

At this point, we all know that our first interaction with customer service will be with a bot. Whether it’s an online chatbot or an automated phone tree, the journey to a human is often long and frustrating. Fine. We don’t like it, but we don’t have a choice.

But when a bot transfers us to a bot masquerading as a person? Do you hate your customers that much?

Some companies do, as my husband and I discovered. I was on the phone with one company trying to resolve a problem, and he was in a completely different part of the house on the phone with another company trying to fix a separate issue. When I wandered to the room where my husband was to get information that the “person” I was talking to needed, I noticed he was on hold. Then he started staring at me funny (not as unusual as you might think). Then he asked me to put my call on speaker (that was unusual). After listening for a few minutes, he said, “I’m talking to the same woman.”

He was right. As we listened to each other’s calls, we heard the same “woman” with the same tenor of voice, unusual cadence of speech, and indecipherable accent. We were talking to a bot. It was not helpful. It took each of us several days and several more calls to finally reach humans. When that happened, our issues were resolved in minutes.

Just because innovation can doesn’t mean you should allow it to.

You are a human. You know more than the machine knows (for now).

You are interacting with other humans who, like you, have a right to be treated with respect.

If you forget these things – how important you and your choices are and how you want to be treated – you won’t have to worry about AI taking your job. You already gave it away.

Image Credit: Pexels

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

An Innovation Lesson From The Rolling Stones

1 Reply

GUEST POST from Robyn Bolton

If you’re like most people, you’ve faced disappointment. Maybe the love of your life didn’t return your affection, you didn’t get into your dream college, or you were passed over for promotion. It hurts. And sometimes, that hurt lingers for a long time.

Until one day, something happens, and you realize your disappointment was a gift. You meet the true love of your life while attending college at your fallback school, and years later, when you get passed over for promotion, the two of you quit your jobs, pursue your dreams, and live happily ever after. Or something like that.

We all experience disappointment. We also all get to choose whether we stay there, lamenting the loss of what coulda shoulda woulda been, or we can persevere, putting one foot in front of the other and playing The Rolling Stones on repeat:

“You can’t always get what you want

But if you try sometimes, well, you might just find

You get what you need”

That’s life.

That’s also innovation.

As innovators, especially leaders of innovators, we rarely get what we want. But we always get what we need (whether we like it or not)

We want to know.

We need to be comfortable not knowing.

Most of us want to know the answer because if we know the answer, there is no risk. There is no chance of being wrong, embarrassed, judged, or punished. But if there is no risk, there is no growth, expansion, or discovery.

Innovation is something new that creates value. If you know everything, you can’t innovate.

As innovators, we need to be comfortable not knowing. When we admit to ourselves that we don’t know something, we open our minds to new information, new perspectives, and new opportunities. When we say we don’t know, we give others permission to be curious, learn, and create.

We want the creative genius and billion-dollar idea.

We need the team and the steady stream of big ideas.

We want to believe that one person blessed with sufficient time, money, and genius can change the world. Some people like to believe they are that person, and most of us think we can hire that person, and when we do find that person and give them the resources they need, they will give us the billion-dollar idea that transforms our company, disrupts the industry, and change the world.

Innovation isn’t magic. Innovation is team work.

We need other people to help us see what we can’t and do what we struggle to do. The idea-person needs the optimizer to bring her idea to life, and the optimizer needs the idea-person so he has a starting point. We need lots of ideas because most won’t work, but we don’t know which ones those are, so we prototype, experiment, assess, and refine our way to the ones that will succeed.

We want to be special.

We need to be equal.

We want to work on the latest and most cutting-edge technology and discuss it using terms that no one outside of Innovation understands. We want our work to be on stage, oohed and aahed over on analyst calls, and talked about with envy and reverence in every meeting. We want to be the cool kids, strutting around our super hip offices in our hoodies and flip-flops or calling into the meeting from Burning Man.

Innovation isn’t about you. It’s about serving others.

As innovators, we create value by solving problems. But we can’t do it alone. We need experienced operators who can quickly spot design flaws and propose modifications. We need accountants and attorneys who instantly see risks and help you navigate around them. We need people to help us bring our ideas to life, but that won’t happen if we act like we’re different or better. Just as we work in service to our customers, we must also work in service to our colleagues by working with them, listening, compromising, and offering help.

What about you?

What do you want?

What are you learning you need?

Image Credit: Unsplash

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

Why You Should Care About Service Design

What is Service Design?

RB: Hi, Leala, thanks for taking the time to talk with me today.

LA: My pleasure! I’m excited about this topic. I’ve managed teams with service designers, and I’ve always been impressed by the magical way they brought together experience strategy, UX, and operations.

RB: I felt the same way after you explained it to me. Before we get too geeked up about the topic, let’s go back to the beginning and define “service.”

LA: Service is something that helps someone accomplish a goal. As a result, every business needs service design because every business is in the service industry.

RB: I’ll be honest, I got a little agitated when I read that because that’s how I define “solution.” But then I saw your illustration explaining that service design moves us from seeing and problem-solving isolated moments to seeing an integrated process. And that’s when it clicked.

LA: That illustration is from Lou Downe’s talk Design in Government Impact for All . Service Design helps us identify what customers want and how to deliver those services effectively by bringing together all the pieces within the organization. It moves us away from fragmented experiences created by different departments and teams within the same company to an integrated process that enables customers to achieve their goals.

Why You Need It

RB: It seems so obvious when you say it. Yet so often, the innovation team spends all their time focused on the customer only to develop the perfect solution that, when they toss it over the wall for colleagues to make, they’re told it’s not possible, and everything stops. Why aren’t we always considering both sides?

LA: One reason, I think, is people don’t want to add one more person to the team. Over the past two decades, the number of individuals required to build something has grown exponentially. It used to be that one person could build your whole website, but now you need user experience designers, researchers, product managers, and more. I think it’s just overwhelming for people to add another individual to the mix. We believe we have all the tools to fix the problem, so we don’t want to add another voice, even if that voice explains the huge disconnect between everything built and their operational failures.

RB: Speaking of operational failures, one of the most surprising things about Service Design is that it almost always results in cost savings. That’s not something most people think about when they hear “design.”

LA: The significant impact on the bottom line is one of the most persuasive aspects of service design. It shifts the focus from pretty pictures to the actual cost implications. Bringing in the operational side of the business is crucial. Building a great customer journey and experience is important, but it’s also important to tie it back to lost revenue and increased cost to serve

Proof It Works

LA: One of the most compelling cases I recently read was about Autodesk’s transition to SaaS, they brought in a service design company called Future Proof. Autodesk wanted to transition from a software licensing model to a software-as-a-service model. It’s a significant transition not just in terms of the business model and pricing but also in how it affects customers.

If you’re a customer of Autodesk, you used to pay a one-time fee for your software, but now you are paying based on users and services. Budgeting becomes messy. The costs are no longer simple and predictable. Plus, it raises lots of questions about the transition, cost predictability, control over access, managing subscriptions, and flexibility. Notice that these issues are about people managing their money and increasing costs. These are the areas where service design can truly help.

Future Proof conducted customer interviews, analyzed each stage of the customer journey, looked at pricing models and renewal protocols, and performed usability studies. When they audited support ticket data for the top five common customer issues, they realized that if Autodesk didn’t change their model, the cost of running software for every customer would increase by 40%, and profit margins would decrease by 15% to 20%.

Autodesk made the change, revenue increased significantly, and their stock price doubled. Service design allows for this kind of analysis and consideration of operational costs.

How to Learn More

RB: Wow, not many things can deliver better service, happier customers, and doubling a stock price. Solid proof that companies, and innovation teams in particular, need to get smart on service design. We’ve talked a lot about the What and Why of Service Design. How can people learn more about the How?

LA: Lou Downe’s book is a great place to start Good Services: How to Design Services That Work. So is Woo, Wow, and Win: Service Design, Strategy, and the Art of Customer Delight by Thomas A Stewart and Patricia O’Connell. I also recommend people check out The Service Design Network for tools and case studies and TheyDo, which helps companies visualize and manage their service design.

Image Credit: Pixabay

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

Leaders Avoid Doing This One Thing

1 Reply

GUEST POST from Robyn Bolton

Being a leader isn’t easy. You must BE accountable, compassionate, confident, curious, empathetic, focused, service-driven, and many other things. You must DO many things, including build relationships, communicate clearly, constantly learn, create accountability, develop people, inspire hope and trust, provide stability, and think critically. But if you’re not doing this one thing, none of the other things matter.

Show up.

It seems obvious, but you’ll be surprised how many “leaders” struggle with this.

Especially when they’re tasked with managing both operations and innovation.

It’s easy to show up to lead operations.

When you have experience and confidence, know likely cause and effect, and can predict with relative certainty what will happen next, it’s easy to show up. You’re less likely to be wrong, which means you face less risk to your reputation, current role, and career prospects.

When it’s time to be a leader in the core business, you don’t think twice about showing up. It’s your job. If you don’t, the business, your career, and your reputation suffer. So, you show up, make decisions, and lead the team out of the unexpected.

It’s hard to show up to lead innovation.

When you are doing something new, facing more unknowns than knowns, and can’t guarantee an outcome, let alone success, showing up is scary. No one will blame you if you’re not there because you’re focused on the core business and its known risks and rewards. If you “lead from the back” (i.e., abdicate your responsibility to lead), you can claim that the team, your peers, or the company are not ready to do what it takes.

When it’s time to be a leader in innovation, there is always something in the core business that is more urgent, more important, and more demanding of your time and attention. Innovation may be your job, but the company rewards you for delivering the core business, so of course, you think twice.

Show up anyway

There’s a reason people use the term “incubation” to describe the early days of the innovation process. To incubate means to “cause or aid the development of” but that’s the 2^nd definition. The 1^st definition is “to sit on so as to hatch by the warmth of the body.”

You can’t incubate if you don’t show up.

Show up to the meeting or call, even if something else feels more urgent. Nine times out of ten, it can wait half an hour. If it can’t, reschedule the meeting to the next day (or the first day after the crisis) and tell your team why. Don’t say, “I don’t have time,” own your choice and explain, “This isn’t a priority at the moment because….”

Show up when the team is actively learning and learn along with them. Attend a customer interview, join the read-out at the end of an ideation session, and observe people using your (or competitive) solutions. Ask questions, engage in experiments, and welcome the experiences that will inform your decisions.

Show up when people question what the innovation team is doing and why. Especially when they complain that those resources could be put to better use in the core business. Explain that the innovation resources are investments in the company’s future, paving the way for success in an industry and market that is changing faster than ever.

You can’t lead if you don’t show up.

Early in my career, a boss said, “A leader without followers is just a person wandering lost.” Your followers can’t follow you if they can’t find you.

After all, “80% of success is showing up.”

Image credit: Pixabay

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

Turn Cynics into Believers in Three Simple Steps

Why You Need to Say Yes to Dr. No

Let’s be honest, no one wants to do this. At best, Dr. No’s negativity and smug predictions of inevitable failure are downers, dampening and discouraging the culture of questioning, experimentation, and learning you’re trying to create. At worst, it can feel like working with a saboteur hell-bent on doing the “I told You So” dance atop the ruins of your innovation team.

But just like eating your vegetables, you need to do it because it will make you and your innovation efforts healthier, stronger, and more likely to live longer.

How to Say Yes to Dr. No

Step 1: Be Human. Together.

As with many things in life, the first step is changing how you think and behave. Naturally, you have feelings, perceptions, and even predictions about Dr. No and their likely behavior. Set them aside. Not because they’re incorrect but because you can’t move forward if you’re standing in a hole.

So, start with what you have in common – Dr. No is a human being, just like you.

Like other human beings, Dr. No needs to feel connected and accepted. When they don’t feel connected and accepted, they will feel defensive and under attack and respond by taking steps to protect themselves and their jobs. But when they connect and feel accepted, you have the foundation for psychological safety.

To establish a connection and foster a feeling of acceptance, try:

Acknowledging the importance of the job they’re doing and its impact on the business
Asking questions to understand better how they think and what they prioritize
Building a rapport by sharing some of your aspirations and concerns and asking about theirs

Step 2: Invite Them on the Journey

People love what they create. It’s the only way to explain why people have outsized attachments to IKEA furniture, distorted art projects, and failed products.

Invite Dr. No to be part of the creation process. Don’t tell them they’re part of it, that’s the business version of kidnapping, and no one likes being kidnapped.

Instead, express your desire for them to be involved because you value their perspective. Ask them how and when they want to be involved. Share how you want them to be involved. Then work together to find a solution that works for both of you. Stay open to experimenting and changing how and when involvement happens. Make this a learning process for both of you as you work to do what’s best for the business.

Step 3: Stay curious

One of the most valuable lessons from Ted Lasso (and not Walt Whitman) is the importance of being curious, not judgmental.

As you do the work of innovation, there will be times when Dr. No lives up (or down) to their name. No matter how much time you invested in your relationship, how much psychological safety you built, or how involved they were in the process, they will still say No.

If you are judgmental, that No is the end of the conversation. If you’re curious, it’s the start.

So, get curious and ask,

What causes you to say that? (probe on what they see, think, and feel)
Have you seen something like this before? What was the context? What happened?
What do you need to see to say Yes?

Engage them in solving the problem with you rather than defending themselves against you.

Can Dr. No become Dr. Yes?

Maybe.

I’ve seen it happen, even to the point that Dr. No became the team’s loudest champion.

I’ve also seen it not happen. But even then, the No is less harsh, devastating, and final.

You won’t know until you try. Certainly, you won’t say no to that.

Image credit: Pexels

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

3 Ways to Make Smarter Decisions – Confidently

2 Replies

3 Ways to Make Smarter Decisions - Confidently

GUEST POST from Robyn Bolton

When my niece was 4 years old, she looked at her mom (my sister) and said, “I can’t wait until I’m an adult so I can be in charge and make all the decisions.” My sister laughed and laughed.

Being in charge looks glamorous from the outside, but it is challenging, painful, and sometimes soul-wrenching. Never is this truer than when you must make a tough decision and don’t have all the data you want or need.

But lately, I’ve noticed more and more executives defer making decisions. They’ll say they want more data, to hear what another executive thinks, or are nervous that we’re rushing to decide.

This deferral is a HUGE problem because making decisions is literally their job! After all, as Norman Schwarzkopf wrote in his autobiography, “When placed in command, take charge.”

When you decide, you lose

A decision is “a choice that you make about something after thinking about several possibilities.” Seems innocent enough, right? Coke or Pepsi. Paper or plastic. Ariana Madix or Raquel Leviss (if you don’t know about this one, consider yourself lucky. If you choose to know about it, click here).

The problem with making decisions is that loss is unavoidable. Heck, the word “decide” comes from the Latin roots “de,” meaning off, and “caedre,” meaning cut. When you choose Coke, paper bags, or Ariana, you are cutting off the opportunity to drink Pepsi with that meal, use a plastic bag to carry your purchases or support Rachel in a pointless pop culture debate.

Decisions get more challenging as the stakes get higher because the fear of loss skyrockets. Loss aversion, a cognitive bias describing why the psychological pain of loss is twice as acute as the pleasure of gain, is common in cognitive psychology, decision theory, and behavioral economics. You see this bias in action when someone refuses to ask questions or challenge the status quo, to take a good deal because it’s below their initial baseline, or to sell an asset (like a house) for less than they paid for it.

No decision is the worst decision

Deciding not to decide is often the worst decision of all. Because it feels like you’re avoiding loss and increasing your odds of making the right decision by gathering more data and input, it’s easy to forget that you’re losing time, employee engagement and morale, and potential revenue and profit.

When you decide not to decide, progress slows or even stops. No decision gives your competition time to catch up or even pass you. Your team gets frustrated, morale drops, and people search for other opportunities to progress and have an impact. The date of the first revenue slips further into the future, slowly becoming just a theoretical number in a spreadsheet.

Decide how to decide

In a VUCA world, a perfect, risk-free decision that offers only upside does not exist. If it did, the business wouldn’t need an executive with your experience, intellect, and courage. Yet here you are.

It’s your job to make decisions.

Make that job easier by deciding how to decide

1. Tell people what you need to see to say Yes. “I’ll know it when I see it” is one of the biggest management cop-outs ever. If you don’t know what you want, don’t waste money and time requiring your team to become mind readers. But you probably know what you want. You’re just afraid of being wrong. Instead of allowing your fear to fuel inefficiency, tell the team what you need or want to see and that, as they make progress, that request might change. Then set regular check-ins so that if/when it happens, it happens quickly and is communicated clearly.

2. Break big decisions down into little decisions. I once worked with a team that had an idea for a new product. They planned to pitch to the executive committee and request 3 million dollars to develop and launch the idea. After some coaxing, we decided to avoid that disaster and brainstormed everything that needed to be true to make the idea work. We devised a plan to test the three assumptions that, if we were wrong, would instantly kill the idea. When we pitched to the executive committee, we received an immediate Yes.

3. Present options and implications. As anyone with a toddler knows, you don’t ask yes or no questions. You give them options – do you want to wear the yellow or pink shirt? If they pick something else, like their Batman costume, you explain the implications of that decision and why the options previously presented are better. Sometimes they pick the yellow shirt. Sometimes they pick the Batman costume. You could force them to make the right decision, but no one wins. (Yes, I just compared managers to toddlers. Prove me wrong).

It’s your decision

Being in charge requires making decisions. When you decide, you lose the option (maybe temporarily, maybe forever) to pursue a different path. But you can’t be afraid to do it.

After all, “Sometimes you win, sometimes you lose, sometimes it rains.”

Image credit: Pixabay

Sign 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

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

The Real Reasons Employees Stay Or Leave

1 Reply

Hint: It’s about more than money

The Real Reasons Employees Stay Or Leave

GUEST POST from Shep Hyken

What if every great employee you (or your company) hired never left? Of course, that’s unrealistic … or is it? Joey Coleman is one of the brightest authors and speakers on the planet. His first book, Never Lose a Customer Again, is one of the very best books I’ve read on how to keep your customers coming back. He’s now taken some of the same ideas that worked for customer retention and written a second book, just as brilliant, Never Lose an Employee Again.

Coleman studied and researched organizations worldwide, and he found that 50% of hourly employees quit before their 100-day anniversary. For non-hourly or salaried employees, it’s 20%. I interviewed Coleman on Amazing Business Radio to learn how we can keep good employees.

“How we onboard employees and make them feel part of our community can differentiate whether they will be long-time employees or leave almost as fast as they came,” Coleman said. “The first 100 days are the most important time in the entire relationship with an employee because this is where the foundation is laid.”

So, why do employees leave? Contrary to popular belief, the No. 1 reason an employee leaves to work elsewhere is not money. In the traditional exit interview, where an employee talks to their employer face-to-face, money is the easiest and safest excuse for an exit. The true reasons for leaving are more telling—and can help prevent an employee from going, even if offered more money somewhere else. Coleman cites the Work Institute employee retention study, sharing the top five reasons employees leave:

No clear career path — This is the top reason employees leave. Nearly one-quarter (24%) don’t see future opportunities in the organization. Most employees want to advance their careers and learn new skills. Laying out a potential path for an employee from the very beginning of their employment with you can have long-term benefits.
Stress or lack of resources — Not providing employees with the tools they need or giving them too heavy of a workload can impact their emotional health, which could lead them to find work at another company.
Health and family matters — As much as an employee may love working with your organization, personal health, a sick child or an aging parent can interfere with their ability to work. Regarding the latter, Coleman says, “Just as some employers provide daycare for young children, some employers in the future will also provide an eldercare program.”
Work/life balance — The job has to fit the employee’s lifestyle. Something as seemingly insignificant as a long commute can negatively impact the employee’s personal life so much that they leave.
Money — Almost one in 10 (9%) leave because of money. That means nine out of 10 leave for other reasons, often within our control.

After reading the reasons listed above, here is Coleman’s top advice:

Affirm the employee made the right decision to come to work at your organization — The concept of affirm is one of the eight phases of the first 100 days Coleman covers in his book. There is a scientifically proven emotional reaction in which a new employee begins to doubt their decision to accept your job offer. It is called “new hire’s remorse,” which happens between when they accept the job offer and their first day. Reaffirm your new employee’s decision to accept your job offer. Establish a personal and emotional connection even before their first day.
On-boarding must be practiced at a higher level — Don’t just onboard the first day or two (or even a week or two). Coleman says, “If you’re not painting a clear path for your people but expecting them to manage and figure out their careers on their own, then you deserve to lose them.” The amount of time you spend with employees over the first 100 days directly correlates to how long they will stay.
The employee’s personal life is important — Notice that three of the five reasons people leave the organization are personal. Coleman says, “You need to know what’s going on between 5 p.m. and 9 a.m. as much as you are interested in what’s happening between 9 a.m. and 5 p.m. What are your people doing and dealing with when they are not at work?”

I’ve often said that you won’t have a business without customers. Coleman makes the case that the same applies to employees. Much of what gets customers to come back is a great customer experience. You can’t deliver a great CX without a great employee experience on the inside of your organization. Coleman says, “People think that customer experience and employee experience are two different silos. The better way to look at this is that they are two sides of the same coin. We must work on both!”

This article originally appeared on Forbes.com

Image Credits: Shep Hyken

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

How to Make Navigating Ambiguity a Super Power

1 Reply

GUEST POST from Robyn Bolton

You are a leader. The boss. The person in charge.

That means you know the answer to every question, make the right decision when faced with every choice, and act confidently when others are uncertain. Right?

(Insert uproarious laughter here).

Of course not. But you act like you do because you’re the leader, the boss, the person in charge.

You are not alone. We’re all doing it.

We act like we have the answers because we’ve been told that’s what leaders do. We act like we made the right decision because that’s what leaders do in a volatile, uncertain, complex, and ambiguous (VUCA) world where we must work quickly and flexibly while doing more with less.

But what if we didn’t?

What if we stopped pretending to have the answer or know the right choice? What if we acknowledged the ambiguity of a situation, explored its options and interpretations for just a short while, and then decided?

We’d make more informed choices. We’d be more creative and innovative. We’d inspire others.

So why do we keep pretending?

Ambiguity: Yea! Meh. Have you lost your mind?!?

Stanford’s d.School calls the ability to navigate ambiguity “the super ability” because it’s necessary for problem-finding and problem-solving. Ambiguity “involves recognizing and stewing in the discomfort of not knowing, leveraging and embracing parallel possibilities, and resolving or emerging from ambiguity as needed.”

Navigating ambiguity is essential in a VUCA world, but not all want to. They found that people tend to do one of three things when faced with ambiguity:

Endure ambiguity as “a moment of time that comes before a solution and is antagonistic to the objective – it must be conquered to reach the goal.”
Engage ambiguity as “an off-road adventure; an alternate path to a goal. It might be rewarding and helpful or dangerous and detrimental. Its value is a chosen gamble. Exhilaration and exhaustion are equally expected.”
Embrace ambiguity as “oceanic and ever-present. Exploration is a challenge and an opportunity. The longer you spend in it, the more likely you are to discover something new. Every direction is a possibility. Navigation isn’t simple. It requires practice and patience.

Students tend to enter the program with a resignation that ambiguity must be endured. They leave embracing it because they learn how to navigate it.

You can too.

In fact, as a leader in a VUCA world, you and your team need to.

How to Embrace (or at least Engage) Ambiguity

When you want to learn something new, the library is one of the best places to start. In this case, the Library of Ambiguity – an incredible collection of the resources, tools, and activities that professors at Stanford’s d.School use to help their students build this super ability.

It’s easy to get overwhelmed by the number of resources, so here are three that I recommend:

Design Project Scoping Guide

What it is: A guide for selecting, framing, and communicating the intentions of a design project
When to use it: When you are defining an innovation project and need to align on scope, goals, and priorities
Why I like it: The guide offers excellent examples of helpful and unhelpful scoping documents.

Learning Zone Reflection Tool

What it is: A tool to help individuals better understand the tolerance of ambiguity, especially their comfort, learning, and panic zones
When to use it: Stanford used this as a reflection tool at the end of an introductory course, BUT I would use it at the start of the project as a leadership alignment and team-building tool:
- Leadership alignment – Ask individual decision-makers to identify their comfort, learning, and panic zones for each element of the Project Scoping Guide (problem to be solved, target customer, context, goals, and priorities), then synthesize the results. As a group, highlight areas of agreement and resolve areas of difference.
- Team-building – At the start of the project, ask individual team members to complete the worksheet as it applies to both the project scope and the process. Individuals share their worksheets and, as a group, identify areas of shared comfort and develop ways to help each other through areas of learning or panic.
Why I like it: Very similar to the Project Playground concept I use with project teams to define the scope and set constraints, it can be used individually to build empathy and support amongst team members.

Team Dashboards

What it is: A tool to build trust and confidence amongst a team working through an ambiguous effort
When to use it: At regular pre-defined intervals during a project (e.g., every team check-in, at the end of each Sprint, once a month)
What I like about it:
- Individuals complete it BEFORE the meeting, so the session focuses on discussing the dashboard, not completing it
- The dashboard focuses on the usual business things (progress against responsibilities, the biggest challenge, next steps) and the “softer” elements that tend to have the most significant impact on team experience and productivity (mood, biggest accomplishment, team balance between talking and doing)

Learn It. Do It.

The world isn’t going to get simpler, clearer, or slower. It’s on you as a leader to learn how to deal with it. When to slow it down and explore and when to speed it up and act. No one is born knowing. We all learn along the way. The Library will help. No ambiguity about that!

Image credit: Pexels

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

5 Tips for Leaders Navigating Uncertainty

From Executives at P&G, CVS, Hannaford, and Intel

5 Tips for Leaders Navigating Uncertainty

GUEST POST from Robyn Bolton

“We have successfully retained the opportunity for improvement.”

When the CEO said this to kick off a meeting, I knew we were in for an adventure. He smirked at the corporate double-speak, paused for the laughter, then outlined all the headwinds facing the business. But the only thing I remember from that meeting was his opening line.

I think about it all the time. Because it seems to apply all the time.

And despite the turmoil brought on by a pandemic, a war, and an economic slowdown, we have successfully retained the opportunity to improve how we deal with uncertainty.

That isn’t to say we haven’t improved over the past three years. In fact, at an event sponsored by NextUp, four executives from P&G, CVS, Hannaford, and Intel shared what they learned and how they changed while navigating uncertainty.

Listen more

Dave DeJohn, Director of Operations for Hannaford, talked about the importance of listening deeply and constantly to employees, especially those on the front lines. Consistent with its core values of family, community, quality, and value, store associates are trained that the customer is always right. However, as incidents of verbal abuse increased during the lockdowns, employee satisfaction and mental health declined. By closely listening and observing what was happening in stores, Hannaford’s leadership modified their customer service approach to “the customer is always right, within reason” and empowered employees to stand up for themselves and each other when faced with hostile shoppers.

Stronger relationships lead to stronger results

Every executive shared stories from the early days of working from home – technical glitches, kids invading calls, and even cats positioning themselves awkwardly in front of cameras when the human stepped away. Far from being signals of a lack of commitment or professionalism, these moments transformed roles and titles into human beings, juggling all the things humans must juggle. Once people started seeing others as fellow humans versus bosses, peers, or subordinates, they connected on a human level and formed genuine and trusting relationships. Those relationships led to better collaboration, more effective troubleshooting, and better business results.

Concise concrete communication is critical

In periods of uncertainty, information is power. But it’s also constantly changing. For that reason, constant communication is a must. But in a large organization, communication often comes from multiple departments – employee relations, HR, health and safety, operations, and marketing, to name a few – and that can be overwhelming. For this reason, DeJohn learned that keeping every message concise (ideally the length of a tweet but no more than a short paragraph) and concrete (specific, tangible, tactical rather than high-level platitudes) proved critical to keeping people aligned and moving forward.

Just because you can, doesn’t mean you need to

Keris Clark, VP of Sales at P&G, spoke about the drastic shift in her work/life balance when she could no longer travel to see customers or attend meetings. Instead of taking the first flight from Boston to Seattle for a meeting and then a red-eye back home, she suddenly had time to work out, cook, and spend time with family. As travel became safer and invitations to far-away meetings came in, she thought more critically about whether or not to book the tickets. Like most of us, she still travels for some things, but it’s no longer the default option now that more people are used to video calls and other ways of working.

We can do things differently and still deliver

COVID’s effect on the supply chain is well documented, and Tiffiny Fisher, Chief of Staff and Technical Assistant for Intel’s America region, gave us a view into Intel’s situation in the earliest days of the pandemic. With fabrication, assembly, and testing sites throughout Asia, Intel had to work quickly to figure out how to continue operating while staying with government lockdown guidelines. Ultimately, hundreds of employees volunteered to leave their families and live in hotels near Intel facilities so that they could continue operating. It was a huge sacrifice by employees and probably not one that anyone would want to make again. Still, it proved that Intel, with the support of its employees, could quickly make massive changes to its operations while continuing to deliver results.

Uncertainty can be deeply uncomfortable, even frightening, even though we face it every day. Building the skills to navigate it and learning lessons about what works and doesn’t can make it easier. But if you still struggle, don’t worry. It just means you’ve successfully retained the opportunity for improvement.

Image credit: Pixabay

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

Human-Centered Change and Innovation

Innovation, change and transformation thought leadership, lovingly curated by Braden Kelley

Category Archives: Management

An Innovation Rant: Just Because You Can Doesn’t Mean You Should

Just because AI can filter resumes doesn’t mean you should remove humans from the process.

Just because you can ghost people doesn’t mean you should.

Just because you can stack bots on bots doesn’t mean you should.

Just because innovation can doesn’t mean you should allow it to.

Turn Cynics into Believers in Three Simple Steps

Why You Need to Say Yes to Dr. No

How to Say Yes to Dr. No

Can Dr. No become Dr. Yes?

3 Ways to Make Smarter Decisions – Confidently

When you decide, you lose

No decision is the worst decision

Decide how to decide

It’s your decision

From Sticky Notes to Digital Transformation

How to Properly Leverage Kanban Boards

A Short History of Kanban

What is Kanban?

Kanban, the Pull System

Elements of the Kanban Board

How to Make Your Kanban Work

Benefits of Using the Kanban Method

From Sticky Notes to a Digital System

Pros and Cons of Digital Kanban Board

Going Digital

Conclusion

The Real Reasons Employees Stay Or Leave

Hint: It’s about more than money

5 Tips for Leaders Navigating Uncertainty

From Executives at P&G, CVS, Hannaford, and Intel

Listen more

Stronger relationships lead to stronger results

Concise concrete communication is critical

Just because you can, doesn’t mean you need to

We can do things differently and still deliver