Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

added emphasis to review effectiveness #8449

Merged
merged 1 commit into from
Jan 17, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions content/departments/engineering/product-planning.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,14 +51,14 @@ quarter. Likewise, not every work item is expected to meet a strategic goal.

Some tips for having an effective review:

- Make sure the priorities for your work is clear -- what's Must Have (P0),
- **Make sure the priorities for your work is clear** -- what's Must Have (P0),
Want To Have (P1) and Nice To Have (P2)? What could get cut?
- Make sure the customer (internal and/or external) impact is clear -- if we do
this work, what's going to be the value to the customer?
- Make sure the business impact is clear -- if we do this work, how does that
- **Make sure the customer (internal and/or external) impact is clear** -- if
we do this work, what's going to be the value to the customer?
- **Make sure the business impact is clear** -- if we do this work, how does that
help us achieve our strategic goals?
- In addition to ensuring that the EPD team is aligned before heading into the
review, try to get as much alignment with execs ahead of time as possible.
review, **try to get as much alignment with execs ahead of time as possible.**

I've noticed that the teams the follow this tips have a smoother review process.

Expand Down
Loading