Category Archives: Management

Why Small Innovations Matter Now More Than Ever

Searching for Silver Linings

Why Small Innovations Matter Now More Than Ever

GUEST POST from Robyn Bolton

Do you feel like you’re drowning in a sea of bad news? You’re not alone. We’re standing in the eye of a storm of war, political division, and endless layoffs. In times like these, why bother with innovation when we’re using all our energy to survive and make sense of things?

I’ve asked myself this question with increasing frequency over the past months.  After hours of searching, querying, and reading to understand why you, me, or any other individual should bother with innovation, I can tell you two things:

  1. There’s no logical, data-backed reason why any individual should bother innovating (there are many logical, data-backed reasons why companies should innovate)
  2. Innovation is the only life raft that’s ever carried us from merely surviving to thriving.

If that seems like a big, overwhelming, and exhausting expectation to place on innovators, you’re right.  But it doesn’t have to be because innovation is also small things that make you smile, spark your curiosity, and prompt you to ask, “How might we…?”

Here are three small innovations that broke through the dark clouds of the news cycle, made me smile, and started a domino effect of questions and wonder.

LEGO Braille Bricks: Building a More Inclusive World

Lego Braille

You know them, and you love them (unless you’ve stepped on one), and somehow, they got even better.  In 2023, LEGO released Braille Bricks to the public.

By modifying the studs (those bumps on the top of the brick) to correspond with the braille alphabet, numbers, and symbols and complementing the toy with a website offering a range of activities, educator resources, and community support, LEGO built a bridge between sighted and visually impaired worlds, one tiny brick at a time.

How might a small change build empathy and connect people?


The Open Book: Fulfilling a Dream by Working on Vacation

The Open Book

Have you ever dreamed of going on vacation so that you could work an hourly job without pay?  Would you believe there is a two-year waitlist of people willing to pay for such an experience?

Welcome to The Open Book, a second-hand bookstore in Wigtown, Scotland, that offers “bibliophiles, avid readers, kindred book lovers, and adventure seekers” the opportunity to live out their dreams of running the bookstore by day and living above it in a tiny apartment by night.  The bookstore is owned and operated by a local nonprofit, and all proceeds, about $10,000 per year, go to supporting the Wigtown Book Festival.

How might you turn your passion into an experience others would pay for?


The Human Library: Checking Out Books That Talk Back

Human Library

If used books aren’t your thing, consider going to The Human Library.  This innovative concept started in Copenhagen in 2000 and has spread to over 80 countries, offering a unique twist on traditional libraries.  Readers “borrow” individuals from all walks of life – from refugees to rockstars refugees, from people with disabilities to those with unusual occupations – to hear their stories, ask difficult questions, and engage in open dialogue.

How might you create opportunities for dialogue and challenge your preconceptions?


Small Things Make a Big Difference

In a world that often feels dark, these small innovations are helpful reminders that if you are curious, creative, and just a bit brave, you can spark joy, wonder, and change.

How will you innovate, no matter how small, to brighten your corner of the world?

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.

False Choice – Founder versus Manager

False Choice - Founder versus Manager

GUEST POST from Robyn Bolton

Paul Graham, cofounder of Y Combinator, was so inspired by a speech by Airbnb cofounder and CEO that he wrote an essay about well-intentioned advice that, to scale a business, founders must shift modes and become managers.

It went viral. 

In the essay, he argued that:

In effect there are two different ways to run a company: founder mode and manager mode. Till now most people even in Silicon Valley have implicitly assumed that scaling a startup meant switching to manager mode. But we can infer the existence of another mode from the dismay of founders who’ve tried it, and the success of their attempts to escape from it.

With curiosity and an open mind, I read on.

I finished with a deep sigh and an eye roll. 

This is why.

Manager Mode: The realm of liars and professional fakers

On the off chance that you thought Graham’s essay would be a balanced and reflective examination of management styles in different corporate contexts, his description of Manager Mode should relieve you of that thought:

