Draft Code Reviewer Outcome Statements
Ask
@afracazo and @mle Please fill out the remaining desired outcome statements in this Google Sheet under the Code Reviewer Outcomes Tab.
@phikai @leducmills, please review and keep us sane.
Goal
Create predictable, repeatable, low-effort, high-efficacy, consistent scoring methods and consistent feedback loops.
- Evaluate the entire Main Job & Prioritize using the ODI/Outcome Opportunity Score survey.
- Baselining (UX Scorecard, CM Scorecard, Heuristic Evaluation) Evaluate the Main Job
- Solution Validation: Evaluate the aspect of the Main Job you are working from to create the design solution (i.e., Small Job + its related Outcome Statements)
What
A desired outcome is the benchmark by which Job Performers gauge success in accomplishing a task. Progress is assessed across three key dimensions: speed, predictability, and efficiency. Advancement along these dimensions signifies both functional and emotional progression in achieving core (i.e., Main Jobs that represent the primary purpose of the product) or consumption (i.e., buying, setting up, maintaining, upgrading, the product, etc.) tasks:
- Speed: Progress is marked by completing tasks faster, reducing the time required for accomplishment.
- Predictability: Progress entails increased reliability and decreased likelihood of deviations or errors.
- Efficiency: Progress is achieved by minimizing waste and optimizing output.
The ideal scenario for Job Performers involves instant task completion, 100% predictability, and 0% efficiency loss. Such perfection facilitates progress and fulfills associated functional and emotional needs.
How
When determining the altitude for Outcome Statements, keep it simple and use the Job Map for reference. Thinking back to your interviews, ask yourself what potential roadblocks the Job Performer tends to have when attempting to complete this Job Stage (be sure to reference your interview data as the foundation for this assessment). Use each Job Step within the Job Stage to continue the assessment. As you go, create Outcome Statements for Speed, Predictability, and Efficiency following the formulas below:
Dimension | Definition | Formula |
---|---|---|
Speed | Measured by time. Progress is evaluated by minimizing the time required to accomplish a specific task in a given context. | Minimize the time it takes to [accomplish something] [in some context] when getting a job done. |
Predictability | Measured using likelihood as the metric. Progress is determined by minimizing the likelihood of undesired outcomes in task completion. | Minimize the likelihood that [some unwanted thing happens] [in some context] when getting a job done. |
Efficiency | Measured using likelihood as the metric. Progress is gauged by minimizing the likelihood of actions leading to waste or inefficiency in task completion. | Minimize the likelihood of [doing something that causes waste/inefficiency] [in some context] when getting a job done. |
You should have an Outcome Statement for each progress dimension (i.e., if you determine that an Outcome for Speed is warranted, then you should continue on that thread and create one for Predictability and one for Efficiency). For example, in the Job Step, Understand the change request information
.
Dimension | Outcome Statement |
---|---|
Speed | Minimize the time it takes to understand the change request information |
Predictability | Minimize the likelihood that the change request information is incorrect |
Efficiency | Minimize the likelihood of asking for more information about the changes |