Read This Because…

Read This Because…

How many times a day do you ask someone to do something? If you total all the requests you make of coworkers, family members, friends, people at restaurants and shops, and even strangers, the total is somewhere between 100 and 1 bazillion.  Now, what if I told you that by including just one word in your request, the odds of receiving a positive response increase by 50%?

And no, that word is not “please.”

The real magic word

Harvard 1978.  Decades before everyone had access to computer labs, home computers, and personal printers, students had to line up at the copy machine to make copies.  You could easily spend hours in line, even if you only had a few copies to make.  It was an inefficient and infuriating problem for students.

It was also a perfect research opportunity for Ellen Langer, a professor in Harvard’s Psychology Department.

Prof. Langer and her colleagues asked students to break into the line using one of three phrases:

  1. “Excuse me, I have 5 pages.  May I use the xerox machine?”
  2. “Excuse me, I have 5 pages.  May I use the xerox machine, because I have to make copies?”
  3. “Excuse me, I have 5 pages.  May I use the xerox machine, because I’m in a rush?”

The results were definitive and surprising.  Students who used the first phrase were successful 60% of the time, but those who used the phrases with “because” were successful 93% and 94% of the time.

“Because” matters.  The reason does not.

Note that in phrases 2 and 3, the reason the student is asking to cut in line isn’t very good. You can practically hear the snarky responses, “Of course, you have to make copies; why else would you be at the copy machine?” or “We’re all in a rush,” and the request is denied.

But that didn’t happen.

Instead, the research (and hundreds of subsequent studies) showed that when the ask is simple or familiar,  people tend to follow instructions or respond positively to requests without paying attention to what’s said, even if the instructions don’t make sense or the request disadvantages them in some way.   Essentially, people hear “because,” assume it’s followed by a good reason and comply.

“Because” matters.  How you use it matters more.

The power of “because” isn’t about manipulation or coercion. It’s about fostering a culture of transparency, critical thinking, and effective communication.

Taking the time to think about when and how to communicate the Why behind your requests increases your odds of success and establishes you as a strategic and thoughtful leader.  But building your “Because’ habit takes time, so consider starting here:

Conduct a “Because” Audit: For one day, track your use of “because.” How many times do you make a request?  How many times to you explain your requests with “because?”  How many times do you receive a request, and how many of those include “because?”  Simply noticing when “because” is used and whether it works provides incredible insights into the impact it can have in your work.

Connect your “Becauses” As leaders, we often focus on the “what” and “how” of directives, but the “why” is equally crucial. Take your top three strategic priorities for the quarter and craft a compelling “because” statement that clearly articulates the reasoning behind it. For instance, “We’re expanding into the Asian market because it represents a $50 billion opportunity that aligns perfectly with our core competencies.” This approach not only provides clarity but also helps in rallying your team around a common purpose.

Cascade the “Because” Habit: Great leaders don’t just adopt best practices; they institutionalize them. Challenge your direct reports to incorporate “because” into their communications. When they bring you requests, ask them for the “because’ if they don’t offer it.  Make it a friendly competition and celebrate people who use this technique to drive better outcomes.

Tell me how you’ll start because then you’re more likely to succeed.

(see what I did there?)

Wisdom from the Waters: An Innovation Leadership Fable

Wisdom from the Waters: An Innovation Leadership Fable

Once upon a time, in a lush forest, there lived a colony of industrious beavers known far and wide for their magnificent dams, which provided shelter and sustenance for many.

One day, the wise old owl who governed the forest decreed that all dams must be rebuilt to withstand the increasingly fierce storms that plagued their land. She gave the beavers two seasons to complete it, or they would lose half their territory to the otters.

The Grand Design: Blueprints and Blind Spots

The beaver chief, a kind fellow named Oakchew, called the colony together, inviting both the elder beavers, known for their experience and sage advice and the young beavers who would do the actual building.

Months passed as the elders debated how to build the new dams. They argued about mud quantities, branch angles, and even which mix of grass and leaves would provide structural benefit and aesthetic beauty.  The young beavers sat silently, too intimidated by their elders’ status to speak up.

Work Begins: Dams and Discord

