Skip to main content

Tag: Strategic

Business Process Changes During a Pandemic

What a difference a couple of months can make! I visited a doctor’s office in early March to treat a broken finger before the covid-19 shutdowns had begun across America.

Like any other clinic, no one wore masks. There were no social distancing measures in place. My doctor extended his hand to shake mine (I gave him an elbow bump in return). There was hand sanitizer available, but that had been the practice over several years of flu outbreaks.

Fast forward two months and consider a follow-up appointment of mine in mid-May. Walking into the clinic was comforting because all the staff and other patients had masks on (but also a little disconcerting). Extensive signage told us the rules, such as waiting in line 6 feet apart. Several chairs in the waiting area were blocked off to enforce social distancing. There were boxes for sanitized and for “used” pens to reduce the spread of germs.

Another change from March was the presence of a “scribe” to assist the doctor with recording notes and observations. This procedure is still relatively new to medicine and may or may not have been precipitated by the pandemic. Still, it was a noticeable change from March, and given my love of process, I even mentioned it to the two of them. My non-expert view is it may reduce the spread of germs since the doctor does not need to handle a computer during a visit.

By now you may be wondering what this has to do with process change. Consider the following five categories for any business which must interact in person with its customers, whether or not they may be ill.

1. Increased risk and liability.

When governmental shutdowns and sheltering in place began, medical facilities closed too. My original follow-up appointment in April was cancelled because of the shutdown. Running a business during a pandemic increases the risk that customers and employees may infect others or may become infected themselves. Visiting or working at a business during a pandemic, whether a clinic or grocery store or gas station, involves some risk.

But what about a medical clinic or emergency room in which a visit is not exactly optional? If an establishment is lax in their procedures or can be shown to be negligent in protecting patients, then a lawsuit may be the result. In short, heightened risks during a pandemic are strong incentives for strengthening business processes to avoid liability.

2. Procedure complications.

The clinic I attended in May had some visible procedure changes and I am sure there were many I could not observe. The physical space was altered with extensive signage and floor markings to encourage social distancing. Simple procedures to provide “clean” and “used” pens for patient safety were small but thoughtful (and appreciated) steps added to the clinic’s daily routine. When I had an x-ray in March for my finger, they simply plopped my hand down on the machine. Two months later a staff person was there to sanitize the surface for my x-ray and undoubtedly before the next patient. Those were just some of the noticeable changes. I am sure the clinic, like airlines, drug stores, or post offices to name a few, must perform additional cleaning and sanitizing not needed pre-pandemic.


Advertisement

3. Increased communications.

Before my visit I received numerous texts and emails explaining what to expect and what was required during my visit. Most of the messaging pertained to wearing masks and distancing which was not done two months ago. It was comforting to me as the customer to get this communication during the pandemic.

My wife and I recently had some electrical work done at our house. The electrician’s company also sent out several texts and emails about their procedures for protecting us and our house from possible germs. We appreciated that and called to clarify one point.

Setting up the communications for the clinic and the electrician may have been a one-time event, but I am sure it still took many hours to perform. As conditions change, so will the communications need to be altered. Having developed and overseen a great deal of customer communication in my career, I know it is a regular part of business. However, having an external trigger like a pandemic represents opportunity costs and delays other kinds of productive work.

4. Added expense.

The additional processes and procedures mentioned earlier will increase the expense of the business who must perform them. Unless an organization has excess capacity in its workforce, they either need to pay overtime or hire additional employees or contract laborers to do the cleaning and sanitizing. Adding scribes in a clinic to help control germs is an added expense.

The supplies needed to operate in a pandemic also increase expenses. Our local grocery store has added plastic barriers in addition to supplying employees with protective masks and sanitizing supplies. They spray and disinfect the check-out lanes between each customer, adding to their expense.

5. Reduced revenue and profits.

With an increase in cost and potentially a decrease in revenue, profits are bound to decrease. Some examples include:

  • Reduced number of patient appointments in a medical clinic to maintain distancing.
  • A national warehouse store we shop at limits the number of customers in their store at any one time to minimize spreading of infections. They still have a steady stream of people waiting to get in, having waited in line with scores of others 45 minutes to access the store recently.
  • Training companies like ours will need to limit attendees to in-person classes to allow proper distancing or will be forced to conduct virtual-only classes.

Any business that limits the number of customers for safety reasons will expect a decrease in revenue. That can be mitigated by online sales for retailers or training companies, but some organizations like chiropractors, beauty parlors, or barbershops cannot replicate what they do in an online fashion. Along with an increase in expenses, profits will decrease which in turn will cause other detrimental effects such as layoffs or closures.

