Category Archives: Design

Why You Don’t Need An Innovation Portfolio

According to Harvard Business Review

Why You Don't Need An Innovation Portfolio

GUEST POST from Robyn Bolton

You are a savvy manager, so you know that you need an innovation portfolio because (1) a single innovation isn’t enough to generate the magnitude of growth your company needs, and (2) it is the best way to manage inherently risky endeavors and achieve desired returns.

Too bad you’re wrong.

According to an article in the latest issue of HBR, you shouldn’t have an innovation portfolio. You should have an innovation basket.

Once you finish rolling your eyes (goodness knows I did), hear me (and the article’s authors) out because there is a nuanced but important distinction.

Our journey begins with the obvious.

In their article “A New Approach to Strategic Innovation,” authors Haijian Si, Christoph Loch, and Stelios Kavadias argue that portfolio management approaches have become so standardized as to be practically useless, and they propose a new framework for ensuring your innovation activities achieve your strategic goals.

“Companies typically treat their innovation projects as a portfolio: a mix of projects that, collectively, aim to meet their various strategic objectives,” the article begins. “MOO,” I think (household shorthand for Master Of the Obvious).

“When we surveyed 75 companies in China, we discovered that when executives took the trouble to link their project selection to their business’s competitive goals, the contribution of their innovation activities performance increased dramatically,” the authors continue. “Wow, fill this under N for No Sh*t, Sherlock,” responded my internal monologue.

The authors go on to present and explain their new framework, which is interesting in its focus on asking and answering seemingly simple questions (what, who, why, and how) and identifying internal weaknesses and vulnerabilities through a series of iterative and inclusion conversations. The process is a good one but feels more like an augmentation of an existing approach rather than a radically new one.

Then we hit the “portfolio” vs. “basket” moment.

According to the authors, once the management team completes the first step by reaching a consensus on the changes needed to their strategy, they move on to the second step – creating the innovation basket.

The process of categorizing innovation projects is the next step, and it is where our process deviates from established frameworks. We use the word “basket” rather than “portfolio” to denote a company’s collection of innovation projects. In this way, we differentiate the concept from finance and avoid the mistake of treating projects like financial securities, where the goal is usually to maximize returns through diversification. It’s important to remember that innovation projects are creative acts, whereas investment in financial securities is simply the purchase of assets that have already been created.

“Avoid the mistake of treating projects like financial securities” and “remember that innovation projects are creative acts.” Whoa.

Why this is important in a practical sense (and isn’t just academic fun-with-words)

Think about all the advice you’ve read and heard (and that I’ve probably given you) about innovation portfolios – you need a mix of incremental, adjacent, and radical innovations, and, if you’re creating a portfolio from scratch, use the Golden Ratio.

Yes, and this assumes that everything in your innovation portfolio supports your overall strategy, and that the portfolio is reviewed regularly to ensure that the right projects receive the right investments at the right times.

These assumptions are rarely true.

Projects tend to enter the portfolio because a senior executive suggested them or emerged from an innovation event or customer research and feedback. Once in the portfolio, they progress through the funnel until they either launch or are killed because of poor test results or a slashed innovation budget.

They rarely enter the portfolio because they are required to deliver a higher-level strategy, and they rarely exit because they are no longer strategically relevant. Why? Because the innovation projects in your portfolio are “assets that have already been created.”

What this means for you (and why it’s scary)

Swapping “basket” in for “portfolio” isn’t just the choice of a new word to bolster the claim of creating a new approach. It’s a complete reframing of your role as an innovation executive.

You no longer monitor assets that reflect purchases or investments promising yet-to-be-determined payouts. You are actively starting, shifting, and shutting down opportunities based on business strategy and needs. Shifting from a “portfolio” to a basket” turns your role as an executive from someone who monitors performance to someone who actively manages opportunities.

And this should scare you.

Because this makes the challenge of balancing operations and innovation an unavoidable and regular endeavor. Gone are the days of “set it and forget it” innovation management, which often buys innovation teams time to produce results before their resources are noticed and reallocated to core operations.

