1
00:00:00,400 --> 00:00:03,960
The Better Business Analysis 
Institute presence. 

2
00:00:03,960 --> 00:00:07,760
The Better Business Analysis 
podcast with Tinsman Walsh. 

3
00:00:12,280 --> 00:00:13,960
Hi, everybody. 
It's Ben from the Better 

4
00:00:13,960 --> 00:00:17,600
Business Analysis Institute. 
And today we've got our second 

5
00:00:17,600 --> 00:00:21,840
BA Bytes episode where we talk 
about the power of Y. 

6
00:00:22,000 --> 00:00:25,680
Have you ever heard the phrase 
there's no such thing as a 

7
00:00:25,680 --> 00:00:28,160
stupid question. 
It's so important here. 

8
00:00:28,440 --> 00:00:32,400
OK, it's around the fact that 
you can ask questions. 

9
00:00:32,400 --> 00:00:35,120
Sometimes I even phrase it. 
This might be a stupid question,

10
00:00:35,200 --> 00:00:39,160
but why? 
In business analysis, the most 

11
00:00:39,160 --> 00:00:43,520
valuable question might be why. 
It's also what but what. 

12
00:00:43,520 --> 00:00:47,480
Always start with the why. 
By asking why behind a 

13
00:00:47,480 --> 00:00:51,240
stakeholder's request or a set 
of requirements, we uncover the 

14
00:00:51,240 --> 00:00:55,360
true needs and motivations 
behind the why or the request. 

15
00:00:55,920 --> 00:00:59,600
This leads to better solutions 
and avoids building features 

16
00:00:59,800 --> 00:01:03,000
that no one really wants, 
including the person who asked 

17
00:01:03,000 --> 00:01:06,480
for it in the 1st place. 
When you're gathering 

18
00:01:06,480 --> 00:01:10,440
requirements, don't be afraid to
dig deeper and ask why. 

19
00:01:11,400 --> 00:01:15,840
I'll give you an example. 
There may be a request from a 

20
00:01:15,840 --> 00:01:20,960
stakeholder that's around they 
saying I want faster checkout 

21
00:01:20,960 --> 00:01:23,640
processing. 
OK, I want a faster checkout 

22
00:01:23,640 --> 00:01:27,560
process. 
It's too slow, but by asking why

23
00:01:27,560 --> 00:01:31,880
you might uncover A deeper 
concern, such as a statistic 

24
00:01:31,880 --> 00:01:35,960
around high car abandonment 
rates and it could be due to a 

25
00:01:36,000 --> 00:01:39,840
tenuous check out flow. 
It's hard for users to use your 

26
00:01:39,840 --> 00:01:43,360
check out process. 
By understanding the why, you 

27
00:01:43,360 --> 00:01:46,840
understand the root cause by 
asking the five YS and the two 

28
00:01:46,840 --> 00:01:51,760
HS, and then not just 
implementing a faster process, 

29
00:01:51,960 --> 00:01:54,920
right, Which might not actually 
solve the problem, You can look 

30
00:01:54,920 --> 00:01:57,920
at more effective solutions that
meet the true needs of that 

31
00:01:57,920 --> 00:02:01,560
stakeholder by maybe redesigning
the process itself. 

32
00:02:02,640 --> 00:02:06,280
OK, the power of the Y is so 
important, that's your top tip. 

33
00:02:06,520 --> 00:02:07,400
See you next week.