A pandemic is a pressing and urgent stimulus for many process changes. Some of the changes will likely disappear in time, such as mask wearing and social distancing. Other changes like increased sanitizing and safety-related communications may be permanent. Organizations hope, of course, that reduced income and profits are temporary and will need to adjust their operations accordingly. You might say there is never a dull moment in process work, but then again, I am a process nerd!

4 key activities for a Business Analyst in the Alpha phase

On one of my earlier blogs, I described what I thought are the 3 key activities a BA should be doing when they were in a Discovery phase of a project.

The feedback I received was positive so I thought I’d give, what I consider to be are the 4 key activities are for a BA in an Alpha phase.

So what exactly is an ‘Alpha’?

In the UK, the Government Digital Service (GDS) defines the phases in an Agile delivery lifecycle as; Discovery, Alpha, Beta, Live and Retiring the service. GDS also cover in detail how the Alpha phase works, but what’s not covered in the article is what each role in a delivery team does within an Alpha, including Business Analysts.

If you’re not familiar with the names of these phases, they are the same for pretty much all Agile project delivery. The most common themes I’ve come across are;

  • Concept, inception, iteration, release, production, retirement

Moving Discovery outputs in to an Alpha

Key outputs from the Discovery the BA should have been heavily involved in include:

  • Stakeholder analysis
  • Understanding and defining the problem
  • Starting the product backlog

Each of these outputs now need to be taken through in to Alpha by the BA and here’s how.


Advertisement

Stakeholder analysis – Use your stakeholder knowledge

An Alpha to me is the exciting part of the Agile delivery lifecycle as this is where you actually start putting ideas and concepts in front of users and you learn ‘how’ they will really interact with your product and get valuable feedback. To ensure you get as honest and realistic feedback as possible, it’s important to try and create as real-life scenarios as possible to test the prototype with users. To do this, the BA should use their knowledge of working with stakeholders in Discovery and take this in to the development of the prototype with the designers on the team. After all, if you were the BA involved in Discovery, one of your key outputs is understanding the users and their needs, and that includes the needs of the business. Therefore, armed with this insightful knowledge, you should work closely with the design team to ensure they also understand the users. 

Understanding and defining the problem – Keeping the product vision in view

During Discovery, the team will have (or certainly should have) defined the problem that needs to be fixed and from that, a product vision should also have been defined. Roman Pichler has an excellent article on how to create a compelling product vision which I highly recommend you read as well as all the other articles he has on his website. 

For me, the product vision is one of, if not the key outputs from Discovery and is something that should be visible and referred all the way through the delivery lifecycle. All too often I’ve seen the product vision put up on the team wall (or worse, in a folder on the Product Owners laptop) but no one seems to take any notice of it and it becomes just a part of the wall space along with user research findings, sprint boards, etc. To make sure the product vision stays in view, and you have wall space, have it beside your user story map (coming up in the next section). Pretty much everything that’s in your user story map should stem from the product vision, so keep them close together.

Starting the product backlog – Make sure prototypes stem from user needs (building your user story map)

How prototypes are developed is different for all teams but in my view, the quicker you get to an interactive prototype, the better. I’m all for sketching out designs to protect costs and save time, but only once a prototype is in the hands of users and seeing their interactions with it, will you start to get valuable (and workable) insights to develop the prototype further. And remember, as the BA, you’re going to start building the product backlog based on the findings and create your user story map. If you’re even half serious about being a Business Analyst, I don’t need to tell you the powerful impact of user story mapping but if you need reminding, here’s Jeff Paton (the guy who came up with the idea of user story mapping) showing you how to create one. 

Help the team design iteratively

Having your user story map on the team wall (or online if you are a in several locations. I recommend www.storiesonboard.com as a user story mapping tool) is a great way to galvanise the team and ensure what you’re doing aligns with the product vision (hence having the vision next to the map). As we know, agile delivery focuses on building products in an iterative way and this principle should apply to designing prototypes in Alpha. I quite often see designers go off and start building complex, end to end user journey. For this very reason, having a user story map will encourage the design team to not think too far ahead. After all, your map will have an ‘MVP’ (or Release 1 if you’re not comfortable with the term MVP) swim-lane where you’ll define as a team what features will (or might) go in the MVP and this is what the design team should be focusing on prototyping.

And finally…

