Skip to main content

Tag: Success

Are You a Great Business Analyst? Here’s How to Tell!

I’m sure many of you think that you are a really great business analyst. You read BA Times, attend BA conferences and write great requirements. But how can you tell if you truly are a great BA?

Recent articles by Kupe Kupersmith and Brad Egeland have outlined many characteristics of a highly performing BA. I’d like to take a slightly different approach and provide you with some questions that you can ask yourself to help determine if you truly are a great BA.

Do you actually know who all of your customers are?

I define “customers” as anyone who utilizes your work to get their job done. Notice I said “work” and not “requirements.” A great BA delivers much more than a set of written requirements. If all you do is write requirements you can stop reading. You are not a great BA. If you are still with me, then take a minute to write down whom you think your customers are for the projects you are currently working on. I’ll wait…

Related Article: The Great Facilitator

Great BAs understand that they serve a diverse group of customers. If you wrote down developers, testers, business SMEs, project manager, product owner/product manager, internal customers who use or support the system, external customers who use and pay for the system and executive management then you are on your way to being a great BA! To succeed, you must consider everyone who will be impacted by the solution your team is working on. Forgetting or neglecting a customer will lead to missed expectations and significantly increase the risk of creating a solution that is not well accepted. Since the pressure to develop the solution is always high, it’s easy to focus heavily on writing perfectly detailed requirements for the developers and testers to understand.

Great BAs remember that we deliver more than just written requirements to developers and testers. We need to explain the business problem to be solved and the vision of the solution. We also need to understand the scope of the project and help the team limit scope creep.

BAs serve various customers whom all have different priorities and agendas within a project. Great BAs can identify each of these customers and understand their priorities. Developers and testers are most concerned with the details of the requirements. They need to know exactly what to develop and what to test which is why they tend to wordsmith the requirements. Product managers/owners are concerned that the end product satisfies the primary business needs of the paying customer. Project managers want to know how many more stories we have left to develop. When will we be done? Internal customers are concerned with how easy the solution will be to support. Executive management doesn’t care about the nitty gritty details of the requirements. They care about overall costs, timelines and whether the project will bring in new revenue or not. Of course, your external customers who pay for the solution want their problem solved.

Great BAs realize that they must do more than just write clear requirements for developers and testers. They must consistently communicate the vision, scope and reason why we are completing the project to everyone who has an interest in the solution.

Do you know exactly what problem you are solving for your customers?

The best solutions explicitly solve a well-defined problem. Ask yourself if all of your customers can describe the problem your team is trying to solve. If the answer is no, then you need to communicate the problem clearly to everyone.

Great BAs clearly define the business problem being solved and communicate it early and often. Everyone needs to be reminded why we are creating the solution. Software development takes time. During that time, it is very easy to forget why we are creating the solution in the first place. This leads to shortcuts, scope creep, and missed expectations. A great BA ensures this never happens. Make it a habit to start your meetings with a quick recap or reminder of the problem we have been tasked to solve.

Do you have empathy for your customers?

Do you really understand the pain they are experiencing due to the problem your team must solve?

Paying customers or people at the ground level who use or support your product every day typically are not consistently involved in a software development project. If a BA truly has empathy for the customers who will be using the completed solution, then the probability of success will skyrocket!

Great BAs take the time to observe and experience the pain of the problem that needs to be solved. Empathy allows a BA to focus on the customer experience within the solution. Deadlines, resource constraints, and scope considerations can contribute to shortcuts that negatively impact the customer experience. Having empathy gives the customers a voice in the development process via the BA.

Do people enjoy coming to your meetings? Are your meetings always fun and productive?

That’s right; I used the words ”fun” and “meeting” in the same sentence!

Great BAs always have an agenda and goals for a meeting clearly communicated.

Great BAs always prepare for their meetings by preparing visuals or determining what facilitation technique is appropriate. You should be using innovative facilitation techniques such as collaborative games to increase the interactivity within your meetings. Do all of your meetings consist of having people sit around a conference table while multitasking on their laptops? If so then they are not fully engaged and participating in your meeting. Don’t be afraid to get people out of their chairs to join you at the whiteboard for a collaborative session.

