Interview feedback from all interviewers compiled into one view before the debrief.
Debriefs fail on missing data: half the panel did not submit feedback, the other half wrote 'seemed good,' and the decision gets made on whoever speaks loudest in the room.
The interviewers had real observations. They are just scattered across threads, notes, and memory -- unassembled when the decision lands.
This routine compiles the panel's feedback after interviews: each interviewer's take, the agreements, and the genuine disagreements.
You walk into the debrief with the panel's actual evidence, and the decision reflects the interviews instead of the loudest opinion.
Copy this prompt into a new Littlebird routine. Edit the days and times to fit your schedule.
Every day after interviews compile feedback from all interviewers into a single summary
You can fake this with a chat skill and enough copy-paste. Most people keep it up for a week, then stop -- because the copy-paste is the actual job.
A routine removes the choreography: the context is already there, the schedule is already set, and the output shows up where you need it.
And it is private by design: SOC 2, GDPR and CCPA aligned, running on your Mac.
The compile shows the gap, so you can chase the missing take before the debrief, not after.
Yes -- the split decisions are exactly where the debrief should spend its time.
Yes. It compiles per round or per loop, whatever the prompt asks for.
No. The business model is subscriptions, not data -- nothing is sold, nothing is trained on, SOC 2, GDPR and CCPA aligned.
Not yet. Littlebird ships for Mac today, and the site keeps a Windows waitlist for launch news.
Put Littlebird to work.