Don’t misunderstand me, and this is based on the feedback from my ‘BA in a Discover’ blog, these are not the only 3 activities a BA will carry out in an Alpha and you will no doubt carry out more than this (e.g. writing the user stories for Beta, working with technical architects/software developers to ensure what is being designed and tested with users can actually be built, continually developing the backlog, etc) however I’ve seen projects where the BAs have not been involved much in the design process and this which has led to problems further down the delivery process. Remember, you as the BA are the bridge between the design team and the developers/testers!!

An Alpha (or iteration) phase can last several weeks and if you as the BA follow these activities, you’ll ensure the product is designed with the users in mind, in an iterative way, and that when you get to the Beta phase (blog coming soon), your product will be delivering the value defined by the product vision.

What is obvious to “You” may not seem obvious to “Me”

How often do we pause and think about a casual conversation we have had with a friend, coworker or even a family member?

How often do we think that a quick text/email/phone call could have resolved a problem instantly?

Recently, I had a conversation with a staff member from my children’s school to check if I could view the accounts details for both my kids on their website via a single login ID. Apparently, it was a possibility and I was informed that the school had linked both the kids accounts on their end, so I was good to go. After multiple attempts, I was still not able to see my second child’s account on their website and was reassured by the school that everything was set up as expected.

So, did my problem ever get resolved? Yes! There was a link on the website – “Change Student” that was not at all obvious and perhaps the reason why my attention was not driven there. I selected the link and bingo, there was my second child’s account and finally I can now view all the details via a single login ID.

How is this related to the Business Analysis world we live in?

1. Communicate, communicate and communicate:

Many times, as a business analyst we tend to make assumptions about the knowledge level of our end users. What may seem “obvious” to us may not necessarily translate as “obvious” to them. In the example above, had I been informed there is a link I am supposed to click to toggle between the two accounts, there would not have been so many follow ups. As a business analyst, communication is a key skill and we should always look for ways to ensure that everyone receives the same message and is exiting from meetings with the same understanding.


Advertisement

2. Keep the customer in mind always:

While designing an application, the end user’s lens should be the top priority, ultimately the system is designed to aid them. Going back to my scenario, had the option to “Change Student” been displayed in a more prominent spot on the website, it would have been an easy find. While designing an application, it is significant to step in the shoes of an end user and as a business analyst, it is our job to ensure there are no gaps between what is required vs what is delivered to the end user.

3. Track “trivial” details:

As a business analyst, during requirements elicitation, if an end user has expressed his/her desire “not” have a specific option displayed at a certain spot in the application, then we should try to understand the reasoning behind it and note them down. Another key thing to keep in mind is, to document all the acronyms or abbreviations, especially the ones that are commonly referenced within the organization.

4. Feedback:

Ensure to receive periodic feedback from the end users – what works vs what does not work? This would make them feel that their needs are being heard and their input is appreciated. Implement their feedback in the next release of the application or at least at a minimum, let them know as to why their suggestion was not rolled out.

In conclusion, always keep the customer in mind and never “assume” we all have the same level of knowledge and understanding. Doing everything in your power and capability to get everyone on the same page is one of the key mantras for the successful implementation of a project.

AI and the Digital BA—What’ It All About? Part 2

This is the second of a two-part article written with answers to some of the most frequently-asked questions I get about artificial intelligence (AI).

In part 1 I addressed some common terms and issues relating to AI as it is used in a business rather than technical context. In this article I will focus on the various roles the BA plays to help organizations with their AI initiatives. As with the last article, I will use a Question and Answer format.

Quick Review of Part 1

What is AI?

AI is an umbrella term that encompasses all digital technologies, like machine learning and predictive analytics, which are used to make predictions and recommendations using massive amounts of data. In short, it’s machines doing human tasks that range from simple to complex.

What is a digital business analyst (BA)?

A digital BA is a trusted advisor who helps organizations with their AI strategies. Rather than developing the strategies, they provide their advice about impacts to and value of AI initiatives.

What skills does a digital BA need?

The skills don’t change, but the subject matter is incredibly complex.

How successful are most companies with their AI efforts?

Not very. Most AI initiatives totally miss the mark and result in all kinds of issues, not the least of which is financial. A recent Forbes article details some of the resulting issues.[i]

What is digital fluency?

Digital fluency is defined as “The ability to interpret information, discover meaning, design content, construct knowledge, and communicate ideas in a digitally connected world.” [ii]

Part 2

What is the role of the BA on digital projects?

