---
# System prepended metadata

title: Principles

---

![](https://i.imgur.com/TUi9QXv.png)

---

Compared to agile/iterative
![](https://i.imgur.com/qCZtgwp.png)

---

Updating each other on what's possible

![](https://i.imgur.com/6WVxwcr.png)

![](https://i.imgur.com/zYOZb2Q.png)
![](https://i.imgur.com/FgQlzMg.png)

Flexibility
![](https://i.imgur.com/7b9RU7z.png)
Chief Engineer's role
![](https://i.imgur.com/xKPEgr0.png)

---
# Principles
![](https://i.imgur.com/VrFjIK9.png)

## 1 - Map the design space
![](https://i.imgur.com/Tsd7MkO.png)




![](https://i.imgur.com/IMvr5Af.png)


![](https://i.imgur.com/k3ogzjW.png)

Choosing suppliers
![](https://i.imgur.com/ppQi29T.png)

![](https://i.imgur.com/DJJ9KXf.png)

![](https://i.imgur.com/B5KMmVR.png)

![](https://i.imgur.com/mvI2oT2.png)

Trade-off Curves and mathematical relationships
![](https://i.imgur.com/c8PXEKv.png)

![](https://i.imgur.com/QCWy37x.png)
![](https://i.imgur.com/l9d2k6B.png)

![](https://i.imgur.com/O24MxYX.png)

Nemawashi - doing the groundwork for finding consensus, which means finding the best overall solution
![](https://i.imgur.com/P3OxkuX.png)


Designs are shared with manufacturing *without* tolerances, so they can build it and adjust parts for fit. (Rather than each dept specifying tolerances like +/- 0.5mm for each part)
![](https://i.imgur.com/tvJjonE.png)


![](https://i.imgur.com/wXFM6mU.png)
![](https://i.imgur.com/5MFb4ap.png)

![](https://i.imgur.com/xYChmBa.png)

![](https://i.imgur.com/Ip8ubQs.png)

Example
![](https://i.imgur.com/FAtGDum.png)
![](https://i.imgur.com/o4er2K9.png)
Compared to US
![](https://i.imgur.com/Atldhtr.png)

Fallbacks
![](https://i.imgur.com/ilq9pJ3.png)

Integration events
![](https://i.imgur.com/Fxdbrzk.png)

![](https://i.imgur.com/MO5nBCt.png)

Rules of thumb
![](https://i.imgur.com/iA9aXX0.png)
![](https://i.imgur.com/G5JojLA.png)

---

daily namawashi time
2-3 dry runs


capabilties, tolerances & trade-offs
checklists
variations and modules

timelines 
content plans 
user interfaces
rituals
decks

Mentoring tolerances:

response time
able to share real experience
makes intros

Fellow needs:

navigate blockchain by the stars
hear from luminaries to be inspired and know what matters
get (weekly) feedback on their project
get (weekly) feedback on their topic exploration
confidence in knowing the terrain / zeitfgeist
feel connected and supported (tribe)

Option Examples: 
1- last working version 
2 - improvement X (need, flexibility/modularity, performance measure) 
3 - improvement Y 
4 - hybrids