The way managers are taught to run companies seems to be like modular design in the sense that you treat subtrees of the org chart as black boxes. You tell your direct reports what to do, and it’s up to them to figure out how. But you don’t get involved in the details of what they do. That would be micromanaging them, which is bad.

Hire good people and give them room to do their jobs. Sounds great when it’s described that way, doesn’t it? Except in practice, judging from the report of founder after founder, what this often turns out to mean is: hire professional fakers and let them drive the company into the ground.

Later, he writes about how founders are gaslit into adopting Manager Mode from every angle, including by “VCs who haven’t been founders themselves don’t know how founders should run companies, and C-level execs, as a class, include some of the most skillful liars in the world.”

Founder Mode: A meritocracy of lifelong learners

For Graham, Founder Mode boils down to two things:

  1. Sweating the details
  2. Engaging with employees throughout the organization beyond just direct reports.  He cites Steve Jobs’ practice of holding “an annual retreat for what he considered the 100 most important people at Apple, and these were not the 100 people highest on the org chart.”

To his credit, Graham acknowledges that getting involved in the details is micromanaging, “which is bad,” and that delegation is required because “founders can’t keep running a 2000 person company the way they ran it when it had 20.” A week later, he acknowledged that female founders “don’t have permission to run their companies in Founder Mode the same way men can.”

Yet he persists in believing that Founder, not Manager, Mode is critical to success,

“Look at what founders have achieved already, and yet they’ve achieved this against a headwind of bad advice. Imagine what they’ll do once we can tell them how to run their companies like Steve Jobs instead of John Sculley.”

Leader Mode: Manager Mode + Founder Mode

The essay is interesting, but I have real issues with two of his key points:

  • Professional managers are disconnected from the people and businesses they manage, and as a result, their practices and behaviors are inconsistent with startup success.
  • Founders should ignore conventional wisdom and micromanage to their heart’s content.

Most “professional managers” I’ve met are deeply connected to the people they manage, committed to the businesses they operate, and act with integrity and authenticity. They are a far cry from the “professional fakers” and “skillful liars” Graham describes.

Most founders I’ve met should not be allowed near the details once they have a team in place. Their meddling, need for control, and soul-crushing FOMO (Fear of Missing Out) lead to chaos, burnout, and failure.

The truth is, it’s contextual.  The leaders I know switch between Founder and Manager mode based on the context.  They work with the passion of founders, trust with the confidence of managers, and are smart and humble enough to accept feedback when they go too far in one direction or the other.

Being both manager and founder isn’t just the essence of being a leader. It’s the essence of being a successful corporate innovator.  You are a founder,  investing in, advocating for, and sweating the details of ambiguous and risky work.  And you are a manager navigating the economic, operational, and political minefields that govern the core business and fund your paycheck and your team.

Image credit: Pexels

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

Why Modifying This One Question Changes Everything

Why Modifying This One Question Changes Everything

GUEST POST from Robyn Bolton

You know that asking questions is essential.  After all, when you’re innovating, you’re doing something new, which means you’re learning, and the best way to learn is by asking questions.  You also know that asking genuine questions, rather than rhetorical or weaponized ones, is critical to building a culture of curiosity, exploration, and smart risk-taking.  But did you know that making a small change to a single question can radically change everything for your innovation strategy, process, and portfolio?

What is your hypothesis?

Before Lean Startup, there was Discovery-Driven Planning.  This approach, first proposed by Columbia Business School professor Rita McGrath and Wharton School professor Ian MacMillan in their 1995 HBR article, outlines a “planning” approach that acknowledges and embraces assumptions (instead of pretending that they’re facts) and relentlessly tests them to uncover new data and inform and update the plan.

It’s the scientific method applied to business.

How confident are you?