As autumn leaves began to fall, Oakchew realized they had yet to start building. Panicked, he ordered work to commence immediately.

The young beavers set to work but found the new method confusing and impractical. As time passed, progress slowed, panic set in, arguments broke out, and the once-harmonious colony fractured.

One group insisted on precisely following the new process even as it became obvious that they would not meet the deadline.  Another reverted to their old ways, believing that a substandard something was better than nothing.  And one small group went rogue, retreating to the smallest stream to figure it out for themselves.

As the deadline grew closer, the beavers worked day and night, but progress was slow and flawed. In desperation, Oakchew called upon the squirrels to help, promising half the colony’s winter food stores.

Just as the first storm clouds gathered, Oakchew surveyed the completed dams. Many were built as instructed, but the rushed work was evident and showed signs of weakness. Most dams were built with the strength and craftsmanship of old but were likely to fail as the storms’ intensity increased. One stood alone and firm, roughly constructed with a mix of old and new methods.

Wisdom from the Waters: Experiments and Openness

Oakchew’s heart sank as he realized the true cost of their efforts. The beavers had met their deadline but at a great cost. Many were exhausted and resentful, some had left the colony altogether, and their once-proud craftsmanship was now shoddy and unreliable.

He called a final meeting to reflect on what had happened.  Before the elders could speak, Oakchew asked the young beavers for their thoughts.  The colony listened in silent awe as the young builders explained the flaws in the “perfect” process. The rogue group explained that they had started building immediately, learning from each failure, and continuously improving their design.

“We wasted so much time trying to plan the perfect dam,” Oakchew admitted to the colony. “If we had started building sooner and learned from our mistakes, we would not have paid such a high cost for success. We would not have suffered and lost so much if we had worked to ensure every beaver was heard, not just invited.”

From that day forward, the beaver colony adopted a new approach of experimentation, prototyping, and creating space for all voices to be heard and valued.  While it took many more seasons of working together to improve their dams, replenish their food stores, and rebuild their common bonds, the colony eventually flourished once more.

The Moral of the Story (just in case it isn’t obvious)

The path to success is paved not with perfect plans but with the courage to act, the wisdom to learn from failures, and the openness to embrace diverse ideas. True innovation arises when we combine the best of tradition with the boldness of experimentation.

Collaboration Software is Killing Collaboration

Collaboration Software is Killing Collaboration

In our race to enable and support hybrid teams, our reliance on collaboration software has inadvertently caused us to forget the art of true collaboration. 

The pandemic forced us to rely on digital platforms for communication and creativity. But as we embraced these tools, something essential was lost in translation. Last week, I watched team members sitting elbow-to-elbow spend two hours synthesizing discovery interviews and debating opportunity areas entirely by chat.

What collaboration is

“Collaboration” seems to have joined the ranks of meaningless corporate buzzwords.  In an analysis of 1001 values from 172 businesses, “collaboration” was the #2 most common value (integrity was #1), appearing in 23% of the companies’ value statements. 

What it means in those companies’ statements is anyone’s guess (we’ve all been in situations where stated values and lived values are two different things).  But according to the dictionary, collaboration is “the situation of two or more people working together to create or achieve the same thing.”

That’s a short definition with a lot of depth. 

  • “The same thing” means that the people working together are working towards a shared goal in which they have a stake in the outcome (not just the completion). 
  • “Working together” points towards interdependence, that everyone brings something unique to the work and that shared goal cannot be achieved without each person’s unique contribution. 
  • “Two or more people” needing each other to achieve a shared outcome requires a shared sense of respect, deep trust, and vulnerability.

It’s easy to forget what “collaboration” means.  But we seem to have forgotten how to do it.

What collaboration is not

As people grow more comfortable “collaborating” online, it seems that fewer people are actually collaborating.   

Instead, they’re:

  • Transacting: There is nothing wrong with email, texts, or messaging someone on your platform of choice.  But for the love of goodness, don’t tell me our exchange was a collaboration. If it were, every trip to the ATM would be a team-building exercise.
  • Offering choices:  When you go out to eat at a fast-food restaurant, do you collaborate with the employee to design your meal?  No.  You order off a menu.  Offering a choice between two or three options (without the opportunity to edit or customize the options), isn’t collaboration.  It’s taking an order.
  • Complying: Compliance is “the act of obeying a law or rule, especially one that controls a particular industry or type of work.”  Following rules isn’t collaboration, it’s following a recipe
  • Cooperating:  Cooperation is when two or more people work together independently or interdependently to achieve someone else’s goal.  Collaboration requires shared objectives and ownership, not just shared tasks and timelines.