The BA is uniquely positioned to interact with every customer associated with a new solution. It is this unique position that allows a truly great BA to ensure the project is a smashing success. Great BAs communicate frequently to each role on the team and are able to remind everyone why we are completing the project in the first place.

Congratulations to those of you who can claim they affirmatively answer these questions for every project! You truly are a great BA!

BAs of the 21st Century: Are We Really Business Technologists?

The good news is that business/technology optimization-focused business analysts are beginning to add value to their organizations at the strategic level. Executives now realize that savvy enterprise business analysts are essential to their success.

WE’VE COME A LONG WAY BABY!

Let’s take a look at the how the 21st-century business analysis profession has evolved from a focus on requirements engineering into an essential strategic business practice.

Related Article: The Future is Now: The 21st Century Enterprise Business Analyst

  • Business analysts work at all levels of organizations, including strategic, tactical and operational.
  • Business analysts work in all business and non-profit sectors including insurance, banking, health, financial services, communications, government, IT, retail, entertainment, energy, health care, education, high tech, community revitalization, and many other domains.
  • As executives and managers recognize the value business analysis brings to their organizations, the 21st-century enterprise business analyst is becoming a business-driven strategic player, an integrator, enabler of organizational change, and driver of business success.
  • As a strategist, the enterprise business analyst often serves as an internal consultant – a business relationship manager at the top of the food chain of the BA profession.

WILL THE REAL ENTERPRISE BUSINESS ANALYST PLEASE STAND UP

The understanding of the value of the enterprise business analyst is finally coming into view. However, because there are so many different titles and roles, it is often unclear which players are actually working as enterprise business analysts.

The enterprise business analyst fulfills many strategic roles, essentially putting her finger in the dike for many functions that have been woefully inadequate in organizations today, from business relationship manager to internal strategic change consultant. According to IIBA, titles for business analysis practitioners include not only the project-level business analyst, business systems analyst, systems analyst, requirements engineer, but also the more enterprise-level process analyst, product manager, product owner, enterprise analyst, business architect, management consultant, business intelligence analyst, data scientist, change manager, and more. Indeed, to fulfill the core purpose of business analysis and of IIBA, to unite a community of professionals to create better business outcomes, the enterprise business analyst’s role has evolved over the past few years to become a central strategic position within organizations.

Hass june

Today there is no one job description that sums up the role of the enterprise business analyst. And to make it even more complex, BAs provide support in the way of strategy analysis, problem analysis, competitive analysis, data analysis, and solution alternative analysis to executives, middle managers, project managers, product managers, software developers, and quality assurance professionals. Some say that enterprise BAs relieve “the burden of analysis” that many of these players simply do not have the time, skills, or inclination to conduct. Without this valuable analysis, business decisions are made absent critical information.

THE EMERGENCE OF THE BUSINESS TECHNOLOGIST

Just when we thought we had identified all the possible roles of the BA working at the enterprise level, another has emerged. Suddenly, or not so suddenly, business literature is talking about the role of the Business Technologist. Are you ready to fill this critical role for your organization? It is very much the purview of the enterprise business analysts.

The business technologist fills the void as businesses grow and new needs emerge. As the competitive landscape changes, innovative solutions are needed for organizations to remain viable. World-class technology is the heart and soul of complex businesses today. Businesses are constantly taking another look at where business and technology can come together for even more efficiency and innovation. Enterprise business analysis practices are the way to make sure organizations are always innovating and getting the most out of their supporting and enabling technology. However, IT talent management has not kept up to recruit and develop skilled business/technology optimization experts to conduct this critical work. CIOs are looking at their high performers to become these enterprise, strategic BAs, but not the BAs we have today. As a result, relatively new roles are emerging such as the business technologist, a new more powerful way of talking about the enterprise business analyst.

