https://wiki.opensourceecology.org/index.php?action=history&feed=atom&title=Heavyweight_Product_ManagementHeavyweight Product Management - Revision history2026-04-07T05:01:43ZRevision history for this page on the wikiMediaWiki 1.39.13https://wiki.opensourceecology.org/index.php?title=Heavyweight_Product_Management&diff=307562&oldid=prevMarcin: /* Notes */2025-05-23T01:58:33Z<p><span dir="auto"><span class="autocomment">Notes</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 01:58, 23 May 2025</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l23">Line 23:</td>
<td colspan="2" class="diff-lineno">Line 23:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''The ideal solution:''' opensource the design, delete the specialists, and fill the ranks with integrators who make a superior product - with a significantly smaller team. This is obvious but it is not practiced.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''The ideal solution:''' opensource the design, delete the specialists, and fill the ranks with integrators who make a superior product - with a significantly smaller team. This is obvious but it is not practiced.</div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">*HBR article states that Heavyweight Product Managers distinguish their work by integrity - referring to the integrated development process where the left hand actually knows what the right hand is doing. This yields consistent, quality results. '''What distinguishes outstanding product developers is the consistency between their formal structures and the informal organization that accomplishes the real work of development.''' [https://hbr.org/1990/11/the-power-of-product-integrity#:~:text=As%20concept%20guardians%2C%20heavyweight%20product,to%20develop%20an%20entire%20vehicle.]</ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td></tr>
<!-- diff cache key wikidb-wiki_:diff::1.12:old-307561:rev-307562 -->
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=Heavyweight_Product_Management&diff=307561&oldid=prevMarcin: /* Links */2025-05-23T01:58:24Z<p><span dir="auto"><span class="autocomment">Links</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 01:58, 23 May 2025</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l25">Line 25:</td>
<td colspan="2" class="diff-lineno">Line 25:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">*HBR article states that Heavyweight Product Managers distinguish their work by integrity - referring to the integrated development process where the left hand actually knows what the right hand is doing. This yields consistent, quality results. '''What distinguishes outstanding product developers is the consistency between their formal structures and the informal organization that accomplishes the real work of development.''' [https://hbr.org/1990/11/the-power-of-product-integrity#:~:text=As%20concept%20guardians%2C%20heavyweight%20product,to%20develop%20an%20entire%20vehicle.]</del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td></tr>
<!-- diff cache key wikidb-wiki_:diff::1.12:old-307560:rev-307561 -->
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=Heavyweight_Product_Management&diff=307560&oldid=prevMarcin: /* Notes */2025-05-23T01:57:52Z<p><span dir="auto"><span class="autocomment">Notes</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 01:57, 23 May 2025</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l22">Line 22:</td>
<td colspan="2" class="diff-lineno">Line 22:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''But the question begs asking: why are hundreds (if not thousands) working on specialized pieces of the project?''' This already seems like failure by design. Does not open source transparency obviate that - and the only challenge is integration? That is, all the specialist knowledge should be transparent and easy to understand by integrators. That is a possibility with open source, and an emphasis on transparency. I suspect that the proprietary nature of all the many parts is what makes it unmanageable - ie, communication between different parts becomes immensely difficult - because few of the components are open or transparent. For example, suppliers may have proprietary parts.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''But the question begs asking: why are hundreds (if not thousands) working on specialized pieces of the project?''' This already seems like failure by design. Does not open source transparency obviate that - and the only challenge is integration? That is, all the specialist knowledge should be transparent and easy to understand by integrators. That is a possibility with open source, and an emphasis on transparency. I suspect that the proprietary nature of all the many parts is what makes it unmanageable - ie, communication between different parts becomes immensely difficult - because few of the components are open or transparent. For example, suppliers may have proprietary parts.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>'''The ideal solution:''' opensource the design, delete the specialists, and fill the ranks with integrators who make a superior product - with a significantly smaller team.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>'''The ideal solution:''' opensource the design, delete the specialists, and fill the ranks with integrators who make a superior product - with a significantly smaller team<ins style="font-weight: bold; text-decoration: none;">. This is obvious but it is not practiced</ins>.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*HBR article states that Heavyweight Product Managers distinguish their work by integrity - referring to the integrated development process where the left hand actually knows what the right hand is doing. This yields consistent, quality results. '''What distinguishes outstanding product developers is the consistency between their formal structures and the informal organization that accomplishes the real work of development.''' [https://hbr.org/1990/11/the-power-of-product-integrity#:~:text=As%20concept%20guardians%2C%20heavyweight%20product,to%20develop%20an%20entire%20vehicle.]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*HBR article states that Heavyweight Product Managers distinguish their work by integrity - referring to the integrated development process where the left hand actually knows what the right hand is doing. This yields consistent, quality results. '''What distinguishes outstanding product developers is the consistency between their formal structures and the informal organization that accomplishes the real work of development.''' [https://hbr.org/1990/11/the-power-of-product-integrity#:~:text=As%20concept%20guardians%2C%20heavyweight%20product,to%20develop%20an%20entire%20vehicle.]</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=Heavyweight_Product_Management&diff=307559&oldid=prevMarcin: /* Notes */2025-05-23T01:57:36Z<p><span dir="auto"><span class="autocomment">Notes</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 01:57, 23 May 2025</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l22">Line 22:</td>
<td colspan="2" class="diff-lineno">Line 22:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''But the question begs asking: why are hundreds (if not thousands) working on specialized pieces of the project?''' This already seems like failure by design. Does not open source transparency obviate that - and the only challenge is integration? That is, all the specialist knowledge should be transparent and easy to understand by integrators. That is a possibility with open source, and an emphasis on transparency. I suspect that the proprietary nature of all the many parts is what makes it unmanageable - ie, communication between different parts becomes immensely difficult - because few of the components are open or transparent. For example, suppliers may have proprietary parts.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''But the question begs asking: why are hundreds (if not thousands) working on specialized pieces of the project?''' This already seems like failure by design. Does not open source transparency obviate that - and the only challenge is integration? That is, all the specialist knowledge should be transparent and easy to understand by integrators. That is a possibility with open source, and an emphasis on transparency. I suspect that the proprietary nature of all the many parts is what makes it unmanageable - ie, communication between different parts becomes immensely difficult - because few of the components are open or transparent. For example, suppliers may have proprietary parts.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>'''The ideal solution:''' opensource the design, delete the specialists, and fill the ranks with integrators who make a superior product - with a smaller team.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>'''The ideal solution:''' opensource the design, delete the specialists, and fill the ranks with integrators who make a superior product - with a <ins style="font-weight: bold; text-decoration: none;">significantly </ins>smaller team.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*HBR article states that Heavyweight Product Managers distinguish their work by integrity - referring to the integrated development process where the left hand actually knows what the right hand is doing. This yields consistent, quality results. '''What distinguishes outstanding product developers is the consistency between their formal structures and the informal organization that accomplishes the real work of development.''' [https://hbr.org/1990/11/the-power-of-product-integrity#:~:text=As%20concept%20guardians%2C%20heavyweight%20product,to%20develop%20an%20entire%20vehicle.]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*HBR article states that Heavyweight Product Managers distinguish their work by integrity - referring to the integrated development process where the left hand actually knows what the right hand is doing. This yields consistent, quality results. '''What distinguishes outstanding product developers is the consistency between their formal structures and the informal organization that accomplishes the real work of development.''' [https://hbr.org/1990/11/the-power-of-product-integrity#:~:text=As%20concept%20guardians%2C%20heavyweight%20product,to%20develop%20an%20entire%20vehicle.]</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=Heavyweight_Product_Management&diff=307558&oldid=prevMarcin: /* Notes */2025-05-23T01:57:23Z<p><span dir="auto"><span class="autocomment">Notes</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 01:57, 23 May 2025</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l20">Line 20:</td>
<td colspan="2" class="diff-lineno">Line 20:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>When cars were designed and developed by a handful of engineers working under the direction of a Henry Ford, a Gottlieb Daimler, or a Kiichiro Toyoda, organization was not an issue. What mattered were the engineers’ skills, the group’s chemistry, and the master’s guidance. These are still vital to product integrity; but the organizational challenge has become immeasurably more complex. Developing a new car involves hundreds (if not thousands) of people working on specialized pieces of the project in many different locations for months or even years at a time. Whether their efforts have integrity—whether the car performs superbly and delights customers—will depend on how the company organizes development and the nature of the leadership it creates.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>When cars were designed and developed by a handful of engineers working under the direction of a Henry Ford, a Gottlieb Daimler, or a Kiichiro Toyoda, organization was not an issue. What mattered were the engineers’ skills, the group’s chemistry, and the master’s guidance. These are still vital to product integrity; but the organizational challenge has become immeasurably more complex. Developing a new car involves hundreds (if not thousands) of people working on specialized pieces of the project in many different locations for months or even years at a time. Whether their efforts have integrity—whether the car performs superbly and delights customers—will depend on how the company organizes development and the nature of the leadership it creates.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>'''But the question begs asking: why are hundreds (if not thousands) working on specialized pieces of the project?''' This already seems like failure by design. Does not open source transparency obviate that - and the only challenge is integration? That is, all the specialist knowledge should be transparent and easy to understand by integrators. That is a possibility with open source, and an emphasis on transparency. I suspect that the proprietary nature of all the many parts is what makes it unmanageable - ie, communication between different parts becomes immensely difficult.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>'''But the question begs asking: why are hundreds (if not thousands) working on specialized pieces of the project?''' This already seems like failure by design. Does not open source transparency obviate that - and the only challenge is integration? That is, all the specialist knowledge should be transparent and easy to understand by integrators. That is a possibility with open source, and an emphasis on transparency. I suspect that the proprietary nature of all the many parts is what makes it unmanageable - ie, communication between different parts becomes immensely difficult <ins style="font-weight: bold; text-decoration: none;">- because few of the components are open or transparent. For example, suppliers may have proprietary parts</ins>.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''The ideal solution:''' opensource the design, delete the specialists, and fill the ranks with integrators who make a superior product - with a smaller team.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''The ideal solution:''' opensource the design, delete the specialists, and fill the ranks with integrators who make a superior product - with a smaller team.</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=Heavyweight_Product_Management&diff=307552&oldid=prevMarcin at 01:52, 23 May 20252025-05-23T01:52:14Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 01:52, 23 May 2025</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Introduction=</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Introduction=</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Leading literature in product development (see seminal works at [[Open Source Product Development]]) indicate that the most successful management style - in complex projects requiring an interdisciplinary approach - is the Heavyweight Project <del style="font-weight: bold; text-decoration: none;">Manager </del>(HPM) model. For successful integration of multiple areas and stakeholders - a strong guiding hand is needed.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Leading literature in product development (see seminal works at [[Open Source Product Development]]) indicate that the most successful management style - in complex projects requiring an interdisciplinary approach - is the Heavyweight Project <ins style="font-weight: bold; text-decoration: none;">Management </ins>(HPM) model. For successful integration of multiple areas and stakeholders - a strong guiding hand is needed.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>This heavyweight product manager is not in a directive as much as a facilitative role - but does have leadership and power to influence decisions in a substantial way.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>This heavyweight product manager is not in a directive as much as a facilitative role - but does have leadership and power to influence decisions in a substantial way.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Applied to OSE, this means:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Applied to OSE, this means:</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*'''This is not inconsistent with high levels of collaboration and [[Collaborative Literacy]]. In fact, high collaborative literacy ENABLES heavyweight product management.''' HPM is a condition of extreme coordination. However, this HPM model is guided not by an [[Asshole]] leader - but by an invisible, <del style="font-weight: bold; text-decoration: none;">gentleHow </del>do we resolve this [[Heavyweight Product Management Paradox]].</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*'''This is not inconsistent with high levels of collaboration and [[Collaborative Literacy]]. In fact, high collaborative literacy ENABLES heavyweight product management.''' HPM is a condition of extreme coordination. However, this HPM model is guided not by an [[Asshole]] leader - but by an invisible, <ins style="font-weight: bold; text-decoration: none;">gentle hand. How </ins>do we resolve this <ins style="font-weight: bold; text-decoration: none;">apparent </ins>[[Heavyweight Product Management Paradox]]<ins style="font-weight: bold; text-decoration: none;">? A high level of collaborative literacy means a level of shared understanding that makes heavyweight product management easy. The HPM manager takes the form of an educator who teaches collaborative literacy. Once shared understanding of problem statements and methods is attained, then the process can effectively run by itself. Each person is autonomous yet coordinated, full of agency yet stigmergic. This is an emergent phenomenon</ins>.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*The project manager does not focus on financial capital to access development effort, but rather a more integrated approach of Open Source capital. This means understanding of Open Source collaboration and how common interest and efficiency can be leveraged in an open and voluntary development process. The advantage of an open source approach is that contributors are not alienated from their work via compensation, but instead rely on their self determination to be part of a team. This provides more authentic and integrated results. See [[9 Forms of Capital]].</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*The project manager does not focus on financial capital to access development effort, but rather a more integrated approach of Open Source capital. This means understanding of Open Source collaboration and how common interest and efficiency can be leveraged in an open and voluntary development process. The advantage of an open source approach is that contributors are not alienated from their work via compensation, but instead rely on their self determination to be part of a team. This provides more authentic and integrated results. See [[9 Forms of Capital]].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*A high management ratio is required for effective use of an HPM's time. This leverage ratio is the amount of time speent managing a certain team, vs the amount of work that the team puts in on the critical path. This ratio should be an absolute minimum of 40:1 management:work time. Ie, one manager is able to extend themselves 40 times. If we assume a low value production scenario of $1k value generated per month, this still indicates that one manager can produce a limit of $40k/month of value via their team, translating to a $1/2M per year organization. In a better scenario of average competent workers at $4k/month value generation, this indicates a $2M/year net organization.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*A high management ratio is required for effective use of an HPM's time. This leverage ratio is the amount of time speent managing a certain team, vs the amount of work that the team puts in on the critical path. This ratio should be an absolute minimum of 40:1 management:work time. Ie, one manager is able to extend themselves 40 times. If we assume a low value production scenario of $1k value generated per month, this still indicates that one manager can produce a limit of $40k/month of value via their team, translating to a $1/2M per year organization. In a better scenario of average competent workers at $4k/month value generation, this indicates a $2M/year net organization.</div></td></tr>
<!-- diff cache key wikidb-wiki_:diff::1.12:old-307503:rev-307552 -->
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=Heavyweight_Product_Management&diff=307503&oldid=prevMarcin at 20:11, 22 May 20252025-05-22T20:11:11Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 20:11, 22 May 2025</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l6">Line 6:</td>
<td colspan="2" class="diff-lineno">Line 6:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Applied to OSE, this means:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Applied to OSE, this means:</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*This is not inconsistent with high levels of collaboration and [[Collaborative Literacy]]. In fact, high collaborative literacy <del style="font-weight: bold; text-decoration: none;">enables </del>heavyweight product management.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*<ins style="font-weight: bold; text-decoration: none;">'''</ins>This is not inconsistent with high levels of collaboration and [[Collaborative Literacy]]. In fact, high collaborative literacy <ins style="font-weight: bold; text-decoration: none;">ENABLES </ins>heavyweight product management<ins style="font-weight: bold; text-decoration: none;">.''' HPM is a condition of extreme coordination. However, this HPM model is guided not by an [[Asshole]] leader - but by an invisible, gentleHow do we resolve this [[Heavyweight Product Management Paradox]]</ins>.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*The project manager does not focus on financial capital to access development effort, but rather a more integrated approach of Open Source capital. This means understanding of Open Source collaboration and how common interest and efficiency can be leveraged in an open and voluntary development process. The advantage of an open source approach is that contributors are not alienated from their work via compensation, but instead rely on their self determination to be part of a team. This provides more authentic and integrated results. See [[9 Forms of Capital]].</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*The project manager does not focus on financial capital to access development effort, but rather a more integrated approach of Open Source capital. This means understanding of Open Source collaboration and how common interest and efficiency can be leveraged in an open and voluntary development process. The advantage of an open source approach is that contributors are not alienated from their work via compensation, but instead rely on their self determination to be part of a team. This provides more authentic and integrated results. See [[9 Forms of Capital]].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*A high management ratio is required for effective use of an HPM's time. This leverage ratio is the amount of time speent managing a certain team, vs the amount of work that the team puts in on the critical path. This ratio should be an absolute minimum of 40:1 management:work time. Ie, one manager is able to extend themselves 40 times. If we assume a low value production scenario of $1k value generated per month, this still indicates that one manager can produce a limit of $40k/month of value via their team, translating to a $1/2M per year organization. In a better scenario of average competent workers at $4k/month value generation, this indicates a $2M/year net organization.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*A high management ratio is required for effective use of an HPM's time. This leverage ratio is the amount of time speent managing a certain team, vs the amount of work that the team puts in on the critical path. This ratio should be an absolute minimum of 40:1 management:work time. Ie, one manager is able to extend themselves 40 times. If we assume a low value production scenario of $1k value generated per month, this still indicates that one manager can produce a limit of $40k/month of value via their team, translating to a $1/2M per year organization. In a better scenario of average competent workers at $4k/month value generation, this indicates a $2M/year net organization.</div></td></tr>
<!-- diff cache key wikidb-wiki_:diff::1.12:old-307501:rev-307503 -->
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=Heavyweight_Product_Management&diff=307501&oldid=prevMarcin at 20:08, 22 May 20252025-05-22T20:08:53Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 20:08, 22 May 2025</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l6">Line 6:</td>
<td colspan="2" class="diff-lineno">Line 6:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Applied to OSE, this means:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Applied to OSE, this means:</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">*This is not inconsistent with high levels of collaboration and [[Collaborative Literacy]]. In fact, high collaborative literacy enables heavyweight product management.</ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*The project manager does not focus on financial capital to access development effort, but rather a more integrated approach of Open Source capital. This means understanding of Open Source collaboration and how common interest and efficiency can be leveraged in an open and voluntary development process. The advantage of an open source approach is that contributors are not alienated from their work via compensation, but instead rely on their self determination to be part of a team. This provides more authentic and integrated results. See [[9 Forms of Capital]].</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*The project manager does not focus on financial capital to access development effort, but rather a more integrated approach of Open Source capital. This means understanding of Open Source collaboration and how common interest and efficiency can be leveraged in an open and voluntary development process. The advantage of an open source approach is that contributors are not alienated from their work via compensation, but instead rely on their self determination to be part of a team. This provides more authentic and integrated results. See [[9 Forms of Capital]].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*A high management ratio is required for effective use of an HPM's time. This leverage ratio is the amount of time speent managing a certain team, vs the amount of work that the team puts in on the critical path. This ratio should be an absolute minimum of 40:1 management:work time. Ie, one manager is able to extend themselves 40 times. If we assume a low value production scenario of $1k value generated per month, this still indicates that one manager can produce a limit of $40k/month of value via their team, translating to a $1/2M per year organization. In a better scenario of average competent workers at $4k/month value generation, this indicates a $2M/year net organization.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*A high management ratio is required for effective use of an HPM's time. This leverage ratio is the amount of time speent managing a certain team, vs the amount of work that the team puts in on the critical path. This ratio should be an absolute minimum of 40:1 management:work time. Ie, one manager is able to extend themselves 40 times. If we assume a low value production scenario of $1k value generated per month, this still indicates that one manager can produce a limit of $40k/month of value via their team, translating to a $1/2M per year organization. In a better scenario of average competent workers at $4k/month value generation, this indicates a $2M/year net organization.</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=Heavyweight_Product_Management&diff=232895&oldid=prevMarcin: /* Links */2020-09-06T22:07:05Z<p><span dir="auto"><span class="autocomment">Links</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 22:07, 6 September 2020</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l13">Line 13:</td>
<td colspan="2" class="diff-lineno">Line 13:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Because the effort required to execute complex, ambitious, integrated projects is on the scale of an Apollo Program or Manhattan Project, it is likely that funding for such is not available. This is especially true if transformative projects are being considered, where inertia and special interests prevent the forward motion of society at large. To address the funding gap, high value, modular products must be undertaken, and positive capital feedback loops should be created via principles of [[Distributive Enterprise]].</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Because the effort required to execute complex, ambitious, integrated projects is on the scale of an Apollo Program or Manhattan Project, it is likely that funding for such is not available. This is especially true if transformative projects are being considered, where inertia and special interests prevent the forward motion of society at large. To address the funding gap, high value, modular products must be undertaken, and positive capital feedback loops should be created via principles of [[Distributive Enterprise]].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*large funding sources, if available, should be questioned</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*large funding sources, if available, should be questioned</div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">=Notes=</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">From the HBR article - [https://hbr.org/1990/11/the-power-of-product-integrity#:~:text=As%20concept%20guardians%2C%20heavyweight%20product,to%20develop%20an%20entire%20vehicle.] -</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">When cars were designed and developed by a handful of engineers working under the direction of a Henry Ford, a Gottlieb Daimler, or a Kiichiro Toyoda, organization was not an issue. What mattered were the engineers’ skills, the group’s chemistry, and the master’s guidance. These are still vital to product integrity; but the organizational challenge has become immeasurably more complex. Developing a new car involves hundreds (if not thousands) of people working on specialized pieces of the project in many different locations for months or even years at a time. Whether their efforts have integrity—whether the car performs superbly and delights customers—will depend on how the company organizes development and the nature of the leadership it creates.</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">'''But the question begs asking: why are hundreds (if not thousands) working on specialized pieces of the project?''' This already seems like failure by design. Does not open source transparency obviate that - and the only challenge is integration? That is, all the specialist knowledge should be transparent and easy to understand by integrators. That is a possibility with open source, and an emphasis on transparency. I suspect that the proprietary nature of all the many parts is what makes it unmanageable - ie, communication between different parts becomes immensely difficult.</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">'''The ideal solution:''' opensource the design, delete the specialists, and fill the ranks with integrators who make a superior product - with a smaller team.</ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*HBR article states that Heavyweight Product Managers distinguish their work by integrity - referring to the integrated development process where the left hand actually knows what the right hand is doing. This yields consistent, quality results. '''What distinguishes outstanding product developers is the consistency between their formal structures and the informal organization that accomplishes the real work of development.''' [https://hbr.org/1990/11/the-power-of-product-integrity#:~:text=As%20concept%20guardians%2C%20heavyweight%20product,to%20develop%20an%20entire%20vehicle.]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*HBR article states that Heavyweight Product Managers distinguish their work by integrity - referring to the integrated development process where the left hand actually knows what the right hand is doing. This yields consistent, quality results. '''What distinguishes outstanding product developers is the consistency between their formal structures and the informal organization that accomplishes the real work of development.''' [https://hbr.org/1990/11/the-power-of-product-integrity#:~:text=As%20concept%20guardians%2C%20heavyweight%20product,to%20develop%20an%20entire%20vehicle.]</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=Heavyweight_Product_Management&diff=232893&oldid=prevMarcin: /* Links */2020-09-06T21:55:40Z<p><span dir="auto"><span class="autocomment">Links</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:55, 6 September 2020</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l15">Line 15:</td>
<td colspan="2" class="diff-lineno">Line 15:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=Links=</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*HBR article states that Heavyweight Product Managers distinguish their work by integrity - referring to the integrated development process where the left hand actually knows what the right hand is doing. This yields consistent, quality results <del style="font-weight: bold; text-decoration: none;">- </del>[https://hbr.org/1990/11/the-power-of-product-integrity#:~:text=As%20concept%20guardians%2C%20heavyweight%20product,to%20develop%20an%20entire%20vehicle.]</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*HBR article states that Heavyweight Product Managers distinguish their work by integrity - referring to the integrated development process where the left hand actually knows what the right hand is doing. This yields consistent, quality results<ins style="font-weight: bold; text-decoration: none;">. '''What distinguishes outstanding product developers is the consistency between their formal structures and the informal organization that accomplishes the real work of development.''' </ins>[https://hbr.org/1990/11/the-power-of-product-integrity#:~:text=As%20concept%20guardians%2C%20heavyweight%20product,to%20develop%20an%20entire%20vehicle.]</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Mini Apollo Program]]</div></td></tr>
<!-- diff cache key wikidb-wiki_:diff::1.12:old-232892:rev-232893 -->
</table>Marcin