However, not all assumptions or hypotheses are created equal.  This was the assertion in the 2010 HBR article “Beating the Odds When You Launch a New Venture.”  Using examples from Netflix, Johnson & Johnson, and a host of other large enterprises and scrappy startups, the authors encourage innovators to ask two questions about their assumptions:

  1. How confident am I that this assumption is true?
  2. What is the (negative) impact on the idea if the assumption is false?

By asking these two questions of every assumption, the innovator sorts assumptions into three categories:

  1. Deal Killers: Assumptions that, if left untested, threaten the idea’s entire existence
  2. Path-dependent risks: Assumptions that impact the strategic underpinnings of the idea and cost significant time and money to resolve
  3. High ROI risks: Assumptions that can be quickly and easily tested but don’t have a significant impact on the idea’s strategy or viability

However, human beings have a long and inglorious history of overconfidence.  This well-established bias in which our confidence in our judgment exceeds the objective (data-based) accuracy of those judgments resulted in disasters like Chernobyl, the sinking of the Titanic, the explosions of the Space Shuttle Challenger and Discovery, and the Titan submersible explosion.

Let’s not add your innovation to that list.

How much of your money are you willing to bet?

For years, I’ve worked with executives and their teams to adopt Discovery-Driven Planning and focus their earliest efforts on testing Deal Killer assumptions. I was always struck by how confident everyone was and rather dubious when they reported that they had no Deal Killer assumptions.

So, I changed the question.

Instead of asking how confident they were, I asked how much they would bet. Then I made it personal—high confidence meant you were willing to bet your annual income, medium confidence meant dinner for the team at a Michelin-starred restaurant, and low confidence meant a cup of coffee.

Suddenly, people weren’t quite so confident, and there were A LOT of Deal Killers to test.

Make it Personal

It’s easy to become complacent in companies.  You don’t get paid more if you come in under budget, and you don’t get fired if you overspend.  Your budget is a rounding error in the context of all the money available to the company.  And your signing authority is probably a rounding error on the rounding error that is your budget.  So why worry about ten grand here and a hundred grand there?

Because neither you, your team, nor your innovation efforts have the luxury of complacency.

Innovation is always under scrutiny.  People expect you to generate results with a fraction of the resources in record time.  If you don’t, you, your team, and your budget are the first to be cut.

The business of innovation is personal.  Treat it that way. 

How much of your time, money, and reputation are you willing to risk?  What do you need your team to risk in terms of their time, money, and professional aspirations?  How much time, money, and reputation are your stakeholders willing to risk?

The answers change everything.

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.

Who is More Creative – Women or Men?

753 Studies Have the Answer

Who is More Creative – Women or Men?

GUEST POST from Robyn Bolton

You were born creative. As an infant, you had to figure many things out—how to get fed or changed, get help or attention, and make a onesie covered in spit-up still look adorable.  As you grew older, your creativity grew, too.  You drew pictures, wrote stories, played dress-up, and acted out imaginary stories.

Then you went to school, and it was time to be serious.  Suddenly, creativity had a time and place.  It became an elective or a hobby.  Something you did just enough of to be “well-rounded” but not so much that you would be judged irresponsible or impractical.

When you entered the “real world,” your job determined whether you were creative.  Advertising, design, marketing, innovation?  Creative.  Business, medicine, law, engineering?  Not creative.

As if Job-title-a-determinant-of-creativity wasn’t silly enough, in 2022, a paper was published in the Journal of Applied Psychology that declared that, based on a meta-analysis of 259 studies (n=79,915), there is a “male advantage in creative performance.”

Somewhere, Don Draper, Pablo Picasso, and Norman Mailer high-fived.

But, as every good researcher (and innovator) knows, the headline is rarely the truth.  The truth is that it’s contextual and complicated, and everything from how the original studies collected data to how “creativity” was defined matters.

But that’s not what got reported.  It’s also not what people remember when they reference this study (and I have heard more than a few people invoke these findings in the three years since publication).

