How to do business analysis with an extreme customer focus?
Angela Wick
| 2 Million+ Trained | Helping BAs Navigate AI | BA-Cube.com Founder & Host | LinkedIn Learning Instructor
In my last LinkedIn Newsletter I spelled out what Modern Analysis looks like, and discussed the Do's & Don'ts, and context of the follow Modern Analysis musts:
- Customer Focus
- Facilitating Decision Making & Problem Solving
- Experiment
- Collaborate Differently
- Your Actions Matter
- Own Your Craft
- Always Be Learning
- Keeper of Responsible Decisions
In this issue, I want to deep dive into Customer Focus and how to do analysis with an extreme customer focus.
First things first! We don’t build technology, change processes, collect data, integrate with third parties or any other typical work where we do analysis, unless it is to benefit humans. These humans are usually our customers, or internal end-users of the product, system, data or process.
For decades we have focused on cost reduction, economies of scale and efficiencies in our change and technology efforts. Serving customers meant getting the lowest price and parity with the competition. For many, this is still a strong focus. For others, digital and innovation is the focus. I am sure for some you are hearing both are the focus. We have all been on the project that met the deadline, scope, and budget, but the user need was not met! What a waste of money! Often this happens when we do not put the customer first in our analysis.
---------------------------------------------------------------------------------------------------------------
EXTREME CUSTOMER FOCUS:
DO: Work from a customer point of view, knowing all other details will follow. The customer context is the anchor!
DON'T: Work from a technical and solution anchored point of view first or as a primary focus. Your team likely has many technical professionals who are focused on this, let them focus on the technical point of view.
CONTEXT: Working from a customer point of view is the modern way of doing business analysis. When we work from a customer and user problem-solving lens with their mindset focused and anchored in making the user's experience better for the things they do that bring them to use the product, all other details will follow and fall into place.
When we work from a solution-first perspective we often miss the mark on solving the real user needs and waste time, money, and energy solving for the wrong problem without knowing it. From what lens are you working?
---------------------------------------------------------------------------------------------------------------
CUSTOMER CENTERED ANALYSIS TECHNIQUES:
Working from a customer perspective means using customer centered techniques before system, data, and technically focused techniques. It means mapping the technical and implementation details to the customer lens.
Techniques to use a customer lens:
1. Customer Journey Mapping: A great Design Thinking technique. Use this technique to truly understand where the customer pain is and map the change/request/requirement/idea to it! If you are new to customer journey mapping, try some practice on your own, then involve the team.
2. Observation: Observe the user performing the task with the product/process/system and see where the user is struggling. It is often far different than you imagine simply reading or talking about the problem or solution.
3. Problem Definition: Understanding the problem and desired outcome from an end-user or customer point of view, and facilitating a shared understanding with the team on this.
Try this “fill in the blank” to define the problem:
________a_______, is frustrated _________b______, in the situation when _____c________.
a. The user
b. The action the user is taking when using the product
c. More about the timing or trigger
So, if the user wants a new button on a screen, and after observing the user with what they are doing when they want to use this new button; we might write something like: The Customer Service Rep is frustrated, in the situation when a call is transferred and they have to ask the customer for their account number again because the transfer loses the customer data as it passes to the next CSR.
This helps us understand that a new button may not be the best way to solve this problem.
4. Empathy Mapping: Another great Design Thinking technique to help us better understand the user, their emotions and needs.
5. User POV Process Flow: You likely know all about process flows, a very common technique for analysts. Can you do it entirely from a user perspective?
6. User Stories - Common on agile teams, depicting user goals/actions/tasks for agile teams to work on.
7. User Story Mapping - Also common on agile teams, showing how user stories relate to one another for a product.
Want to learn more about these techniques and more!
Continuously learn modern analysis skills with me in two ways:
My Linkedin Learning Courses - Ten courses all about business analysis, and agile analysis.
BA-Cube.com BA-Cube is a unique membership site with business analysis learning content, Live Events, and Mentoring! Our live events and mentoring make the learning real and go deep, making your real work come to life with the new learning. 7-Day Free Trial and a special offer for 15% off membership (use code LI-Newsletter15). Join us in our community of hundreds of analysis professionals to elevate skills and performance.
This post contains affiliate links and I will be compensated if you click my links and make a purchase.
And so many more!
What is your favorite customer centered thinking technique?
Comment below!
Product Lead | Strategist | Digital Transformation | Building the best in class products for customers in telecom domain | Follow me for posts about Product Management & Leadership
3 年The essential thing for me is helping the customer (if internal) or whom represent them like product manager to define the problem and not jumping into conclusion or solution immediately ... this will give me a clear picture how to build the user story with stakeholders and apply the best solution with UX/UI and development teams. Very nice reading ... thanks Angela Wick !
Project Manager/Business Analyst @ Sasser Family Companies | PMP Certified
3 年Very useful
Landon Fleming
Associate Product Manager BP UK | Business Analyst |Infosys Consulting | Ex Wipro UK | BioFuels | Energy | SAP Implementation | Requirements Engineering | Business Improvement | Digital Transformation | Process Maps
3 年Wonderful insight into identifying Customer’s perspective.
Product Owner|Agile Enthusiast|Business Analysis & Consulting
3 年When it comes to any digital transformation projects the focus is mostly on either the technology or on the project itself rather than giving attention to the real customer/ end user needs. When it comes to internal context even if you are working in an agile team, the user needs to be clearly understood and communicated with the technical team as well. Any gap in either of these two will result in the failure of the digital transformation project