If you aren’t careful about building and vigorously defending your innovation basket, it will be easy to pluck resources from it and allocate them to the more urgent and “safer” current business needs that also contribute to the strategic changes identified.

Leaving you with an innovation portfolio.

Image Credit: Pixabay

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

Great Coaches Do These Things

Great Coaches Do These Things

GUEST POST from Mike Shipulski

Good coaches listen to you. They don’t judge, they just listen.

Good coaches continually study the game. They do it in private, but they study.

Good coaches tell you that you can do better, and that, too, they do in private.

Good coaches pick you up off the floor. They know that getting knocked over is part of the game.

Good coaches never scream at you, but they will cry with you.

Good coaches never stop being your coach. Never.

Good coaches learn from you, and the best ones tell you when that happens.

Good coaches don’t compromise. Ever.

Good coaches have played the game and have made mistakes. That’s why they’re good coaches.

Good coaches do what’s in your best interest, not theirs.

Good coaches are sometimes wrong, and the best ones tell you when that happens.

Good coaches don’t care what other people think of them, but they care deeply about you.

Good coaches are prepared to be misunderstood, though it’s not their preference.

Good coaches let you bump your head or smash your knee, but, otherwise, they keep you safe.

Good coaches earn your trust.

Good coaches always believe you and perfectly comfortable disagreeing with you at the same time.

Good coaches know it’s always your choice, and they know that’s how deep learning happens.

Good coaches stick with you, unless you don’t do your part.

Good coaches don’t want credit. They want you to grow.

Good coaches don’t have a script. They create a custom training plan based on your needs.

Good coaches simplify things when it’s time, unless it’s time to make things complicated.

Good coaches aren’t always positive, but they are always truthful.

Good coaches are generous with their time.

Good coaches make a difference.

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.






Why You Should Care About Service Design

Why You Should Care About Service Design

GUEST POST from Robyn Bolton

What if a tool had the power to delight your customers, cut your costs, increase your bottom line, and maybe double your stock price? You’d use it, right?

That’s precisely the power and impact of Service Design and service blueprints. Yet very few people, especially in the US, know, understand, or use them. Including me.

Thankfully, Leala Abbott, a strategist and researcher at the intersection of experience, innovation, and digital transformation and a lecturer at Parsons School of Design, clued me in.

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

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

Where People Go Wrong with Minimum Viable Products

Where People Go Wrong with Minimum Viable Products

GUEST POST from Greg Satell

Ever since Eric Reis published his bestselling book, The Lean Startup, the idea of a minimum viable product (MVP) has captured the imagination of entrepreneurs and product developers everywhere. The idea of testing products faster and cheaper has an intuitive logic that simply can’t be denied.

Yet what is often missed is that a minimum viable product isn’t merely a stripped down version of a prototype. It is a method to test assumptions and that’s something very different. A single product often has multiple MVPs, because any product development effort is based on multiple assumptions.

Developing an MVP isn’t just about moving faster and cheaper, but also minimizing risk. In order to test assumptions, you first need to identify them and that’s a soul searching process. You have to take a hard look at what you believe, why you believe it and how those ideas can be evaluated. Essentially, MVP’s work because they force you to do the hard thinking early.

Every Idea Has Assumptions Built In

In 1990, Nick Swinmurn had an idea for a business. He intended to create a website to sell shoes much like Amazon did for books. This was at the height of the dotcom mania, when sites were popping up to sell everything from fashion to pet food to groceries, so the idea itself wasn’t all that original or unusual.

What Swinmurn did next, however, was. Rather than just assuming that people would be willing to buy shoes online or conducting expensive marketing research, he built a very basic site, went to a shoe store and took pictures of shoes, which he placed on the site. When he got an order, he bought the shoes retail and shipped them out. He lost money on every sale.

That’s a terrible way to run a business, but a great — and incredibly cheap — way to to test a business idea. Once he knew that people were willing to buy shoes online, he began to build all the elements of a fully functioning business. Ten years later, the company he created, Zappos was acquired by Amazon for $1.2 billion.

