Tag Archives: project management

Lobsters and the Wisdom of Ignoring Your Customers

Lobsters and the Wisdom of Ignoring Your Customers

GUEST POST from Robyn Bolton

Being the smart innovator (and businessperson) you are, you know it’s important to talk to customers. You also know it’s important to listen to them.

It’s also important to ignore your customers.

(Sometimes)

Customers will tell you what the problem is. If you stay curious and ask follow-up questions (Why? and Tell me more), they’ll tell you why it’s a problem and the root cause. You should definitely listen to this information.

Customers will also tell you how to fix the problem. You should definitely ignore this information.

To understand why, let me tell you a story.

Eye Contact is a Problem

Years ago, two friends and I took a day trip to Maine. It was late in Fall, and many lobster shacks dotting the coast were closed for the season. We found one still open and settled in for lunch.

Now, I’m a reasonably adventurous eater. I’ll try almost anything once (but not try fried tarantulas). However, I have one rule – I do not want to make eye contact with my food.

Knowing that lobsters are traditionally served with their heads still attached, I braced for the inevitable. As the waitress turned to me, I placed the same order as my friends but with a tiny special request. “I’ll have the lobster, but please remove its head.”

You know that scene in movies when the record scratches, the room falls silent, and everyone stops everything they’re doing to stare at the person who made an offending comment? Yeah, that’s precisely what happened when I asked for the head to be removed.

The waitress was horrified, “Why? That’s where all the best stuff is!”

“I don’t like making eye contact with my food,” I replied.

She pursed her lips, jotted down my request, and walked away.

A short time later, our lunch was served. My friends received their lobsters as God (or the chef) intended, head still attached. Then, with great fanfare, my lobster arrived.

Its head was still attached.

But we did not make eye contact.

Placed over the lobster’s eyes were two olives, connected by a broken toothpick and attached to the lobster’s “ears” by two more toothpicks.

The chef was offended by my request to remove the lobster’s head. But, because he understood why I wanted the head removed, he created a solution that would work for both of us – lobster-sized olive sunglasses.

Are you removing the head or making sunglasses?

Customers, like me, are experts in problems. We know what the problems are, why they’re problems, and what solutions work and what don’t. So, if you ask us what we want, we’ll give you the solution we know – remove the head.

Innovators, like you and the chef, are experts in solutions. You know what’s possible, see the trade-offs, and anticipate the consequences of various choices. You also take great pride in your work and expertise, so you’re not going to give someone a sub-par solution simply because they asked for it. You’re going to provide them with olive sunglasses.

Next time you talk to customers, stay curious, ask open-ended questions, ask follow-up questions, and build a deep understanding of their problems. Then ignore their ideas and suggestions. They’ll only stand in the way of your olive sunglasses.

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.

A Superpower That Can Save The Day

Same But Different

GUEST POST from Mike Shipulski

If there’s one superpower to develop, it’s to learn how to assess a project and get a good feel for when it will launch.

When you want to know how long a project will take, ask this simple question: ‘What must the project team learn before the project can launch?” By starting with this single question, you will start the discussion that will lead you to an understanding of what hasn’t been done before and where the uncertainty is hiding. And if there’s one thing that can accelerate a project, it’s defining where the uncertainty is hiding. And knowing this doubly powerful, like a pure two-for-one, because if you know where uncertainty is, by definition, you know where it isn’t. Where the uncertainty isn’t, you can do what you did last time, and because you’ve done it before, you know how long it will take. No new tools, no new methods, no new analyses, no new machines, no new skillsets, no new anything. And for the remaining elements of the project, well, that’s where the uncertainty is hiding and that’s where you will focus on the learning needed to secure the launch.

But it can be difficult to understand the specific learning that must be done for a project to launch. One trick I like to use is the Same-But-Different method. It goes like this. Identify a project that launched (Project A) that’s most similar to the one that will launch next (Project B) and perform a subtraction of sorts. Declare that Project B (the one you want to launch) is the same as Project A (the one you already launched) but different in specific ways and then define those differences as clearly and tightly as possible. And where it’s different, that’s where the learning energy must be concentrated.

Same-But-Different sounds simplistic and trivial, but it isn’t. More than anything, it’s powerful. For the elements that are the same, you do what you did last time, which is freeing. And for the small subset if things that are different, you dig in!

Same-But-Different drives deep clarity and extreme focus, which result in blistering progress and blinding effectiveness.

