
---
Compared to agile/iterative

---
Updating each other on what's possible



Flexibility

Chief Engineer's role

---
# Principles

## 1 - Map the design space



Choosing suppliers




Trade-off Curves and mathematical relationships




Nemawashi - doing the groundwork for finding consensus, which means finding the best overall solution

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)





Example


Compared to US

Fallbacks

Integration events


Rules of thumb


---
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