Notice how he didn’t just assume that his business idea was viable. He tested it and validated it. He also learned other things, such as what styles were most popular. Later, Zappos expanded to include handbags, eyewear, clothing, watches, and kids’ merchandise.

The Cautionary Tale Of Google Glass

Now compare how Swinmurn launched his business with Google’s Glass debacle. Instead of starting with an MVP, it announced a full-fledged prototype complete with a snazzy video. Through augmented reality projected onto the lenses, users could seamlessly navigate an urban landscape, send and receive messages and take photos and videos. It generated a lot of excitement and seemed like a revolutionary new way to interact with technology.

Yet criticism quickly erupted. Many were horrified that hordes of wandering techno-hipsters could be surreptitiously recording us. Others had safety concerns about everything from people being distracted while driving to the devices being vulnerable to hacking. Soon there was a brewing revolt against “Google Glassholes.”

Situations like the Google Glass launch are startlingly common. In fact, the vast majority of new product launches fail because there’s no real way to know whether you have the right product-market fit customers actually get a chance to interact with the product. Unfortunately, most product development efforts start by seeking out the largest addressable market. That’s almost always a mistake.

If you are truly creating something new and different, you want to build for the few and not the many. That’s the mistake that Google made with its Glass prototype.

Identifying A Hair On Fire Use Case

The alternative to trying to address the largest addressable market is to identify a hair-on-fire use case. The idea is to find a potential customer that needs to solve a problem so badly that they almost literally have their hair on fire. These customers will be more willing to co-create with you and more likely to put up with the inevitable bugs and glitches that always come up.

For example, Tesla didn’t start out by trying to build an electric car for the masses. Instead, it created a $100,000 status symbol for Silicon Valley millionaires. Because these customers could afford multiple cars, range wasn’t as much of a concern. The high price tag also made a larger battery more feasible. The original Tesla Roadster had a range of 244 miles.

The Silicon Valley set were customers with their hair on fire. They wanted to be seen as stylish and eco-friendly, so were willing to put up with the inevitable limitations of electric cars. They didn’t have to depend on them for their commute or to pick the kids up at soccer practice. As long as the car was cool enough, they would buy it.

Interestingly, Google Glass made a comeback as an industrial product and had a nice run from 2019 to 2023 before they went away for good. For hipsters, an augmented reality product is far from a necessity, but a business that needs to improve productivity can be a true “hair-on-fire” use case. As the product improves and gains traction, it’s entirely possible that it eventually makes its way back to the consumer market in some form.

Using An MVP To Pursue A Grand Challenge

One of the criticisms of minimum viable products is that they are only suited for simple products and tweaks, rather than truly ambitious projects. Nothing could be further from the truth. The reality is that the higher your ambitions, the more important it is for you to start with a minimum viable product.

IBM is one company that has a long history of pursuing grand challenges such as the Deep Blue project which defeated world champion Garry Kasparov at chess and the Blue Gene project which created a new class of “massively parallel” supercomputers. More recently were the Jeopardy grand challenge, which led to the development of its current Watson business and the Debater project.

Notice that none of these were fully featured products. Rather they were attempts to, as IBM’s Chief Innovation Officer, Bernie Meyerson, put it to me, invent something that “even experts in the field, regard as an epiphany and changes assumptions about what’s possible.” That would be hard to do if you were trying to create a full featured product for a demanding customer.

That’s the advantage of creating an MVP. It essentially acts as a research lab where you can safely test hypotheses and eliminate sources of uncertainty. Once you’ve done that, you can get started trying to build a real business.

— Article courtesy of the Digital Tonto blog
— 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.






How Not to Get in Your Own Way

How Not to Get in Your Own Way

GUEST POST from Mike Shipulski

If you could get another good job at the drop of a hat, how would you work differently? Would you speak your mind or bite your tongue?

If you didn’t care about getting a promotion, would you succumb to groupthink or dissent?

If your ego didn’t get in the way, would you stop following the worn-out recipe and make a new one?

