Know what matters this week without status theater.
Act as a thoughtful operations & teams specialist. The task is weekly team pulse. Context: [team, priorities, blockers, meeting cadence].
1. Design an async update with outcomes and asks.
2. Define a 20-minute meeting agenda for decisions only.
3. Write the escalation path.
4. Set a weekly completion signal..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful operations & teams specialist. The task is handoff checklist. Context: [task, systems, next owner, deadline].
1. List verified state, pending work, risks and key links.
2. Require readback on critical items.
3. Add a duplicate-action check.
4. Write an example handoff..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Send a problem to the right person at the right time.
Act as a thoughtful operations & teams specialist. The task is escalation ladder. Context: [incident types, roles, hours, severity].
1. Define severity in observable terms.
2. Map first, second and emergency contacts.
3. Set response windows and status cadence.
4. Write a short escalation template..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Interview candidates against the job, not charisma.
Act as a thoughtful operations & teams specialist. The task is hiring scorecard. Context: [role, outcomes, must-have skills, panel].
1. Define four job-relevant competencies and behavior anchors.
2. Write structured questions and work sample.
3. Assign interviewer coverage.
4. Set scoring rules before meeting candidates..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Help someone become useful without guessing where to ask.
Act as a thoughtful operations & teams specialist. The task is new hire buddy plan. Context: [role, team, tools, first-month goals].
1. Schedule first-week introductions and access checks.
2. Make a searchable question channel.
3. Define three early wins.
4. Write buddy check-ins and a week-four feedback loop..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful operations & teams specialist. The task is retrospective that changes something. Context: [project, participants, incidents, time].
1. Collect facts and timeline before opinions.
2. Facilitate start, stop and continue with evidence.
3. Limit to two improvements with owners.
4. Set a date to test whether changes worked..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful operations & teams specialist. The task is decision log. Context: [decision, options, owner, evidence, date].
1. Record context, options, assumptions and why one won.
2. Include dissent and revisit triggers.
3. Write a compact template.
4. Create a retrieval naming convention..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful operations & teams specialist. The task is vendor comparison sheet. Context: [need, candidates, budget, requirements].
1. Make weighted criteria and deal-breakers.
2. Include implementation and exit costs.
3. Score evidence separately from sales claims.
4. List reference questions and the final decision rule..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful operations & teams specialist. The task is process bottleneck finder. Context: [workflow steps, handoffs, throughput, pain].
1. Map cycle time versus active time.
2. Identify queues and rework loops.
3. Choose one constraint to fix first.
4. Design a two-week before-after measurement..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Catch expensive mistakes without creating 100 boxes.
Act as a thoughtful operations & teams specialist. The task is quality checklist design. Context: [deliverable, recurring errors, reviewers, time budget].
1. Rank failure modes by cost and frequency.
2. Write concise checks with clear pass/fail evidence.
3. Place checks at the step where correction is cheapest.
4. Review false alarms monthly..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Commit to a month without pretending everyone has 40 free hours.
Act as a thoughtful operations & teams specialist. The task is team capacity planner. Context: [team, leave, meetings, projects, deadline].
1. Compute realistic focus capacity per person.
2. Map committed and unplanned work.
3. Propose a protected buffer.
4. Show what must drop if an urgent request arrives..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Keep people informed while the cause is still unknown.
Act as a thoughtful operations & teams specialist. The task is incident status update. Context: [incident, impact, audience, current evidence].
1. Write a factual status with what is affected, what is not known and next update time.
2. Avoid unverified root-cause claims.
3. Give a short internal and external version.
4. Define resolution criteria..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Ask another team for help with everything they need to decide.
Act as a thoughtful operations & teams specialist. The task is cross-team dependency note. Context: [request, owner, deadline, impact, alternatives].
1. Write a concise dependency brief with exact deliverable and why date matters.
2. Offer scoped options.
3. Make an explicit acknowledgment request.
4. Set a fallback if they cannot take it..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful operations & teams specialist. The task is remote team norms. Context: [team size, time zones, tools, pain points].
1. Define channel purposes and response expectations.
2. Write decision and documentation rules.
3. Set quiet hours and urgency exceptions.
4. Create an onboarding cheat sheet..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful operations & teams specialist. The task is delegation brief. Context: [goal, deadline, recipient's skill, constraints].
1. Describe outcome and done test.
2. Specify autonomy and required checkpoints.
3. List resources and risks.
4. Write the first handoff message and a non-micromanaging follow-up..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Reduce random interruptions without blocking help.
Act as a thoughtful operations & teams specialist. The task is office hours design. Context: [expert team, requester types, common questions].
1. Choose frequency and intake form.
2. Define what is eligible versus urgent.
3. Write a queue triage rule.
4. Measure wait time and repeat questions to improve docs..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Show exceptions that need action, not just pretty charts.
Act as a thoughtful operations & teams specialist. The task is operations dashboard. Context: [process, metrics, thresholds, users].
1. Choose three leading and two lagging measures.
2. Specify refresh cadence and data owner.
3. Design alert thresholds and drill-down paths.
4. Name decisions each visual supports..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Build coverage while distributing undesirable slots fairly.
Act as a thoughtful operations & teams specialist. The task is shift schedule fairness. Context: [staff, availability, legal constraints, coverage].
1. Define coverage and rest rules to verify.
2. Propose rotation and preference collection.
3. Make a conflict-resolution rule.
4. Show how swaps are recorded and approved..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Change a procedure without trapping people on old instructions.
Act as a thoughtful operations & teams specialist. The task is standard work update. Context: [old SOP, change, affected roles, start date].
1. Write a diff summary in plain language.
2. Identify training and access updates.
3. Archive old version visibly.
4. Define a feedback window and rollback trigger..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Remove meetings that no longer pay for themselves.
Act as a thoughtful operations & teams specialist. The task is meeting portfolio audit. Context: [recurring meetings, attendees, agendas, decisions].
1. Classify decide, coordinate, inform or habit.
2. Convert inform-only to async.
3. Redesign the essential meetings with decision owner and pre-read.
4. Calculate hours returned..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.