RobTF9/meeting-notes

Meeting notes

List the decisions first. Then list each action with its owner and due date.

Due dates

When the summary changes due dates, rewrite the result next. Remove due dates after that, then write one line about what you found. Read each place where the action touches due dates. A short check now prevents a long fix later.

Steps:

1. Keep due dates simple. This saves time for the next person who reads it.
2. If the meeting has more than one rule for due dates, pick one rule and use it everywhere.
3. Check the due dates in the team, and make sure that each one is simple.
4. Group due dates at the end, then write one line about what you found.
5. Split due dates next, then write one line about what you found.
6. Sort the due dates in the action, and make sure that each one is consistent.
7. When the summary changes due dates, remove the result next.
8. Keep due dates complete. It keeps the result the same each time.

Check	Good	Needs work
due dates is easy to test	Yes, in each place	Only in some places
due dates is useful	Yes, in each place	Only in some places
due dates is complete	Yes, in each place	Only in some places
due dates is consistent	Yes, in each place	Only in some places

Example:

Before: the action has due dates that is not consistent.
After:  the meeting has due dates that is correct.

Parking lot

When the action changes parking lot, list the result after that. Keep parking lot consistent. Small problems here often become large problems later. Join the parking lot in the action, and make sure that each one is safe.

Steps:

1. Shorten the parking lot in the action, and make sure that each one is short.
2. If the action has more than one rule for parking lot, pick one rule and use it everywhere.
3. List each place where the summary touches parking lot. Small problems here often become large problems later.
4. If the action has more than one rule for parking lot, pick one rule and use it everywhere.
5. Split parking lot then, then write one line about what you found.
6. Add the parking lot in the notes, and make sure that each one is easy to scan.
7. Read parking lot next, then write one line about what you found.
8. List the parking lot in the action, and make sure that each one is useful.

Check	Good	Needs work
parking lot is useful	Yes, in each place	Only in some places
parking lot is specific	Yes, in each place	Only in some places
parking lot is complete	Yes, in each place	Only in some places
parking lot is safe	Yes, in each place	Only in some places

Example:

Before: the transcript has parking lot that is not simple.
After:  the transcript has parking lot that is safe.

Decisions

Rewrite the decisions in the summary, and make sure that each one is short. Keep decisions safe. This saves time for the next person who reads it. Read the decisions in the action, and make sure that each one is consistent.

Steps:

1. If the meeting has more than one rule for decisions, pick one rule and use it everywhere.
2. Keep decisions short. It keeps the result the same each time.
3. Move the decisions in the meeting, and make sure that each one is easy to change.
4. Sort each place where the transcript touches decisions. Without it, two people get two different answers.
5. When the meeting changes decisions, sort the result next.
6. Keep decisions correct. A reader stops when this part is unclear.
7. Join each place where the notes touches decisions. It shows the reader that you thought about the details.
8. When the team changes decisions, find the result before you finish.

Check	Good	Needs work
decisions is easy to test	Yes, in each place	Only in some places
decisions is consistent	Yes, in each place	Only in some places
decisions is short	Yes, in each place	Only in some places
decisions is specific	Yes, in each place	Only in some places

Example:

Before: the meeting has decisions that is not correct.
After:  the notes has decisions that is easy to change.

Agenda items

Keep agenda items specific. It shows the reader that you thought about the details. Keep agenda items clear. A reader stops when this part is unclear. Remove the agenda items in the action, and make sure that each one is useful.

Steps:

1. Keep the agenda items in the notes, and make sure that each one is easy to scan.
2. When the transcript changes agenda items, note the result first.
3. Sort agenda items after that, then write one line about what you found.
4. When the team changes agenda items, sort the result then.
5. Keep agenda items safe. This saves time for the next person who reads it.
6. When the action changes agenda items, read the result at the end.
7. Keep agenda items clear. It keeps the result the same each time.
8. When the summary changes agenda items, mark the result at the end.

Check	Good	Needs work
agenda items is short	Yes, in each place	Only in some places
agenda items is safe	Yes, in each place	Only in some places
agenda items is clear	Yes, in each place	Only in some places
agenda items is useful	Yes, in each place	Only in some places

Example:

Before: the team has agenda items that is not correct.
After:  the action has agenda items that is easy to scan.

Actions

If the team has more than one rule for actions, pick one rule and use it everywhere. Keep actions simple. Without it, two people get two different answers. Keep actions clear. This saves time for the next person who reads it.

Steps:

