Skip to main content

Tag: Planning

It’s Time to Put Genuine Care for People and Empathy Back into Business Analysis

I recently accepted a new business analysis position because too many days were filled of dread for work.

I couldn’t figure out the reason for my boredom and lack of fulfillment, until one day, it dawned on me. 

I missed people. 

I know that sounds silly – in business analysis you are often surrounded by people in meetings or requirement elicitation sessions with stakeholders. Even though I worked with a great team of people each day, I took too many calls rather than sitting face-to-face, collaborating in meetings. I often didn’t have the time to really get to know the stakeholder and feared key requirements and details were missing because of this lack of relationship between me and other team members. 

If my children, friends or family members came to me only when they needed something – I would be resentful and our relationship would suffer. Work shouldn’t be any different. Whether it’s the developer who will be building the user story you wrote on the website, the QA tester trying to break the new feature or the marketing manager with the vision for the functionality, the more we become real people to one another, the better. I’m not saying we need to sit and chat all day or learn each other’s deep dark secrets, but having a genuine interest in getting to know your team members can be invaluable. 


Advertisement

You don’t have to be a manager to ask how someone’s day is going or how things are going. I believe it’s all of our responsibility to do whatever we can to make sure the team is rowing in the same direction. At the first marketing company I worked at, we grew extremely fast. The two owners of the company tried as hard as possible to usher us through the transition but also needed to focus on sales to keep the company thriving. 

At only 26-years-old, without a lick of management experience, I went desk to desk at least 1-2 times per month to a staff of almost 50 and asked people how they were doing. “How’s life?” I’d say. At first, people were thrown back by the question, something to this day still puts a tear in my eye. People often commented I was the only one who ever asked them that question and soon opened up and told me about troubles at work or funny stories about their kids. I would then see if there was anything within my control to help the troubles they mentioned in terms of workflow, process or communication. If they needed someone to help go to bat for them with management, I would help facilitate the tough discussions. I also remembered the details about my co-workers lives because I truly care about them as people. 

A developer once confided in me I was the only business analyst or project manager who made them feel like a person and not just an employee hired to just write code as fast as possible. I’ve dined with wealthy business executives that I needed requirements and ideas from accustomed to small talk and everyone agreeing with everything he or she said. I’ll tell you, it seemed at times I was one of few to really talk to them like a person and even – gasp – not just nod my head in politeness. I know, deep down, my candor (though oftentimes even a little more reserved than I would like) led to better project requirements and follow-on business. 

I once worked for a company called Sherpa CRM, a content relationship management tool for senior living. Each day, sales counselors would use Sherpa not only to gather information about prospective residents, but to learn about the senior citizen’s reason for staying in their homes – hopes, fears and hesitations. A psychology exists behind every interaction in business, big or small. My time at Sherpa taught me the difference between sympathy and empathy and how being able to truly put yourselves in someone’s shoes can be invaluable no matter your career path. 

At the end of the day, people are people, and the more we start treating each other that way, the happier we all will be.

Why is Data so Important for Leaders?

The rise of digitisation has had a huge impact upon all industries and organisations and big data is at the forefront of this digital transformation.

Organisations and their leaders now have access to valuable insights into their business, customers, competitors and marketplace, allowing them to make strategic, data-driven business decisions. But why is data so important for leaders and how can it transform their role in an organisation?

‘As data and analytics become pervasive, the ability to communicate in this language, to become data literate, is the new organisational readiness factor’ Carlie J.Idione – Gartner Research

Streamlining the customer experience

Emerging technologies such as Artificial Intelligence (AI) are allowing leaders and businesses to automate certain work processes such as customer service. This not only allows for additional resources to be allocated to strategic business decisions, but it collects valuable data and trends from customer feedback that in turn improves the customer experience. Whilst most organisations will already have a strong idea of their target audience and demographic, it’s important not to stand still and constantly develop innovative products and services for the ‘new wave’ of consumers. A great example of this is Spotify, who used AI to sort through customer data and highlighted the most unique customer trends around the world, simultaneously humanising consumer data and creating a lucrative global marketing campaign.


Advertisement

Strategic Decision Making

Algorithms and real-time predictive data are enabling leaders to make better-informed decisions. These decisions are made on a basis of tangible data and trends resulting in less guesswork and increased accuracy. Predicting future industry trends can put an organisation ahead of the curve, spotting potentially lucrative business opportunities before their competitors. By analysing these trends, organisations can create products and services based on consumer need and desire, rather than ‘educated’ guesswork.

Shaping stronger leaders

A successful leader in the digital era should have a strong analytics aptitude and demonstrate logical thinking and verbal and quantitative reasoning. Rather than resting on their laurels they should always be looking for the next business opportunity and data-driven technologies can make this job significantly easier. Rather than being motivated by emerging technologies, strong leaders and analysts should be motivated on solving problems using well analysed data and algorithms. Leading a business through this era of digital transformation takes a unique set of skills, which can be developed through courses such as a Master of Business Administration.

The Future of Business Analysis

We are in an era of rapid technological and digital transformation, and modern businesses are adapting in line with this.

