Kevin Wojkovich

Andre Eleuterio

Noah S-C

Pietrorosa77

Jean-Hadrien Chabran

Devon

David Veszelovszki

Jean du Plessis

Robert Lin

Crystal Augustus

Thorsten Ball

Jordan Plahn

Rafał Leszczyński

david-sandy

Joe Chen

Rob Rhyne

Nick Snyder

Patrick Dubroy

# Product and Engineering

## Purpose

[Product](product/index.md) and [Engineering](engineering/index.md) work closely together to create value for our customers by delivering a high quality product that solves their problems.

- Product is responsible for defining, scoping, and prioritizing the problems we want to solve for our customers.
- Engineering is responsible for determining how to solve the problems. This includes defining, scoping, and prioritizing technical problems engineering needs to solve to deliver high quality solutions to the prioritized customer problems.

## Links

Reference:

- [Current strategy](strategy-goals/index.md)
- [Current team](team/index.md)
- [KPIs](https://sourcegraph.looker.com/boards/20)
- [Department Meeting](team-culture/department-meeting.md)
- [Team rituals](team-culture/index.md)

[How to](process/index.md):

- [Headcount planning](process/headcount-planning.md)
- [Planning](process/planning.md)
- [Reporting progress](process/reporting-progress.md)

## Handbook organization

Documentation that is relevant to both product and engineering belongs in the top-level product-engineering folder.

Documentation that is primarily or exclusively relevant to product or engineering belongs in the appropriate product or engineering subfolder.


<section class="h0Wrapper headingWrapper"><section class="h1Wrapper headingWrapper"><h1 id="product-and-engineering"><a class="anchor" aria-hidden tabindex="-1" href="#product-and-engineering"><span class="icon icon-link"></span></a>Product and Engineering</h1>
<section class="h2Wrapper headingWrapper"><h2 id="purpose"><a class="anchor" aria-hidden tabindex="-1" href="#purpose"><span class="icon icon-link"></span></a>Purpose</h2>
<p><a href="product-engineering/product">Product</a> and <a href="product-engineering/engineering">Engineering</a> work closely together to create value for our customers by delivering a high quality product that solves their problems.</p>
<ul>
<li>Product is responsible for defining, scoping, and prioritizing the problems we want to solve for our customers.</li>
<li>Engineering is responsible for determining how to solve the problems. This includes defining, scoping, and prioritizing technical problems engineering needs to solve to deliver high quality solutions to the prioritized customer problems.</li>
</ul>
</section><section class="h2Wrapper headingWrapper"><h2 id="links"><a class="anchor" aria-hidden tabindex="-1" href="#links"><span class="icon icon-link"></span></a>Links</h2>
<p>Reference:</p>
<ul>
<li><a href="product-engineering/strategy-goals">Current strategy</a></li>
<li><a href="product-engineering/team">Current team</a></li>
<li><a href="https://sourcegraph.looker.com/boards/20">KPIs</a></li>
<li><a href="./product-engineering/team-culture/department-meeting">Department Meeting</a></li>
<li><a href="product-engineering/team-culture">Team rituals</a></li>
</ul>
<p><a href="product-engineering/process">How to</a>:</p>
<ul>
<li><a href="./product-engineering/process/headcount-planning">Headcount planning</a></li>
<li><a href="./product-engineering/process/planning">Planning</a></li>
<li><a href="./product-engineering/process/reporting-progress">Reporting progress</a></li>
</ul>
</section><section class="h2Wrapper headingWrapper"><h2 id="handbook-organization"><a class="anchor" aria-hidden tabindex="-1" href="#handbook-organization"><span class="icon icon-link"></span></a>Handbook organization</h2>
<p>Documentation that is relevant to both product and engineering belongs in the top-level product-engineering folder.</p>
<p>Documentation that is primarily or exclusively relevant to product or engineering belongs in the appropriate product or engineering subfolder.</p></section></section></section>

Product and Engineering