And for some reason unknown to me, asking a team to define the novel elements of a project is at least fifty times more difficult than asking them how Project B is different than Project A. So, it feels good to the team when they can use Same-But-Different to quickly easily define what’s different and then point directly to the uncertainty. And once the team knows where the uncertainty is hiding, it’s no longer hiding.

And if there’s one thing a project team likes, it’s knowing where the uncertainty is hiding.

Image credit: Unsplash

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

3 Mind-Blowing Things I Learned in Nebraska

3 Mind-Blowing Things I Learned in Nebraska

GUEST POST from Robyn Bolton

In the Before Times, we attended conferences to learn, make connections, and promote ourselves and our businesses. Then COVID hit, and conferences became virtual.   Although that made them easier to attend, it also made them easier to skip. Because, if we’re honest, most conferences were more about connecting and promoting than learning.

Last week, I went to one of those rare, almost mythical, conferences more focused on learning and connecting than promoting. It was fantastic! It was also in Nebraska (which is a pretty interesting place, btw).

Here are my three biggest mind-blowing takeaways from Inside Outside’s IO2022 Summit:

“Strategy is the direction you take to win in the future”

Kareen Proudian, Managing Partner at Faculty of Change

It’s a bit embarrassing to admit, but if you asked me to define “Strategy,” I’d respond with a long and rambling answer. Which means I can’t define “strategy.”  This admission is especially embarrassing because I have a resume littered with places where I developed, drafted, and implemented strategies, so I should have learned what the word means. But nope, I didn’t.

I suspect I’m not alone.

Asking for the definition of strategy is like asking if you must wear clothes to the office. You should know the answer. But unlike whether or not clothing is mandatory, most of us don’t know the answer, AND it’s easy to get away with never knowing the answer.

The elegant simplicity of Kareen’s definition of strategy blew my mind. It’s short, memorable, and something that most people can understand. Maybe I should share the definition with my alma maters and past employers.

“When we feel threatened, our IQ drops 50 to 70 points”

Alla Weinberg, CEO at Spoke & Wheel

When I first heard talk about Psychological Safety and Safe Spaces in today’s business world, I rolled my eyes. Hard. As a Gen X-er, I grumbled about how we didn’t need “safe spaces” when I grew up because we were tough and self-reliant, and I lamented the inevitable downfall of society caused by weak and coddled Millennials.

I was wrong.

Psychological Safety is absolutely and unquestionably essential for individuals to grow, teams to work, companies to operate and innovate, and societies to function and evolve. I’ve seen teams and businesses transform and achieve unbelievable success by discussing and living the elements they require for Psychological Safety. I’ve also seen teams and businesses fail in its absence.

These results aren’t surprising when you realize that you feel threatened when you are in a complex situation in which you cannot accurately predict the outcomes. And when you feel threatened, you are half as intelligent, effective, and creative as you are when you’re calm.

So, if you’re a manager and you’re upset that your people aren’t as intelligent, effective, or creative as they should be, it may not be their fault. It may be yours.

“Stage expertise, not industry expertise, is key to innovation success”

Sean Sheppard, Managing Partner at U+

There is deep comfort in the known. It’s why we gravitate to people like us. It’s also why companies ask job candidates and consultants about their experience in the industry and choose those with deep experience and impressive expertise. Often, there’s nothing with this question or the resulting decision.

Sometimes, it’s precisely the wrong question.

Sometimes, functional expertise is significantly more important than industry experience. After all, if you’re the hiring manager at a healthcare company looking for a Director of Finance, who would you hire – a Marketing Director from a competitor or a Finance Director from a CPG company?

That’s the case with innovation.

Decades of real-world experience (not to mention the successful launch of 100+ startups) show that successful corporate startup teams had expertise (mindsets, skillsets, executional drive) in the startup’s phase and a working knowledge of the industry rather extensive industry expertise and little to no innovation experience.

Questions are good. The right questions are better. So, the next time you’re staffing up an innovation team (or hiring a consultant), choose based on their innovation experience and willingness to learn about your industry.

Innovation happens everywhere

That’s why people from San Francisco, Austin, Washington DC, NYC, Toronto, Boston, and dozens of other places converged on Lincoln, Nebraska.

We went to see innovation in action and learn about the thriving startup community in the middle of the country. We also went to learn and connect with others committed to creating new things that create value.

Getting our minds blown was a bonus.

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.

Three HOW MIGHT WE Alternatives That Actually Spark Creative Ideas

