Home / Business & Strategy / Project Management

Project Context Brief That Guards Past Decisions

Gives the AI a brief of your project, what you are building, the decisions already taken and the conventions to follow, so it uses it in every answer, warns you when a request contradicts a decision and confirms it understood before starting.

project contextdecisionsconventionsai assistant
Project: [name]
What we are building: [description]
Decisions already taken: [list]
Conventions to respect: [list]

Rules for this conversation:
- Use this brief in every answer you give.
- If something I ask goes against a decision already taken, flag it.
- Before we begin, confirm that you have understood.
More in Project Management
Business Process Flow with Bottlenecks and FixesNewProject ManagementLays out the process flow for a business process you name, step by step, then flags the likely bottlenecks and suggests ways to make it more efficient.
Business process: [specific business process]

Task: create a process flow diagram for this process, written as numbered steps.

Then:
1. Identify the potential bottlenecks.
2. Suggest improvements to efficiency.
Change Management Plan for an AI Rollout in 6 Phases6 phasesNewProject ManagementPlans how a client gets employees to really adopt an AI initiative: a portrait of the most resistant employee, the change messaging, the best internal channels, a 90-day adoption plan, a funnel from rollout to retention and 7 resistance risks with mitigation wording.
  1. Phase 1 — Portrait of the resistant employee
    Context: my client is introducing [AI initiative] in [describe the organization].
    
    Task: help me sketch the employee who is most likely to push back against it.
    
    Describe:
    - their role
    - what they fear about AI
    - the rumors reaching them
    - the words they use when they talk about the change
    - what frustrates them day to day
    - how they have already tried to resist
    - where they let off steam (Slack, lunch breaks, 1-on-1s)
    
    Close with a single summary paragraph that I will use as the basis of my strategy.
  2. Phase 2 — Change messaging strategy
    Portrait of the resistant employee:
    [paste the portrait]
    
    AI rollout: [describe the rollout]
    
    Task: help me build the full set of change management messages for this rollout.
    
    Include:
    - the core narrative that leadership will tell
    - the specific value angle for frontline teams
    - 3 distinct framings, one per employee tier
    - the emotional triggers that bring resistance down
    - the 5 main objections employees will have but not voice, each with the reply leadership will give
  3. Phase 3 — Internal communication channels
    Context: my client is introducing [AI initiative] in an organization of [size].
    
    Task: considering where employees really pay attention and how real change usually reaches them, recommend the 3 best internal channels for communicating the change.
    
    For each channel, explain:
    - why it suits this workforce
    - which content performs best there
    - how much investment it requires
    - what success would look like
    
    Then list the channels to avoid, with the reason for each.
  4. Phase 4 — 90-day adoption plan
    Context: my client is introducing [AI initiative] in [team or function].
    
    Task: build a full change adoption plan covering 90 days.
    
    Include:
    - adoption pillars aligned with how employees think and feel
    - a week-by-week calendar of internal touchpoints (as a table)
    - moments where leadership is visible
    - the rhythm of training
    - metrics that reveal genuine adoption, as opposed to compliance on the surface
  5. Phase 5 — Funnel from rollout to retention
    Context: my client is introducing [AI tool] to [employee group].
    
    Task: design the full adoption funnel, from the first time people hear about it to lasting everyday use.
    
    Cover these stages:
    1. how the first announcement is received
    2. the campaign aimed at early adopters
    3. the training sequence for managers
    4. the moment of the mass rollout
    5. the retention strategy that turns early usage into a permanent habit
  6. Phase 6 — Resistance risks and mitigation
    Scope of the AI rollout:
    [paste the scope]
    
    Task: name the 7 largest risks of resistance in this rollout.
    
    For each risk, state:
    - where it appears
    - who in the organization will raise it first
    - the political price if leadership ignores it
    - the precise mitigation wording I should build into the rollout plan, so the issue is handled before it surfaces
Meeting Transcript to Decisions and Action Items for Slack or EmailNewProject ManagementTurns a meeting transcript into the decisions taken, the action items with their owners, the open issues and anything that needs a follow-up, formatted to paste directly into Slack or an email.
Meeting transcript:
[paste it]

Extract:
- the decisions that were made
- the action items, each with its owner
- the issues still open
- anything that requires a follow-up

Format the result so that I can paste it directly into Slack or an email.
Practical Framework for Managing a Team or ProjectNewProject ManagementBuilds a hands-on framework for running a team or project in your type of workplace, covering leadership approaches, communication systems, productivity methods and ways to resolve conflict.
Give me a practical framework for running [team or project] effectively in a [work environment, e.g. remote startup, hybrid agency, corporate department].

Organize it under these headings:
1. Leadership strategies
2. Communication systems
3. Productivity frameworks
4. Approaches to resolving conflict

Make every part fit that specific work environment.
PRD Template with User Stories and Success MetricsNewProject ManagementGenerates a reusable product requirements document (PRD) template for your type of product, including dedicated sections for user stories, technical specs and the metrics that define success.
Type of product: [type of product]

Task: produce a product requirements document (PRD) template that fits this product.

Include sections for:
- user stories
- technical specifications
- success metrics