A digital BA can be involved in many aspects of an AI initiative. Some of the roles that a BA may play include one, several, or all of these:

    • Strategic BA. In this role BAs help organizations determine the value and direction of the AI effort. Some of the specific outputs can include:
      • Business case on the value of the AI initiative
      • Recommendation(s) on the best strategic approach to the AI initiative
      • High-level implementation plan
      • Pitfalls to avoid
      • First look at state of the data to be used
      • High-level governance plan

Advertisement

  • AI coordinator who implements the AI strategies. In this role the BA coordinates AI initiatives across project and portfolios.
  • BA on a project(s) that is part of the AI initiative. Although this role is similar to any BA role, there are some differences. The BA will need at least working knowledge of, if not expertise in, AI.
  • Business data analyst. In this capacity the BA may
    • Analyze the current data to determine how much is useable, how much needs to be cleansed, and how much needs to be collected
    • Recommend an approach to cleansing the dirty data
    • Help determine the data needed for predictive analysis and other AI functions
    • Interpret statistical analysis resulting from AI functions
    • Be an AI translator to facilitate communications between the data scientist and the business stakeholders.

What’s the difference between a data scientist, data analyst, and BA who works a lot with data?

These 3 roles can be confusing. At first glance we might not recognize differences or understand why the distinctions are important, but they are. I discussed the possible roles of the BA above, so here is a brief description of the other two.

Let’s take the easy one first—the data scientist. Not that the role is easy, it’s just easier to explain why this one is different from the other two. The data scientist is the most technical and needs the most expertise. About three-fourths have master’s degrees in mathematics and statistical analysis. Over half have Ph.Ds.

Data scientists create the predictive models. They determine what the machines need to do in order to meet the business objectives. They decide which algorithms are best given the objective of the AI initiative so that the machines can be trained to learn. Having said that, unless there is good governance and substantial input from business stakeholders and decision-makers, those algorithms have the potential to be created with built-in biases. Likewise, they may not be the best ones to solve the business problem.

The data analyst. This is really a subset of the BA role. I described some of the high-level functions above. On AI projects it’s necessary to focus on the data because it’s so integral to the success of the effort. Machines learn based on historical data. Issues like dirty and redundant data, as well as ownership of the data aren’t easy and require a strong facilitator and influencer to resolve. This data analyst role is such an important role that IIBA has created a new certification—the certification in business data analysis (CBDA).

What are some of the business and technical pitfalls that the digital BA should be aware of?

Here are some of the big ones:

Strategic

  • Beginning with AI as a solution without a defined problem
  • No real AI strategy
  • Unrealistic expectations of what AI can do for the organization

Data and technology

  • Dirty data
  • Business processes don’t support the technology
  • Weak security

Organizational and communications pitfalls

  • Siloed and cumbersome business architectures
  • Inflexible organizational structures
  • The data scientists create the business rules
  • The data scientists talk directly to the business and the business does not understand
  • Confusing roles on AI projects
  • Built-in biases in the algorithms

In Part 3 of this article, we will explore other aspects of how BAs can help organizations get the most value from their AI initiatives. Some of the topics we will cover include the need for governance on AI efforts, the recognition of the importance of the AI translator role, the digital PM, and more. 

[i] https://www.forbes.com/sites/insights-kpmg/2019/12/10/data-governance-is-risk-number-one/?utm_source=TWITTER&utm_medium=social&utm_content=2937780067&utm_campaign=sprinklrForbesMainTwitter#90dd59b91c81

[ii] https://www.slideshare.net/RobinAshford/guiding-learners-toward-digital-fluency

4 Business Analyst Interview Questions and Answers to Kickstart Your Career

If you’re just starting your career as a Business Analyst (BA),

knowing the usual types of interview questions can help you prepare to impress your potential employers. 

After all, knowing the possible interview questions will help you prepare the right answers that will make you stand out from other candidates who are vying for the same position.

Although the requirements for Business Analyst positions vary depending on the company, there are a set of common questions that you’re most likely to hear in every interview. 

These questions could range from a simple “Why a career in Business Analysis?” to more in-depth queries, like the kind of tools you use, so the more familiar you are with these questions, the better equipped you’ll be to ace your interviews. 

To aid you on how to do just that, here are four Business Analyst interview questions and possible answers to help you prepare to leave a positive impression on your prospective companies. 

Question 1. What is the role of a Business Analyst in a company?

As a business analyst, you play a crucial role in guiding businesses to improve their products, services, software, and processes through data analysis. 

Plus, you can bridge the gap between IT and your employers to help boost efficiency and translate data into useful and actionable insights. 

As such, you’ll need to emphasize the specific roles of business analysts. If you have experience in the field, discuss some of your previous functions with your interviewers. 

