BQ - Judgment from incomplete data
Template
- background
- something can be improved, not decided to work on it
- many factor might contribute to decision making
- list factors: budgets, work priorities, is the feature on critical path, impact on the potential user
- Can't make decision when all info collected, too inefficient
- prioritise the important info, how did I collect, and how did I make the final decision based on this incomplete data collected
- Quantify the result and impact
- Indicate learning from this project
Story
- S
- User have reported a bug, seeing some accounts have their description badge length exceeding the limit
- The Quality Assurance team immediately started to investigate the issue, to provide more information to our backend team to address this issue effectively
- T
- However, since this is a online issues, and individual may leverage this bug to attack this server, therefore despite the lack of information, I decide to start resolve this issue immediately
- A
- Firstly, I arranged a quick conversation with the team member responsible for the implementation logic regarding the badge length
- Improve efficiency
- Once understood the logic, I dived into the code straight away to locate the bug
- Then, I added a additional layer of checking in the backend and pushed online
- Firstly, I arranged a quick conversation with the team member responsible for the implementation logic regarding the badge length
- R
- The issue was quickly fixed, and not more cases of user bug report
- L
- The importance of evaluate the situation, if the downside of not responding is huge, act proactively despite the incomplete information.
- Prioritise gathering of important information, in this case, it is...