<h1 id="product-management-is-broken-engineers">Product Management Is Broken Engineers<a aria-hidden="true" class="anchor-heading icon-link" href="#product-management-is-broken-engineers"></a></h1>
<ul>
<li><a href="https://newsletter.posthog.com/p/product-management-is-broken-engineers">https://newsletter.posthog.com/p/product-management-is-broken-engineers</a></li>
<li>topics: <a href="/wiki/notes/gqicLYiQ0ASZT14Zr1SXm">Product Management</a> <a href="/wiki/notes/0qh4smppnx90isobvuhgk3d">Software Development</a></li>
</ul>
<h2 id="highlights">Highlights<a aria-hidden="true" class="anchor-heading icon-link" href="#highlights"></a></h2>
<ol>
<li>PMs don't control Engineers</li>
<li>Engineers make product deciions</li>
<li>Product managers give engineers context</li>
</ol>
<ul>
<li>Analyze product analytics</li>
<li>Investigate opportunities</li>
<li>Do competitor research</li>
<li>Conduct user research (although engineers should still talk to users)</li>
<li>Share industry news</li>
<li>Track the results of the team's work</li>
</ul>
<ol start="4">
<li>Accountability through feedback loops
a. Product engineers set their own quarterly goals
We used to do OKRs and metric-based goals, but we ran into two problems with it:</li>
</ol>
<ul>
<li>Teams wasted too much time coming up with the right metric to focus on.</li>
<li>focused on small quick wins to move those metrics, rather than building what our users actually wanted.
b. Product managers run monthly growth reviews</li>
</ul>
<ol start="5">
<li>Learn fast by optimizing for speed</li>
</ol>

Product Management Is Broken Engineers

public-notes


Welcome! And beware!  

## Purpose

This vault is the "[[learning-in-public|ar.swyx.learn-in-public]]" part of my Second Brain. If you share some of my interests, please [reach out](https://djradon.github.io)! 

## Contents

- [[t]] my personal wikipedia
- [[idea]] (not necessarily mine)
- Resource Notes, including highlights, thoughts and metadata, for various things:
  - [[ar]] mostly articles, papers and web pages
  - [[book]]
  - [[community]]
  - [[course]]
  - [[event]]
  - [[game]]
  - [[loc]]
  - [[org]]
  - [[user]] 
  - [[prdct]] mostly software products, but also ontologies
  - [[recipe]]
  - [[video]] movies, tv episodes, youtube, etc
- [[vs]]
- [[wanted]]
- Some "Metadata Notes":
  - [[tags]] which may refer to any and multiple (or none) of the above
  - [[c]]: ways to categorize resources
  - [[p]]: ways to assert things about resources (mostly abandoned)

In terms of the [[t.km.zettelkasten]] method, this wiki is a commingling of literature notes with something @Sönke-Ahrens warned about: a "personal Wikipedia or a database" [^1]. 

In terms of [[t.tm.getting-things-done]], it's references, someday-maybe, next actions, and public projects.

## Beware!

This is a cluttered cupboard of jumbled jottings riddled with inaccuracies, confusion, and mistakes.

## What This Is Not

- evergreen-notes/digital-garden: for "synthesized" / original-ish publishable big-idea notes that should evolve over time, props to @andy-matuschak and @maggie-appleton
- blog: for "point-in-time" items to be shared: personal news, articles, etc.
  - e.g., [[ar.substack.carpe-noctem]]


[^1]: [[book.how-to-take-smart-notes]]  