Organisations are now dependent on business analysts and project managers to guide them through this digital disruption and advise on best practice and emerging technologies. Predictive technologies such as machine learning, Artificial Intelligence and The Internet of Things can now provide industry trends and data patterns that have the power to significantly impact a business and its operations.

Digital Transformation

There are several different challenges that come with rapid digital transformation. Ensuring that organisations are readily prepared and have skilled specialists such as data scientists in place is essential. Having the appropriate software tools to analyse, manage and cleanse large amounts of data is key to staying competitive in the current digital climate. Organisations will need to make strategic business decisions that can be used as rules in machine learning and making the wrong decision can be catastrophic. The role of a business analyst in 2019 will become increasingly digital- focused.


Advertisement

Becoming Agile 

Agile is a project management methodology that is defined by the Association of Project Management (APM) as ‘an approach based on delivering requirements iteratively and incrementally throughout the project life cycle. At the core of agile is the requirement to exhibit central values and behaviours of trust, flexibility, empowerment and collaboration.’ As organisations are becoming more and more agile, the demand for business analysts to work on agile projects is set to increase. Adopting agile practice such as facilitating change, clear communication and engagement will be necessary for business analysts to effectively contribute.

What’s next?

According to the 2018 report, ‘The Future of Jobs’, reskilling will be imperative for the future workforce. By 2022, more than half of the working population, 54%, will need significant reskilling and upskilling. A commitment to continual learning and further education is imperative for business analysts that want to remain competitive and progress in their careers. The report also outlined that by 2022, 85% of companies will have adopted user and entity big data analytics, meaning that the role of a business analyst will transform in line with the change.
Increased demand for soft skills such as communication and critical thinking in the industry will become more prevalent. Although the future looks bright for the industry as by 2020, the number of job profiles for all US business analysts is set to increase from 364,000 openings to 2,720,000 as indicated by IBM.

Requirement Analysis for E-commerce Projects

E-Commerce – A platform that has revolutionized the way we shop.

From clothing merchandize to grocery items, almost all our daily requirements are now met by such platforms. Such an application plays a crucial role in many businesses these days. 

For an e-commerce project, the main business requirement is the same – A user comes to the platform and purchases products. The challenge for a business analyst is to visualize all the processes in between. The scope of an e-commerce application is large. At the micro level, the requirements can vary depending on the nature of the products being sold. At the macro level, a business analyst can make an outline of the following requirements – business and functional that hold true for a majority e-commerce platforms. A checklist can include the following pointers:

1. User actions on the website

What all actions can a user perform on the website besides making a purchase? These include:

  • Searching for products on the home page or throughout the website and on what basis. Products can be searched on the basis of product name, categories, brands etc.
  • Sorting products based on the filters provided. Which filters need to be placed? For clothes these can be colours, sizes and types. For grocery these can be fruits, vegetables, frozen foods and dairy products. For health insurance products these can be age group, premium limit, waiting period, maternity cover etc.
  • Adding products to a wish-list. If these products can indefinitely remain in the wish list till their respective stocks last or can remain for a definite period of time.
  • Making use of available promotional offers and discounts and the business logics behind them.
  • Creating an account. Is an account mandatory for making a purchase? Is buying as a guest user an option?

2. Admin Console

This is an important module of any e-commerce application. A business analyst should clearly determine the aspects that an admin can control from the backend. These include:

  • Product Management – All the metadata of the products – Product images, description, seller information, prices etc. Admin should be able to manage this data i.e. add, remove and edit a product.
  • Content management – The design aspect of the website i.e. the static pages a user sees at the front end. It’s important to create an attractive and effective website to attract and retain traffic. The answers that a business analyst should seek here are – How will these pages be maintained? Will these pages be uploaded or a provision has to be made for the admin user such that pages are created through the system?
  • Master Management – Besides the product data, there are other masters that need to be managed at the back end. Country, State and city masters, seller masters etc. are just a few examples. For instance pin code masters help in extracting a city when the user enters the pin code while adding the shipping address.
  • Admin should be able to carry out promotional activities. Admin user should be able to create promo codes and offers as per the business requirements. 

3. Inventory and logistics Management and Order Fulfilment

Remember how we add some products to our wish lists and when it’s time to buy them, some of the products go out of stock. Or the time when a sale is announced at mid-night but you log in early morning only to see that the products in sale were brought overnight. We have all been through such times. At the backend, this management is crucial to keep the website up to date with the latest numbers. Whether new products are added, products are returned or exchanged, dispatched, all the logistics and stock details should be maintained in a robust system. Additionally once the products are purchased, some businesses require fulfilment systems that can be used by the dispatch and customer services teams. A business analyst should capture all the business requirements around this piece.


Advertisement

4. User checkout and payment

  • Generally users can check out as registered users or as guest users. An option of creating a new account is also available. Some businesses require customers to make an account in order to place orders. The information required to create an account needs to be considered.
  • Payment options can vary – Cash on Delivery, E-Wallets, 3rd Party Payment Gateways. Vendors are selected as per the requirement of the business.
  • The shipping charges and methods. These can be either maintained at the backend or made static.

