From 1ae55c793fad01076f3b10a40c64e8020a839d23 Mon Sep 17 00:00:00 2001 From: Chris Sells Date: Wed, 17 Jan 2024 13:13:49 -0800 Subject: [PATCH] added emphasis to review effectiveness (#8449) --- content/departments/engineering/product-planning.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/departments/engineering/product-planning.md b/content/departments/engineering/product-planning.md index f2570e531886..fb30ec0f583f 100644 --- a/content/departments/engineering/product-planning.md +++ b/content/departments/engineering/product-planning.md @@ -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.