That is why I was happy to see Fortune report on a new study just published in the Journal of Applied Psychology. The study cites findings from a meta-analysis of 753 studies (n=265,762 individuals) that show men and women are equally creative. When “usefulness (of an idea) is explicitly incorporated in creativity assessment,” women’s creativity is “stronger.”

Somewhere, Mary Wells LawrenceFrida Kahlo, and Virginia Woolf high-fived.

Of course, this finding is also contextual.

What makes someone “creative?”

Both studies defined creativity as “the generation of novel and useful ideas.”

However, while the first study focused on how context drives creativity, the second study looked deeper, focusing on two essential elements of creativity: risk-taking and empathy. The authors argued that risk-taking is critical to generating novel ideas, while empathy is essential to developing useful ideas.

Does gender influence creativity?

It can.  But even when it does, it doesn’t make one gender more or less creative than the other.

Given “contextual moderators” like country-level culture, industry gender composition, and role status, men tend to follow an “agentic pathway” (creativity via risk-taking), so they are more likely to generate novel ideas.

However, given the same contextual moderators, women follow a “communal pathway” (creativity via empathy), so they are more likely to generate useful ideas.

How you can use this to maximize creativity

Innovation and creativity go hand in hand. Both focus on creating something new (novel) and valuable (useful).  So, to maximize innovation within your team or organization, maximize creativity by:

  • Explicitly incorporate novelty and usefulness in assessment criteria.  If you focus only on usefulness, you’ll end up with extremely safe and incremental improvements.  If you focus only on novelty, you’ll end up with impractical and useless ideas.
  • Recruit for risk-taking and empathy.  While the manifestation of these two skills tends to fall along gender lines, don’t be sexist and assume that’s always the case.  When seeking people to join your team or your brainstorming session, find people who have demonstrated strong risk-taking or empathy-focused behaviors and invite them in.
  • Always consider the context.  Just as “contextual moderators” impact people’s creative pathways, so too does the environment you create.  If you want people to take risks, be vulnerable, and exhibit empathy, you must establish a psychologically safe environment first.  And that starts with making sure there aren’t any “tokens” (one of a “type”) in the group.

Which brings us back to the beginning.

You ARE creative.

How will you be creative today?

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.

I Sent AI a Survey

… and the Results Were Brilliant … and Dangerous

I sent AI a survey and the results were brilliant and dangerous

GUEST POST from Robyn Bolton

AI is everywhere: in our workplaces, homes, schools, art galleries, concert halls, and even neighborhood coffee shops.  We can’t seem to escape it.  Some hope it will unlock our full potential and usher in an era of creativity, prosperity, and peace. Others worry it will eventually replace us. While both outcomes are extreme, if you’ve ever used AI to conduct research with synthetic users, the idea of being “replaced” isn’t so wild.

For the past month, I’ve beta-tested an AI research tool that allows you to create surveys, specify segments of respondents, send the survey to synthetic respondents (AI-generated personas), and get results within minutes. 

Sound too good to be true?

Here are the results from my initial test:

  • 150 respondents in 3 niche segments (50 respondents each)
  • 51 questions, including ten open-ended questions requiring short prose responses
  • 1 hour to complete and generate an AI executive summary and full data set of individual responses, enabling further analysis

The Tool is Brilliant

It took just one hour to gather data that traditional survey methods require a month or more to collect, clean, and synthesize. Think of how much time you’ve spent waiting for survey results, checking interim data, and cleaning up messy responses. I certainly did and it made me cry.

The qualitative responses were on-topic, useful, and featured enough quirks to seem somewhat human.  I’m pretty sure that has never happened in the history of surveys.  Typically, respondents skip open-ended questions or use them to air unrelated opinions.

Every respondent completed the entire survey!  There is no need to look for respondents who went too quickly, chose the same option repeatedly, or abandoned the effort altogether.  You no longer need to spend hours cleaning data, weeding out partial responses, and hoping you’re left with enough that you can generate statistically significant findings.