Successful business technologists need more than pure technical skill: they must know how to solve strategic and operational problems in an integrated way, across multiple technology domains.i
James Kaplan. Principal at McKinsey&Companyii

Hass june2

Business technology (BT) is described as the ever-increasing reliance on information technology by businesses of all types to handle and optimize their businesses.iii James Kaplan defines the business technologist as “an executive or a manager who’s responsible for making sure an enterprise gets the most value from its investments in business technology. It includes not only the CIO and all the CIO’s reports who may be working on issues of technology strategy, or in technology delivery, but also many people in business units, or business functions, who are charged with thinking about what technology investments will create the most business value.”iv

COMBINING DISCIPLINES LEADS TO SUCCESS

The business technologist (as well as the enterprise business analyst) is not a title but a skill set that converges lots of different disciplines such as engineering, architecture, strategy development, operational management, transformational design, project and change management, financial viability analysis, creativity and innovation, and complexity management. Traditional IT and organizational talent management have not sought after or developed individuals with a combination of the skills required of these disciplines. So it is easy to see why the enterprise business analyst working as a business technologist – fulfilling that elusive role that combines many talents and competencies – is emerging as a critical role in the 21st century.

Hass june3

Clearly, one individual cannot embody the diverse skills and competencies required of these disciplines. Therefore, perhaps the most critical skill for the enterprise business analyst/business technologist (EBA/BT) is the ability to bring diverse individuals together to foster creativity, to drive radical collaboration, as the Stanford D-School calls it. BAs transition from project-focused to enterprise work because they become skilled at combining an interconnected set of practices to “…foster the type of integrative, cross-cutting business-technology problem solving that’s required to address the most sophisticated challenges around applying new types of technologies, about addressing new types of business problems, about … creating innovative delivery models to capture opportunities as they arise in the marketplace.”v

Clearly, the business analysis profession needs to step up to the plate to close the gap in business/technology optimization talent, and the EBA/BT is emerging as that transformational role. EBA/BTs are drastically changing the way we manage projects by adopting a more holistic view of change initiatives so that we:

  • Focus on delivery of business value and innovation vs. requirements management,
  • View change initiatives holistically, understanding that critical projects will likely impact the entire business ecosystem of people, process, organizations, rules, data, applications, and technology,
  • Embrace architecture and design to help temper complexity and uncertainty, and
  • Strike a balance between analysis and intuition, and order and disruptive change.

In future articles, we will discuss the business technologist in more depth, other roles of the enterprise business analyst, as well as the business and technical domains within which they do their magic.

 

Becoming a Better Business Technologist, May 2016. McKinsey and Company. Online at http://www.mckinsey.com/business-functions/business-technology/our-insights/becoming-a-better-business-technologist.
ii Mark McDonald, Ph.D., former group vice president and head of research in Gartner Executive Programs http://blogs.gartner.com/mark_mcdonald/2012/01/30/amplifying-the-role-of-the-business-analyst/
iii TechTarget. Online at: http://searchcio.techtarget.com/definition/business-technology-BT
iv Becoming a Better Business Technologist, May 2016. McKinsey and Company. Online at http://www.mckinsey.com/business-functions/business-technology/our-insights/becoming-a-better-business-technologist.
v Becoming a Better Business Technologist, May 2016. McKinsey and Company. Online at http://www.mckinsey.com/business-functions/business-technology/our-insights/becoming-a-better-business-technologist.

6 Audiobooks Every Business Analyst Must Listen To

Let’s say on an average you commute 2 hours everyday (to and from work) – which I do. So, that’s 10 hours a week and roughly 520 hours a year. If an average audiobook is about 8 hours in length, then technically you can listen to 65 books in a year!

Well, practically speaking that might be a lofty goal. You will also have to mix in music, podcasts, reading or just observing strange behaviors of your fellow-commuters. Right?

However, what about a goal of listening to 6 books? Much more achievable, eh?

Related Article: Want to Improve?  Don’t Make Resolutions.   Play Games and Keep Score!

If you have never heard of audiobooks and you always thought listening was for music and radio only, think again!

