Continuing Improvement: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Tangible Assets= | =Tangible Assets= | ||
*'''Contribution Tracking''' - For [[Extreme Manufacturing]] workshops - where people learn efficient production - data collection is required regarding participation. This is important for events such as the [[Future Builders Crash Course]] - where at times participation is only 50%. To break this barrier, automated participation tracking can be developed, such as via video capture in an open, large, dedicated space - such as the [[Hangar]]. This would show the number of participants in realtime, and be visible in an app. | *'''Contribution Tracking''' - For [[Extreme Manufacturing]] workshops - where people learn efficient production - data collection is required regarding participation. This is important for events such as the [[Future Builders Crash Course]] - where at times participation is only 50%. To break this barrier, automated participation tracking can be developed, such as via video capture in an open, large, dedicated space - such as the [[Hangar]]. This would show the number of participants in realtime, and be visible in an app. The goal here is to increase participation to near full at all times, such as 95% or better (2 sigma). | ||
Revision as of 07:41, 11 December 2025
Tangible Assets
- Contribution Tracking - For Extreme Manufacturing workshops - where people learn efficient production - data collection is required regarding participation. This is important for events such as the Future Builders Crash Course - where at times participation is only 50%. To break this barrier, automated participation tracking can be developed, such as via video capture in an open, large, dedicated space - such as the Hangar. This would show the number of participants in realtime, and be visible in an app. The goal here is to increase participation to near full at all times, such as 95% or better (2 sigma).
Basics
- A Philosophy of constanly improving; "good enough" doesn't exist, and development is never over
- Development is never "fully" over, can be stable/usable etc, but there is always room for growth and improvement
- This is how we involve customers in ongoing open source product development.