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,40 @@
|
||||
id: nemawashi-informal-alignment
|
||||
title: Nemawashi Informal Alignment
|
||||
description: >-
|
||||
A Japanese organisational practice of informally consulting each
|
||||
stakeholder one-on-one before a formal decision meeting, so the meeting
|
||||
confirms rather than surprises. Originating in Japanese corporate and
|
||||
bureaucratic culture, nemawashi (literally "digging around the roots")
|
||||
prepares the ground for consensus.
|
||||
source: Japanese corporate practice / nemawashi tradition
|
||||
source_url: https://www.japanintercultural.com/
|
||||
tags: [japanese, nemawashi, decision-making, consensus, workplace]
|
||||
forked_from: null
|
||||
image: null
|
||||
steps:
|
||||
- headline: Map the stakeholders
|
||||
description: >-
|
||||
The proposer identifies everyone whose support or non-objection is
|
||||
needed for the decision to hold, including those outside the formal
|
||||
meeting.
|
||||
- headline: Consult each individually
|
||||
description: >-
|
||||
The proposer meets each stakeholder one-on-one, shares the proposal,
|
||||
and hears their concerns, questions, and suggested changes —
|
||||
before any group meeting.
|
||||
- headline: Revise the proposal
|
||||
description: >-
|
||||
The proposer revises the proposal in light of what they have heard,
|
||||
incorporating concerns or preparing responses for them.
|
||||
- headline: Confirm in formal meeting
|
||||
description: >-
|
||||
When the formal meeting convenes, each stakeholder has already seen
|
||||
the proposal and raised their concerns. The meeting confirms the
|
||||
decision quickly.
|
||||
outcome: >-
|
||||
A decision is confirmed in a formal meeting with no surprises, because
|
||||
the real deliberation happened in prior individual conversations.
|
||||
practice: >-
|
||||
Nemawashi is not backroom dealing — it is respect for each person's
|
||||
stake. Skipping it and springing a proposal in a meeting is read as
|
||||
discourtesy, not efficiency.
|
||||
Reference in New Issue
Block a user