Three How Might We Alternatives That Actually Spark Creative Ideas

GUEST POST from Robyn Bolton

Q: How might we brainstorm new ideas to serve our customers better?

A: Have a brainstorming session that starts with “How Might We help customers [Job to be Done/problem]?”

If only it were that simple.

How Might We (HMW) is an incredible tool (not BS, as some would assert), but we misuse it. We focus too much on the “we” and not enough on the “might.”

Might > We

HMW was first used to prompt people to be “wildly creative while simultaneously leveraging [company’s] innate strengths.”

IDEO popularized the prompt as a way to solve “wicked problems” – problems so complex that there is no right or wrong answer.

In both of these cases, the assumption was that the word “might” would free people from the shackles of today’s thinking and constraints and give people permission to dream without fear of judgment and reality.

“We” kept ideas tethered to the reality of the company’s “innate strengths,” providing a modicum of comfort to executives worried that the session wouldn’t result in anything useful and would, therefore, be a waste of time.

We > Might

Alas, as time went on and HMW became more popular, we lost sight of its intent (prompt wildly creative thinking about wicked problems) and twisted it to our purposes.

  • We end the HMW sentence with our problems (e.g., HMW cut costs by getting more customers to use self-service tools?).
  • We use it to brainstorm solutions to things that aren’t even problems (e.g., HMW eliminate all customer service options that aren’t self-serve?)
  • We mentally replace “might” with “will” so we can emerge from brainstorming sessions with a tactical implementation plan.

How Might Can YOU Fix HMW?

If you’re not getting creative, radical, or unexpected ideas from your brainstorming sessions, you have an HMW problem.< As a result, continuing to use HMW as a tool to prompt creative, radical, or unexpected ideas is the definition of insanity. And you are not insane. Instead, mix it up. Use different words to articulate the original intent of HMW.

How would we solve this problem if the answer to every request is YES?

Innovation thrives within constraints. Brainstorming doesn’t.

Even when you tell people not to constrain themselves, even implore them to value “quantity over quality,” you still get more “safe” ideas rather than more “crazy” ideas.

Do more than tell. Make a world without constraints real. Explicitly remove all the constraints people throw at ideas by creating a world of infinite money, people, capabilities, willingness, appetite for risk, and executive support. Doing this removes the dreaded “but” because there is no “but we don’t have the money/people/capabilities” or “but management will never go for it” and creates space for “and.”

What would we ask for if we were guaranteed a YES to only ONE request?

This question is often asked at the end of a brainstorm to prioritize ideas. But it’s equally helpful to ask it at the beginning.

This question shifts our mindset from “the bosses will never say yes, so I won’t even mention it” to “the bosses will say yes to only one thing, so it better be great!”  It pulls people off the sidelines and reveals what people believe to be the most critical element of a solution.   It drives passionate engagement amongst the whole team and acts as a springboard to the next brainstorm – How Might We use (what they said yes to) to solve (customers’ Jobs to be Done/problem)?

How would we solve the problem if the answer to every request is NO?

This one is a bit risky.

Some people will throw their hands in the air, declare the exercise a waste of time and effort, and collapse into a demotivated blob of resignation.

Some people will feel free. As Seth Godin wrote about a journal that promises to reject every single person who submits an article, “The absurdity of it is the point. Submitting to them feels effortless and without a lot of drama, because you know you’re going to get rejected. So instead of becoming attached to the outcome, you can simply focus on the work.”

For others, this will summon their inner rebel, the part of themselves that wants to stick it to the man, prove the doubters wrong, and unleash a great “I told you so” upon the world. To them, “No” is the start of the conversation, not the end. It fires them up to do their best work.

Don’t invite the first group of people to the brainstorm.

Definitely invite the other two groups.

How Might Will/Do YOU Fix HMW?

If you want something different, you need to do something different.

Start your next brainstorm with a new variation on the old HMW prompt.

How do people react? Does it lead to more creative or more “safe” ideas?

How might we adjust to do even better next time?

Image credit: Pexels

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

Making Innovation the Way We Do Business (easy as ABC)

Making Innovation the Way We Do Business (easy as ABC)

GUEST POST from Robyn Bolton

“We need to be more innovative.”

How many times have you said or heard that? It’s how most innovation efforts start. It’s a statement that reflects leaders’ genuine desire to return to the “good ol’ days” when the company routinely created and launched new products and enjoyed the publicity and growth that followed.

But what does it mean to be more innovative?

