> For the complete documentation index, see [llms.txt](https://iam.highonproduct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://iam.highonproduct.com/modules/building-your-profile/pm-projects-what-you-need-to-know.md).

# PM Projects: What You Need to Know

### **What is a PM Project?**

Proof of work to show that you’ve done some work in or related to the PM field. 

### **Why do you need projects?**

* Adds weight to your CV (especially when you’re in early college with little-to-zero experience)
* Signals your strengths to the interviewer 
* More impressive projects make you stand out from the crowd

### **What makes a good project?**

* [x] Sticking to the basics
* [x] Being user-first
* [x] Ideas are prioritized + quantifiable
* [x] Ties into team expectations, business value and company vision

{% hint style="info" %}
Use this as a checklist in the future!
{% endhint %}

### **What do each of these signal?**

* You consider the user’s pain points
* You will track, iterate and improve
* You are a true ‘manager’

<figure><img src="https://1497394829-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjuZ4cfYiBjTKCnpI7Tua%2Fuploads%2F52iFR1tlODXhXb4T7W9m%2Fimage.png?alt=media&amp;token=e26dfa62-3310-4153-89c3-1270bd52c16c" alt=""><figcaption><p>©️ High On Product</p></figcaption></figure>

Do read this blog by Julie Zhuo for product critique and deep insights on how to see product management in two lenses:

{% embed url="<https://medium.com/the-year-of-the-looking-glass/how-to-do-a-product-critique-98b657050638>" %}

Continuing from Julie's blog, Manas Saloi's post adds more ideas and ways to make your product critique better. (Also, Manas Saloi is a great resource for any questions about products.)

{% embed url="<https://manassaloi.com/2020/12/01/product-critique.html>" %}

### Where to find PM Projects?

* Your own ideas and observations
* LinkedIn (Search Flipkart APM decks/Nextleap GP/Insurjo Projects)
* PM School Weekly Challenge
* Product Competitions
* High On Product :)

The next page will help you get started:

{% content-ref url="/spaces/juZ4cfYiBjTKCnpI7Tua/pages/3vY4r46ilu8L08Rqc5fU" %}
[How-Tos to Get Started](/modules/building-your-profile/how-tos-to-get-started.md)
{% endcontent-ref %}

### **What should you do after all this?**

* [x] Make a Product Portfolio
* [x] Make it interesting, add a pinch of your personality, humor and emojis.

- **High Effort:** Personal Website
- **Low Effort:** Use Notion (Refer to [this thread](https://twitter.com/Rahul_J_Mathur/status/1687738487934464000\)))

{% embed url="<https://twitter.com/Rahul_J_Mathur/status/1687738487934464000>)" %}
<https://twitter.com/Rahul\\_J\\_Mathur/status/1687738487934464000>)
{% endembed %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://iam.highonproduct.com/modules/building-your-profile/pm-projects-what-you-need-to-know.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.