LUMARA · PRACTICE STUDIO

Better conversations. One small step at a time.

Turn what you read, hear and see into English you can use. Try an idea. Hear yourself. Try again.

LISTEN PRACTISE GROW

Free learning tools · no AI creditsVocabulary, photos, audio, whiteboard, PDFs, games and a 3D room.

01 · YOUR MATERIAL

Before You Add a Button, Ask What the Customer Needs to Do

Use the example, paste text, or open this tool from an article or course module.

English text to practise

Workplace Growth Daily · 2026-10-06 LUMARA Workplace Growth Daily · 6 October 2026 Illustrative scene: A customer asks for a download button. By lunchtime, three colleagues have sketched its colour, location and possible friendship with the export menu. Nobody has asked what the customer wants to download—or why. The button already has a stronger project plan than the problem. Today’s angle: listen for the task behind the requested solution. Perhaps the customer needs a record for a colleague, not another feature. This is a research-backed practical briefing, not a breaking-news report. One supplied research page was updated on 30 September; that does not establish that its findings are newly collected. The exercises below are LUMARA’s practical suggestions, not tested findings from the cited research. What is changing 1. Internal development is receiving more attention. CIPD’s survey of 1,014 UK employers with HR decision-making responsibilities found that 48% reported increasing efforts to develop talent in-house over the previous year. Fieldwork ran from 2 April to 2 May 2026; the release was published on 22 September 2026. This describes employer activity, not proof that training improved retention. CIPD: Almost half of employers are upskilling their workers For a real team: choose a skill attached to a customer task. Practising how to clarify a request is a modest development activity you can observe, rather than a broad instruction to “be more customer-focused”. 2. Managers shape important working conditions. Gallup reports that managers account for 70% of the variance in team engagement. Its page also identifies expectations, recognition and development among the conditions managers influence. Published 27 July 2026, updated 30 September 2026. This is an engagement finding—not a claim that managers cause 70% of productivity or that today’s exercise will increase sales. Gallup: How Managers Impact Team Productivity For a real team: make listening part of supported work. Define when to ask a follow-up question, allow time for it and recognise useful discoveries—not only fast replies. Build a skill in 10 minutes Named skill: need-first listening—separating what someone requests from what they are trying to accomplish, without dismissing their proposed solution. A 10-minute exercise Work in pairs with one anonymised customer request. If none is available, use the illustrative download-button scenario. - Minutes 0–2: The listener reads the request and writes two headings: “What we know” and “What we are assuming”. - Minutes 2–5: The customer role-player explains the intended task. The listener asks: “What would this help you do?” and “What happens now when you try?” Avoid pitching a fix. - Minutes 5–7: The listener summarises: “You need to do , but gets in the way. Have I understood?” The role-player corrects it. - Minutes 7–10: Together, write one need statement and one unanswered question. Visible success criteria: the note separates evidence from assumptions, names the customer’s task without prescribing a feature, and records a correction or explicit confirmation. If you cannot meet those checks, keep the uncertainty visible. Staff and management: respect in both directions Managers should set a clear expectation: clarify ambiguous requests, but do not turn every simple enquiry into an interview. Treat colleagues respectfully, invite their observations and recognise careful listening even when it challenges a preferred idea. Allocate practice time within working hours and remove another task if the workload cannot absorb it. Manager—say this: “We’re testing one clarification question, not asking you to handle more cases. Tell me where it helps and where it adds effort. I’ll review the workload with you, and we’ll credit the people who uncover useful needs.” Staff can bring management a specific example, distinguish observation from interpretation and propose an alternative. Raise concerns early rather than silently absorbing extra work. Staff—say this: “I support understanding the customer’s task. I disagree with adding questions to every reply: this straightforward case would become slower. Could we limit the test to ambiguous requests and check handling time?” Constructive disagreement does not mean accepting bullying, humiliation or retaliation. Use an appropriate reporting or support route if those occur. Work better as a team Run a 15-minute exercise with four roles: facilitator/timekeeper, customer-evidence reader, assumption challenger and recorder. In a smaller team, combine roles. 1. Minutes 0–3: The reader presents one anonymised request and its available context. Keep personal customer information off the board. 2. Minutes 3–6: Everyone silently adds notes under “Requested solution”, “Intended task” and “Unknown”. Mark interpretations as assumptions. 3. Minutes 6–10: The challenger asks what evidence supports the intended task. The group drafts one neutral clarification question; the facilitator prevents a feature-design debate. 4. Minutes 10–13: Agree one possible response if the customer confirms the need, and one reason that response might be unsuitable. 5. Minutes 13–15: The recorder completes a shared card: request, evidence, unknown, question, possible response and named follow-up owner. Tangible output: one request-to-need card, ready for a customer conversation—not a feature commitment. Leave unresolved points unresolved. Turn teamwork into measurable growth LUMARA’s low-cost experiment: for seven days, use one need-first question on a small, predefined category of ambiguous requests. Keep existing safeguards and service commitments unchanged. Owner: the customer-service team lead, supported by a participating colleague who logs outcomes in an existing spreadsheet. Baseline: review the previous seven days of comparable requests. Record how many needed another customer contact because the original task remained unclear, plus typical handling time. Note the sample size; a small or uneven sample limits interpretation. During the test, record whether the customer confirmed or corrected the need statement and whether further clarification was required. Do not treat silence as confirmation. Balancing measure: track handling time and ask participating staff whether the extra question made workload harder to manage. Stop if it creates unsafe pressure or inappropriate questioning. Seven-day review—13 October: compare clarification-related repeat contacts and handling time with the baseline. Discuss differences in case complexity. Keep, revise or stop the approach; do not claim causation, retention gains or revenue growth from this small comparison. Try it today - Select one ambiguous customer request. - Separate the stated request from your assumptions. - Practise one neutral question for ten minutes. - Build one shared request-to-need card. - Name the experiment owner and book the seven-day review. Discussion question: Which customer request are we already designing a solution for, before we understand the task it needs to support?

Mini-lessons use the first 6,000 characters. Audio lets you work through the full text, up to 18,000 characters.

02 · LISTEN AND SPEAK

Listen. Repeat. Make it yours.

Listen with your browser’s free voice (Google when available). To download an audio file, prepare a copy on this device.

PassageVoiceSpeed

Workplace Growth Daily · 2026-10-06 LUMARA Workplace Growth Daily · 6 October 2026 Illustrative scene: A customer asks for a download button. By lunchtime, three colleagues have sketched its colour, location and possible friendship with the export menu. Nobody has asked what the customer wants to download—or why. The button already has a stronger project plan than the problem.