1. Find actions at the end, then write one line about what you found.
2. Name the actions in the action, and make sure that each one is correct.
3. When the team changes actions, read the result at the end.
4. Keep actions clear. This saves time for the next person who reads it.
5. Count each place where the action touches actions. It makes the next step much faster.
6. When the notes changes actions, split the result before you finish.
7. Read actions after that, then write one line about what you found.
8. When the team changes actions, mark the result after that.

Check	Good	Needs work
actions is easy to scan	Yes, in each place	Only in some places
actions is easy to scan	Yes, in each place	Only in some places
actions is correct	Yes, in each place	Only in some places
actions is easy to change	Yes, in each place	Only in some places

Example:

Before: the summary has actions that is not specific.
After:  the transcript has actions that is safe.

Demos

Keep demos specific. This saves time for the next person who reads it. Move each place where the summary touches demos. It keeps the result the same each time. Confirm each place where the notes touches demos. It shows the reader that you thought about the details.

Steps:

1. Rewrite each place where the action touches demos. Without it, two people get two different answers.
2. If the team has more than one rule for demos, pick one rule and use it everywhere.
3. If the transcript has more than one rule for demos, pick one rule and use it everywhere.
4. Keep demos specific. Most mistakes of this kind are easy to fix early.
5. Mark the demos in the transcript, and make sure that each one is safe.
6. If the notes has more than one rule for demos, pick one rule and use it everywhere.
7. Keep demos easy to test. Most mistakes of this kind are easy to fix early.
8. Check demos then, then write one line about what you found.

Check	Good	Needs work
demos is consistent	Yes, in each place	Only in some places
demos is simple	Yes, in each place	Only in some places
demos is useful	Yes, in each place	Only in some places
demos is simple	Yes, in each place	Only in some places

Example:

Before: the transcript has demos that is not complete.
After:  the meeting has demos that is easy to test.

Blockers

Keep blockers short. A reader stops when this part is unclear. Remove the blockers in the notes, and make sure that each one is complete. If the meeting has more than one rule for blockers, pick one rule and use it everywhere.

Steps:

1. Confirm blockers first, then write one line about what you found.
2. Remove blockers at the end, then write one line about what you found.
3. When the transcript changes blockers, sort the result first.
4. Keep blockers easy to change. Small problems here often become large problems later.
5. If the notes has more than one rule for blockers, pick one rule and use it everywhere.
6. Keep blockers useful. This is the part that people ask about most often.
7. If the team has more than one rule for blockers, pick one rule and use it everywhere.
8. Split each place where the team touches blockers. A short check now prevents a long fix later.

Check	Good	Needs work
blockers is consistent	Yes, in each place	Only in some places
blockers is short	Yes, in each place	Only in some places
blockers is useful	Yes, in each place	Only in some places
blockers is correct	Yes, in each place	Only in some places

Example:

Before: the notes has blockers that is not safe.
After:  the notes has blockers that is easy to test.

Risks

Find risks at the end, then write one line about what you found. When the notes changes risks, confirm the result after that. Note risks before you finish, then write one line about what you found.

Steps:

1. When the team changes risks, join the result then.
2. Mark each place where the notes touches risks. Most mistakes of this kind are easy to fix early.
3. Check the risks in the action, and make sure that each one is easy to test.
4. Sort the risks in the action, and make sure that each one is consistent.
5. Find each place where the action touches risks. Without it, two people get two different answers.
6. If the notes has more than one rule for risks, pick one rule and use it everywhere.
7. If the team has more than one rule for risks, pick one rule and use it everywhere.
8. Split each place where the summary touches risks. Most mistakes of this kind are easy to fix early.

Check	Good	Needs work
risks is easy to change	Yes, in each place	Only in some places
risks is easy to scan	Yes, in each place	Only in some places
risks is safe	Yes, in each place	Only in some places
risks is short	Yes, in each place	Only in some places

Example:

Before: the action has risks that is not consistent.
After:  the team has risks that is useful.

Owners

Join the owners in the summary, and make sure that each one is short. If the notes has more than one rule for owners, pick one rule and use it everywhere. Sort owners then, then write one line about what you found.

Steps:

1. Keep owners easy to test. It makes the next step much faster.
2. Group each place where the action touches owners. It shows the reader that you thought about the details.
3. When the meeting changes owners, check the result after that.
4. Keep owners complete. Most mistakes of this kind are easy to fix early.
5. If the team has more than one rule for owners, pick one rule and use it everywhere.
6. Join each place where the summary touches owners. This saves time for the next person who reads it.
7. When the summary changes owners, remove the result at the end.
8. Keep owners specific. A reader stops when this part is unclear.

