OllaSuper
Home / Experts / Project Manager Expert
Build · Expert

Project Manager Expert

Sprint retros, RAID logs, status reports, async standups — the connective tissue.

Starter prompts

4 ways to start with PM.

Click any → opens in app with prompt pre-loaded
Sprint retro
→
What worked, what didn't
▸ Preview prompt
Write a sprint retrospective summary. Three columns: What went well, What didn't, What we'll change next sprint. Three items per column, each with an owner.
RAID log entry
→
New risk this week
▸ Preview prompt
Draft a RAID log entry for a new risk: dependency on a third-party API's uptime. Include description, impact rating (1–5), probability (%), mitigation plan, owner, review date.
Status report (RAG)
→
Red / amber / green
▸ Preview prompt
Compose a one-page project status report. RAG status with reason, milestones (done / on track / at risk), budget vs. actual, top 3 risks, top 3 asks of leadership.
Async standup
→
Yesterday / today / blockers
▸ Preview prompt
Write my async standup update for today. Yesterday I shipped a code review and a small fix; today I'll start the email template integration; blocker is waiting on copy from marketing. Under 80 words.
What it does

Tasks PM ships every week.

Cadence
  • Async standup updates
  • Sprint retros
  • Weekly status reports
  • Bi-weekly stakeholder updates
Risk
  • RAID log entries
  • Risk register reviews
  • Mitigation memos
  • Escalation notes
Reports
  • Project status (RAG)
  • Milestone reports
  • Budget vs. actual narratives
  • Quarterly portfolio review
Worked sample

A real PM chat.

No edits · no cherry-picks
You
Weekly project status report for the calendar-sync project. Currently amber.
PM

Project: Two-way calendar sync — Week of 9 Jun

RAG: 🟡 Amber

Why amber: The Google OAuth scope review is taking longer than the 2-week estimate. We're at week 3 with no green light. This is the only thing blocking us from internal eat-our-own-dogfood.

Milestones

  • 🟢 OAuth scope setup (Outlook): done, 1 week ahead
  • 🟡 OAuth scope setup (Google): blocked on Google review (week 3 of 2-week SLA)
  • 🟢 Webhook intake service: provisioned, in load testing
  • 🟢 Event write logic: code complete, in code review
  • 🟡 Internal dogfood: blocked by Google OAuth

Budget vs. actual: ₹4.2L spent of ₹6.8L approved. Tracking 8% under for the quarter; we'll likely come in at 90% of budget.

Top 3 risks

  1. Google OAuth review continues to slip — high impact, medium probability. Mitigation: I've escalated to our Google partnerships contact for a status update by EOD Friday.
  2. Conflict-resolution edge case (user reschedules in both tools before sync) — medium impact, low probability. Mitigation: shipping with "system-of-record = our system" as default; revisit if user complaints exceed 10/month post-launch.
  3. Microsoft Graph rate limits at scale — medium impact, low probability. Mitigation: load test next week at 5× expected traffic.

Top 3 asks of leadership

  1. Anyone with a Google Cloud Platform escalation contact, please ping me
  2. Approval to start the public beta on 100 customers in 2 weeks, conditional on Google OAuth being unblocked by then
  3. Pre-approval for ₹1.2L additional budget if we need to extend the contractor's engagement by 2 weeks (backup plan)
✦ grounded in your files + site · memory on · 200M proxies + 4,000 tools
Pairs well with

PM works best alongside these 2.

Engineering Expert Code reviews, RFCs, design docs, post-mortems — direct, technical, blameless. Product Expert PRDs, beta launches, roadmaps, user-interview summaries — what to ship and why.
Put PM on your team.
Plus 18 other experts. One subscription. No setup.
Start free →