Worked questionsSkill 04: Make the decision and bring people along
Nobody owns the launch decision. What do you do?
High agency isn’t acting alone. Create motion inside the boundaries you actually have.
The question
At RelayDesk, a fictional support workspace, sales owns the customer conversation, engineering owns implementation and risk evidence, and product frames the value and proposed scope. No one has been named to approve the launch.
- Sales
- Has told a customer auto-send is coming. What exactly was promised is unclear.
- Engineering
- Flags that a wrong answer, once sent, can’t be unsent.
- Product (you)
- Frames the value and the proposed scope. You are not anyone’s manager.
Invented scenario. No contract, legal permission or reporting line is implied.
“Sales promised auto-send, engineering flags policy risk, and nobody owns the launch decision. What do you do next?”
Your turn
Say your answer out loud, or jot notes below. Both work. Or skip to the worked answer.
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Establish the facts and the outcome
“First I’d find out what was promised, to whom, and what a good resolution looks like for that customer, before arguing for or against the feature.”
Why it works: It separates commercial pressure from actual obligations and customer value.
Step 2: Represent the strongest objections
“Sales needs credibility and value; engineering is warning that a wrong answer can’t be unread. I’d ask for concrete failure examples and compare bounded alternatives.”
Why it works: It treats both functions fairly instead of caricaturing either.
Step 3: Create motion within your boundaries
“I’d propose reviewed drafts or a limited pilot, put the evidence together and ask the accountable sponsor to name an approver. I wouldn’t act as everyone’s boss or ship around an unresolved risk.”
Why it works: High agency doesn’t mean going around authority.
Step 4: Close the loop
“I’d record the scope, decision, owner, evidence and review date, align what the customer is told, and revisit if the evaluation fails.”
Why it works: It ends with a specific next action instead of another meeting.
The answer, in short
- Decision
- Propose reviewed drafts or a limited pilot, and ask the accountable sponsor to name who approves the launch.
- Because
- It keeps the customer conversation moving without shipping around an unresolved policy risk or inventing authority you don’t have.
- What would change it
- If the promise turns out to be contractual, or the evaluation clears auto-send for a narrow category, the scope changes and the decision is revisited.
A real interviewer may follow up: “Tell me about a time you changed a decision after disagreement.” Use your own experience: what you did, what changed your mind and how it turned out. Don’t memorise an invented story.
Common traps
- Launching unilaterally.
- Waiting indefinitely for permission without proposing a path.
- Treating alignment as a status document.
- Inventing a personal success story.
Check your answer
- Did I show initiative?
- Did I respect authority and risk boundaries?
- Did I represent the strongest opposing case?
- Did I name who is accountable and when to revisit?
Want to practise explaining this decision aloud? Try an AI coach on Socratify.
Last reviewed Nov 9, 2026