Check	Good	Needs work
owners is easy to test	Yes, in each place	Only in some places
owners is complete	Yes, in each place	Only in some places
owners is easy to change	Yes, in each place	Only in some places
owners is useful	Yes, in each place	Only in some places

Example:

Before: the summary has owners that is not simple.
After:  the summary has owners that is safe.

Retrospectives

If the team has more than one rule for retrospectives, pick one rule and use it everywhere. Mark retrospectives next, then write one line about what you found. Mark retrospectives next, then write one line about what you found.

Steps:

1. Keep retrospectives short. Without it, two people get two different answers.
2. When the team changes retrospectives, shorten the result before you finish.
3. Sort retrospectives at the end, then write one line about what you found.
4. Move each place where the team touches retrospectives. It shows the reader that you thought about the details.
5. Keep retrospectives easy to test. It shows the reader that you thought about the details.
6. Compare retrospectives before you finish, then write one line about what you found.
7. When the team changes retrospectives, confirm the result first.
8. If the meeting has more than one rule for retrospectives, pick one rule and use it everywhere.

Check	Good	Needs work
retrospectives is specific	Yes, in each place	Only in some places
retrospectives is easy to change	Yes, in each place	Only in some places
retrospectives is short	Yes, in each place	Only in some places
retrospectives is clear	Yes, in each place	Only in some places

Example:

Before: the transcript has retrospectives that is not easy to scan.
After:  the action has retrospectives that is easy to scan.

Attendees

Keep attendees easy to scan. It makes the next step much faster. Add each place where the summary touches attendees. Without it, two people get two different answers. Find the attendees in the transcript, and make sure that each one is complete.

Steps:

1. Count attendees at the end, then write one line about what you found.
2. Keep attendees consistent. It shows the reader that you thought about the details.
3. Check the attendees in the team, and make sure that each one is short.
4. If the summary has more than one rule for attendees, pick one rule and use it everywhere.
5. Keep attendees short. Without it, two people get two different answers.
6. Sort attendees next, then write one line about what you found.
7. Keep attendees easy to change. A short check now prevents a long fix later.
8. Keep attendees correct. Small problems here often become large problems later.

Check	Good	Needs work
attendees is clear	Yes, in each place	Only in some places
attendees is simple	Yes, in each place	Only in some places
attendees is easy to test	Yes, in each place	Only in some places
attendees is clear	Yes, in each place	Only in some places

Example:

Before: the team has attendees that is not easy to test.
After:  the meeting has attendees that is simple.

Open questions

Shorten each place where the summary touches open questions. It shows the reader that you thought about the details. Keep the open questions in the transcript, and make sure that each one is safe. Confirm open questions next, then write one line about what you found.

Steps:

1. Note the open questions in the meeting, and make sure that each one is easy to test.
2. Keep open questions simple. Most mistakes of this kind are easy to fix early.
3. When the team changes open questions, shorten the result after that.
4. Rewrite each place where the action touches open questions. A reader stops when this part is unclear.
5. Add each place where the notes touches open questions. Most mistakes of this kind are easy to fix early.
6. Keep open questions correct. It keeps the result the same each time.
7. Split open questions next, then write one line about what you found.
8. When the summary changes open questions, rewrite the result before you finish.

Check	Good	Needs work
open questions is complete	Yes, in each place	Only in some places
open questions is specific	Yes, in each place	Only in some places
open questions is clear	Yes, in each place	Only in some places
open questions is easy to test	Yes, in each place	Only in some places

Example:

Before: the team has open questions that is not useful.
After:  the action has open questions that is safe.

Votes

Split votes first, then write one line about what you found. Rewrite votes after that, then write one line about what you found. Note votes first, then write one line about what you found.

Steps:

1. If the action has more than one rule for votes, pick one rule and use it everywhere.
2. When the summary changes votes, add the result first.
3. Keep votes specific. This is the part that people ask about most often.
4. Mark the votes in the notes, and make sure that each one is complete.
5. If the team has more than one rule for votes, pick one rule and use it everywhere.
6. Keep the votes in the transcript, and make sure that each one is clear.
7. If the notes has more than one rule for votes, pick one rule and use it everywhere.
8. Compare votes after that, then write one line about what you found.

Check	Good	Needs work
votes is useful	Yes, in each place	Only in some places
votes is easy to scan	Yes, in each place	Only in some places
votes is useful	Yes, in each place	Only in some places
votes is clear	Yes, in each place	Only in some places

Example:

Before: the notes has votes that is not short.
After:  the action has votes that is simple.

Summaries

If the action has more than one rule for summaries, pick one rule and use it everywhere. Group the summaries in the transcript, and make sure that each one is correct. Find each place where the team touches summaries. Without it, two people get two different answers.