The Results are Dangerous

When I presented the results to my client, complete with caveats about AI’s limitations and the tool’s early-stage development, they did what any reasonable person would do – they started making decisions based on the survey results.

STOP!

As humans, we want to solve problems.  In business, we are rewarded for solving problems.  So, when we see something that looks like a solution, we jump at it.

However, strategic or financially significant decisions should never rely ona single data source. They are too complex, risky, and costly.  And they definitely shouldn’t be made based on fake people’s answers to survey questions!

They’re Also Useful.

Although the synthetic respondents’ data may not be true, it is probably directionally correct because it is based on millions and maybe billions of data points.  So, while you shouldn’t make pricing decisions based on data showing that 40% of your target consumers are willing to pay a 30%+ premium for your product, it’s reasonable to believe they may be willing to pay more for your product.

The ability to field an absurdly long survey was also valuable.  My client is not unusual in their desire to ask everything they may ever need to know for fear that they won’t have another chance to gather quantitative data (and budgets being what they are, they’re usually right).  They often ignore warnings that long surveys lead to abandonment and declining response quality. With AI, we could ask all the questions and then identify the most critical ones for follow-up surveys sent to actual humans.

We Aren’t Being Replaced, We’re Being Spared

AI consumer research won’t replace humans. But it will spare us the drudgery of long surveys filled with useless questions, months of waiting for results, and weeks of data cleaning and analysis. It may just free us up to be creative and spend time with other humans.  And that is brilliant.

Image credit: Microsoft Copilot

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

The Hidden Cost of Waiting

The Hidden Cost of Waiting

GUEST POST from Mike Shipulski

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

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

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

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

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

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

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

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

Image credit: Pexels

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






ISO Innovation Standards

The Good, the Bad, and the Missing

ISO Innovation Standards

GUEST POST from Robyn Bolton

In 2020, the International Standards Organization, most famous for its Quality Management Systems standard, published ISO 56000Innovation Management—Fundamentals and Vocabulary. Since then, ISO has released eight additional innovation standards. 

But is it possible to create international standards for innovation, or are we killing creativity?

That’s the question that InnoLead founder and CEO Scott Kirsner and I debated over lunch a few weeks ago.  Although we had heard of the standards and attended a few webinars, but we had never read them or spoken with corporate innovators about their experiences.

So, we set out to fix that.

Scott convened an all-star panel of innovators from Entergy, Black & Veatch, DFW Airport, Cisco, and a large financial institution to read and discuss two ISO Innovation Standards: ISO 56002, Innovation management – Innovation management systems – Requirements and ISO 56004, Innovation Management Assessment – Guidance.

The conversation was honest, featured a wide range of opinions, and is absolutely worth your time to watch

Here are my three biggest takeaways.

The Standards are a Good Idea

Innovation doesn’t have the best reputation.  It’s frequently treated as a hobby to be pursued when times are good and sometimes as a management boondoggle to justify pursuing pet ideas and taking field trips to fun places.

However, ISO Standards can change how innovation is perceived and supported.

Just as ISO’s Quality Management Standards established a framework for quality, the Innovation Management Standards aim to do the same for innovation. They provide shared fundamentals and a common vocabulary (ISO 56000), requirements for innovation management systems (ISO 56001 and ISO 56002), and guidance for measurement (ISO 56004), intellectual property management (ISO 56005), and partnerships (ISO 56003). By establishing these standards, organizations can transition innovation from a vague “trust me” proposition to a structured, best-practice approach.

The Documents are Dangerous

However, there’s a caveat: a little knowledge can be dangerous. The two standards I reviewed were dense and complex, totaling 56 pages, and they’re among the shortest in the series. Packed with terminology and suggestions, they can overwhelm experienced practitioners and mislead novices into thinking they have How To Guide for success.