Innovation’s ABCs

A is for Architecture

Architecture includes most of the elements people think of when they start the work to become more innovative – strategy, structure, processes, metrics, governance, and incentives.

Each of these elements answers fundamental questions:

  • Strategy: Why is innovation important? How does it contribute to our overall strategy?
  • Structure: Who does the work of innovation?
  • Process: How is the work done?
  • Metrics: How will we know when we’re successful? How will we measure progress?
  • Governance: Who makes decisions? How and when are decisions made?
  • Incentives: Why should people invest their time, money, and political capital? How will they be rewarded?

When it comes to your business, you can answer all these questions. The same is true if you’re serious about innovation. If you can’t answer the questions, you have work to do. If you don’t want to do the work, then you don’t want to be innovative. You want to look innovative*.

B is for Behavior

Innovation isn’t an idea problem. It’s a leadership problem.

Leaders that talk about innovation, delegate it to subordinates and routinely pull resources from innovation to “shore up” current operations don’t want to be innovative. They want to look innovative.

Leaders who roll up their sleeves and work alongside innovation teams, ask questions and listen with open minds, and invest and protect innovation resources want to be innovative.

To be fair, it’s incredibly challenging to be a great leader of both innovation and operations. It’s the equivalent of writing equally well with your right and left hands. But it is possible. More importantly, it’s essential.

C is for Culture

Culture is invisible, pervasive, and personal. It is also the make-or-break factor for innovation because it surrounds innovation architecture, teams, and leaders.

Culture can expand to encourage and support exploration, creativity, and risk-taking. Or it can constrict, unleashing antibodies that swarm, suffocate, and kill anything that threatens the status quo.

Trying to control or change culture is like trying to hold water in your fist. But if you let go just a bit, create the right conditions, and wait patiently, change is possible.

Easy as 123

The most common mistake executives make in the pursuit of being “more innovative” is that they focus on only A or only B or only C.  But, as I always tell my clients, the answer is “and, not or.”

  1. Start with Architecture because it’s logical, rational, and produces tangible outputs like org charts, process flows, and instruction manuals filled with templates and tools. Architecture is comforting because it helps us know what to do and how.
  2. Use Architecture to encourage Behavior because the best way to learn something is to do it. With Architecture in place (but well before it’s finished), bring leaders into the work – talking to customers, sharing their ideas, and creating prototypes. When leaders do the work of innovation, they quickly realize what’s possible (and what’s not) and are open to learning how to engage (behave) in a way that supports innovation.
  3. Leverage Architecture and Behavior to engage Culture by creating the artifacts, rituals, and evidence that innovation can happen in your company, is happening and will continue to happen. As people see “innovation” evolve from a buzzword to a small investment to “the way we do business,” their skepticism will fade, and their support will grow.

Just like the Jackson 5 said

ABC, It’s easy a 123

Architecture, behavior, culture – they’re all essential to enabling an innovation capability that repeatedly creates new revenue.

And while starting with architecture, building new leadership behaviors, and investing until the culture changes isn’t easy, it’s the 123 steps required to “be more innovative.”

Image credit: Wikimedia Commons

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

Four Things You Need to Succeed in The Good Place

Four Things You Need to Succeed in The Good Place

GUEST POST from Robyn Bolton

You have, no doubt, seen the design squiggle. The ubiquitous scribble is all loopy and knotty in the beginning until it finally sorts itself into a straight line by the end.

It illustrates the design process – “the journey of researching, uncovering insights, generating creative concepts, iteration of prototypes and eventually concluding in one single designed solution” – and its elegant simplicity has led it to be adopted by all sorts of other disciplines, including innovation.

But when I showed it to a client, her immediate response was, “It’s Jeremy Bearimy!”*

Wha????

And that is how I discovered The Good Place, a sitcom about four humans who die, go to The Good Place, and struggle to learn what it means to be good.

The show, created by Michael Schur of The Office and Parks and Recreation fame, is a brilliant treatise on ethics and moral philosophy. It also contains valuable wisdom about what innovators need to succeed.

Questions

With all due respect, “It’s the way it’s always been done” is an excuse that’s been used for hundreds of years to justify racism, misogyny…

Tahani Al-Jamil

This quote was a gut punch from the show’s fourth and final season. As innovators, we often hear people ask why change is needed. “If it ain’t broke, don’t fix it!” they proclaim.

But sometimes it is broke, and we don’t know it. At the very least, it can always be better.

