Team feedback loop: sharing and revising

Team feedback loop: sharing and revising

Why it matters: Team workflows improve when feedback is structured and revisions are tracked.

Goals

• Share drafts with a rubric.
• Collect feedback as actionable items.
• Revise and record changes.

Key definitions

• Rubric: A scoring guide with criteria (clarity, correctness, tone, completeness).
• Change log: A record of what changed and why.
• Reviewer question: A question that targets a specific risk or gap.

Workflow (step-by-step)

1. Attach a rubric to the draft.
2. Ask reviewers for 3 issues and 3 improvements tied to rubric criteria.
3. Convert feedback into a prioritized task list.
4. Revise and create a short change log.
5. Re-run QA and ship.

Example (good vs bad)

✅ Good: Feedback becomes tasks; revisions are traceable; QA happens before shipping.

❌ Bad: Feedback is vague (“looks good”) and problems appear after shipping.

Checklist

• Rubric included.
• Feedback is actionable.
• Changes logged.
• QA rerun before ship.

Metrics / criteria

• Revision cycles decrease; fewer post-ship issues.
• Measurable: You can say whether the output is correct/complete (pass/fail or a score).
• Effort: You can produce the result in 15–30 minutes using the workflow.
• Clarity: Another person can run your prompt and get a similar outcome.

Common mistakes + fixes

• Pitfall: Unstructured feedback. Fix: Require rubric-based comments and examples.
• Pitfall: Vague instructions. Fix: Add constraints, examples, and a success checklist.
• Pitfall: One-shot prompting. Fix: Iterate: draft → critique → revise → verify.
• Pitfall: No validation. Fix: Add QA steps, tests, and explicit “what counts as done”.

Student tasks

1. Apply the workflow to one real work task related to team feedback loop: sharing and revising.
2. Create a small artifact: prompt, checklist, rubric, table, draft, or decision note.
3. Run one quality check and record what changed after the check.
4. Write a 3-sentence reflection: what worked, what failed, and what you will reuse.

Useful external sources

• OpenAI prompt engineering guide: https://platform.openai.com/docs/guides/prompt-engineering — Prompt structure, iteration, constraints, and evaluation habits.
• NIST AI Risk Management Framework: https://www.nist.gov/itl/ai-risk-management-framework — Risk framing, governance language, and verification mindset.
• OWASP Top 10 for Large Language Model Applications: https://owasp.org/www-project-top-10-for-large-language-model-applications/ — Practical AI safety risks such as prompt injection, leakage, and insecure output handling.
• Google People + AI Guidebook: https://pair.withgoogle.com/guidebook/ — Human-centered AI design, user control, feedback, and failure modes.

Bibliography

• OpenAI prompt engineering guide. https://platform.openai.com/docs/guides/prompt-engineering
• NIST AI Risk Management Framework. https://www.nist.gov/itl/ai-risk-management-framework
• OWASP Top 10 for Large Language Model Applications. https://owasp.org/www-project-top-10-for-large-language-model-applications/
• Google People + AI Guidebook. https://pair.withgoogle.com/guidebook/