fix: rename seed files and IDs to match cleaned titles
All 100 seed YAML files now have: - Filenames that match their id field - IDs that are slugs of their titles - No cultural identifiers in titles or IDs 70 files renamed. e.g. quaker-meeting-for-worship.yaml -> meeting-for-worship.yaml, moroccan-jmaa-village.yaml -> jmaa-village-assembly.yaml, japanese-hansei.yaml -> hansei-reflection.yaml
This commit is contained in:
@@ -0,0 +1,37 @@
|
||||
id: radical-candor-feedback
|
||||
title: Radical Candor Feedback
|
||||
description: >-
|
||||
A feedback practice that combines caring personally with challenging
|
||||
directly, avoiding the pitfalls of ruinous empathy and obnoxious
|
||||
aggression. Developed by Kim Scott based on her experience at Google and
|
||||
Apple.
|
||||
source: Kim Scott, "Radical Candor"
|
||||
source_url: https://www.radicalcandor.com/
|
||||
tags: [feedback, workplace, communication, management]
|
||||
forked_from: null
|
||||
image: null
|
||||
steps:
|
||||
- headline: Care personally
|
||||
description: >-
|
||||
The giver establishes that they care about the receiver as a person —
|
||||
not just as a performer — through prior relationship and genuine
|
||||
attention.
|
||||
- headline: Challenge directly
|
||||
description: >-
|
||||
The giver states the challenge or criticism clearly and specifically,
|
||||
without softening it into vagueness or padding it with praise.
|
||||
- headline: Invite reciprocation
|
||||
description: >-
|
||||
The giver invites the receiver to challenge them back, opening the
|
||||
feedback to be two-way rather than hierarchical.
|
||||
- headline: Commit to action
|
||||
description: >-
|
||||
Both parties agree on what will change and how progress will be
|
||||
checked.
|
||||
outcome: >-
|
||||
The receiver hears a clear challenge from someone who demonstrably cares,
|
||||
making the feedback both heard and actionable.
|
||||
practice: >-
|
||||
Without the caring, direct challenge becomes aggression. Without the
|
||||
challenge, caring becomes toothless empathy. Both must be present. Build
|
||||
the relationship before delivering hard feedback.
|
||||
Reference in New Issue
Block a user