Debate: remote work should be a right, not a perk

Beginner

8 min

A workplace panel. You are arguing that any role that can be done remotely should be allowed to be, and the other side runs a company.

A beginner-level session of about 8 minutes. 3 rebuttal rounds against an opponent. Each round runs up to 60 seconds.

The difference between a perk and a right is who gets to say no. Nobody on the panel is going to argue that remote work is impossible, so the disagreement moves almost immediately from whether it works to whether a worker should be able to insist on it. That is a harder sentence to defend, and it is the one you signed up for. The founder opposite has run both models and asks about particular people rather than about policy, so general claims get absorbed and handed back. What you need is a version of the right that has edges: which roles, decided by whom, refused on what grounds. Say that in the first minute and the rest of the debate becomes a negotiation about the edges.

Angles worth taking

State the shape of the right early: which roles qualify, who decides, and what a valid refusal would look like.
A right that can never be refused is easy to attack, so build the exceptions in yourself rather than defending an absolute.
Replace any version of "it works for me" with one arrangement you have seen and the specific thing that held it together.
Have a mechanism ready for how a new joiner learns the job, not a reassurance that they will be fine.
If a challenge lands, say so plainly and then say what survives it, because silence after a good point reads as agreement.

Who is in the room

You play

A student defending the motion

You speak with

A founder who has run both models and believes mandating remote rights would break how junior people learn

Ready to speak?

Free to start. You need a TalkDrill account to speak — reading this page does not.

Browse all roleplay scenarios

The format

The motion you defend

If a job can be done remotely, the employee should have the right to do it remotely.

Rebuttal rounds

Time per round

60 seconds

Modes

Learn (guided) · Mock (exam-real)

How a roleplay session works

Read your brief

Your role, the situation, and what a good outcome looks like. The counterpart has their own brief, and you do not get to read it.

Open the conversation

You speak first in most scenarios. How you open sets what you can ask for later, which is most of the exercise.

Handle the turn

Somewhere in the middle it stops going your way — a refusal, a counter-offer, a rebuttal you did not prepare for. That moment is the scenario.

Read the report

Outcome, the phrases you used and the ones you missed, fluency and clarity, and the specific line worth rewriting.

What you're scored on

Across every roleplay, the report looks at the same four things — because they are what makes a real conversation work or fail.

Your objective

Hold the position against practical objections about culture, onboarding and accountability — and answer them with more than "it works for me".

Task outcome

Whether you got what the brief asked for: the refund, the extension, the concession, the point conceded.

Appropriacy

Whether the register fits. A complaint that is too soft gets nothing; the same complaint too hard gets a manager and no refund.

Recovery

What you do with the unexpected turn — repair, rephrase, push back, or stall. This is where most of the marks move.

Delivery

Fluency, pronunciation and pace, judged in conversation rather than in a prepared monologue.

More roleplay scenarios