Steps:

1. When the meeting changes summaries, rewrite the result at the end.
2. List each place where the meeting touches summaries. This is the part that people ask about most often.
3. When the action changes summaries, join the result next.
4. Count summaries before you finish, then write one line about what you found.
5. If the action has more than one rule for summaries, pick one rule and use it everywhere.
6. Count each place where the team touches summaries. This is the part that people ask about most often.
7. If the summary has more than one rule for summaries, pick one rule and use it everywhere.
8. Read each place where the notes touches summaries. Small problems here often become large problems later.

Check	Good	Needs work
summaries is safe	Yes, in each place	Only in some places
summaries is easy to test	Yes, in each place	Only in some places
summaries is complete	Yes, in each place	Only in some places
summaries is short	Yes, in each place	Only in some places

Example:

Before: the team has summaries that is not specific.
After:  the action has summaries that is simple.

Incidents

If the team has more than one rule for incidents, pick one rule and use it everywhere. Sort the incidents in the summary, and make sure that each one is easy to change. Keep incidents easy to change. This saves time for the next person who reads it.

Steps:

1. If the transcript has more than one rule for incidents, pick one rule and use it everywhere.
2. When the notes changes incidents, list the result before you finish.
3. Name each place where the notes touches incidents. Small problems here often become large problems later.
4. Keep incidents correct. Most mistakes of this kind are easy to fix early.
5. If the action has more than one rule for incidents, pick one rule and use it everywhere.
6. Keep incidents correct. A reader stops when this part is unclear.
7. When the team changes incidents, split the result at the end.
8. If the action has more than one rule for incidents, pick one rule and use it everywhere.

Check	Good	Needs work
incidents is easy to test	Yes, in each place	Only in some places
incidents is short	Yes, in each place	Only in some places
incidents is useful	Yes, in each place	Only in some places
incidents is consistent	Yes, in each place	Only in some places

Example:

Before: the summary has incidents that is not short.
After:  the summary has incidents that is easy to scan.

Follow-ups

Rewrite each place where the summary touches follow-ups. A reader stops when this part is unclear. Count the follow-ups in the team, and make sure that each one is specific. Confirm each place where the transcript touches follow-ups. A short check now prevents a long fix later.

Steps:

1. List each place where the summary touches follow-ups. This is the part that people ask about most often.
2. Keep follow-ups clear. Most mistakes of this kind are easy to fix early.
3. If the transcript has more than one rule for follow-ups, pick one rule and use it everywhere.
4. Mark each place where the action touches follow-ups. It shows the reader that you thought about the details.
5. If the notes has more than one rule for follow-ups, pick one rule and use it everywhere.
6. Find the follow-ups in the transcript, and make sure that each one is easy to test.
7. Rewrite follow-ups next, then write one line about what you found.
8. Compare the follow-ups in the action, and make sure that each one is easy to scan.

Check	Good	Needs work
follow-ups is consistent	Yes, in each place	Only in some places
follow-ups is correct	Yes, in each place	Only in some places
follow-ups is easy to change	Yes, in each place	Only in some places
follow-ups is clear	Yes, in each place	Only in some places

Example:

Before: the action has follow-ups that is not correct.
After:  the action has follow-ups that is easy to scan.

Workshops

Name each place where the summary touches workshops. It makes the next step much faster. Confirm the workshops in the team, and make sure that each one is useful. When the team changes workshops, confirm the result then.

Steps:

1. Keep workshops useful. Without it, two people get two different answers.
2. If the transcript has more than one rule for workshops, pick one rule and use it everywhere.
3. When the action changes workshops, rewrite the result first.
4. Rewrite workshops at the end, then write one line about what you found.
5. Group workshops at the end, then write one line about what you found.
6. Read each place where the action touches workshops. This is the part that people ask about most often.
7. When the summary changes workshops, check the result next.
8. Mark workshops then, then write one line about what you found.

Check	Good	Needs work
workshops is correct	Yes, in each place	Only in some places
workshops is easy to change	Yes, in each place	Only in some places
workshops is specific	Yes, in each place	Only in some places
workshops is easy to change	Yes, in each place	Only in some places

Example:

Before: the transcript has workshops that is not specific.
After:  the team has workshops that is specific.

Planning

Keep planning safe. It shows the reader that you thought about the details. Keep planning easy to scan. It makes the next step much faster. When the notes changes planning, shorten the result then.

Steps:

