A key performance indicator (KPI) is a measurable value that demonstrates how effectively an organisation is achieving a key business objective or critical success factor (CSF). A KPI should be relevant, specific, measurable, achievable, realistic and time-bound (SMART). Therefore, options C, D and E are appropriate KPIs for the CSF ‘provide excellent customer service’, as they measure aspects of customer satisfaction and loyalty that are directly related to the quality of service provided by the hotel chain. Option A is not an appropriate KPI, as it does not measure customer service, but rather customer consumption. Option B is not an appropriate KPI, as it does not measure customer service, but rather customer preference.

The end users are classified as high interest, low power on a power/interest grid. This is because they are directly affected by the new reporting tool and have a strong preference for not using it, but they do not have much authority or influence to change the project decision or outcome. Option A is the correct answer.

The key issue described—staff creating manual workarounds to satisfy important customers—often reflects tacit knowledge and “what really happens” in day-to-day work, not what is written in policies or what people might summarise in a survey. The guidance is clear that while interviews and workshops can reveal stakeholder views, the “back-story” of real working practices can differ; techniques such as work shadowing and observation help clarify what actually happens.

Shadowing is specifically defined as following a user as they carry out their job for a period (e.g., a day or two) in order to find out what the job entails. This is exactly the kind of technique that exposes hidden steps, exceptions, customer-specific handling, and unofficial procedures—precisely the conditions that drive workarounds when a COTS package does not fit real operational needs.

The observation section also highlights that seeing the workplace provides a much better understanding of problems and difficulties faced by business users and helps uncover tacit information that would otherwise remain unstated. Additionally, the guidance even uses customer services as an example area where an analyst might shadow staff to record real call types, durations, and retrieval delays—evidence that supports discovering process pain and mismatch early.

Therefore, shadowing customer service personnel (D) would have been most likely to uncover the workaround drivers earlier.

To identify underlying causes, the analyst needs a technique that helps them explore what is happening in practice and uncover where breakdowns or inefficiencies might be occurring. The documentation describes scenario analysis as “telling the story of a task or transaction,” and explains it is useful when analysing or redesigning processes because it helps staff and analysts work through the steps required, visualise them clearly, and understand what triggers the work and what actions must be completed to achieve a successful outcome.

In a retail setting, declining sales can result from failures or friction in key customer-facing scenarios (e.g., browsing, ordering, returns, stock availability, customer service escalation). By building and walking through scenarios end-to-end, the analyst can pinpoint where delays, handoffs, rework, unclear decision points, or system constraints occur—each of which can contribute to poorer customer outcomes and, ultimately, sales decline. Scenario work also creates a concrete basis for validating hypotheses with stakeholders and for identifying what evidence and data should be gathered next.

The other options are less directly “cause-finding” for the stated problem. A customer journey map focuses on experience and touchpoints (useful, but it may not expose operational root causes in enough detail). Use case diagrams define system interactions for requirements, not root cause diagnosis. A business activity model gives a conceptual “what activities exist” overview; it is valuable for gaps, but scenario analysis is the technique explicitly positioned to walk through transactions to reveal where problems arise.

The business analysis guidance notes that reviewing a company website can reveal useful inferences about the organisation’s branding, values, priorities, and strategic positioning, including how it balances cost versus perceived quality. In particular, the guidance contrasts “populist” signals (primary colours, flashing icons, exclamation marks, “Bargain!” language) with a quieter, more restrained design, which tends to imply a more premium / quality-focused positioning.

The described site is muted (greys/whites), uses “lots of white space,” and includes only a few carefully chosen images. Those choices align strongly with conclusion D: the company is positioning its offering as high quality rather than “cheap and cheerful.” The seamless movement through information and concise, well-structured sections also indicate attention to usability and information architecture—signals consistent with high technical and design standards (conclusion C).

However, nothing in the description proves the firm is “well established” (A), “market leading” (B), or “very profitable” (E). Those claims require external evidence (market share, history, financial performance), whereas the website evidence supports positioning and quality/technical execution, not market status or profitability.

The technique that best supports identifying root causes of problematic attitudes is the rich picture. The documentation explains that many problematic business situations have “human and cultural aspects” that traditional structured models (like process or data models) cannot capture well. These aspects include differing viewpoints, misunderstandings, stress, dissatisfaction with management, frustration at inadequate resources, and other “people” factors that can directly affect outcomes. A rich picture explicitly enables the analyst to document these human factors alongside information flows and other issues, because it is intentionally unstructured and allows a “brain dump” of what is happening and how people feel about it.

The guidance also positions rich pictures as particularly useful in messy situations with multiple causes, helping the analyst see connections between issues and progressively enrich understanding as new information emerges. This matters in the scenario: complaints about the UI may reflect deeper causes such as poor navigation, unclear content, inconsistent interaction patterns, internal constraints, or misalignment between user expectations and design choices—plus stakeholder tensions about priorities. A rich picture is designed to surface and connect these causes and perceptions early in investigation.

A mind map can help structure information, but the rich picture is explicitly highlighted as the technique that captures the essence of the whole situation, especially where attitudes and cultural factors are significant.

An external requirement is a business rule that is imposed by an external source, such as a law, regulation, or standard. The business rule in this question is a legal obligation that EuroCoach has to comply with, so it is an external requirement. Option C is the correct answer.