Where you are
You lead the team building a scheduling platform. A client email has moved the demo forward by twenty-four hours.
Escenario 5 · Rol A
The full demo cannot be ready a day early
Direct and constructive. The client has moved Friday’s demo to Thursday. You start. About 10 turns · 9 minutes.
Your screen only. Don't show it. Separate what is ready, what can be made safe and what must remain a roadmap item.
Tu información
You lead the team building a scheduling platform. A client email has moved the demo forward by twenty-four hours.
You want a truthful Thursday demo of the core flow, with enough testing to avoid showing unfinished features as complete.
The manager promises a full demo, and the team either misrepresents unfinished work or misses the new meeting.
Notas, no frases
| Original demo | Friday · 2:00 p.m. |
| New demo | Thursday · 2:00 p.m. |
| Core booking flow | stable · desktop |
| Accessibility check | 2 hours · required |
| Analytics import | 6 hours after fresh client file |
| Client data file | not received |
| Static analytics preview | 3 hours · Maya |
| Tradeoff | mobile filters move to Monday |
| Team boundary | no work after 7:00 p.m. |
| Decision needed | Wednesday · 10:00 a.m. |
Palabras para esta situación
| Word | What it is | Here |
|---|---|---|
| accessibility check | a review of whether people with different needs can use a product | the required test for the booking flow |
| analytics import | the process of bringing measurement data into a system | the feature blocked by the missing client file |
| core flow | the main sequence a user must complete | searching, selecting and confirming a booking |
| dependency | something that must happen before another task can finish | the fresh data file needed for analytics |
| misrepresent | to describe something in a way that creates a false impression | the risk of calling estimated data complete |
| roadmap item | work planned for a later stage rather than the current release | a transparent status for unfinished analytics |
| scope | the work and features included in a delivery | what Thursday’s demo can honestly cover |
| static preview | a fixed example that does not use live data | the limited analytics option Maya can build |
| tradeoff | a choice that gains one benefit by giving up another | analytics preview now or mobile filters on time |
| walkthrough | a guided explanation of a process or product | the format for the core booking demo |
Ayuda común
Use blocks 1, 2, 3 [receives], 5, 6, 7 [grants] and 8. Do not say only that there is “not enough time”; attach time and dependency to each feature.
Solo para tu rol
| Purpose | Form | Effect |
|---|---|---|
| challenging the full scope | I can’t describe the analytics as complete without the client data file. | reject one misleading promise with its reason |
| clarifying the priority | Which outcome does the client need to see in order to decide? | learn what the shorter demo must accomplish |
| explaining the dependency | The import will take six hours once we receive the fresh file. | separate team time from an external blocker |
| holding the quality boundary | The accessibility check has to remain in Thursday’s plan. | protect a required test from schedule pressure |
| offering the stable scope | We can demonstrate the complete booking flow on desktop. | name work that is genuinely ready |
| proposing the preview | Maya could build a labeled static preview if mobile filters move to Monday. | offer a limited alternative with its cost |
| requesting honest language | The invitation should call analytics a preview, not a finished feature. | align the external message with the actual product |
| summarizing the demo | Thursday includes …; … remains a preview; … moves to Monday. | check scope, label and consequence |
Cuándo terminar
Close when both people record the same seven details:
Después de hablar
Para repasar
Will request, is going to attend y will remain permiten distinguir decisiones nuevas, planes y estados futuros.
If Maya builds the preview y if the file arrives conectan elecciones reales con sus consecuencias.
The file will be deleted y the scope has been confirmed describen controles y entregables con foco en el proceso.
The flow that is stable y the person who owns security precisan alcance y responsabilidades.
Has to remain, cannot promise y should include expresan requisito, límite y recomendación.
Whereas, provided that, although y therefore sostienen el razonamiento del compromiso parcial.
¿Abriste la ficha equivocada? Cambia al rol B sin leer más.
Ir al rol BToda esta práctica es gratuita. Ver cómo enseñamos inglés en WeLearn — presencial en Bucaramanga u online. El diagnóstico de nivel es gratis.