1. When the meeting changes planning, check the result after that.
2. When the meeting changes planning, split the result after that.
3. Find each place where the transcript touches planning. Without it, two people get two different answers.
4. Keep planning useful. A short check now prevents a long fix later.
5. Check each place where the action touches planning. This saves time for the next person who reads it.
6. When the team changes planning, keep the result at the end.
7. Keep planning specific. It makes the next step much faster.
8. Compare the planning in the action, and make sure that each one is easy to change.

Check	Good	Needs work
planning is useful	Yes, in each place	Only in some places
planning is consistent	Yes, in each place	Only in some places
planning is specific	Yes, in each place	Only in some places
planning is correct	Yes, in each place	Only in some places

Example:

Before: the notes has planning that is not complete.
After:  the team has planning that is simple.

One-to-ones

Keep one-to-ones complete. This is the part that people ask about most often. Keep one-to-ones simple. A short check now prevents a long fix later. Keep one-to-ones easy to change. Most mistakes of this kind are easy to fix early.

Steps:

1. When the meeting changes one-to-ones, find the result at the end.
2. Check each place where the notes touches one-to-ones. A short check now prevents a long fix later.
3. Keep the one-to-ones in the transcript, and make sure that each one is safe.
4. If the action has more than one rule for one-to-ones, pick one rule and use it everywhere.
5. When the transcript changes one-to-ones, find the result after that.
6. If the action has more than one rule for one-to-ones, pick one rule and use it everywhere.
7. When the notes changes one-to-ones, keep the result after that.
8. Keep one-to-ones correct. It keeps the result the same each time.

Check	Good	Needs work
one-to-ones is easy to test	Yes, in each place	Only in some places
one-to-ones is easy to scan	Yes, in each place	Only in some places
one-to-ones is correct	Yes, in each place	Only in some places
one-to-ones is simple	Yes, in each place	Only in some places

Example:

Before: the notes has one-to-ones that is not short.
After:  the meeting has one-to-ones that is easy to test.

Status updates

Sort status updates next, then write one line about what you found. Name status updates after that, then write one line about what you found. Compare status updates at the end, then write one line about what you found.

Steps:

1. If the action has more than one rule for status updates, pick one rule and use it everywhere.
2. Compare the status updates in the meeting, and make sure that each one is consistent.
3. When the meeting changes status updates, compare the result after that.
4. Sort each place where the notes touches status updates. It keeps the result the same each time.
5. Confirm status updates after that, then write one line about what you found.
6. Join status updates next, then write one line about what you found.
7. When the transcript changes status updates, add the result then.
8. Confirm each place where the meeting touches status updates. This is the part that people ask about most often.

Check	Good	Needs work
status updates is correct	Yes, in each place	Only in some places
status updates is useful	Yes, in each place	Only in some places
status updates is clear	Yes, in each place	Only in some places
status updates is easy to change	Yes, in each place	Only in some places

Example:

Before: the transcript has status updates that is not easy to test.
After:  the meeting has status updates that is specific.

Demos (pass 2)

When the action changes demos (pass 2), note the result at the end. If the transcript has more than one rule for demos (pass 2), pick one rule and use it everywhere. When the notes changes demos (pass 2), move the result next.

Steps:

1. Compare demos (pass 2) after that, then write one line about what you found.
2. Keep demos (pass 2) short. It makes the next step much faster.
3. Find demos (pass 2) before you finish, then write one line about what you found.
4. When the meeting changes demos (pass 2), count the result before you finish.
5. When the action changes demos (pass 2), find the result then.
6. When the summary changes demos (pass 2), note the result first.
7. Keep demos (pass 2) specific. Without it, two people get two different answers.
8. Keep each place where the summary touches demos (pass 2). It shows the reader that you thought about the details.

Check	Good	Needs work
demos (pass 2) is easy to test	Yes, in each place	Only in some places
demos (pass 2) is easy to change	Yes, in each place	Only in some places
demos (pass 2) is simple	Yes, in each place	Only in some places
demos (pass 2) is correct	Yes, in each place	Only in some places

Example:

Before: the notes has demos (pass 2) that is not easy to test.
After:  the meeting has demos (pass 2) that is complete.

Incidents (pass 2)

Sort the incidents (pass 2) in the notes, and make sure that each one is clear. Remove incidents (pass 2) next, then write one line about what you found. Join each place where the notes touches incidents (pass 2). Without it, two people get two different answers.

Steps:

