What will you finish in your first week?
You join RelayDesk as a product and operations generalist. The founder sends four requests and says they all matter.
The question
RelayDesk and all people, customers and estimates are fictional. You have 12 focused hours after onboarding. One person does each activity, sequentially; estimates are elapsed working hours. The founder has made restoring service to the blocked customers the first priority.
| Hours | |
|---|---|
| Restore imports for 12 blocked customers | 4 |
| Check where new users abandon onboarding | 3 |
| Interview two customers about onboarding | 2 |
| Polish the investor-demo screens | 6 |
The demo is useful, but no external demo deadline has been promised. All work is in your approved role scope.
Restore the blocked imports and learn which onboarding problem to address next. Give the founder a clear commitment before starting.
“Choose your next action and explain the trade-off.”
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: Which outcome comes first?
What would you do here? Open the move you’d make.
Start with the customer outcome
The strong move. The founder named service restoration and customer learning as the current outcomes.
Polish the demo because it is easiest to show.
Tempting, but it misses something. A visible output is not the stated priority.
See how a strong candidate says it
“Restore the blocked imports, then use the customer interviews and onboarding check to guide the next change.”
Why it works: The founder named service restoration and customer learning as the current outcomes.
Step 2: What fits the week?
What would you do here? Open the move you’d make.
Commit to nine hours of work
The strong move. All four requests need 15 hours; the available budget is 12.
Promise all four and work faster with AI.
Tempting, but it misses something. AI use does not remove the stated delivery estimates.
See how a strong candidate says it
“The service fix, onboarding check and interviews take 4 + 3 + 2 = 9 hours. Keep 3 hours free and defer the 6-hour polish.”
Why it works: All four requests need 15 hours; the available budget is 12.
Step 3: How does the new estimate change it?
The import owner confirms the fix needs 7 hours, rather than 4. The other estimates and the 12-hour budget stay unchanged.
What would you do here? Open the move you’d make.
Update the commitment to 12 hours
The strong move. The revised fix consumes the three spare hours.
Keep the original three-hour buffer in the update.
Tempting, but it misses something. That would count the same three hours twice.
See how a strong candidate says it
“The useful bundle now takes 7 + 3 + 2 = 12 hours. Keep that commitment and make the loss of buffer visible.”
Why it works: The revised fix consumes the three spare hours.
Step 4: What do you say to another request?
The founder now asks whether the 6-hour demo polish can be added to the same week. No extra capacity is available yet.
What would you do here? Open the move you’d make.
Expose the six-hour gap
The strong move. The new request needs a real trade-off.
Accept the demo and leave the interviews half done.
Tempting, but it misses something. That hides a changed commitment and abandons the agreed learning outcome.
See how a strong candidate says it
“Adding the demo makes 18 hours. Ask the founder to change scope or assign approved capacity; do not quietly promise it.”
Why it works: The new request needs a real trade-off.
The answer, in short
- Decision
- Commit to restoration and customer learning within 12 hours.
- Because
- The updated bundle uses all available time.
- What would change it
- Approved extra capacity or a changed priority could replace part of the commitment.
Common traps
- Busy is not the same as useful.
- A fast draft is not an approved capacity increase.
Check your answer
- I named the intended outcome.
- I added every committed hour.
- I updated the estimate.
- I made the new trade-off explicit.
Last reviewed Nov 10, 2026