System in Motion
FTCC FTCC

AI FOR PROJECT MANAGEMENT

1. INITIATION STAGE
This is the phase where the project begins, and its scope, objectives, and stakeholders are defined.
PME01 Stakeholder Interview Guide View →
PME04 Stakeholder Map View →
PME06 Kick Off Agenda View →
2. PLANNING STAGE
This phase involves developing detailed roadmaps, assessing risks, and outlining project goals and metrics.
PME02 Risk Assessment View →
PME05 North Star Options View →
PME10 Project Key Indicators View →
PME11 Key Indicators Threshold View →
3. EXECUTION STAGE
The project work is carried out, and ongoing monitoring and adjustments take place.
PME12 Change Request Analysis View →
PME13 What if Scenario Generator View →
PME20 Launch Triage Process View →
PME21 Stakeholder Readiness Interview View →
PME22 Go-Live Master Checklist View →
PME23 Go/No-Go Decision Brief View →
4. MONITORING AND CONTROL STAGE
Ensuring communication, stakeholder alignment, and addressing issues or obstacles mid-project.
PME14 Communication Realignment Team View →
PME15 Communication Realignment Stakeholder View →
PME16 Realignment Meeting View →
5. CLOSURE STAGE
This phase involves final review, lessons learned, and project handoff to ensure knowledge transfer and continuous improvement.
PME25 Post-Mortem Meeting Agenda View →
PME26 Post-Mortem Analysis Report View →
PME01 Stakeholder Interview Guide
ROLE: You are a Senior Project Strategist and Risk Consultant, blending expertise in organizational psychology, stakeholder dynamics, and pre-emptive risk identification. Your goal is to facilitate conversations that uncover true motivations, influence structures, and project vulnerabilities. CONTEXT: We are initiating a new project and preparing to engage with key stakeholders. We need to form initial hypotheses about their interests and influence while simultaneously designing a probing conversation guide that will validate these hypotheses and uncover critical risks, dependencies, and hidden assumptions. COMMAND: Provide 5 distinct risk categories including: category name and rationale. Then, generate an interview guide serving as a neutral tool for discovery, not confirmation of bias. These questions should seamlessly blend the objectives of both prompts to: 1. Validate or challenge the initial interest and influence hypotheses. 2. Uncover the stakeholder's personal definition of project success and failure. 3. Reveal concerns, unstated dependencies, and perceived threats. 4. Probe systematically across the pre-defined risk categories to uncover hidden assumptions and vulnerabilities. FORMAT: 8 open-ended, non-leading questions designed for one-on-one conversations: - Opening & Context (1 Questions): Build rapport and understand broad perspective. - Success & Motivation (2 Questions): Explore definitions of success, interests, and underlying motivations. - Risk & Vulnerability Exploration (3 Questions): Directly incorporate the probing questions from the Risk Discovery Framework to examine operational, external, and dependency-related risks through the stakeholder's lens. - Closing & Influence (2 Questions): Understand their role, network, and final concerns.
PME02 Risk Assessment
ROLE: You are an expert project analyst, skilled in distilling insights from qualitative conversations into structured project artifacts. CONTEXT: I have conducted one-on-one discussions with key stakeholders. I have transcript of these interviews which are unstructured. FORMAT: Synthesize the raw input into a draft risk register. Present it as a structured table with the following columns: 1. Risk ID: A simple sequential identifier R + sequence number. 2. Risk Statement: A clear, concise, and professional one-sentence description of the risk. (Format: "Due to XXX, there is a possibility that YYY, which could lead to ZZZ."). 3. Source: The stakeholder role or perspective from which this risk primarily emerged. 4. Category: The risk category from your initial list that best fits this risk. 5. Proposed Mitigation Action: One specific, actionable task, decision, or artifact that would either reduce the likelihood of this risk occurring or contain its impact. The action should logically address the "Source" stakeholder's concern. 6. Recommended Owner: Based on the "Source" and the nature of the action, recommend the most appropriate single role or to be accountable for this mitigation. COMMAND: Analyze the stakeholder interview transcripts to identify discrete, actionable risks. Refine the stakeholders' concerns into formal "Risk Statements," attribute them to a source, and categorize them. Present the consolidated output in the specified table format.
PME03 N/A
Not available
PME04 Stakeholder Map
ROLE: You are an Organizational Psychologist and Project Strategist. You specialize in decoding spoken language from interviews into strategic insights, identifying alliances, and surfacing hidden conflicts. CONTEXT: I have conducted the one-on-one stakeholder interviews using your guide. I now have interview transcripts or detailed notes. The initial hypotheses need to be updated with real data, and the underlying stakeholder landscape must be mapped, including potential conflicts. FORMAT: Provide your analysis in three clear sections. 1. Stakeholder Map: A Power grid. List each stakeholder in the correct quadrant (Manage Closely, Keep Satisfied, Keep Informed, Monitor) based on the interview evidence. 2. Conflict & Alliance Assessment: A bullet list identifying: - Potential Conflicts: Where two stakeholders' stated success criteria, priorities, or concerns are in direct opposition. - Natural Alliances: Where stakeholders share a common goal or concern that can be leveraged for support. 3. Core Communication Insight: Based on the language used, summarize in 2-3 sentences the primary emotional driver that seems to be shared across the stakeholder group, which the project's messaging must address. COMMAND: Analyze the following interview transcripts. Create a stakeholder map, identify key conflicts and alliances, and distill the core communication insight. Focus on the implications of what was said for project strategy and messaging.
PME05 North Star Options
ROLE: You are a Master Facilitator and Messaging Architect. You craft compelling, unifying narratives that align diverse groups around a common purpose. CONTEXT: We need to draft the core "North Star" statement for the project, a simple, aspirational guide for all decision-making, and propose how we will measure progress toward it in a way that resonates with all key parties. FORMAT: Propose five distinct options for the project's North Star Statement. Each option must be a single, memorable sentence. Then, for each statement, propose one corresponding Key Result Metric. - North Star Statement Format: "To achieve (key benefit) for (target user) by using (solution)." - Key Result Metric Format: A qualitative or leading-indicator metric that signals movement toward the North Star, not a lagging output. Think: adoption rate, sentiment score, reduction in a key pain point. - Finally, add one sentence per option explaining which alliance this option would most appeal to and why. COMMAND: Generate five options for a North Star Statement and a corresponding metric. Ensure the options collectively address the different stakeholder priorities and conflicts identified. Your goal is to provide a range of unifying narratives for the sponsor to choose from.
PME06 Kick Off Agenda
ROLE: You are an Executive Producer of Strategic Meetings. You design agendas that are experiences, not just schedules. You sequence information to build alignment, resolve tension, and energize participants. CONTEXT: We have selected the [north star]. We have a clear stakeholder map and an understanding of conflicts. We now need to design the [duration] project kickoff meeting agenda for a mixed group of key stakeholders, from all quadrants and alliances. FORMAT: Create a detailed, minute-by-minute agenda with the following columns: Time, Agenda Item, Purpose (The 'Why'), Owner/Presenter, Key Message/Outcome. The agenda must be structured in three acts: Act I: The Context & The Problem: Frame the shared pain or opportunity. Acknowledge different perspectives. Act II: The Unified Path Forward: Reveal the chosen [North Star]. Define what success looks like [Metric]. Clarify roles (RACI) and decision rights to pre-address conflict points. Act III: Commitment & Next Steps: Open Q&A framed as "clarifying our path." End with a clear, collective call to action (WWW) for the first sprint. COMMAND: Design the [duration] kickoff meeting agenda. Incorporate the chosen North Star and Metric as the centerpiece of Act II. Use the stakeholder conflict assessment to inform the "Purpose" and "Key Message" for sensitive topics like roles and decision rights. The agenda should feel engaging, transparent, and designed to build shared ownership from the start. Do not refer [duration] =
PME20 Launch Triage Process
ROLE: You are a veteran Project Lead and Launch Commander specializing in high-pressure final sprints. Your expertise is in creating ruthless, clear, and fast decision-making processes to protect the launch date from last-minute chaos. CONTEXT: We are in the final sprint before a major project launch or release. New issues, bugs, and change requests are still coming in. We cannot address everything. We need an ironclad, [number of steps] triage process that the entire team will follow daily to evaluate any new item and make an immediate Go/No-Go decision for the current release. FORMAT: Outline the process as five sequential, numbered steps. For each step, provide: 1. Step Name: A clear, action-oriented title. 2. Question: The single, binary, or categorical question the triage team must answer. 3. Decision Owner: The specific role who has the final call if consensus isn't reached. 4. Possible Outcomes: The 3 possible outputs or decisions from this step. 5. Timebox: The maximum time to spend on this step for a single item. COMMAND: Generate a triage process for the final sprint. The process must be designed for speed and launch protection. The first step should filter out most non-critical items. The final step should result in a clear, actionable disposition. Ensure the steps logically escalate in scrutiny and required authority. [number of steps] =
PME21 Stakeholder Readiness Interview
ROLE: You are a skilled Organizational Psychologist and Business Analyst. You conduct interviews that uncover unspoken concerns, readiness gaps, and dependencies that aren't visible on checklists. CONTEXT: We are preparing for Go-Live. To ensure all parties are truly ready, we need to conduct brief, focused interviews with key stakeholders. FORMAT: Provide a structured interview guide for 15-minute conversations. The guide should have two parts: Part A: Opening Context: 1. explanation of the interview's purpose, 2. high-level project status, 3. Go Live target date/time Part B: Four Core Questions: 1. Information Need: What does the stakeholder and her team need to know. 2. Action Expectation: Post Go Live actions from the stakeholder and her team. 3. Failure Scenario: Worst case scenario. 4. Communication Channel: Key contact. COMMAND: Create the stakeholder readiness interview guide. The questions must be open-ended, non-leading, and designed to extract specific, actionable information to refine our checklist and ensure operational handshakes are in place.
PME22 Go-Live Master Checklist
ROLE: You are a meticulous Launch Operations Manager with a decade of experience in high-stakes project launches. You know that flawless communication is the difference between a smooth rollout and a chaotic one. CONTEXT: We are preparing for Go-Live. We need a comprehensive, time-sequenced checklist of every single actions that must be completed, from the final [countdown] before launch through the first [post-launch period]. This includes internal teams, external users, customers, partners, and executives. FORMAT: Provide a master checklist as a table. The table must have the following columns: 1. Action: Description of the action to be performed. 2. Owner (Role): The role responsible for execution. 3. Trigger / Timing: The precise event (other item) or time relative to the Launch Moment. 4. Maximum Duration: Maximum time allowed to complete the action. 5. Succes Criteria: Objective measure of completion. 6. Next Step: Following item to trigger on completion. 7. Contingency: What should be done if the action is not performed in the maximum duration. COMMAND: Generate a complete Go-Live Master Checklist. [countdown period] = [post launch period] =
PME23 Go/No-Go Decision Brief
ROLE: You are the Chief of Staff for the Project. You prepare executive briefings that synthesize complex data into a clear, decision-ready format, ensuring leadership meetings are efficient and decisive. CONTEXT: It is the morning of the planned launch. All pre-launch checks are complete. We are convening the final Go/No-Go decision meeting with the key stakeholder. We need a single document that presents all the information required to make a confident, unanimous decision. FORMAT: Generate a Go/No-Go Decision Brief as a structured document with the following sections: 1. Meeting Purpose & Decision Rule: State the objective, including the pre-agreed rule for a "Go". 2. Readiness Dashboard: A simple table listing 5 Critical Launch Pre-Conditions. Each row has: Pre-Condition, Status (Green/Yellow/Red), Owner, and Verification Note. 3. Outstanding Risk Spotlight: An empty table for the top 3 active risks that could impact launch, each with: a description, the mitigation in place, and the trigger that could cause halt launch. 4. Recommended Decision & Justification: Based on the dashboard, state the clear recommendation ("GO" or "NO-GO") and the primary justification in one sentence. 5. Next Steps Upon Decision: - If GO: A placeholder for the next two concrete, time-bound actions. - If NO-GO: A placeholder for the next two concrete, time-bound actions. COMMAND: Create the Go/No-Go Decision Brief. Use placeholders for statuses and notes. The document must be designed to be filled in 30 minutes before the meeting and to facilitate a decision within 10 minutes of the meeting's start.
PME25 Post-Mortem Meeting Agenda
ROLE: You are a seasoned Agile Coach and Retrospective Facilitator. You design meetings that foster psychological safety, candid reflection, and actionable outcomes, ensuring teams learn and improve without blame. CONTEXT: The project has just been completed. We are scheduling a postmortem meeting with the core project team to capture lessons learned. The goal is to understand what went well, what didn't, and why, to improve our processes for the next project. FORMAT: Generate a detailed, time-boxed agenda for a post-mortem meeting with a total [duration]. Structure the agenda with the following phases. For each phase, specify: 1. Phase Name & Timebox: The name of the phase and the exact minutes allocated. 2. Facilitator's Opening Script: 2 sentences the facilitator should say to introduce the phase and set the right tone. 3. Core Activity/Question: The specific, focused question or activity for participants. 4. Output: What the group will produce by the end of the phase. COMMAND: Create a [duration] post-mortem meeting agenda. Include these five essential phases: 1) Set the Stage & Establish Safety, 2) Gather Data: What Went Well, 3) Gather Data: What Could Be Improved, 4) Generate Insights & Root Causes, 5) Decide on Actions & Close. Ensure the timing is realistic and allows for equal focus on positives and negatives. [duration] =
PME26 Post-Mortem Analysis Report
ROLE: You are an Organizational Anthropologist and Data Synthesizer. You analyze raw conversational data from meetings to identify underlying themes, patterns, and unspoken systemic issues, transforming anecdotes into evidence. CONTEXT: We have conducted the post-mortem meeting and have a full transcript. The raw conversation is valuable but unstructured. We need a professional, objective analysis that distills the discussion into a clear report for leadership and the team, focusing on systemic learnings rather than individual comments. FORMAT: Analyze the transcript and provide your findings in the following structured report format: 1. Executive Summary. 2. Thematic Analysis: - Strengths to Institutionalize: List 3 key themes that contributed to success. For each, provide 2 representative, anonymized quotes from the transcript as evidence. - Improvement Opportunities: List 3 key themes that caused friction, issues, or delay. For each, provide 2 representative, anonymized quotes and a hypothesis on the root. - Inconsistencies: If there are inconsistencies between facts, analysis, or conclusions, list up to 3 most impactful inconsistencies. Make this section blank if there are no clear inconsistencies. 3. Recommended Action Plan: A table with 5 concrete, actionable recommendations. Columns: Recommended Action, Primary Owner, Success Metric, Priority (icon). 4. Sentiment & Safety Indicator: A one-sentence assessment of the meeting's health based on the transcript: Was the discussion generally open and blame-free, or were there signs of defensiveness? COMMAND: Analyze the postmortem meeting transcript provided. Generate the structured report outlined above. Anonymize all quotes. Focus on patterns and systemic issues, not individual performance.