So, while “it’s the way it’s always been done” at your company probably (hopefully) doesn’t include racism, misogyny, sexism, and other genuinely horrible things, framing the status quo as an enabler of those horrors is a harsh wake-up call to the dangers of an unquestioning commitment to continuing to do things the way they’ve always been done.

Decisions (not just Ideas)

If you’re always frozen in fear and taking too long to figure out what to do, you’ll miss your opportunity, and maybe get sucked into the propeller of a swamp boat.

Jason Mendoza

Even though Jason Mendoza is the resident idiot of The Good Place, he occasionally (and very accidentally) has moments of profound insight. This one to a situation that innovators are all too familiar with – analysis paralysis.

How often do requests for more data, more (or more relevant) benchmarks, or input from more people slow down decisions and progress? These requests are rarely rooted in doubt about the data, benchmarks, or information you presented. They are rooted in fear – the fear of making the wrong decision, being blamed or shamed, and losing a reputation or even a job.

But worse than being wrong, blamed, shamed, or unemployed is missing an opportunity to radically improve your business, team, or even the world. It’s the business equivalent of getting sucked into the propeller of a swamp boat.

Actions (not just decisions)

In football, trying to run out the clock and hoping for the best never works. It’s called “prevent defense.” You don’t take any chances and just try and hold on to your lead. But prevent defense just PREVENTS you from winning! It’s always better to try something.

Jason Mendoza

Jason does it again, this time invoking a lesson learned from his beloved Jacksonville Jaguars.

Few companies publicly admit to adopting a prevent defense, even though most companies engage in it. They play prevent defense when they don’t invest in innovation, focus exclusively on maintaining or incrementally improving what they currently do, or confine their innovation efforts to events like hackathons and shark tanks.

Incremental improvements and innovation theater keep you competitive. But they won’t get you ahead of the competition or make you a leader in your industry. In fact, they prevent it by making you feel good and safe when you’re really just running out the clock.

Perseverance

Come on, you know how this works. You fail and then you try something else. And you fail again and again, and you fail a thousand times, and you keep trying because maybe the 1,001st idea might work. Now, I’m gonna and try to find our 1,001st idea.

Michael

It’s hard to explain this quote without sharing massive spoilers, so let’s just say that The Good Place is an experiment that fails. A lot.

But it’s also an experiment that generates profound learning and universe-altering changes, things that would not have been possible without the failures.

Yes, smart innovators know when to kill a project. They also know when to try one more time. Wise innovators know the difference.

One final bit of wisdom

Innovation is hard. You will run into more resistance than expected, and things will rarely work out as planned. As long as you keep trying and learning, you won’t fail.

To paraphrase Jason Mendoza (again), you’re not a failed innovator, you’re pre-successful.

*For those of you who are, like I was, unfamiliar with Jeremy Bearimy, here’s a clip explaining it (WARNING: SPOILERS)

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

You Can’t Innovate Without This One Thing

You Can't Innovate Without This One Thing

GUEST POST from Robyn Bolton

It just landed on your desk. Or maybe you campaigned to get it. Or perhaps you just started doing it. How the title of “Innovation Leader” got to your desk doesn’t matter nearly as much as the fact that it’s there, along with a budget and loads of expectations.

Of course, now that you have the title and the budget, you need a team to do the work and deliver the results.

Who should you look for? The people that perform well in the current business, with its processes, structures, and (relative) predictability, often struggle to navigate the constant uncertainty and change of innovation. But just because someone struggles in the process and structure of the core business doesn’t mean they’ll thrive creating something new.

What are the qualities that make someone a successful innovator?

70 answers

A lot of people have a lot to say about the qualities and characteristics that make someone an innovator. When you combine the first four Google search results for “characteristics of an innovator” with the five most common innovation talent assessments, you end up with a list of 70 different (and sometimes conflicting) traits.

The complete list is at the end of this article, but here are the characteristics that appeared more than once:

  1. Curious
  2. Persistent
  3. Continuously reflective
  4. Creative
  5. Driven
  6. Experiments
  7. Imaginative
  8. Passionate

It’s a good list, but remember, there are 62 other characteristics to consider. And that assumes that the list is exhaustive.

+1 Answer

It’s not. Something is missing.

There is one characteristic shared by every successful innovator I’ve worked with and every successful leader of innovation. It’s rarely the first (or second or third) word used to describe them, but eventually, it emerges, always said quietly, after great reflection and with dawning realization.

Vulnerability.

