BAPv5 Exam Dumps : BCS Practitioner Certificate in Business Analysis Practice v5.2

Design Thinking is an approach for solving complex problems by focusing on human needs and desires. It involves five stages: empathise, define, ideate, prototype and test. Therefore, options B, D and E are correct answers, as they suggest good techniques to help with the different stages of Design Thinking. Empathise is the stage where the problem is explored from the perspective of the users and their emotions, motivations and pain points are understood. A good technique to help with this stage is Customer Journey Map, which is a visual representation of the steps and emotions that a user goes through when interacting with a product or service. It helps to identify the pain points and opportunities for improvement in the user experience. Create is the stage where the users are represented by creating personas, which are fictional characters that embody the characteristics, goals and needs of a typical user group. Personas help to empathise with the users and design solutions that suit their preferences and expectations. Define is the stage where the problem is clearly defined and articulated based on the insights gained from the empathise stage. A good technique to help with this stage is Current user needs or problems, which is a statement that summarises what the users need or want to achieve and what prevents them from doing so. It helps to focus on the core problem and set the direction for ideation. Option A is not a correct answer, as Prototype is not a stage of Design Thinking, but a technique that can be used in the Prototype stage. Prototype is the stage where the ideas are turned into tangible and testable prototypes that can be used to demonstrate and evaluate the solutions. A good technique to help with this stage is Scenario Analysis, which is a technique that explores how different scenarios or situations could affect the outcomes of the solutions. It helps to test the feasibility and desirability of the prototypes. Option C is not a correct answer, as Evaluate is not a stage of Design Thinking, but a technique that can be used in the Test stage. Test is the stage where the prototypes are tested with real users and feedback is collected and analysed to refine and improve the solutions. A good technique to help with this stage is Mind Mapping, which is a technique that organises and visualises information in a hierarchical and associative way. It helps to capture and structure feedback and identify patterns and insights.

The documentation explains that CSFs are the areas where things “must go right,” and KPIs are the measures that show whether progress is being made toward achieving a CSF. KPIs should focus on specific performance areas and should be defined so they are SMART and monitored regularly.

For a CSF of “excellent customer service,” appropriate KPIs should reflect customer experience outcomes and customer loyalty/retention. Option C (“number of customers who post negative feedback”) is directly linked to service quality: negative feedback is a clear indicator that customers perceive service failures. Tracking it (and ideally setting a target such as “no more than X per month”) provides a measurable signal of whether service is improving.

Option D (“percentage of customers who renew their annual subscription”) is also strongly linked to customer service because renewal rates are a widely used indicator of customer satisfaction and loyalty: customers who experience consistently good service are more likely to continue their membership. As a KPI, it is measurable, trendable over time, and can be given SMART targets.

The other options are not direct indicators of customer service quality: restaurant ordering (A) is sales/upsell behaviour, fitness improvement (B) is an outcome of training/programming rather than service, and payment method (E) is an administrative preference. Therefore, the best KPIs for this CSF are C and D.

The documentation is explicit about how BAMs should be used when multiple stakeholder perspectives exist. It states that initially there will be one BAM for each distinct perspective, and later these models are examined to identify where there is agreement or conflict. The ultimate aim is to combine them and, through discussion with stakeholders, achieve a consensus BAM.

This is important because different stakeholders can hold different (yet valid) “world views” about the same organisation—what the book describes as “duck-rabbit” perspectives—so the analyst must understand and reconcile them to avoid building change based on a single partial view. Once the separate BAMs exist (Finance, Marketing, Logistics, Stores), the next logical step is therefore to facilitate negotiation and collaboration to create one agreed model that represents the idealised way forward and that stakeholders will “buy in” to.

Option A is unnecessary at this point because CATWOE is used to help derive activities and perspectives; the BAMs already exist. Option C (asking the Managing Director to pick) is specifically described as a fallback only if stakeholders cannot agree; it is less desirable than securing shared agreement because it risks lack of acceptance and weaker commitment to the final model.