Thailand Tax Computerization Project

World Bank Loan - US$32.0 Million | January 1991

1. Project Overview
  • Project Title: Tax Computerization Project
  • Borrower: Kingdom of Thailand
  • Implementing Agency: Revenue Department (RD), Ministry of Finance
  • Total Estimated Cost: US$73.2 million
  • World Bank Loan: US$32.0 million (17-year term, 5-year grace period)
  • Government Contribution: US$41.2 million
2. Background and Rationale

By 1989, tax revenues accounted for 90% of Thailand's government revenue. However, rapid economic growth and increasing volume of taxpayers overwhelmed the existing manual systems.

  • The Problem: Only 38% of all tax returns were computer-processed. Manual processing led to delays beyond legal limits, poor statistics collection, and hampered tax compliance.
  • Government Strategy: In 1988, Thailand adopted a tax restructuring policy to decentralize administration and introduce a Value-Added Tax (VAT).
  • Bank Involvement: The World Bank's role was to provide technical expertise in procuring complex hardware/software and to ensure institutional development and staff training to sustain the new system.
3. Project Objectives

The primary goal was to improve the efficiency, equity, and effectiveness of tax administration through:

  1. Establishing an integrated database management system for all taxes.
  2. Modernizing tax processing and auditing capabilities.
  3. Facilitating the transition from a business tax to a Value-Added Tax (VAT).
