Please enable JavaScript.

Coggle requires JavaScript to display documents.

Initial Recruiter Screen - Coggle Diagram

- - - - We faced a serious problem in our system—users who bought our service couldn't use it. If we didn't sort it out within half a day, our support team would've been overwhelmed with too many requests. Support team members must spend about 10 minutes for each request to cancel and repurchase the service. Our assessment said fixing it would take three days. We thought about stopping our sales service for three days to fix it, but that would've caused big financial loss and even worse, a terrible reputation.
        
        In that critical moment, an idea struck me. I proposed the development of a script that could detect and automatically do what exactly a support team member did, whenever the problem occurred.
        
        With swift action, I immediately allocated resources—two individuals focused on crafting the script while another two worked on resolving the underlying technical problem.
        
        Surprisingly, we finished the script in a few hours, just before the support team got overwhelmed. This stopped a crisis and gave us time to solve the main problem.
  - - - Critical Path
        
        We assigned tasks based on strengths and expertise
        
        Extra Hours, made sure nobody got too tired
        
        Daily stand-up meeting - to make sure we were on track
        
        Monitoring, Correcting any small deviation
        
        Working under pressure -> more human errors -> so testing is more important, sometimes because of a tight deadline, the test stage scarified
    - - Algorithm for credit run out predication
        
        tension, slow our team down
        
        Organize a meeting -> pros and cons, So that everyone felt heard
        result -> two main method to implement it but we couldn't choose between them, so we decided to implement both of them to test them on the real world data
        
        surprisingly, the first method worked better on the customer with high consumption and the other method worked better for low-consumption ones
        
        So, we used different methods for different customers to predicate their credit run out
  - - - Documentation
        
        Glossary, General terms are devil
        
        Taking feedback from stakeholders to make sure we are on the same page
    - - Documentation
        
        Glossary, Avoid general terms
        
        Taking feedback from stakeholders to make sure we are on the same page
        
        Planning in such a way that we have a deliverable for the users in short intervals to get feedback
        
        UI Prototype (Even the Interactive one)