Modern testing for modern stacks

Different perspective when thinking about the product or our service. As a tester we need to think about my testing artefacts. We focus on people whom we communicate often like developers and think less about people whom we dont interact (Business owners or vp etc) and our artifacts would just cater to developers which is bad.At Qxf2, we definitely have a good first mile. The mind map, ACC models the reporting which we do caters to everyone. Getting our testing report better. Better py test failure summary is also related to getting someone use our product easily

For any product to get through the first mile successfully, it's important to maintain simplicity. As we make it simple at the beginning, it's also important to explain to the customer what else they can do with this product. The work we have done to be highlighted-What we did, how much it will be useful for customers. The product we made should be understandable by others. It's not necessary that all features have to be implemented in our product. Start with small steps and then we can go beyond if it.

It's a very well written article, pleased to read it. It can be used as a guide for the first mile of a product. What I learnt is that first mile should not be neglected. I liked the explanation of 1st-mile failure vs the zone. He's shared great examples which make it easy to understand. Products are great only when customers express interest & get to the zone. Later he explains do-show-explain. This can be another debate/topic by itself. The feed must be engaging, I agree in 'devils in the default'. It should be the most sought part than the after part. We need to engage new users than pro users. With respect to qxf2, I think we are good now than earlier days. We have crossed our first mile. However if we are doing something new, maybe we can think of these principles in mind and act.

It's a very good article written by Scott Belsky. Explained with good examples and it's easy to understand. It's true, first mile of any product is very important. Scott very well explained the 1st-mile failure vs the zone with example of Twitter and I agree with his following note: users don't need to know how to use your product at the beginning; they just need to know what to do next! At Qxf2, we design Mindmap, ACC model, POM with super hero test during our first mile at client, Mindmap and ACC model gives clear idea about product, what features included in product and what not?? Which indirectly answer what we need to add to product to make product better? And our templates are very easy to understand and robust, because of our POM, we are capable to write any test script within 2 -3 days, usually we starts with writing super hero test which fight with super-villans of product. I also like Scott's explanation about Do-Show-Explain and I completely agree DO > Show > Explain.

I can relate my experience with Paytm application for this topic. I initially started using Paytm finding it to be very user-friendly. But later i noticed it started getting heavy (which is understandable) and not as user friendly as it used to be. It was like going from one touch recharge to looking where to click to recharge. In a client's product i found the ACC and Mindmap really useful. I created a Mindmap while i started on a client and when our work was done with them after months i pulled up the old Mindmap and i was able to realize the changes made to the application. Viewing the service we offer as a product the importance of the readme file cannot be emphasized enough. Irrespective of how matured our framework gets we are always going to be judged on how helpful we are with getting set up it? so before creating conditions should think about and try to achieve that conditions.If we consider about an organization, the conditions to be meaningful and effective in motivating employees, they must be tied to larger organizational ambitions. No matter what level the employee is at, he should be able to articulate exactly how his efforts feed into the broader company strategy.Make sure conditions are attainable but challenging -since employees are ultimately responsible for reaching the outcomes of the conditions,let them set the conditions.The conditions whatever we set not to be too difficult and also not easy.Once we set what is the outcomes,we should ask employees to create conditions to meet the outcomesConnect individuals goals to broader organization objectives.