Whether you rolled your eyes or pumped your fist at the word made famous by Brene Brown, you’ve no doubt heard it and formed an opinion about it.

Vulnerability is the “quality or state of being exposed to the possibility of being attacked or harmed, either physically or emotionally.”  Without it, innovation is impossible.

Innovation requires the creation of something new that creates value. If something is new, some or all of it is unknown. If there are unknowns, there are risks. Where there are risks, there is the possibility of being wrong, which opens you up to attack or harm.

When you talk to people to understand their needs, vulnerability allows you to hear what they say (versus what you want them to say).

In brainstorming sessions, vulnerability enables you to speak up and suggest an idea for people to respond to, build on, or discard.

When you run experiments, vulnerability ensures that you accurately record and report the data, even if the results aren’t what you hoped.

Most importantly, as a leader, vulnerability inspires trust, motivates your team, engages your stakeholders, and creates the environment and culture required to explore, learn, and innovate continuously.

n + 1 is the answer

Just as you do for every job in your company, recruit the people with the skills required to do the work and the mindset and personality to succeed in your business’ context and culture.

Once you find them, make sure they’re willing to be vulnerable and support and celebrate others’ vulnerability. Then, and only then, will you be the innovators your company needs.


Here’s the full list of characteristics:

  1. Action-oriented, gets the job done
  2. Adaptable
  3. Ambitious
  4. Analytical, high information capacity, digs through facts
  5. Associative Thinker, makes uncommon connections
  6. Breaks Boundaries, disruptive
  7. Business minded
  8. Collaborative
  9. Compelling Leader
  10. Competitive
  11. Consistent
  12. Continuously reflects (x3)
  13. Courageous
  14. Creative (x3)
  15. Curious (x4), asks questions, inquisitive, investigates
  16. Delivers results, seeks tangible outcomes
  17. Disciplined
  18. Divergent Thinker
  19. Driven (x3)
  20. Energetic
  21. Experiments (x2)
  22. Financially oriented
  23. Flexible, fluid
  24. Formally educated and trained
  25. Futuristic
  26. Giving, works to benefit others, wants to make the world better
  27. Goal-oriented
  28. Has a Growth mindset
  29. Highly confident
  30. Honest
  31. Imaginative (x2)
  32. Influential, lots of social capital
  33. Instinctual
  34. Intense
  35. Iterating between abstract and concrete thinking
  36. Learns through experiences
  37. Likes originality, seeks novelty
  38. Loyal
  39. Motivated by change, open to new experiences
  40. Networks, relates well to others
  41. Observes
  42. Opportunistic mindset, recognizes opportunities
  43. Opportunity focused
  44. Passionate (x2)
  45. Patient
  46. Persistent (x4)
  47. Persuasive
  48. Playful
  49. Pragmatic
  50. Proactive
  51. Prudent
  52. Rapidly recognizes patterns
  53. Resilient
  54. Resourceful
  55. Respects other innovators
  56. Seeks understanding
  57. Self-confident
  58. Socially intelligent
  59. Stamina
  60. Takes initiative
  61. Takes risks
  62. Team-oriented
  63. Thinks big picture
  64. Thrives in uncertainty
  65. Tough
  66. Tweaks solutions constantly
  67. Unattached exploration
  68. Visionary
  69. Wants to get things right
  70. Willing to Destroy

And the sources:

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.

Is Scrum or Kanban Right for Your Team?

GUEST POST from Art Inteligencia

In the fast-paced world of software development and project management, two agile methodologies stand out: Scrum and Kanban. While both aim to improve efficiency and productivity, they each have unique attributes that make them suitable for different types of teams and projects. Understanding these differences is crucial in making an informed decision about which methodology to implement for your team.

Understanding Scrum

Scrum is a structured framework for managing complex projects. It divides work into set periods known as sprints, typically lasting 2-4 weeks. The hallmark of Scrum is its focus on regular, iterative progress and transparency. Key roles include the Scrum Master, who facilitates the process, and the Product Owner, who prioritizes the backlog of work items.

Key Features of Scrum

  • Time-boxed sprints
  • Daily stand-up meetings
  • Defined roles and responsibilities
  • Regular reviews and retrospectives

Understanding Kanban

Kanban, on the other hand, is a visual method for managing workflow. It doesn’t prescribe fixed iterations or roles but relies on a board (physical or digital) to visualize tasks as they move through different stages of completion. Kanban aims to optimize the flow and limit work in progress (WIP).

