# Nemawashi

## The What

> The concept of nemawashi was then applied in business particularly in decision-making and consensus-building. In business, nemawashi is the act of gathering information and feedback from employees through one-on-one or small group discussions. Much like giving special attention to each root system in a tree, we apply the same concept to our organization’s employees. Nemawashi is usually done when introducing change, presenting new ideas, deciding on business matters, and getting everyone to agree on something..

<figure><img src="/files/iQ2pC3sOsegFeWgV7mkm" alt=""><figcaption><p><a href="https://kanbanzone.com/resources/lean/toyota-production-system/nemawashi/">https://kanbanzone.com/resources/lean/toyota-production-system/nemawashi/</a></p></figcaption></figure>

## The How

### Draft your proposal

* Keep it draft and informal (easy for asking for feedback than a formal presentation)
* Keep it high level (big picture is helpful)
* Keep it simple - short and spot-on
* Keep it non-tech friendly

### Chat with individuals

* Start with the most relevant staff in the tech team
* Followed by key stakeholders (Product Manager, Strategy Manager)
* Give your manager a heads up

### Revise your proposal

* Keep revising your proposals and chatting with individuals
* Stop until the direction is aligned
* Stop until you are certain about the scope and execution

### Make the decision

* Get the thumb ups
* Start small
* Iterate towards the goal

## :white\_check\_mark: Exceptions

* Nemawashi isn't for minor, well-defined issues => Just do it
* Overusing Nemawashi turns you into a talker rather than a doer

## :red\_circle: Red Flags

* No one cares *<mark style="background-color:green;">// are you tackling the right problem?</mark>*
* No honest feedback *<mark style="background-color:green;">// do you provide a safe zone to speak up</mark>*
* Lots of push back *<mark style="background-color:green;">// step back and get the vision aligned</mark>*
* Make a decision before getting aligned *<mark style="background-color:green;">// conflicts are only postponed till the execution stage.</mark>*

## :scroll: Tips

* Keep it open-ended for direct and honest feedback
* Focus on understanding, not winning
* Know when to stop

## :hole: Pitfalls

* Having no feedback // good? bad? I think it’s a bad sign
* Having different opinions // good? bad? I take it as a good sign


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://jamiewen00.gitbook.io/tech-lead-handbook/product/nemawashi.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.