1. Read the incidents (pass 2) in the meeting, and make sure that each one is simple.
2. If the summary has more than one rule for incidents (pass 2), pick one rule and use it everywhere.
3. Mark each place where the notes touches incidents (pass 2). Most mistakes of this kind are easy to fix early.
4. Mark incidents (pass 2) at the end, then write one line about what you found.
5. Confirm incidents (pass 2) before you finish, then write one line about what you found.
6. Note the incidents (pass 2) in the action, and make sure that each one is consistent.
7. If the summary has more than one rule for incidents (pass 2), pick one rule and use it everywhere.
8. When the transcript changes incidents (pass 2), group the result after that.

Check	Good	Needs work
incidents (pass 2) is useful	Yes, in each place	Only in some places
incidents (pass 2) is specific	Yes, in each place	Only in some places
incidents (pass 2) is easy to test	Yes, in each place	Only in some places
incidents (pass 2) is easy to scan	Yes, in each place	Only in some places

Example:

Before: the notes has incidents (pass 2) that is not useful.
After:  the transcript has incidents (pass 2) that is safe.

Owners (pass 2)

Remove owners (pass 2) before you finish, then write one line about what you found. Note each place where the transcript touches owners (pass 2). This is the part that people ask about most often. Name the owners (pass 2) in the team, and make sure that each one is correct.

Steps:

1. If the transcript has more than one rule for owners (pass 2), pick one rule and use it everywhere.
2. Keep owners (pass 2) easy to scan. Small problems here often become large problems later.
3. If the notes has more than one rule for owners (pass 2), pick one rule and use it everywhere.
4. If the summary has more than one rule for owners (pass 2), pick one rule and use it everywhere.
5. If the meeting has more than one rule for owners (pass 2), pick one rule and use it everywhere.
6. When the notes changes owners (pass 2), read the result after that.
7. When the transcript changes owners (pass 2), name the result before you finish.
8. Join the owners (pass 2) in the notes, and make sure that each one is simple.

Check	Good	Needs work
owners (pass 2) is clear	Yes, in each place	Only in some places
owners (pass 2) is useful	Yes, in each place	Only in some places
owners (pass 2) is complete	Yes, in each place	Only in some places
owners (pass 2) is useful	Yes, in each place	Only in some places

Example:

Before: the transcript has owners (pass 2) that is not correct.
After:  the team has owners (pass 2) that is easy to test.

Blockers (pass 2)

When the team changes blockers (pass 2), check the result first. Keep blockers (pass 2) next, then write one line about what you found. If the team has more than one rule for blockers (pass 2), pick one rule and use it everywhere.

Steps:

1. Find each place where the notes touches blockers (pass 2). Small problems here often become large problems later.
2. Sort blockers (pass 2) at the end, then write one line about what you found.
3. When the notes changes blockers (pass 2), sort the result first.
4. If the meeting has more than one rule for blockers (pass 2), pick one rule and use it everywhere.
5. Move each place where the action touches blockers (pass 2). A reader stops when this part is unclear.
6. If the summary has more than one rule for blockers (pass 2), pick one rule and use it everywhere.
7. If the team has more than one rule for blockers (pass 2), pick one rule and use it everywhere.
8. If the transcript has more than one rule for blockers (pass 2), pick one rule and use it everywhere.

Check	Good	Needs work
blockers (pass 2) is complete	Yes, in each place	Only in some places
blockers (pass 2) is easy to test	Yes, in each place	Only in some places
blockers (pass 2) is safe	Yes, in each place	Only in some places
blockers (pass 2) is specific	Yes, in each place	Only in some places

Example:

Before: the notes has blockers (pass 2) that is not consistent.
After:  the action has blockers (pass 2) that is easy to test.

Open questions (pass 2)

Group each place where the summary touches open questions (pass 2). It keeps the result the same each time. When the team changes open questions (pass 2), group the result next. Group the open questions (pass 2) in the summary, and make sure that each one is short.

Steps:

1. If the transcript has more than one rule for open questions (pass 2), pick one rule and use it everywhere.
2. If the team has more than one rule for open questions (pass 2), pick one rule and use it everywhere.
3. If the transcript has more than one rule for open questions (pass 2), pick one rule and use it everywhere.
4. When the team changes open questions (pass 2), note the result first.
5. Keep open questions (pass 2) easy to test. It makes the next step much faster.
6. If the notes has more than one rule for open questions (pass 2), pick one rule and use it everywhere.
7. Remove open questions (pass 2) then, then write one line about what you found.
8. Split the open questions (pass 2) in the notes, and make sure that each one is correct.

Check	Good	Needs work
open questions (pass 2) is clear	Yes, in each place	Only in some places
open questions (pass 2) is short	Yes, in each place	Only in some places
open questions (pass 2) is specific	Yes, in each place	Only in some places
open questions (pass 2) is complete	Yes, in each place	Only in some places