Key Features of Kanban

  • Visual workflow management
  • Continuous delivery
  • WIP limits
  • Flexibility and adaptability

Case Study 1: XYZ Software Development

The Challenge

XYZ Software Development was struggling with long development cycles, leading to delayed product launches and stakeholder dissatisfaction. The company needed a structured approach to manage their complex projects more efficiently.

The Solution: Scrum

Adopting Scrum allowed XYZ to break their projects into manageable sprints. The introduction of clear roles and regular stand-ups fostered better communication and accountability. After implementing Scrum, XYZ saw a 30% reduction in development time and an increase in stakeholder satisfaction.

Case Study 2: Alpha Marketing Agency

The Challenge

Alpha Marketing Agency faced difficulties in adapting to sudden project changes and managing a high volume of small tasks. Their team needed a flexible method to handle continuously incoming work without predefined time constraints.

The Solution: Kanban

Switching to Kanban enabled Alpha to visualize their workflow. The flexible approach allowed them to quickly adapt to changes and effectively manage small, incoming tasks. By implementing Kanban, Alpha improved their task completion rate by 25% and achieved greater flexibility in their operations.

Conclusion

Choosing between Scrum and Kanban largely depends on your team’s specific needs and the nature of your projects. If your team thrives on structure, clear roles, and regular iterations, Scrum may be the better choice. However, if your team needs flexibility and the ability to adapt on the fly, Kanban could be the way to go. By understanding the strengths and applications of each methodology, you can make an informed decision that will drive your team toward greater efficiency and success.

Remember, the goal of both methodologies is to improve productivity and facilitate better project management, so it may also be worth considering a hybrid approach that leverages the strengths of both Scrum and Kanban.

Bottom line: Futurology is not fortune telling. Futurists use a scientific approach to create their deliverables, but a methodology and tools like those in FutureHacking™ can empower anyone to engage in futurology themselves.

Image credit: Pexels

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

Change Management Best Practices for Project Managers

Change Management Best Practices for Project Managers

GUEST POST from Art Inteligencia

In today’s fast-paced business environment, effective change management is essential for project managers. Whether you are implementing new technology, restructuring your organization, or launching a new product, managing change effectively can be the difference between success and failure. This article outlines some of the best practices for managing change, supported by real-world case studies, to help project managers navigate the complexities of change with confidence.

Best Practices

1. Involve Stakeholders Early

Engaging stakeholders from the outset ensures that you capture their insights, foster collaboration, and gain buy-in. Early involvement helps to identify potential challenges and develop strategies to address them.

2. Clear Communication

Clear, consistent, and transparent communication is vital for managing change. Project managers should establish multiple communication channels and regularly update all stakeholders on the progress and impact of the change.

3. Provide Training and Support

A well-planned training program and ongoing support can help ease the transition and equip team members with the skills and knowledge they need to succeed in the new environment.

4. Monitor and Adjust

Continuous monitoring and adjustment are essential to address unforeseen challenges that may arise during the implementation of change. Regular feedback loops and flexibility in approach enable project managers to make necessary adjustments in real time.

5. Celebrate Milestones

Acknowledging and celebrating milestones, no matter how small, can boost morale and maintain momentum throughout the change process. Recognizing contributions keeps team members motivated and engaged.

Case Studies

Case Study 1: TechCorp’s Digital Transformation

TechCorp, a mid-sized technology firm, decided to undergo a digital transformation to enhance its operational efficiency and customer experience. The project manager, Lisa, implemented the following change management best practices:

  • Involvement of Stakeholders: Lisa organized workshops and focus groups with employees from different departments to gather input and ensure that their concerns were addressed.
  • Clear Communication: She established bi-weekly newsletters and town hall meetings to keep everyone informed about the progress and next steps.
  • Training and Support: A comprehensive training program was rolled out, including online courses and hands-on sessions, to help employees adapt to the new tools and processes.
  • Monitoring and Adjustment: Lisa set up a feedback mechanism enabling employees to share their experiences and suggestions, allowing her to make necessary adjustments promptly.
  • Celebrating Milestones: Quarterly events were held to celebrate the team’s achievements and recognize individual contributions, which fostered a positive environment.

As a result of these efforts, TechCorp successfully implemented its digital transformation, achieving a 30% increase in operational efficiency and a 20% improvement in customer satisfaction.

Case Study 2: HealthPlus Hospital’s EHR Implementation

