Artificial Idea | AI careers · practical prompts · no hype Thursday, October 9, 2025 · Issue #20 · Prompt Tutorial
The screening paradox
5 prompts that turn meeting notes into action plans instantly
Meetings are where decisions get made and forgotten in the same hour. These five prompts ensure the decision survives the room.
Issue #19 made the case that the professionals advancing through the AI transition are those who make their strategic contributions visible rather than absorbing additional volume quietly and hoping someone notices. Visibility requires communication. And one of the most consistent places where professional visibility is either built or lost is in the written record that follows a meeting.
Most meeting notes are a liability disguised as a deliverable. They are long enough to suggest thoroughness and vague enough to be useless. They record what was said without capturing what was decided. They list action items without establishing ownership. They are read once by the person who wrote them and never again by anyone else. Two weeks after the meeting, the decisions made in it are being relitigated because nobody can agree on what was actually agreed.
This is not a minor administrative problem. A 2024 study by the Project Management Institute found that poor meeting documentation was cited as a contributing factor in 67% of project failures examined, with the most common failure mode being the gap between what participants believed had been decided and what the written record actually captured. That gap is not usually the result of dishonesty. It is the result of meeting notes that were written to record rather than to drive action, and that therefore failed at the only function that justifies writing them.
These five prompts fix that. Each one addresses a specific meeting type with a specific output requirement. Together they cover the majority of the meetings that consume a knowledge worker's week.
Prompt 1: The decision meeting summariser
The problem it solves: capturing what was actually decided in a meeting where multiple options were discussed and the path forward needs to be unambiguous to everyone who was in the room and everyone who was not.
You are a chief of staff helping me document
a meeting in a way that creates clarity
and accountability rather than just
a record of what was discussed.
Here are my raw notes from the meeting:
[paste notes]
Meeting context: [who attended, what the
meeting was convened to decide, and
any relevant background]
Please produce a meeting summary structured
as follows:
1. Decision made: a single, unambiguous
statement of what was decided,
written so that someone who was
not in the room cannot misinterpret it
2. What was considered: the two or three
alternative options or perspectives
that were discussed before the
decision was reached, in one sentence each
3. What was explicitly ruled out:
any options or approaches that
were actively rejected and should
not be revisited without new information
4. Action items: each item on a separate
line with owner name, specific
deliverable, and deadline
5. Open items: questions or dependencies
that remain unresolved and need
resolution before the decision
can be fully implemented,
with a named owner for each
Flag anything in my notes that is
ambiguous enough that the summary
could be read in more than one way.
I would rather know about the ambiguity
now than discover it when someone
acts on a different interpretation.
The section on what was explicitly ruled out is the one most meeting summaries omit and the one that prevents the most wasted time. Decisions made in meetings are frequently relitigated not because participants disagree with the outcome but because they do not remember that a specific alternative was considered and rejected. Documenting the rejection is as important as documenting the decision.
Prompt 2: The project status meeting converter
The problem it solves: turning a project update meeting, which typically produces a long set of notes covering multiple workstreams at varying levels of relevance, into a focused document that tells stakeholders what they actually need to know.
You are a programme manager helping me
produce a project status summary that
senior stakeholders will actually read
and act on.
Raw notes from the status meeting:
[paste notes]
Project context: [project name, current
phase, key stakeholders, and the
primary concerns or questions
stakeholders have about this project
right now]
Please produce:
1. Overall status in one sentence:
on track, at risk, or off track,
with the single most important
reason for that assessment
2. Progress since last update:
the two or three most significant
things that moved forward,
stated in terms of outcomes
not activities
3. Issues requiring attention:
any problems, blockers, or risks
that require a decision or action
from someone outside the project team,
each with a specific ask and deadline
4. Decisions needed: explicit questions
that need answers from stakeholders
before the project can proceed,
with the consequence of delay
stated for each
5. Next milestone: what the team
will deliver by the next update,
stated specifically enough that
everyone will agree on whether
it was achieved
Constraints: Maximum one page.
Lead with what stakeholders need
to act on, not with what the
team has been doing.
If my notes do not contain enough
information to complete any section,
flag the gap rather than filling
it with placeholder language.
The constraint to lead with what stakeholders need to act on rather than what the team has been doing reflects one of the most important principles in senior stakeholder communication. Senior stakeholders reading a project update are not primarily interested in effort. They are interested in whether the project is on track, what problems require their attention, and what decisions they need to make. Everything else is context, and context should follow the headline, not precede it.
Prompt 3: The brainstorming session synthesiser
The problem it solves: turning a brainstorming session, which typically produces a large, undifferentiated list of ideas at varying levels of quality and feasibility, into a structured output that can be acted on rather than filed.
You are a strategic facilitator helping me
synthesise the output of a brainstorming
session into something actionable.
Raw output from the session: [paste notes,
sticky note summaries, or whiteboard content]
Context: [what problem or opportunity
the session was addressing, who participated,
and what constraints or criteria
good ideas need to meet]
Please:
1. Cluster the ideas into three to five
themes, naming each theme and listing
the specific ideas that belong to it
2. Identify the two or three ideas with
the highest potential impact relative
to the constraints provided,
with a brief rationale for each
3. Identify any ideas that initially
sound appealing but contain assumptions
worth examining before investing
in them further
4. Identify any tension or contradiction
between ideas that the group will
need to resolve before moving forward
5. Propose a specific next step for
each high-potential idea:
what would need to happen in the
next two weeks to test whether
the idea has merit
Do not discard ideas that seem
unconventional. Flag them separately
as worth revisiting rather than
removing them from the synthesis.
The instruction not to discard unconventional ideas reflects a consistent finding in creativity research. Brainstorming sessions produce their most valuable outputs at the margins, in ideas that seem impractical or unusual on first read but contain an insight that becomes visible on closer examination. A synthesis process that filters aggressively for immediate feasibility systematically discards the ideas most likely to produce genuine differentiation.
Prompt 4: The one-on-one meeting tracker
The problem it solves: maintaining continuity across recurring one-on-one meetings, ensuring that commitments made in one conversation are tracked and followed up in the next, and building a record of development conversations that is useful for performance review season.
You are helping me maintain a structured
record of my one-on-one meetings that
creates continuity and accountability
across conversations.
Notes from today's one-on-one: [paste notes]
Notes from previous one-on-one:
[paste if available, or indicate this
is the first session]
Context: [whether this is a meeting
with your manager or a direct report,
and any relevant background about
current priorities or concerns]
Please produce:
1. Commitments carried forward:
any items committed to in the
previous meeting and their
current status based on today's notes
2. New commitments: specific actions
committed to in today's conversation,
with owner and timeframe
3. Themes: any patterns or topics
that have appeared in multiple
consecutive meetings that may
warrant a more structured conversation
4. Development observations:
any discussion of growth,
feedback, or capability development
worth documenting for future reference
5. Follow-up prompt: one specific
question to open the next
one-on-one that builds on
what was discussed today
Keep this summary under 300 words.
It should be a working document,
not a transcript.
The themes section is the one that produces the most value over time and the least value in any single meeting. Patterns across multiple one-on-ones surface issues that individual conversations obscure: a direct report who consistently raises the same concern in different forms, a manager who consistently returns to the same expectation without stating it directly, a development area that keeps appearing without a concrete plan attached to it. Tracking themes across sessions is what turns a series of individual conversations into a coherent development relationship.
Prompt 5: The cross-functional alignment meeting converter
The problem it solves: documenting a meeting involving multiple teams or functions, where different participants have different priorities, different interpretations of what was agreed, and different downstream actions to take.
You are helping me document a cross-functional
meeting in a way that creates shared clarity
across teams with different priorities
and perspectives.
Raw notes: [paste notes]
Meeting context: [what functions or teams
were represented, what the meeting
was trying to achieve, and any
known tensions or competing priorities
between the groups]
Please produce:
1. Shared understanding: what all parties
agreed on, stated in terms specific
enough that different interpretations
are not possible
2. Outstanding differences: where parties
left the meeting with different
understandings or unresolved disagreements,
stated neutrally and specifically
3. Actions by team: a separate action
list for each function or team represented,
with owner and deadline for each item
4. Dependencies: where one team's
action depends on another team's
output, with the dependency chain
stated explicitly
5. Escalation items: anything that
could not be resolved in the meeting
and requires a decision from
someone not in the room,
with a recommended escalation path
Flag any section of my notes where
the record is insufficient to reconstruct
what was agreed. Those gaps are
the highest-risk items in any
cross-functional alignment.
The dependencies section is the structural component most commonly missing from cross-functional meeting documentation, and its absence is the most common source of missed deadlines in multi-team projects. When Team A's deliverable is the input for Team B's work, and that dependency is not explicitly documented, the delay that results when Team A slips is experienced by Team B as a surprise rather than a foreseeable consequence of a known dependency. Documenting dependencies makes the consequence of slippage visible before it happens rather than after.
Building the habit
These prompts produce their full value only when used consistently rather than occasionally. A meeting summary produced once, for a particularly important meeting, is useful. A meeting summary produced for every significant meeting, using a consistent format, creates something more valuable: an organisational memory that allows patterns to be seen, commitments to be tracked, and decisions to be revisited with accurate information rather than reconstructed recollection.
The professionals who build this habit are not doing more administrative work. They are doing less, because the time they invest in a rigorous meeting summary consistently reduces the time spent in follow-up conversations, clarification emails, and decision relitigations that are the direct consequence of inadequate documentation.
The meeting summary is not the output of the meeting. It is the mechanism by which the meeting produces any output at all.
Monday we are addressing a question that has been implicit in every issue of this newsletter and that deserves direct treatment: what does it mean to upskill in a way that actually changes your career trajectory, rather than in a way that produces a certificate, consumes time, and changes nothing? The distinction matters because the upskilling industry is currently one of the largest beneficiaries of AI-related anxiety, and a significant proportion of what it is selling is not what professionals actually need.
The answer is more specific, and more actionable, than most upskilling advice suggests.
— The Artificial Idea team