5. Promo code application

It’s important for a business analyst to clarify the application area of these codes. At what point of the user journey can a user apply a promo code?

6. Mailers

Automated mails are triggered to customers on a majority of actions – when an order is placed, when an order is returned or an exchange request is placed, when complaints are logged, when new accounts are created, etc. Besides the standard practices, promotional campaigns are also run. Requirements should capture the mails to be sent for every action and the content for each mailer.

7. Reports

Analytics is an integral part of e-commerce in today’s date. A lot of third party tools are used by businesses to curate reports that’ll help the businesses to make informed decisions and plan further actions. The type of reports should be added to the business requirements.

Poor requirements can triple the length of the project

Requirements are the lifeblood of the project. Period.

And bad requirements or missing requirements can triple the length of the project. Worse, they can kill a project altogether due to time or budget (or both) issues.

I just had a simple home project for my wife go south because I failed to get the requirements fully defined before starting. I thought I had everything right, but I made some assumptions without asking certain questions. Keep in mind she is my very organized wife who hates it when I ask too many questions before starting a project for her. But our project customers have a potential to be problematic, stubborn, demanding or even uncooperative, right?

Next project today I got detailed requirements and then clarified and asked a couple of questions. We were definitely on the same page. When the project was over an hour later – complete to the original specs (I thought, anyway) and I asked if this looked ok and she said “oh heck no.” This was an example of some customers who just can’t be pleased or impressed. You may have to cut them loose if this keeps happening, but in my specific case with my wife, of course, that isn’t going to happen… you get the picture.

So, what can we do to ensure this doesn’t happen / and to keep my wife from getting mad at me on my next home project? We can focus on these 4 things…

Schedule enough planning time.

One of the biggest reasons there are disconnects between what the customer wants, the requirements that get documented, and the solution your team builds is lack of enough planning time. Requirements are so critical – you really can’t spend too much time on them as long as it is reasonable for the project. But cutting corners on the requirements definition phase is a definite no-no. There is no specific yardstick on how long to spend planning and documenting requirements. I wish I could give you an exact formula and if I could I would probably be a millionaire. Initially, for a good-sized tech project that is going to last 6 months or more, I would put at least 2-3 weeks into the schedule with 3-4 dedicated meetings and several assigned subtasks. Understand that the window for documenting requirements may expand or contract – it will be hard to predict but you must document detailed requirements thoroughly and as accurately as possible. Period.

Ask more questions even if it may seem like too many.

The bottom line is this – we need to avoid bad requirements and mis-understood requirements at almost all costs. Extend the requirements definition phase out if necessary – even if it injures the project budget and timeline early on. That is far better than extremely costly rework later in the project that might also serve to triple the length of the project as suggested by this article’s title. Take more time to analyze, define and document requirements. Ask more questions – lots of questions – of the customer project sponsor, the subject matter experts (SMEs), the ultimate end users – anyone and everyone on the customer side that knows what they want and need from the solution. Complete requirements that are complex and detailed set the stage for successful user acceptance testing (UAT) as well as a well-designed end solution that will meet the users’ needs and bring a successful conclusion to the project engagement.


Advertisement

Repeat the requirements individually as they are documented.

This may seem either obvious or overly mundane – depending on the individual or personality type. And you can argue till your out of breath against it but if it saves even a few hours of re-work by 2 or 3 project team members that could be $10,000 of project budget saved just be clarifying a requirement out loud. It goes along with my stance of following up after every meeting with notes from the meeting to make sure everyone is on the same page. We all have the potential to hear things and interpret things differently and we all go into each communication incident with some pre-conceived notions and are therefore bound to come out the other side with some varying understandings. Repeat requirements – get common understanding. It’s logical… common sense. Most PM best practices are that logical. It’s not rocket science.

Review the full set of requirements before beginning any project work or next phase.

Once all the requirements for the effort are detailed and complete, the business analyst should schedule a 3-5-hour session (longer, if necessary – depends on the complexity of the project and the size of the requirements document you’ve assembled) to review and discuss the full set of connected requirements. Do these now make sense and fit together right to form the intended solution? I do this and have never regretted it. There has never been a project where at least five or ten key requirements weren’t missing some detail or omitted completely. On multi-million-dollar projects that may translate into a savings of $100,000 or more of re-work and lost schedule fixing what was wrong or missing. Again, this session is just good common sense… good communication and good management. Planning and documenting is critical, so is follow-up to ensure common understanding and completeness.

Summary / call for input

The bottom line is this – whether it’s a big 18-month tech project for a client you’ve known for two weeks or a two-hour Saturday morning project for your wide who you’ve known for almost 36 years, clarity and completeness in project requirements is critical. Anything less can leave you with lost revenue, profitability and time or on the home front… well that’s going to vary a bit with each relationship… but it could prove to be problematic for a couple days.

Readers – what are your thoughts? Have you had projects start with less than complete rand clarified and fully understood requirements? How badly has it affected your project revenue, profitability and timeline? Please share and discuss.