Your world of learning is about to change!

In this post I will share 6 must-listen audiobooks for business analysis practitioners. Read on to start your audiobooks journey.

The first one of the list …

1. Start With Why – How Great Leaders Inspire Everyone to Take Action

Why are some people and organizations more innovative, more influential, and more profitable than others? Why do some command greater loyalty from customers and employees alike? Even among the successful, why are so few able to repeat their successes over and over? People like Martin Luther King Jr., Steve Jobs, and the Wright Brothers might have little in common, but they all started with why. This book is for anyone who wants to inspire others or who wants to find someone to inspire them.

What’s in it for a Business Analyst?

Learn about the “Golden Circle” and how great companies work from inside out of that circle. Go from “why” to “what” to “how” and apply this in your practice to understand the “why” of a certain area of analysis. This concept could be applied both at macro (strategy) and micro (detailed analysis) levels in an organization.

2. Seven Habits of Highly Effective People

The 7 Habits of Highly Effective People has been a top seller for the simple reason that it ignores trends and pop psychology for proven principles of fairness, integrity, honesty, and human dignity.

What’s in it for a Business Analyst?

This was the first audiobook I listened to, and that’s how I started my audiobooks journey about 15 years ago. There are many things to apply to your business analysis practice, including being proactive and setting goals.

3. Getting Things Done -The Art of Stress-Free Productivity

From core principles to proven tricks, Getting Things Done has the potential to transform the way you work – and the way you experience work. At any level of implementation, David Allen’s entertaining and thought-provoking advice shows you how to pick up the pace without wearing yourself down.

What’s in it for a Business Analyst?

If you want to master the art of getting things done, and take your personal productivity to the next level, this is a must-listen book.

4. How To Win Friends and Influence People

For over 60 years, the rock-solid, time-tested advice in this audiobook has carried thousands of now-famous people up the ladder of success in their business and personal lives.

What’s in it for a Business Analyst?

We deal with people side of analysis on a daily basis. If you want to learn how to form friendships, bonds and build trust with your stakeholders, listening to this book will help you go the extra mile.

5. Linchpin – Are You Indispensable?

Linchpins are the essential building blocks of great organizations. Like the small piece of hardware that keeps a wheel from falling off its axle, they may not be famous but they’re indispensable. And in today’s world, they get the best jobs and the most freedom. Have you ever found a shortcut that others missed? Seen a new way to resolve a conflict? Made a connection with someone others couldn’t reach? Even once? Then you have what it takes to become indispensable, by overcoming the resistance that holds people back.

What’s in it for a Business Analyst?

I am a big champion of Seth’s work. He is one of the inspirations behind my first book and also TheBACoach brand. My key takeaway from this book was that everyone now can be an artist. According to him:

An artist is not just some person who messes around with paint and brushes, an artist is somebody who does “emotional work.””

Work that you put your heart and soul into. Work that matters. Work that you gladly sacrifice all other alternatives for.

Business Analysts are artists of the knowledge work, and this book will help you discover this in various ways.

6. Just Listen – Discover the Secret of Getting Through to Absolutely Anyone

You’ve got a business colleague who’s hostile, a client who’s furious, a staffer who’s deeply cynical—how do you get people to do what you want in tough situations like these? In Just Listen, veteran psychiatrist and business coach Mark Goulston reveals the secret to how to get through to anyone, even when productive communication seems impossible.

What’s in it for a Business Analyst?

From the audiobook page:

Here’s the challenge,” Mark says. “People have their own needs, desires, and agendas. They have secrets they’re hiding from you. And they’re stressed, busy, and often feeling like they’re in over their heads. To cope, they throw up barricades that make it difficult to reach them even when your goals are in sync with their own.” But the good news is that there are simple strategies that can make you compelling, and break down the walls that keep you from getting through to the people you need to buy into your ideas and goals.

Which one of these have you listened to and/or look forward to listen to? Do you have any additional recommendations?

Please use the comment space below to leave your comments, feedback and questions.

