01
Gather the ownership trail
Collect the ticket history, current blocker, involved responsibilities, and delivery impact before diagnosing the stall.
Made for Engineering Managers
Find the Real Owner of Stalled Work
Also useful for: people in Engineering Managers, people in Technical Leads
20 min
Intermediate
Decisions
Finish What You Started
Need to Make a Decision
Turn a stalled engineering ticket into a clear ownership decision and a specific next move.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Find the exact point where progress stopped, separate missing decisions from missing execution, and name one person accountable for moving the work forward.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Locate the exact stall
Find the first unresolved event after the last confirmed progress and classify the type of stall.
03
Name one accountable owner
Match the required next action to the person with the authority or control needed to complete it.
04
Send the ownership reset
Turn the finding into a neutral message with a deadline and escalation path.
Make Your Play
Find the Real Owner of Stalled Work
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Paste the relevant timeline, comments, decisions, attempted handoffs, and dates in chronological order.
0/10000
Describe what can't move forward and what appears to be missing right now.
0/10000
List each involved person or team, their responsibility, and any known decision authority.
0/10000
State the affected milestone, deadline, dependency, or customer impact.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Gather the ownership trail
Collect the ticket history, current blocker, involved responsibilities, and delivery impact before diagnosing the stall.
02
Locate the exact stall
Find the first unresolved event after the last confirmed progress and classify the type of stall.
03
Name one accountable owner
Match the required next action to the person with the authority or control needed to complete it.
04
Send the ownership reset
Turn the finding into a neutral message with a deadline and escalation path.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Paste the ticket timeline in order, including decisions, comments, handoffs, and dates. Use job functions instead of names if the details are sensitive. Check that the proposed owner controls the next action before sending the message.
Advanced instructions
Include links between dependent tickets, prior decision records, service ownership, and approval boundaries. Challenge the proposed owner by asking whether another person has stronger authority or control over the exact next action.
Use this when
A ticket, project, or dependency has stopped moving, several people appear involved, and no one is clearly accountable for the next decision or handoff.
You'll need
- Ticket or project history
- Current blocker
- People and teams involved
- Delivery impact and timing
You'll get
- The last confirmed progress point documented
- The first unresolved event classified
- One concrete next action defined
- One accountable owner named with evidence
- Contributors and reviewers separated from ownership
- A time-bound ownership message ready to send.
By the end of this playbook
You will have:
- The last confirmed progress point documented
- The first unresolved event classified
- One concrete next action defined
- One accountable owner named with evidence
- Contributors and reviewers separated from ownership
- A time-bound ownership message ready to send.
Examples
Progress 1 of 4