BATimes Nov07 01

Here are some of the things you can consider to help you discuss the roles of a BA. 

  • Business analysts can take on specific roles within a company project such as System Analyst, Application Designer, Business Planner, Technical Architect, Data Analyst, etc. 

If you’ve played these specific roles in the past, expound on what you did and the solutions you came up with. 

  • The job of a BA will vary based on the requirements of your potential employer – some BA roles may be limited to IT projects, with a few extending to marketing, accounting, finance, and more. 
  • Your primary role as a BA is to help determine the needs of your company, uncover the problems – including using predictive technology to predict future issues (to some extent) – and come up with business solutions.   
  • Aside from technical skills, your role as a BA will require you to have a good grasp on engineering concepts, possess leadership qualities, and excellent communication skills. 

Question 2. What are the crucial tools for Business Analysis?

There is a wide array of tools and software that business analysts use to perform several functions required of the role. 

With that said, interviewers will ask you what the crucial tools are for business analysis so they’ll know which ones you’re proficient in and what you can bring to their company.   

If you are proficient with tools like MS Office, Structured Query Language (SQL), Blueprint, programming languages such as Python and R, Tableau, and more, bring them up during the interview. 

Most interviewers will also ask you outrightly about the tools and the training you are certified in, but instead of going through the whole list, bring to focus a few of your most recent ones. 

For instance, if you have undergone a CBAP certification training course, then discuss how it has enhanced your skills and how you can apply it to your prospective company.

BATimes Nov07 02

Doing so helps give your potential employers an idea about your skills and proficiency, and whether or not you already have what they need or if they need to train you for specific tools. 


Advertisement

Question 3. How do you handle difficult stakeholders?

Remember that being a Business Analyst means coming up with solutions, but you’ll also need to prepare for the possibility when your proposed solutions are met with resistance. 

Many factors can contribute to this, but among the rest, human factors like – difficult stakeholders – might be one of the most challenging to handle. 

Your potential employers will want to know how you can manage this type of situation since it is bound to happen in every company.  

You won’t need to provide an entire outline of your answers during your actual interview, but keep these few points in mind when formulating your possible responses. 

  • Spot your “difficult” stakeholders from the group, listen to what they have to say, and exercise a significant amount of patience.  

If you cut them off or be impolite towards them, it will only lead to misunderstandings, and that will not help you resolve any of your issues. 

  • Some stakeholders are difficult because they are not comfortable with some of the things in your project. So take the time to dig deeper into their issues by listening to what they say and answering any questions they might have.
  • As much as possible, meet and discuss with your difficult stakeholders personally as a way of showing them that you are committed to working towards the same goal with them. 
  • Continuously engaging your difficult stakeholders helps them understand that their contribution is valuable to your project. Their resistance could also stem from valid points of view, so it’s crucial that you don’t just dismiss their opinions.  

Keep in mind that there are no perfect answers, but being prepared for possible questions like this will always help you have concrete responses.

Question 4.  Do you have any questions for me? 

Asking tons of questions comes with the job of being a Business Analyst, and one of the best places to demonstrate your ability to ask relevant and insightful questions is during your interview. 

This part of the interview that you can turn into a conversation by asking questions about the company, its processes, and more.

Aside from demonstrating your abilities, asking relevant questions also shows your potential employers your interest in their company, which can only help increase your chances of getting the job.   

BATimes Nov07 03

Here are a few questions that you can ask your interviewers. 

  • How does your company handle systems analysis, and do you have a dedicated systems analyst?” 

There are companies with job postings for BAs when what they really want is a Systems Analyst/BA, so it’s best to clarify this ahead if this is not the type of role you would like to fulfill. 

  • Which project phases are your BAs involved with?”

If your interviewer says that business analysts are only involved in requirements, then the company might be looking for a Requirement Analyst specialist. 

This might not suit you if you want to perform a deeper and wider BA role, so you should get this out of the way during the interview. 

  • Does your company have a central BA team, or does each function have its own BA team?”  

Asking this question will help you determine whether or not there is a central team that will allow the pooling of knowledge. 

Bottomline

There might not be perfect answers to your business analyst interview questions, but being prepared by learning the possible responses will help equip you for the big day. 

Remember that being a business analyst means solving problems, and your interview Q&A is the first obstacle you need to overcome in a long list of challenges coming your way in a BA career. 

Also Read: Business Analyst Manager Interview Questions

Did you learn something from this post? Please share this with your network if you agree. Cheers!