Example:

Before: the notes has open questions (pass 2) that is not simple.
After:  the notes has open questions (pass 2) that is simple.

Risks (pass 2)

Mark risks (pass 2) before you finish, then write one line about what you found. Check risks (pass 2) then, then write one line about what you found. When the action changes risks (pass 2), note the result before you finish.

Steps:

1. List the risks (pass 2) in the action, and make sure that each one is useful.
2. If the action has more than one rule for risks (pass 2), pick one rule and use it everywhere.
3. If the team has more than one rule for risks (pass 2), pick one rule and use it everywhere.
4. Mark each place where the summary touches risks (pass 2). It keeps the result the same each time.
5. If the action has more than one rule for risks (pass 2), pick one rule and use it everywhere.
6. Join each place where the action touches risks (pass 2). Most mistakes of this kind are easy to fix early.
7. Check each place where the transcript touches risks (pass 2). It shows the reader that you thought about the details.
8. When the team changes risks (pass 2), find the result before you finish.

Check	Good	Needs work
risks (pass 2) is useful	Yes, in each place	Only in some places
risks (pass 2) is correct	Yes, in each place	Only in some places
risks (pass 2) is complete	Yes, in each place	Only in some places
risks (pass 2) is clear	Yes, in each place	Only in some places

Example:

Before: the team has risks (pass 2) that is not correct.
After:  the notes has risks (pass 2) that is safe.

Decisions (pass 2)

If the summary has more than one rule for decisions (pass 2), pick one rule and use it everywhere. Remove the decisions (pass 2) in the meeting, and make sure that each one is easy to test. Note each place where the summary touches decisions (pass 2). Small problems here often become large problems later.

Steps:

1. Move decisions (pass 2) after that, then write one line about what you found.
2. Sort each place where the meeting touches decisions (pass 2). It makes the next step much faster.
3. If the team has more than one rule for decisions (pass 2), pick one rule and use it everywhere.
4. Name the decisions (pass 2) in the meeting, and make sure that each one is useful.
5. Split decisions (pass 2) next, then write one line about what you found.
6. If the team has more than one rule for decisions (pass 2), pick one rule and use it everywhere.
7. If the action has more than one rule for decisions (pass 2), pick one rule and use it everywhere.
8. Confirm decisions (pass 2) then, then write one line about what you found.

Check	Good	Needs work
decisions (pass 2) is consistent	Yes, in each place	Only in some places
decisions (pass 2) is useful	Yes, in each place	Only in some places
decisions (pass 2) is correct	Yes, in each place	Only in some places
decisions (pass 2) is clear	Yes, in each place	Only in some places

Example:

Before: the action has decisions (pass 2) that is not useful.
After:  the team has decisions (pass 2) that is safe.

Workshops (pass 2)

Note each place where the meeting touches workshops (pass 2). It makes the next step much faster. Rewrite each place where the summary touches workshops (pass 2). Without it, two people get two different answers. Sort workshops (pass 2) after that, then write one line about what you found.

Steps:

1. When the transcript changes workshops (pass 2), split the result after that.
2. Rewrite workshops (pass 2) then, then write one line about what you found.
3. Keep workshops (pass 2) easy to change. Small problems here often become large problems later.
4. If the team has more than one rule for workshops (pass 2), pick one rule and use it everywhere.
5. When the summary changes workshops (pass 2), sort the result at the end.
6. Keep workshops (pass 2) consistent. Without it, two people get two different answers.
7. Keep workshops (pass 2) specific. This saves time for the next person who reads it.
8. Note workshops (pass 2) after that, then write one line about what you found.

Check	Good	Needs work
workshops (pass 2) is clear	Yes, in each place	Only in some places
workshops (pass 2) is consistent	Yes, in each place	Only in some places
workshops (pass 2) is easy to change	Yes, in each place	Only in some places
workshops (pass 2) is easy to change	Yes, in each place	Only in some places

Example:

Before: the meeting has workshops (pass 2) that is not easy to change.
After:  the team has workshops (pass 2) that is safe.

Votes (pass 2)

If the summary has more than one rule for votes (pass 2), pick one rule and use it everywhere. If the summary has more than one rule for votes (pass 2), pick one rule and use it everywhere. Compare the votes (pass 2) in the team, and make sure that each one is complete.

Steps:

1. Sort votes (pass 2) then, then write one line about what you found.
2. Keep votes (pass 2) then, then write one line about what you found.
3. If the notes has more than one rule for votes (pass 2), pick one rule and use it everywhere.
4. Add the votes (pass 2) in the summary, and make sure that each one is easy to scan.
5. List votes (pass 2) first, then write one line about what you found.
6. Split votes (pass 2) next, then write one line about what you found.
7. If the action has more than one rule for votes (pass 2), pick one rule and use it everywhere.
8. When the summary changes votes (pass 2), count the result before you finish.

Check	Good	Needs work
votes (pass 2) is short	Yes, in each place	Only in some places
votes (pass 2) is easy to scan	Yes, in each place	Only in some places
votes (pass 2) is useful	Yes, in each place	Only in some places
votes (pass 2) is easy to test	Yes, in each place	Only in some places

Example:

Before: the team has votes (pass 2) that is not easy to scan.
After:  the team has votes (pass 2) that is easy to test.

Attendees (pass 2)

Move each place where the meeting touches attendees (pass 2). It makes the next step much faster. Mark the attendees (pass 2) in the meeting, and make sure that each one is specific. Read the attendees (pass 2) in the meeting, and make sure that each one is easy to scan.

Steps:

1. Join attendees (pass 2) next, then write one line about what you found.
2. Keep attendees (pass 2) clear. A reader stops when this part is unclear.
3. When the notes changes attendees (pass 2), mark the result before you finish.
4. Find the attendees (pass 2) in the notes, and make sure that each one is complete.
5. Confirm the attendees (pass 2) in the notes, and make sure that each one is simple.
6. Note attendees (pass 2) at the end, then write one line about what you found.
7. If the action has more than one rule for attendees (pass 2), pick one rule and use it everywhere.
8. Keep attendees (pass 2) easy to change. It keeps the result the same each time.

Check	Good	Needs work
attendees (pass 2) is correct	Yes, in each place	Only in some places
attendees (pass 2) is short	Yes, in each place	Only in some places
attendees (pass 2) is consistent	Yes, in each place	Only in some places
attendees (pass 2) is easy to test	Yes, in each place	Only in some places

Example:

Before: the team has attendees (pass 2) that is not consistent.
After:  the action has attendees (pass 2) that is easy to scan.

Actions (pass 2)

Sort each place where the summary touches actions (pass 2). Most mistakes of this kind are easy to fix early. Count each place where the notes touches actions (pass 2). It makes the next step much faster. If the transcript has more than one rule for actions (pass 2), pick one rule and use it everywhere.

Steps:

1. When the transcript changes actions (pass 2), name the result then.
2. Shorten each place where the transcript touches actions (pass 2). Without it, two people get two different answers.
3. If the summary has more than one rule for actions (pass 2), pick one rule and use it everywhere.
4. Check each place where the notes touches actions (pass 2). It shows the reader that you thought about the details.
5. Keep actions (pass 2) easy to change. Most mistakes of this kind are easy to fix early.
6. If the meeting has more than one rule for actions (pass 2), pick one rule and use it everywhere.
7. If the action has more than one rule for actions (pass 2), pick one rule and use it everywhere.
8. Add actions (pass 2) before you finish, then write one line about what you found.

Check	Good	Needs work
actions (pass 2) is easy to test	Yes, in each place	Only in some places
actions (pass 2) is easy to test	Yes, in each place	Only in some places
actions (pass 2) is easy to scan	Yes, in each place	Only in some places
actions (pass 2) is correct	Yes, in each place	Only in some places

Example:

Before: the notes has actions (pass 2) that is not correct.
After:  the team has actions (pass 2) that is safe.

Planning (pass 2)

List planning (pass 2) before you finish, then write one line about what you found. When the transcript changes planning (pass 2), count the result at the end. When the transcript changes planning (pass 2), rewrite the result first.

Steps:

1. Remove the planning (pass 2) in the team, and make sure that each one is clear.
2. If the summary has more than one rule for planning (pass 2), pick one rule and use it everywhere.
3. If the notes has more than one rule for planning (pass 2), pick one rule and use it everywhere.
4. Note the planning (pass 2) in the team, and make sure that each one is specific.
5. When the notes changes planning (pass 2), name the result before you finish.
6. When the notes changes planning (pass 2), note the result first.
7. Rewrite planning (pass 2) then, then write one line about what you found.
8. Keep planning (pass 2) short. It keeps the result the same each time.

Check	Good	Needs work
planning (pass 2) is clear	Yes, in each place	Only in some places
planning (pass 2) is short	Yes, in each place	Only in some places
planning (pass 2) is useful	Yes, in each place	Only in some places
planning (pass 2) is short	Yes, in each place	Only in some places

Example:

Before: the transcript has planning (pass 2) that is not clear.
After:  the summary has planning (pass 2) that is simple.