Loading...
Community presentation
You are a senior IT project manager and executive presentation designer. Create a concise, professional slide presentation summarizing project accomplishments, upcoming delivera…
Create your own version
Use this visual direction as inspiration for a new Presenton deck.
Use this designCreator prompt
You are a senior IT project manager and executive presentation designer. Create a concise, professional slide presentation summarizing project accomplishments, upcoming deliverables, and items requiring confirmation. **Presentation title:** Project Status Update — FTAC Uniforma Platform & NOVO **Reporting date:** September 28, 2026 **Audience:** Management and project stakeholders **Tone:** Clear, factual, and results-focused. ### Source information **FTAC Uniforma Platform** - A meeting was held on Tuesday, September 22, 2026, with the Business Analyst (BA) and Project Manager (PM). - The project flow and deliverables were confirmed during the meeting. - Status: Flow and deliverables confirmed. Do not imply that development or delivery is complete. **NOVO — Fairmont Critical Items** - Critical items raised by Fairmont were developed and deployed by end of day on Tuesday, September 22, 2026. - Status: Development and deployment completed. - Client acceptance and deployment environment were not specified. **NOVO — Workforce Management** - User Acceptance Testing (UAT) was conducted on Wednesday, September 23, 2026. - Status: UAT conducted; results and sign-off were not provided. **NOVO — Document Checklist Enhancement** - An initial endorsement occurred on Tuesday, September 22, 2026. - Endorsement to Quality Assurance (QA) is scheduled for Tuesday, September 29, 2026. - The recipient of the initial endorsement was not specified. Keep it separate from the upcoming QA endorsement. - Status: QA endorsement scheduled. **NOVO — Document Checklist Detailed Activities** | Activity | Owner | Target date | Status / clarification | |---|---|---|---| | Deliver the Display Name update | Jojo | September 29, 2026 | Scheduled for delivery | | Load the Magsaysay, STCW, and Basic document sets | Not specified | Not specified | Activity listed; completion status not provided | | Confirm standardization of Flag and Position | Zai | Not specified | For confirmation | | Confirm the process for encoding master documents for a new principal | Zai | Not specified | For confirmation | | Use the internal tool to address the remaining documents without codes | Edson | Not specified | Action identified; completion status not provided | Treat the upcoming “Tuesday” delivery as September 29, 2026. Do not assume that all Document Checklist activities share this deadline or are prerequisites for QA endorsement. ### Slide structure Create a five-slide presentation: **Slide 1 — Executive Summary** - Summarize FTAC flow and deliverables confirmation. - Highlight NOVO critical-item deployment and Workforce Management UAT. - Highlight the upcoming Document Checklist QA endorsement and Display Name delivery. - Use a compact table with Project / Workstream, Key Update, and Status. **Slide 2 — FTAC Uniforma Platform** - Present the meeting date and participants by role. - Summarize confirmation of the project flow and deliverables. - Keep the update factual without inventing scope details or implementation commitments. **Slide 3 — NOVO Accomplishments** - Present Fairmont critical-item development and deployment on September 22. - Present Workforce Management UAT on September 23. - Clearly distinguish completed deployment from UAT execution. - Indicate that UAT results and sign-off were not provided. **Slide 4 — Document Checklist Action Tracker** - Present all five detailed Document Checklist activities in a readable table. - Include Activity, Owner, Target Date, and Status. - Clearly identify Jojo’s September 29 delivery. - Visually distinguish Zai’s two confirmation items from delivery and operational activities. - Use “Not specified” for missing owners or dates. **Slide 5 — Upcoming Milestones and Required Confirmations** - Show the two scheduled September 29 activities: - Document Checklist enhancement endorsement to QA. - Display Name update delivery — Jojo. - List the confirmation items: - Standardization of Flag and Position — Zai. - Master document encoding process for a new principal — Zai. - Identify missing tracking information separately: - Owner, schedule, and completion status for loading Magsaysay, STCW, and Basic document sets. - Schedule and completion status for Edson’s internal-tool activity. - Workforce Management UAT results and sign-off. - Do not describe missing information as a blocker unless explicitly confirmed. ### Design and content requirements - Use a clean corporate layout with navy, teal, and white. - Use large, readable text, consistent status labels, and generous spacing. - Keep each slide concise. Preserve every source activity without repeating excessive detail. - Use full dates instead of relative references. - Retain the names Jojo, Zai, and Edson exactly as provided. - Preserve “Magsaysay,” “STCW,” “Basic,” “Flag,” “Position,” and “Display Name” as supplied labels. - Do not invent owners, deadlines, progress percentages, testing outcomes, deployment environments, dependencies, or business benefits. - Do not claim that UAT passed, deployment was to production, QA endorsement is complete, or documents have already been loaded. - Label suggested actions as “Recommended”; do not present them as agreed commitments. - Include short speaker notes for each slide, explaining the updates without adding unsupported facts. ### Output Create the finished presentation if slide-generation tools are available. Otherwise, provide complete slide-by-slide content with titles, on-slide text, suggested layouts, and speaker notes.
Presentation overview
This community presentation was shared by Zagara Gaming PH as a complete 6-slide example. You are a senior IT project manager and executive presentation designer. Create a concise, professional slide presentation summarizing project accomplishments, upcoming delivera… The preview lets you review the full sequence in order, rather than judging the design from a single cover image.
Use it as a reference for planning your own deck: notice how the amount of information changes from slide to slide, where visual emphasis appears, and how repeated design choices help the presentation feel connected. Community examples are inspiration, not locked templates, so you can keep the ideas that fit your audience and replace anything that does not.
Learn from the example
Look at the job each slide performs. Identify where the deck introduces its subject, develops the main points, adds evidence or examples, and moves toward a conclusion.
Notice which element attracts attention first and how headings, supporting text, images, and data are separated. Strong hierarchy makes the intended reading order obvious.
Compare spacing, typography, color, and repeated components across the slides. Consistent rules help varied content feel like one presentation instead of unrelated screens.
Make it your own
Begin with your audience and the decision, lesson, or action the presentation should support. Replace the topic, examples, evidence, and visuals with material you can verify, then edit every slide for one clear takeaway. You can borrow the visual direction without copying the creator's wording or message. Presenton will use this community deck as a design reference while you develop content for your own purpose.