Innovation is contextual.  Its strategies, priorities, and metrics must align with the broader organizational goals.  Using the standards as a mere checklist is more likely to lead to wasted time and effort building the “perfect” innovation management system while management grows increasingly frustrated by your lack of results.

The Most Important Stuff is Missing

Innovation is contextual, but there are still non-negotiables:   

  • Leadership commitment AND active involvement: Innovation isn’t an idea problem. It’s a leadership problem.  If leadership delegates innovation, fails to engage in the work, and won’t allocate required resources, you’re efforts are doomed to fail.
  • Adjacent and Radical Innovations require dedicated teams: Operations and innovation are fundamentally different. The former occurs in a context of known knowns and unknowns, where experience and expertise rule the day. The latter is a world of unknown unknowns, where curiosity, creativity, and experimentation are required. It is not reasonable to ask someone to live in both worlds simultaneously.
  • Innovation must not be a silo: Innovation cannot exist in a silo. Links must be maintained with the core business, as its performance directly impacts available resources and influences the direction of innovation initiatives.

These essential elements are mentioned in the standards but are not clearly identified. Their omission increases the risk of further innovation failures.

Something is better than nothing

The standards aren’t perfect.  But one of the core principles of innovation is to never let perfection get in the way of progress. 

Now it’s time to practice what we preach by testing the standards in the real world, scrapping what doesn’t work, embracing what does, and innovating and iterating our way to better.

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.

Building Competence Often More Important Than a Vision

Building Competence Often More Important Than a Vision

GUEST POST from Greg Satell

In 1993, when asked about his vision for the failing company he was chosen to lead, Lou Gerstner famously said, “The last thing IBM needs right now is a vision.” What he meant was that if IBM couldn’t figure out how to improve operations to the point where it could start making money again, no vision would matter.

Plenty of people have visions. Elizabeth Holmes had one for Theranos, but its product was a fraud and the company failed. Many still believe in Uber’s vision of “gig economy” taxis, but even after more than 10 years and $25 billion invested, it still loses billions. WeWork’s proven business model became a failure when warped by a vision.

The truth is that anyone can have a vision. Look at any successful organization, distill its approach down to a vision statement and you will easily be able to find an equal or greater success that does things very differently. There is no silver bullet. Successful leaders are not the ones with the most compelling vision, but those who build the skills to make it a reality.

Gandhi’s “Himalyan Miscalculation”

When Mahatma Gandhi returned to India in 1915, after more than two decades spent fighting for Indian rights in South Africa, he had a vision for the future of his country. His view, which he laid out in his book Hind Swaraj, was that the British were only able to rule because of Indian cooperation. If that cooperation were withheld, the British Raj would fall.

In 1919, when the British passed the repressive Rowlatt Acts, which gave the police the power to arrest anyone for any reason whatsoever, he saw an opportunity to make his vision a reality. He called for a nationwide campaign of civil disobedience, called a hartal, in which Indians would refuse to work or do business.

At first, it was a huge success and the country came to a standstill. But soon things spun wildly out of control and eventually led to the massacre at Amritsar, in which British soldiers left hundreds dead and more than a thousand wounded. He would later call the series of events his Himalayan Miscalculation and vowed never to repeat his mistake.

What Gandhi realized was that his vision was worthless without people trained in his Satyagraha philosophy and capable of implementing his methods. He began focusing his efforts on indoctrinating his followers and, a decade later, set out on the Salt March with only about 70 of his most disciplined disciples.

This time, he triumphed in what is remembered as his greatest victory. In the end, it wasn’t Gandhi’s vision, but what he learned along the way that made him a historic icon.

The Real Magic Behind Amazon’s 6-Page Memo

We tend to fetishize the habits of successful people. We probe for anomalies and, when we find something out of the ordinary, we praise it as not only for its originality, but consider it to be the source of success. There is no better example of this delusion than Jeff Bezos’s insistence on using six-page memos rather than PowerPoint in meetings at Amazon.