Is a Multi-tiered BA Certification Program the Way to Go?

For anyone waiting for the unveiling of the new certification program from International Institute of Business Analysis™ (IIBA®), I have been wondering whether such changes will be helpful for organizations and the practitioner community as a whole.

The one thing I have learned over the years from the community was that the certification process, including how one applies and qualifies for these exams needs to be more straightforward and avoid complexity at all levels. Having been proposed for some time now, we still don’t know enough about the changes being made to the program to form an opinion – or do we?

Here are a few factors I have been thinking about with regards to these changes. I would love to hear what you have been pondering. In this post, I am simply putting the questions out to the community for consideration. I form no opinion, but as a current Certified Business Analysis ProfessionalTM (CBAP®) I am really interested in knowing what other certification holders are thinking.

Related Article: Top 5 Reasons Organizations Should Support Certifications

1. Level 1 – Today knowledge based certificates in business analysis are plentiful as a large number of training providers already offer BA certificates. Will this new Tier 1 certification be a differentiator in the industry? Several years ago IIBA spoke with EEPs about providing a jointly branded BA certificate, and for many really good reasons Endorsed Education Providers (EEPs) did not want IIBA crossing the line into the training space. Has enough changed here? Do employers and practitioners believe Level 1 recognition from IIBA which assesses general BA knowledge (no experience) is more significant than a certificate from an EEP whose sole focus is on training?

2. Level 2 – The market for the Certification of Competency in Business AnalysisTM (CCBA®) has never really taken off, as of today after 5 years, there are only 850 CCBA holders. Are the proposed changes to scenario-based exam questions significant enough here to help IIBA grow this certification or are there other issues with this certification that if addressed would help the viability of the CCBA®?

3. Level 3 – The CBAP® used to be the gold standard, and those of us who acquired the CBAP® felt like we were demonstrating our senior level experience to employers. After all, the CBAP® has always been an experienced based exam. In the early years, many of us struggled to find employers who found the certification as a differentiator or who deemed it mandatory for employment. Over the years some awareness has taken place; although still not as widespread as the PMP.

CBAP® recipients felt the certification demonstrated their commitment to the profession and identified themselves as senior practitioners. With the proposed changes, CBAPs will no longer be the top tier. Are CBAPs ok with this? Do CBAPs feel an urge to run out and spend more time and money to get back on the top tier of the ladder? Anyone feeling like their credential is less attractive or valuable to you, to your employers or to the BA community? On the other hand, are the CBAPs excited about pursuing this next higher level certification?

4. Level 4 – Lastly, the new level geared to thought leaders. It has always been the case that thought leaders are recognized in the community by their contributions. Their credibility is achieved through the engagements they are completing within organizations, with the research they are performing, the articles, books, and other products and services they provide the community at large. If you look today, many very influential, experienced, top-notch thought leaders do not have a credential nor do they need it because they are already well-known in the industry for the work they are doing for all us. I am very curious to hear from the community whether our thought leaders require a certification to be recognized or acknowledged as a thought leader? If organizations are looking for thought leaders to be validated through such a process, is such a model scalable since level 4 will require an assessment?

Lastly, I want to ask about the idea of moving to a competency-based framework for certification. Back in the day when Angela Wick and her team developed the Competency Model, it was and still is an amazing product. The team spent countless hours building a framework to help articulate what skills and competencies define a novice business analyst from an expert business analyst, but it was a tool that must be applied along with a lot of other factors to be able to tell an accurate story of competency.

For example, if you are a business analyst in an organization and are not working on large, complex, transformational projects you may never leverage a lot of the skills in the upper categories of the competency framework. For your organization, for the role you have been hired into, does that make you less competent? What about the business analysts in financial institutions responsible for bringing their clients online with a standardized financial service, where each client is a new project, but the projects have little variation to them? These business analysts become very proficient working in their organization as a business analyst/implementation analyst without needing to leverage many of the top tier skills in the framework. Does this mean they are less valuable or less competent to their organization because their projects are consistent in type and size?

