Turn a vague two-sentence project brief into a detailed execution plan | AI Prompt for Productivity — teliprompt

5 days ago•

Turn a vague two-sentence project brief into a detailed execution plan

Views

3.4K

Copies

1.2K

Likes

474

Comments

0

Copy rate

34.0%

Prompt

You are a senior program manager with 15 years of experience running cross-functional projects. I'll give you a short project brief — sometimes only two sentences — and you need to expand it into a comprehensive execution plan.

Project brief: "[project_brief]"
Team size: [team_size]
Timeline: [timeline]

Your execution plan must include:
1. Project objective restated as a measurable goal
2. Stakeholder map (RACI matrix)
3. Work breakdown structure (WBS) with 3 levels of depth
4. Phase-by-phase timeline with milestones
5. Risk register (top 5 risks with mitigation strategies)
6. Resource allocation overview
7. Definition of done for each major deliverable
8. Communication plan (cadence, channels, audiences)

Be specific and actionable. No filler. Every line item should be something a team member can act on immediately.

Customise this prompt

Fill in 3 variables to personalise this prompt

Preview

You are a senior program manager with 15 years of experience running cross-functional projects. I'll give you a short project brief — sometimes only two sentences — and you need to expand it into a comprehensive execution plan. Project brief: "[project_brief]" Team size: [team_size] Timeline: [timeline] Your execution plan must include: 1. Project objective restated as a measurable goal 2. Stakeholder map (RACI matrix) 3. Work breakdown structure (WBS) with 3 levels of depth 4. Phase-by-phase timeline with milestones 5. Risk register (top 5 risks with mitigation strategies) 6. Resource allocation overview 7. Definition of done for each major deliverable 8. Communication plan (cadence, channels, audiences) Be specific and actionable. No filler. Every line item should be something a team member can act on immediately.

# Execution Plan: Internal Knowledge Base Migration **Original Brief:** "We need to move our internal wiki from Confluence to Notion before Q3. The content is a mess and nobody can find anything." **Measurable Objective:** Migrate 100% of active Confluence content (pages edited in the last 18 months) to a restructured Notion workspace, achieving a 90%+ employee satisfaction score on findability within 60 days of launch. --- ## 1. Stakeholder Map (RACI) | Activity | Project Lead | IT Ops | Content Owners | Dept Heads | End Users | |---|---|---|---|---|---| | Content audit | A | C | R | I | — | | IA design | R | C | C | A | I | | Migration tooling | I | R | — | — | — | | Content cleanup | C | — | R | A | — | | QA & validation | A | R | R | I | C | | Training & rollout | R | C | I | A | R | **Legend:** R = Responsible, A = Accountable, C = Consulted, I = Informed --- ## 2. Work Breakdown Structure ### Phase 1 — Discovery & Audit (Weeks 1–2) - 1.1 Export full Confluence space inventory (page count, last-edit dates, ownership) - 1.2 Categorize pages: Active (edited <18 mo), Stale (18–36 mo), Archive (>36 mo) - 1.3 Interview 8–10 power users on pain points and search patterns - 1.4 Map existing taxonomy vs. actual navigation paths (analytics review) - 1.5 Produce audit report with content volume per department ### Phase 2 — Information Architecture (Weeks 3–4) - 2.1 Design new Notion workspace structure (team spaces, shared databases, tags) - 2.2 Create naming conventions and template library (5 core templates) - 2.3 Define metadata schema (owner, department, review-date, status) - 2.4 Validate IA with 3 department heads via card-sorting exercise - 2.5 Finalize migration priority order (high-traffic pages first) ### Phase 3 — Migration & Cleanup (Weeks 5–8) - 3.1 Configure Notion workspace (SSO, permissions, integrations) - 3.2 Run automated migration tool for bulk content transfer - 3.3 Manual cleanup pass — fix broken links, reformat tables, update screenshots - 3.4 Content owners review and approve their migrated sections - 3.5 Redirect old Confluence URLs to new Notion pages ### Phase 4 — Validation & Launch (Weeks 9–10) - 4.1 QA checklist: links, images, permissions, search indexing - 4.2 Beta launch to 20 volunteer users, collect structured feedback - 4.3 Fix critical issues from beta feedback - 4.4 Company-wide launch with announcement and training sessions - 4.5 Decommission Confluence read-write access (keep read-only for 60 days) --- ## 3. Risk Register | # | Risk | Likelihood | Impact | Mitigation | |---|---|---|---|---| | 1 | Content owners don't prioritize cleanup | High | High | Assign dedicated cleanup sprints; get dept head sign-off on deadlines | | 2 | Automated migration breaks formatting | Medium | Medium | Run test migration on 50-page sample first; build cleanup playbook | | 3 | Users resist adoption | Medium | High | Appoint department champions; track adoption metrics weekly | | 4 | SSO/permissions misconfiguration | Low | High | IT runs permission audit before launch; test with 5 accounts across roles | | 5 | Timeline slips due to content volume | Medium | Medium | Prioritize top 200 pages by traffic; migrate long-tail content post-launch | --- ## 4. Communication Plan - **Weekly standup** (15 min, Slack huddle): Project team — progress, blockers - **Biweekly update** (async, email): Dept heads — milestone status, decisions needed - **Launch announcement** (all-hands + Slack): Full company — what changed, where to go, how to get help - **Post-launch check-in** (week 2 and week 4): Survey + office hours for questions --- ## 5. Definition of Done - **Discovery:** Audit report approved by project sponsor - **IA:** Workspace structure validated by 3+ department leads - **Migration:** 100% of active pages transferred, 0 broken internal links - **Launch:** 80%+ of employees have logged into Notion; satisfaction survey sent - **Close:** Confluence read-only archived; retrospective completed