There’s nothing wrong with any of these activities.  Just don’t confuse them with collaboration because it sends the wrong message to your people. 

Why this matters

This isn’t an ivory-tower debate about semantics.

When people believe that simple Q&A, giving limited and unalterable options, following rules, and delivering requests are collaboration, they stop thinking.  Curiosity, creativity, and problem-solving give way to efficiency and box-checking.  Organizations stop exploring, developing, and innovating and start doing the same thing better, faster, and cheaper.

So, if you truly want your organization to grow because it’s filled with creative and empathetic problem-solvers, invest in reclaiming the true spirit of collaboration.  After all, the next big idea isn’t hiding in a chat log—it’s waiting to be born in the spark of genuine collaboration.

Leaked MrBeast Document: A Shining Example of Leadership

Leaked MrBeast Document: A Shining Example of Leadership

In the often murky world of corporate communication, a leaked MrBeast document has emerged as a beacon of clarity. Far from being your typical vague, jargon-filled memo, this onboarding document is a crystal-clear recipe for success that’s as refreshing as it is rare.

But first, let’s address the elephant in the room. MrBeast’s empire isn’t without its share of controversy. Reports of toxic work environments, unsafe conditions for contestants, and allegations of rigged games cast a shadow over his content creation machine and his leadership capabilities. These are serious issues that merit investigation and discussion. As a result, this post isn’t an endorsement of MrBeast as a leader, it’s an endorsement of an onboarding document that he wrote.

The Secret Sauce: Clarity Meets Innovation

What sets this document apart is its razor-sharp clarity and relentless focus on creativity. Unlike the vague platitudes that plague many corporate communications, job descriptions, and performance matrixes, this document clearly outlines expectations, success metrics, and the strategies and tactics to fuel continuous innovation.

This clarity is transformative for people and organizations. When team members understand both the guardrails and the goals, they channel their creative energy into groundbreaking ideas rather than second-guessing their approach and worrying about repercussions.

Expectations: Always Be Learning

The first principle is a clear directive: always be learning. In MrBeast’s world, this isn’t just about personal growth—it’s about staying ahead in a rapidly changing digital landscape. This commitment to continuous learning fuels innovation by ensuring the team is constantly exploring new technologies, trends, and creative techniques.

While some see the definition of A, B, and C-players as evidence of a toxic workplace, the fact is that it’s the reality in most workplaces.  It’s the absence of clarity, usually disguised by claims of family-like cultures that value diversity, that makes workplaces toxic. 

Metrics: The Start of a Feedback Loop

The focus on specific success metrics like Click-Through Rate and Average View Duration isn’t just about measurement—it’s about creating a feedback loop for innovation. Clear benchmarks developed over time allow teams to quickly assess the impact of new ideas and iterate accordingly.  It also removes the temptation and ability to “move the goalposts” to create the appearance of success.

Strategy: Structure Meets Creativity

After describing what success looks like for employees and how they’ll be measured, the document outlines a structured content formula akin to an innovation strategy. It provides a clear framework of priorities, goals, and boundaries while encouraging creative experimentation within those boundaries.

Starting with a step-by-step guide to making videos with a “wow” factor, the document also emphasizes the criticality of focusing on “critical components” and managing dependencies and

Far from the usual corporate claims that direction and “how to’s” constrain creativity and disempower employees, this approach creates a safety net that allows employees to be successful while still pushing the envelope of what’s possible in content creation.

How to Become Your Version of (a non-controversial) Mr. Beast

You don’t have to be a content creator, social media savant, or company founder to follow MrBeast’s lead.  You have to do something much more difficult – communicate clearly and consistently.

  1. Clearly define what success looks like (and doesn’t) for your employees and projects.
  2. Establish frameworks that encourage bold ideas while maintaining focus.
  3. Define objective success metrics and consistently measure, track, and use them.