In my opinion, the role of the business analyst is defined by the organization based on a multitude of factors that really can’t be standardized across industries because there are an infinite number of factors that apply. To make an assessment of competency, consultants have to work with the organization to conduct interviews, look at templates, watch processes and practices first hand, and understand the project environment to assess competency within context. Knowing this ‘as-is’ state is very critical before conducting a gap-analysis to assess what competencies are missing. I have performed competency assessments for years in this fashion. My question here for the community is could a 3rd party working outside the walls of your organization assess competency without having this ‘as-is’ picture? Is this approach old school and is this 4 tier approach answering some newer needs organizations have today about the competency of their BA resources?

Lastly, I myself am interested in understanding the research completed to support a 4 tier certification. Typically I have seen a role delineation study conducted to provide the insight to align and structure a product like certification. I am not proposing it has not been done, but simply asking whether anyone knows. Since I don’t know, I am really interested in raising some dialogue in the community to hear your likes/dislikes to the pending 4 tier structure.

Please share your thoughts and provide different perspectives.

Failing for Success

Failing never feels good because, well, it feels like failure. Nobody wants to fail. We are driven to be number 1, top dog and the big winner. Nobody has ever said, “Wow! That’s awesome! You failed!” The black and white checkered flag falls, and the winner is ordained. The fear of failure is so strong and painful that it’s amazing how far we will go to avoid it. Fleeing, running, hiding, or avoiding it all together.

We put ourselves into a make-believe world where no mistakes can be made, and we overwork ourselves to the point of exhaustion all in the name of ‘not failing.’ We keep ourselves deluded in the belief that failure isn’t an option, and we are at a loss on how to handle failure.

Being fearful of failure, we create elaborate plans to avoid it but it happens anyway. Systems, processes and people just don’t operate with 100% accuracy. If everything ran perfectly every time, we certainly wouldn’t need a helpdesk or second level support.

But failure isn’t as evil as we make it out to be. How did you learn to walk? You certainly just didn’t jump to your feet and start running a marathon. It took lots of trial and error to learn how to put one foot in front of the other to propel yourself forward. Even crawling took some trial and error! After we get on our feet, we forget that in order to get there, we fell, toppled, and wobbled our way to success. There wasn’t a surefire way to learn to walk. We had to fail in order to learn.

Related Article: Avoid These Phrases – Or Your Project Will Fail

Experimental learning has taught us that failure is the best way to learn. Remember back to the days you first started to learn something new like riding a bike. You didn’t do it perfectly the first time and probably fell a few times. Someone was there to pick you up off the ground and put you back on the bike. You learned by failure – that leaning too far one way or another will cause you to fall off the bike.

The last thing I learned was my home thermostat. It connects to the internet and allows me to control the temperature and fan from anywhere. After successfully setting up the thermostat, I started to play around with it. I failed multiple times trying to figure out some of the features. At one point I simply wiped it clean and started over. In learning how to fix the things, I also figured out some cool new ways I could save energy and use it better. I experimented, failed, and learned.

An interesting experiment was performed by Ryan Babineaux and John Krumboltz a few years ago for the book “Fail Fast, Fail Often”. This experiment was simple. A group of students was divided into 2 groups. The first group was told, “You have 90 days to create was many clay pots as you can.” This first group or “Volume Group” was told to focus on volume and forget about quality. The other group was told, “You need to make one perfect clay pot.” The second group was the “Quality Group” and was focused entirely on quality and avoided any kind of volume. Both teams were told they were in a contest to see who could make the best looking and functional clay pot.

You would expect that the group focused entirely on the quality of clay pot would have the most well-designed pot because they were entirely focused on the design. Since the volume group was focused so heavily on just making pot after pot, odds are none of their pots would be that well designed.

At the end of the 90 days, both teams put all their pots out for judgment by a panel of clay pot artists and experts. I’m don’t know who these people are, but I will say they have one incredible niche job for judging just clay pottery. Can you even make money at that?