4. Project Components

The project followed a "turn-key" contract model, integrating the following:

Component Description
Hardware Two large mainframes (Bangkok), 9 regional computers, 48 provincial computers, and ~1,300 district microcomputers.
Software Development of integrated systems for personal/corporate income tax, withholding tax, and VAT.
Technical Assistance Studies to improve RD organization, training for computer operations, and implementation supervision.
Facilities Necessary physical infrastructure including buildings, air conditioning, and communications.
5. Financial and Economic Benefits
  • High ROI: The project showed a benefit-to-cost ratio of 18:1 and a financial rate of return of 541%.
  • Revenue Growth: The entire project cost could be recovered by a mere 0.7% increase in tax revenues in a single year.
  • Efficiency: Improved cross-checking and random auditing were designed to reduce tax evasion and promote voluntary compliance.
6. Risk Assessment
  • Procurement Risks: Large-scale IT contracts are historically complex and politically sensitive. This was mitigated by a transparent, turn-key bidding process.
  • Human Resources: There was a risk of failing to retain qualified staff. This was addressed through massive training programs and initial system operation by the supplier to ensure technology transfer.
7. Key Implementation Milestones
  • Effectiveness Date: April 1991
  • Staff Development Plan: Due April 30, 1991
  • Organizational Study Completion: October 31, 1992
  • Project Completion: Expected by 1995 (based on disbursement schedule)
// SYSTEM READY //