There are two parts to this myth. First is the aversion to PowerPoint, which most corporate professionals use, but few use well. Second, the novelty of a memo, structured in a particular way, as the basis for structuring a meeting. Put them together and you have a unique ritual which, given Amazon’s incredible success, has taken on legendary status.

But delve a little deeper and you find it’s not the memos themselves, but Amazon’s writing culture that makes the difference. When you look at the company, which thrives in such a variety of industries, there are a dizzying array of skills that need to be integrated to make it work smoothly. That doesn’t just happen by itself.

What Jeff Bezos has done is put an emphasis on communication skills, in general and writing in particular. Amazon executives, from the time they are hired, learn that the best way to get ahead in the company is to learn how to write with clarity and power. They hone that skill over the course of their careers and, if they are to succeed, must learn to excel at it.

Anyone can ban PowerPoint and mandate memos. Building top-notch communication skills across a massive enterprise, on the other hand, is not so easy.

The Real Genius Of Elon Musk

In 2007, an ambitious entrepreneur launched a new company with a compelling vision. Determined to drive the shift from fossil fuels to renewables, he would create an enterprise to bring electric cars to the masses. A master salesman, he was able to raise hundreds of millions of dollars as well as the endorsement of celebrities and famous politicians.

Yet the entrepreneur wasn’t Elon Musk and the company wasn’t Tesla. The young man’s name was Shai Agassi and his company, Better Place, failed miserably within a few years. Despite all of the glitz and glamour he was able to generate, the basic fact was that Agassi knew nothing about building cars or the economics of lithium-ion batteries.

Musk, on the other hand, did the opposite. He did not attempt to build a car for the masses, but rather for Silicon Valley millionaires who wouldn’t need to rely on a Tesla to bring the kids to soccer practice, but could use it to zoom around and show off to their friends. That gave Musk the opportunity to learn how to manufacture cars efficiently and effectively. In other words, to build competency.

When we have a big vision, we tend to want to search out the largest addressable market. Unfortunately, that is where you’ll find stiff competition and customers who are already fairly well-served. That’s why it’s almost always better to identify a hair-on-fire use case—something that a small subset of customers want or need so badly they almost literally have their hair on fire—and scale up from there.

As Steve Blank likes to put it, “no business plan survives first contact with a customer.” Every vision is wrong. Some are off by a little and some are off by a lot. But they’re all wrong in some way. The key to executing on a vision is by identifying vulnerabilities early on and then building the competencies to overcome them.

Why So Many Visions Become Delusions

When you look at the truly colossal business failures of the last 20 years, going back to Enron and LTCM at the beginning of the century to the “unicorns” of today, a common theme is the inability to make basic distinctions between visions and delusions. Delusions, like myths, always contain some kernel of truth, but dissipate when confronted with real world problems.

Also underlying these delusions is a mistrust of experts and the establishment. After all, if a fledgling venture has the right idea then, almost by definition, the establishment must have the wrong idea. As Sam Arbesman pointed out in The Half Life of Facts, what we know to be true changes all the time.

Yet that’s why we need experts. Not to give us answers, but to help us ask better questions. That’s how we can find flaws in our ideas and learn to ask better questions ourselves. Unfortunately recent evidence suggests that “founder culture” in Silicon Valley has gotten so out of hand that investors no longer ask hard questions for fear of getting cut out of deals. \

The time has come for us to retrench, much like Gerstner did a generation ago, and recommit ourselves to competence. Of course, every enterprise needs a vision, but a vision is meaningless without the ability to achieve it. That takes more than a lot of fancy talk, it requires the guts to see the world as it really is and still have the courage to try to change it.

— Article courtesy of the Digital Tonto blog and previously appeared on Inc.com
— Image credits: Pexels

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






Projects Don’t Go All Right or All Wrong