The surprising result was that the volume team that just made as many clay pots as they could won the competition. How is that even possible? Why did volume win out over quality?

The quality team has so focused on quality and creating the perfect design that they didn’t take any time to experiment or play with the clay. The volume team, on the other hand, interacted with the clay constantly. The first few clay pots produced by the volume team were damn ugly, but they continued to play and experiment. The volume team while trying to achieve a greater volume of clay pots actually learned more about creating clay pots and were more comfortable with the clay. So even though the volume team had a lot of failures, they succeeded and won.

Failure can make you stronger and more agile if you choose to learn from it. “That didn’t work – let’s try something different” attitude. This is the whole concept around failing fast. The faster you fail, the more you learn from that failure. Don’t fail just once, fail multiple times.

Failing safe is about creating an environment where experimentation and learning do not cause injury to yourself or your organization. Like in the experiment, an environment needs to be created in which experimentation can occur with wild abandon safely. No one was harmed in the making of clay pottery.

In the technology world, we use the term “prototyping”. Many prototyping situations in technology are severely limited. The environment is too confined or restrained for experimentation, and often very few failures occur to learn from. A better safe environment in on that this not restricted and open for experimentation.

Playing and changing everything in a production environment where your customer experiences your experiments has a tendency to make your customers unhappy. Build an environment where you can play without consequence. You may have to start over from scratch and rebuild the environment after a wild night of experimentation. Plan on creating a way to rebuild your safe environment quickly so that experimentation isn’t slowed down.

Create other safe and soft landing environments where you can bounce your ideas of others. Maybe your environment isn’t about a physical space or system but a room filled with flip charts and whiteboards.

Pulling together a group of colleagues to idea share, collaborate and innovate creates a safe environment as long as ground rules and expectations are set ahead of time. Set the expectations that experimenting and innovating is the goal. The more ideas, the better. We are not driving for perfection. It’s like a brainstorming meeting on steroids. Encourage crazy ideas and actually try it out. There are no judgments and the wildest crazy ideas are always welcomed.

Another tactic is to experiment with screen or report design by having multiple variations mocked up. The key is not just to focus on one mockup but to have many mockups. This allows the group to “riff” off each other by taking elements of different mockups and combining them together in new exciting ways.

One of my favorite tactics is user experience development and testing space. User experience folks will tell you it’s a preferred tactic to have users just play with your interface (screen or report) and watch how they use it. Gather a group and invite them to play or experiment with a design. The designers in the room are silently watching actual users interact with their design. The designers learn from watching the group play and experiment with the design. Designers then change the interface based on their observations. Rinse and repeat. One session is usually not enough. They key here is not to tell the user how to use the interface but to let them play and experiment freely in a safe environment.

A badass professional can open themselves up to new experiences so they can learn. They understand that failure can happen and work to create safe environments in which to play and experiment. Our culture needs to change the way we see failure. We must start seeing failure as an opportunity to innovate and not as something bad.

To succeed without learning is a failure. There are many instances in my life where I have executed a task perfectly the first time only to fail the second time miserably. Beginners luck can be a curse because you miss the opportunity to learn from failure. Only through failing do we truly learn.

A badass professional is reflective in their failure but not to the point of obsession. Look back and determine if there was a lesson to be learned. What went well? What didn’t go so well? What still baffles me? What if I did something different instead? Then get up off the warm fuzzy safe pillow in your safe environment and try it again. Remember you didn’t learn to walk without falling first.

Take the example of switching jobs. You prepare that killer resume and get in the door for an interview. You did your homework on the company and prepared yourself for the usual interview questions. It seems like everything went well but you didn’t get the job. Learning from failure requires being reflective or thinking about it. This shouldn’t be an all-day marathon conversation going around in your head. Jot down a few things you thought you could do better. Follow-up and get some feedback from the interviewer if you can or a colleague on interviewing better. You failed to get the job, but you succeeded in learning how to do it better next time.

Let’s build a strategy together on how to help your organization fail in a safely and fail faster so they can learn and drive innovative new solutions and approaches.