If you don’t judge yourself by the number of people who work for you, would your work be better? Would you choose to work on different projects? How do you feel about that?

If you knew your time at the company was finite, how would your contribution change? Who would you stop working with? Who would you start working with? Wouldn’t that feel good?

If you didn’t care about your yearly rating, wouldn’t your rating improve?

If you cared more about helping others, wouldn’t your talents (and the returns) be multiplied?

If your time horizon was doubled, wouldn’t work on projects that are important at the expense of those that are urgent?

If your ego didn’t block you from working on projects that might fail, wouldn’t you work on projects that could obsolete your best work?

If you cared about the long-term success of the company, wouldn’t you work more with young people to get them ready for the next decade?

If you cared solely about doing the right projects in the right way, wouldn’t you help your best team members move to the most important projects, even if that meant they worked for someone else?

If you cared about helping people develop, would you formalize their development areas and help them grow, or take the easy route and let them flounder?

If you didn’t care about getting the credit, how would you and your work be different? Would the company be better for it? How about your happiness?

If you declined every other meeting and just read the meeting minutes, would that be a problem? And even if there are no meeting minutes to read, don’t you think that you’d get along just fine? And don’t you think you’d get more done?

What would you have to change to work more often with young people?

What would you have to change so your best people could be moved to the most important projects?

What would you have to change so you’d dissent when that’s what’s needed?

What would you have to change to develop others, even if it cost you a promotion?

What would you have to change so you could ditch the urgent projects and start the meaningful ones?

What would you have to change so you could spend more time developing young talent?

What would you have to change so you could attend fewer meetings and make more progress?

What would you have to change so you could work on the most outlandish projects?

What’s in the way of looking inside and figuring out how to live differently?

If you were able to change, who would you start work with? Who would you stop working with? Which projects would you start and which would you stop? Which meetings would you skip? Who are the three young people you’d help grow?

If you were able to change, would you be better for it? And how about the people that work with you? And how about your family? And wouldn’t your company be better for it?

So I ask you – What’s in the way? And what are you going to do about it?

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.






Three Maps to Innovation Success

3 Maps to Innovation Success

GUEST POST from Robyn Bolton

Several years ago, my now-husband and I were in London. It was his first time in the city but my 4th or 5th so, naturally, I talked a big game about how well I knew the city and how I would be, with the help of our handy tourist map, our tour guide.

Things were going fine until I took the wrong road leading away from Buckingham Palace. I thought we were heading straight to Parliament. We were not. 

After a walk that lasted far longer than it should have, he nervously asked,” We’re lost, aren’t we?”

With wounded pride and astounding stubbornness, I declared, “We’re not lost. I know exactly where we are. It’s just not where we want to be.”

Maps are incredibly useful. Until they’re not.

Innovation literature has more maps than a Rick Steves’ guidebook, and most are quite useful. If they’re used at the right time for the right purposes in the right way by the right people (which is a lot of rights that have to be right).

Here are three of my favorites – 2 classics and a new one that blew my mind

Stakeholder Map:

Stakeholder Map

Avoid getting blind-sided, buttering up the wrong people, or ignoring potential champions

  • What it is: A visual representation of the people, roles, and groups who (1) are involved in and affected by a challenge or system and (2) have the power to affect or are likely to be affected by the proposed solution. Stakeholders can be internal and/or external to the organization
  • Why you need one: To prioritize where and how you spend your time understanding, influencing, communicating, collaborating, persuading, and selling
  • When to create it: At the very beginning of a project and then updating as you learn more
  • How to use it: Interaction Design Foundation explains it simply and concretely:
    • Brainstorm who your internal AND external stakeholders are
    • Prioritize them using an Influence x Interest two-by-two matrix
    • Engage and communicate based on their place in the chart

Journey Map

Customer Journey Map