This leaked MrBeast document offers more than just a glimpse into a YouTube empire; it’s a masterclass in leadership in the era of hybrid workplaces, geographically dispersed teams, and emerging cultures and norms. 

The document’s approach shows that innovation doesn’t have to be chaotic. By providing clear expectations and frameworks, leaders can create an environment where creativity thrives, and groundbreaking ideas can be rapidly developed and implemented.

When viewed in the bigger context of the MrBeast organization, however, the document is also a reminder that no matter how clear you think your communication is, you must be vigilant for those who claim that bad behavior is just a “misunderstanding.” Leaders know that no amount of views, clicks, or revenue is worth sacrificing the well-being of their teams.

‘We Can’t Do That’ is a Lie.  These Are the Truths.

‘We Can’t Do That’ is a Lie. These Are the Truths.

How many times have you proposed a new idea and been told, “We can’t do that?” Probably quite a few.  My favorite memory of being told, “We can’t do that,” happened many years ago while working with a client in the publishing industry:

Client: We can’t do that.

Me: Why?

Client: Because we already tried it, and it didn’t work.

Me: When did you try it?

Client: 1972

Me: Well, things certainly haven’t changed since 1972, so you’re right, we definitely shouldn’t try again.

I can only assume they appreciated my sarcasm as much as the idea because we eventually did try the idea, and, 30+ years later, it did work. But the client never would have enjoyed that success if my team and I had not seen through “we can’t do that” and helped them admit (confess) what they really meant.

Quick acknowledgment

Yes, sometimes “We can’t do that” is true.  Laws and regulations define what can and can’t be done.  But they are rarely as binary as people make them out to be.  In those gray areas, the lie of “we can’t do that” obscures the truth of won’t, not able to, and don’t care.

“I won’t do it.”

When you hear “can’t,” it usually means “won’t.”  Sometimes, the “won’t” is for a good reason – “I won’t do the dishes tonight because I have an urgent deadline, and if I don’t deliver, my job is at risk.”  Sometimes, the “won’t” isn’t for a good reason – “I won’t do the dishes because I don’t want to.”  When that’s the case, “won’t” becomes “can’t” in the hope that the person making the request backs off and finds another solution. 

For my client, “We can’t do that” actually meant, “I won’t do that because it failed before and, even though that was thirty years ago, I’m afraid it will fail again, and I will be embarrassed, and it may impact my reputation and job security.”

You can’t work with “can’t.”  You can work with “won’t.”  When someone “won’t” do something, it’s because there’s a barrier, real or perceived.  By understanding the barrier, you can work together to understand, remove, or find a way around it.

“I’m not able to do it.”

“Can’t” may also come with unspoken caveats.  We can’t do that because we’ve never done it before and are scared.  We can’t do that because it is outside the scope of our work.  We can’t do that because we don’t know how. 

Like “won’t,” you can work with “not able to” to understand the gap between where you are now and where you want to go.  If it’s because you’re scared of doing something new, you can have conversations to get smarter about the topic or run small experiments to get real-world learnings.  If you’re not able to do something because it’s not within your scope of work, you can expand your scope or work with people who have it in their scope.  If you don’t know how, you can talk to people, take classes, and watch videos to learn how.

“I don’t care.”

As brave as it is devastating, “we can’t do that” can mean “I don’t care enough to do that.” 

Executives rarely admit to not caring, but you see it in their actions. When they say that innovation and growth are important but don’t fund them or pull resources at the first sign of a wobble in the business, they don’t care. If they did care, they would try to find a way to keep investing and supporting the things they say are priorities.

Exploring options, trying, making an effort—that’s the difference between “I won’t do it” and “I don’t care.”    “I won’t do that” is overcome through logic and action because the executive is intellectually and practically open to options. “I don’t care” requires someone to change their priorities, beliefs, and self-perception, changes that require major personal, societal, or economic events.

Now it’s your turn to tell the truth

Are you willing to ask the questions to find them?

Founder Mode vs. Manager Mode: Why It’s a False Choice

Founder Mode vs. Manager Mode: Why It’s a False Choice

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.