Verified against ChatGPT · 2026-08-10
Set up a recurring 1:1 agenda that survives the third week of getting skipped for status updates
Builds a reusable 1:1 meeting structure for a specific manager-report pair, weighted toward the report's actual priorities and career goals so the meeting doesn't quietly collapse into a status-update readout the report could have sent in a Slack message.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Build a recurring 1:1 agenda template for the manager-report pair below, designed to survive being run weekly for months without collapsing into pure status updates. MANAGER AND REPORT Engineering manager and a mid-level engineer who's been on the team for a year and a half. MEETING LENGTH AND FREQUENCY 30 minutes, weekly, Tuesday afternoons. WHAT THIS 1:1 HAS DRIFTED INTO BEING It's become a rundown of sprint ticket status that's already visible in the project tracker — nothing surprising or personal comes up anymore. REPORT'S STATED CAREER GOAL OR GROWTH AREA Wants to move toward a tech lead track and get more experience scoping projects before they're assigned, not just executing them. Structure the template with the report owning the majority of the agenda, not the manager — this is their meeting, not a manager-led check-in, and the template should say so explicitly at the top. Allocate roughly the given meeting length across three zones: a short section for anything genuinely time-sensitive that couldn't wait (capped tightly, since this is exactly the section that expands to eat the whole meeting if left uncapped), a section for whatever the report actually wants to raise that week (left open, prompted by a rotating question rather than a blank field, since a blank "anything else" field is what a tired report skips), and a recurring section tied to the stated career goal, so growth conversations happen on a predictable cadence rather than only when there's spare time left over. If the current-drift note describes a specific failure pattern (the meeting has become pure status updates, or gets cancelled whenever the manager is busy), add one explicit structural fix for that exact pattern rather than a generic reminder to "make time for 1:1s." WHAT NOT TO DO Do not include a generic "how are you doing" opener with no more specific prompt behind it — a template that only ever asks that gets a reflexive "fine" and burns the opening minutes on nothing. Do not make every section mandatory every week; name which section can be skipped in a light week so the template doesn't create its own pressure to fill time with filler. OUTPUT FORMAT The reusable agenda template itself (section names, rough time allocation, the rotating prompts for the open section), followed by one paragraph directly addressing the named current-drift pattern and the specific structural change meant to fix it.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
The well-documented failure mode of recurring 1:1s is that they quietly regress to status-update meetings because status updates are the path of least resistance for both parties when nothing more specific is on the agenda — a manager under time pressure defaults to asking about ticket progress, and a report with nothing pre-loaded defaults to answering with exactly that, so the drift is structural, not a one-time lapse, which is why a generic reminder to "make 1:1s more personal" rarely fixes it and this prompt instead builds the fix into the template's actual structure. Capping the time-sensitive-items section tightly targets the specific mechanism by which status updates crowd out everything else: without an explicit cap, urgent-feeling but low-value updates naturally expand to consume the full meeting because they feel more immediately actionable than a career conversation, even when they're objectively less important over a longer horizon. Using a rotating prompt instead of a blank "anything else" field addresses a real behavioral pattern: a tired or busy person facing an open-ended blank field defaults to "nothing, I'm good," while a specific rotating question (what's the most interesting problem you worked on this week, what's something you're stuck on that you haven't raised yet) actually produces an answer because it's concrete enough to react to rather than requiring the report to generate a topic from nothing. Building a recurring, guaranteed slot for the stated career goal rather than leaving growth conversations to "whenever there's time" directly counters the observed pattern where career development conversations are the first thing dropped under time pressure precisely because they don't feel urgent in any single week, even though their absence compounds into real career stagnation over a year.
What you get back
This is your meeting — you own the agenda. Time-Sensitive (5 min cap): anything that genuinely can't wait until next week. Your Topic (15 min, rotating prompt): 'What's something you're stuck on that hasn't come up yet?' Career Track (10 min, every other week): progress toward tech-lead scoping experience — what project could you help scope next sprint? Fix for the drift: sprint-ticket status moves out of this meeting entirely and into the async project tracker update, freeing the full 30 minutes for the two sections above.
Verified against
ChatGPT GPT-5.1 · 2026-08-10
Changelog
- 2026-08-10 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