Spot opportunities to create radical value through incremental innovations

  • What it is: A visual representation of what your customer/consumer/user does, thinks, and feels as they move from awareness of a need/want/JTBD to loyalty to a solution. Journey maps should dig deep into moments where customers currently interact with your organization and highlight opportunities where interaction can and should occur
  • Why you need one: To identify opportunities for innovation by surfacing customer current pain points between your customer and your business (or competitors if your business isn’t there and can/should be)
  • When to create it:
    • Create the basic structure (start and end point) or a hypothesized journey before primary research.
    • During research, work with individual stakeholders to develop their maps using (and adapting) your initial structure.
    • At the end of research and before ideation, synthesize insights into the smallest possible number of maps to use as inspiration for solution brainstorming
  • How to use it: IDEO offers simple instructions and tips based on practical use:
    • Brainstorm who your internal AND external stakeholders are
    • Prioritize them using an Influence x Interest two-by-two matrix
    • Engage and communicate based on their place in the chart

Service Map:

Service Design Blueprint

Make journey maps actionable (and see how your innovation affects your operations)

  • What it is: A visual representation of the people, touchpoints, processes, and technology required/desired both frontstage (what customers see) and backstage (what happens behind the scenes). Similar to process documentation with a special focus on the customer
  • Why you need one: Doing something new (i.e., innovating) often requires changes to internal operations, organizations, and processes, but these changes are often ignored or unexplored until late in the process, potentially slowing or stopping the development and launch of a new solution.
  • When to create it: Draft a baseline current state once you have 50% confidence in the general area or type of solution to be created (e.g., we want to improve the use of digital tools in classrooms, so let’s create a service map for our current digital offerings and operations). Then continually revise and update it as the solution/service develops.
  • How to use it: Interaction Design Foundation offers practical instructions and advice.
    • Identify the service to be blueprinted
    • Identify the customers to be service
    • Examine the customers’ experience of the process (customer journey map)
    • Identify the role and impact of employees, processes, technology, and other operational and organizational factors on the service
    • Link activities together to show a natural flow between frontstage and backstage

What’s your favorite map (innovation or otherwise)?

Image credits: Pixabay, Interaction Design Foundation

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.

Let Yourself Draw Inspiration from Others

Let Yourself Draw Inspiration from Others

GUEST POST from Mike Shipulski

When you try something new, check to see who has done something similar. Decompose their design approach. What were they trying to achieve? What outcome were they looking for? Who were their target customers? Do this for at least three existing designs – three real examples that are for sale today.

Here’s a rule to live by: When trying something new, don’t start from scratch.

What you are trying to achieve is unique, but has some commonality with existing solutions. The outcome you are looking for is unique, but it’s similar to outcomes others have tried to achieve. Your target customers are unique, but some of their characteristics are similar to the customers of the solutions you’ll decompose.

Here’s another rule: There are no “clean sheet” sheet designs, so don’t try to make one.

There was an old game show called Name That Tune, where contestants would try to guess the name of a song by hearing just a few notes. The player wins when they can name the tune with the *fewest* notes. And it’s the same with new designs – you want to provide a novel customer experience using the fewest new notes.

A rule: Reuse what you can, until you can’t.

Because the customer is the one who decides if your new offering offers them new value, the novel elements of your design don’t have to look drastically different in a side-by-side comparison way. But the novel elements of your offering do have to make a significant difference in the customer’s life. With that said, however, it can be helpful if the design element responsible for the novel goodness is visually different from the existing alternatives. But if that’s not the case, you can add a non-functional element to the novelty-generating element to make it visible to the customer. For example, you could add color, or some type of fingerprint, to the novel element of the design so that customers can see what creates the novelty for them. Then, of course, you market the heck out of the new color or fingerprint.

A rule: It’s better to make a difference in a customer’s life than, well, anything else.

Don’t be shy about learning from what other companies have done well. That’s not to say you should violate their patents, but it’s a compliment when you adopt some of their best stuff. Learn from them and twist it. Understand what they did and abstract it. See the best in two designs and combine them. See the goodness in one domain and bring it to another.

Doing something for the first time is difficult, why not get inspiration from others and make it easier?

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.






Productive Disagreement Requires Trust

Productive Disagreement Requires Trust