HealthPlus Hospital undertook the challenging task of implementing a new Electronic Health Records (EHR) system. The project manager, Robert, followed these best practices:

  • Involvement of Stakeholders: Robert included doctors, nurses, and administrative staff in the planning process to understand their needs and ensure the system met their requirements.
  • Clear Communication: Weekly meetings and a dedicated intranet site were used to keep everyone up to date on the project’s status and provide answers to frequently asked questions.
  • Training and Support: A multi-phase training program was launched, including on-site workshops and one-on-one sessions, to prepare staff for the new system.
  • Monitoring and Adjustment: An ongoing evaluation system was created to identify and address issues as they arose, ensuring minimal disruption to hospital operations.
  • Celebrating Milestones: Each successful phase of implementation was celebrated with a small event and recognition certificates for employees who played key roles.

Through these efforts, HealthPlus Hospital achieved a seamless transition to the new EHR system, leading to improved patient care and increased staff efficiency.

Conclusion

Effective change management is critical for the success of any project. By involving stakeholders early, maintaining clear communication, providing adequate training and support, monitoring and adjusting strategies, and celebrating milestones, project managers can lead their teams through change successfully. The case studies of TechCorp and HealthPlus Hospital demonstrate how these best practices can be applied in real-world scenarios to achieve positive outcomes.

SPECIAL BONUS: Be sure and get your Visual Project Charter template and other FREE tools from the Human-Centered Change methodology on our FREE Human-Centered Change Tools page.

Image credit: Unsplash

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

Why Change is Hard

Why Change is Hard

In 250 Words or Less

When we think about change, often we look at it as being done to us, not something that we are part of. Initiating change is a scary, overwhelming process that we often avoid because we lack the tools to accumulate buy-in and successfully plan and execute the change in the face of the following obstacles/barriers:

  1. psychological/political
  2. logistical
  3. financial
  4. external

This leads to inaction and preservation of the status quo until the pain becomes too much to bear, or the promise of the change becomes so enticing, that people are willing to drop their resistance and begin engaging in the activities necessary to realize the intended outcomes of the change.

Organizations must identify up-front not only why people may resist, but also who will likely resist. Some of the typical reasons why people will resist include:

  • loss of certainty (includes fear of job loss)
  • loss of purpose, direction, or status
  • loss of mastery (includes loss of expertise/recognition)
  • loss of control or ownership
  • loss of connection or attachment
  • lack of trust or clarity
  • fear of failure (feel unprepared)
  • seeing proposed change as irrelevant or a bad idea

Finally, change is hard because even if you idedntify and overcome the resistance/obstacles/barriers, hiding below the surface is the even more daunting prospect that according to a 2009 ProSci study, 73% of organizations are at or near change saturation — the point at which organizations are incapable of absorbing additional change.

(248 words)

SPECIAL BONUS

One tool I created for the Change Planning Toolkit™ that will assist you in creating a stronger change strategy and more targeted communications as you lower resistance and get people to choose change are the Eight Change Mindsets:

Eight Change Mindsets to Harness for Success

Obviously it is really hard to fit everything into 250 words so I had to leave some great other highlights of why change is hard, including this one:

In a 2008 global CEO study conducted by IBM on the enterprise of the future, the top challenges to successfully implementing strategic change were identified as:

  1. changing mindsets and attitudes (58 percent)
  2. corporate culture (49 percent)
  3. underestimating complexity (35 percent)
  4. shortage of resources (33 percent)
  5. lack of commitment from higher management (32 percent)
  6. lack of change know-how (20 percent)
  7. lack of motivation of employees involved (16 percent)

And here are some other challenges I would have included in the list:

  • lack of tools
  • lack of training
  • stakeholder misalignment
  • lack of buy in
  • change saturation
  • change fatigue
  • lack of change readiness
  • missing prerequisites
  • underestimating resistance
  • missing resources needed to succeed
  • underestimating risks and barriers
  • underestimating benefits of the status quo

To make change easier you’ll definitely want to transform how you plan and execute change into a more visual and collaborative approach, ideally suited for remote and hybrid interactions. It’s all laid out in my latest book Charting Change and supported by the Change Planning Toolkit™. A growing number of universities are picking up and teaching this new modern approach. Why not you?

Sources:

  1. Charting Change by Braden Kelley, Palgrave Macmillan, 2016
  2. Marsh survey on health, productivity and absenteeism—Prosci, 2009

Image Credit: Unsplash


Accelerate your change and transformation success

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