Define what success looks like for pdflow along with supporting metrics and tracking plan
Currently the only agreed upon way we have to track success for the new draft pd-flow is surveying for NPS. While this will be a valid checkpoint, it is a lagging indicator (we won't be able to effectively survey prior to full adoption over a few cycles) and it's qualitative only.
Per the pd-flow WG's exit criteria we want to have qualitative and quantitative measures. What are some good potential quantitative ways to measure success of the new pd-flow?
Sisense Cycle Time Reporting
Before vs. After PDF Page Comparison
Collaboration Touchpoints | Total Steps | Word Count | |
---|---|---|---|
Old Flow | Total = 11 Validation phase 1: 2 (sensing mechanisms, feedback from internal/community) Validation Phase 2: 2 (working with designer to refine backlog, working with research) Validation Phase 3: 1 (team review of proposed solution) Validation Phase 4: 1 (PM and Designer collaborate with research) Review Step: 1 Build Phase 1: 1 (review and breakdown of designs as a team) Build Phase 2: 2 (instrumentation, release post) Build Phase 3: 1 (dogfooding) Build Phase 4: n/a? (this was already updated) |
Total = 68 Validation phase 1: 3 Validation Phase 2: 9 Validation Phase 3: 4 Validation Phase 4: 17 Review Step: 6 Build Phase 1: 12 Build Phase 2: 10 Build Phase 3: 4 Build Phase 4: 3 |
6025 |
New Flow | Total = 37 - 3x+ increase Validation phase 1: 4 (sensing mechanisms, feedback from stakeholders, listing who to inform, who to collaborate with) Validation Phase 2: 5 (working with research, listing who to inform, listing who to collaborate with, communicate with stable counterparts and stakeholders, consider review with leadership) Validation Phase 3: 9 (listing who to collaborate with, who to inform, diverge as team, converge as team, validate approach with stakeholders, user validation, review proposal with team, review with leadership, engage engineering peers) Validation Phase 4: 3 (who to collaborate with, who to inform, gather feedback from stakeholders) Review Step: 1 Build Phase 1: 5 (who to collaborate with, who to inform, review with contributors, POC with engineering, quad planning) Build Phase 2: 6 (who to collaborate with, who to inform, keep stakeholders informed regularly, asynchronous updates, SET activities, technical writers review docs) Build Phase 3: 4 (who to inform, who to collaborate with, follow up with stakeholders, release post, dogfooding) Build Phase 4: n/a? (not going to do a compare here) |
Total = 30 - great than 50% reduction Validation phase 1: 2 Validation Phase 2: 2 Validation Phase 3: 4 Validation Phase 4: 2 Review Step: 6 Build Phase 1: 3 Build Phase 2: 2 Build Phase 3: 6 Build Phase 4: 3 |
4934 (18% reduction) |
Edited by Michael Karampalas