Projects Don't Go All Right or All Wrong

GUEST POST from Howard Tiersky

What The Heck Went Right?!

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

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

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

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

What went right is more useful than what went wrong.

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

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

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

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

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

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

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

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

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

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

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

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

This article originally appeared on the Howard Tiersky blog

Image Credits: Unsplash

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






Why Neglecting New Hire Ideas Hurts Revenue

The Cost of Silence

Why Neglecting New Hire Ideas Hurts Revenue

GUEST POST from Robyn Bolton

Stop me if this sounds familiar. A new hire bounces into your office and, with all the joy and enthusiasm of a new puppy, rattles off a list of ideas. You smile and, just like with new puppies, explain why their ideas won’t work, and encourage them to be patient and get to know the organization. 

Congratulations!  You just cost your company money. Not because the new hire’s idea was the silver bullet you’ve been seeking but because you taught them that it’s more critical for them to do their jobs and maintain the status quo than to ask questions and share ideas.

If that seems harsh, read the new research from Harvard Business School professor Amy Edmondson.

Year 1: Rainbows and Unicorns (mostly)

From 2017 through 2021, Dr. Edmonson and her colleagues collected data from over 10,000 physicians.  Using biannual (every two years) surveys, they asked physicians to rate on a 5-point scale how comfortable they felt offering opinions or calling out the mistakes of colleagues or superiors. 

It was little surprise that agreement with statements like “I can report patient safety mistakes without fear of punishment” were highest amongst people with less than one year of service at their employer.

These results all come down to one thing: high levels of psychological safety.

Years 2+: Resignation and Unhappiness

However, psychological safety erodes quickly in the first year because:

  • There’s a gap between words and actions: When new hires join an organization, they believe what they hear about its culture, values, priorities, and openness.  Once they’re in the organization and observe their colleagues’ and superiors’ daily behavior, they experience the disconnect, lose trust, and shift into self-protection mode.
  • Their feedback and ideas are rebuffed: This scenario is described above, but it’s not the only one.  Another common situation occurs when a new hire responds to requests for feedback only to be met with silence or exasperation, a lack of follow-through or follow-up, or is openly mocked or met with harsh pushback
  • Expectations increase with experience: It’s easier to ask questions when you’re new, and no one expects you to know the answers.  Over time, however, you are expected to learn the answers and you no longer feel comfortable asking questions, even if there’s no way you could know the answer.

20 years to regain what was lost in 1

According to Edmondson’s research, it takes up to 20 years to rebuild the safety lost in the first year.

As a leader, you can slow that erosion and accelerate the rebuilding when you:

  • Recognize the Risk: Knowing that new hires will experience a drop in psychological safety, staff them on teams that have higher levels of safety
  • Walk the Talk: Double down on demonstrating the behaviors you want. Immediately act on feedback that points out a gap between your words and actions.
  • Ask questions: Demonstrate your openness by being curious, asking questions, and asking follow-up questions.  As Edmonson writes, “You are training people to contribute by constantly asking questions.”
  • Promises Made = Promises Kept: If you ask for feedback, act on it.  If you ask for ideas, act on some and explain why you’re not executing others.
  • Be Vulnerable: Admit your mistakes and uncertainties.  It sets a powerful example that it’s okay to be imperfect and to ask for help. It also creates an environment for others to do the same.

The Cost of Silence vs. The Cost of Time

Building and maintaining psychological safety takes time and effort.  It takes 5 minutes to listen to and respond to an idea.  It takes hours to ensure new hires join safe teams.  It takes weeks to plan and secure support for post-hackathon ideas. 

But how does that compare to 20 years of lost ideas, improvements, innovations, and revenue?  To 20 years of lost collaboration, productivity, and peak effectiveness? To 20 years of slow progress, inefficiency, and cost?

How many of your employees stick around 20 years to give you the chance to rebuild what was lost?

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.