GUEST POST from Mike Shipulski

When there’s disagreement between words and behavior, believe the behavior. This is especially true when the words deny the behavior.

When there’s disagreement between the data and the decision, the data is innocent.

When there’s agreement that there’s insufficient data but a decision must be made, there should be no disagreement that the decision is judgment-based.

When there’s disagreement on the fact that there’s no data to support the decision, that’s a problem.

When there’s disagreement on the path forward, it’s helpful to have agreement on the process to decide.

When there’s disagreement among professionals, there is no place for argument.

When there’s disagreement, there is respect for the individual and a healthy disrespect for the ideas.

When there’s disagreement, the decisions are better.

When there’s disagreement, there’s independent thinking.

When there’s disagreement, there is learning.

When there’s disagreement, there is vulnerability.

When there’s disagreement, there is courage.

When there’s disagreement, there is trust.

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.






Do you ever admit you don’t know?

Do you ever admit you don't know?

GUEST POST from Mike Shipulski

When you are asked a question and you don’t know the answer, what do you say? What does that say about you?

What happens to people in your organization who say “I don’t know.”? Are they lauded or laughed at? Are they promoted, overlooked, or demoted? How many people do you know that have said: “I don’t know.”? And what does that say about your company?

When you know someone doesn’t know, what do you do? Do you ask them a pointed question in public to make everyone aware that the person doesn’t know? Do you ask oblique questions to raise doubt about the person’s knowing? Do you ask them a question in private to help them know they don’t know? Do you engage in an informal discussion where you plant the seeds of knowing? And how do you feel about your actions?

When you say “I don’t know.” you make it safe for others to say it. So, do you say it? And how do you feel about that?

When you don’t know and you say otherwise, decision quality suffers and so does the company. Yet, some companies make it difficult for people to say “I don’t know.” Why is that? Do you know?

I think it’s unreasonable to expect people to know the answer to know the answers to all questions at all times. And when you say “I don’t know.” it doesn’t mean you’ll never know; it means you don’t know at this moment. And, yet, it’s difficult to say it. Why is that? Do you know?

Just because someone asks a question doesn’t mean the answer must be known right now. It’s often premature to know the answer, and progress is not hindered by the not knowing. Why not make progress and figure out the answer when it’s time for the answer to be known? And sometimes the answer is unknowable at the moment. And that says nothing about the person that doesn’t know the answer and everything about the moment.

It’s okay if you don’t know the answer. What’s not okay is saying you know when you don’t. And it’s not okay if your company makes it difficult for you to say you don’t know. Not only does that create a demoralized workforce, but it’s also bad for business.

Why do companies make it so difficult to say “I don’t know.”? You guessed it – I don’t know.

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 Real Problem with Problems

The Real Problem with Problems

GUEST POST from Mike Shipulski

If you don’t know what the problem is, that’s your first problem.

A problem can’t be a problem unless there’s a solution. If there’s no possible solution, don’t try to solve it, because it’s not a problem.

If there’s no problem, you have a big problem.

If you’re trying to solve a problem, but the solution is outside your sphere of influence, you’re taking on someone else’s problem.

If someone tries to give you a gift but you don’t accept it, it’s still theirs. It’s like that with problems.

If you want someone to do the right thing, create a problem for them that, when solved, the right thing gets done.

Problems are good motivators and bad caretakers.

A problem is between two things, e.g., a hammer and your thumb. Your job is to figure out the right two things.

When someone tries to give you their problem, keep your hands in your pockets.

A problem can be solved before it happens, while it happens, or after it happened. Each time domain has different solutions, different costs, and different consequences. Your job is to choose the most appropriate time domain.

If you have three problems, solve one at a time until you’re done.

Solving someone else’s problem is a worst practice.

If you solve the wrong problem, you consume all the resources needed to solve the right problem without any of the benefits of solving it.

Ready, fire, aim is no way to solve problems.

When it comes to problems, defining IS solving.

If you learn one element of problem-solving, learn to see when someone is trying to give you their problem.

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.