China
Africa
Explore chapters and articles related to this topic
Program Benefits Management
Published in Ginger Levin, PgMP® Practice Test Questions, 2018
List of planned benefits.Map of the planned benefits to the components.Measurement of each benefit.KPIs and their thresholds.Risk assessment and probability.Status or progress indicators.Target dates and milestones.Person, group, or organization responsible.Process to measure progress against the benefits plan.Tracking and communicating progress to stakeholders.
Rules of Thumb
Published in Tamara Munzner, Visualization Analysis and Design, 2014
From the user's point of view, the latency of an interaction is the time between their action and some feedback from the system indicating that the operation has completed. In a vis system, that feedback would most naturally be some visual indication of state change within the system itself, rather than cumbersome approaches such as printing out status indications at the console or a popup dialog box confirmation that would interfere with the flow of exploration. The most obvious principle is that the user should indeed have some sort of confirmation that the action has completed, rather than being left dangling wondering whether the action is still in progress, or whether the action never started in the first place (for example, because they missed the target and clicked on the background rather than the intended object). Thus, feedback such as highlighting a selected item is a good way to confirm that the desired operation has completed successfully. In navigation, feedback would naturally come when the user sees the new frame is drawn from the changed viewpoint. Visual feedback should typically take place within the immediate response latency class: around one second. Another principle is that if an action could take significantly longer than a user would naturally expect, some kind of progress indicator should be shown to the user. A good rule of thumb for significantly longer is crossing from one latency class into another, as shown in Table 6.1.
Time swipes when you’re having fun: reducing perceived waiting time while making it more enjoyable
Published in Behaviour & Information Technology, 2023
Christof Van Nimwegen, Emiel Van Rijn
Two types of progress indicators are distinguished in design-guidelines by Apple (Apple Inc. 2019) and Google (Google Inc. 2016). These can be determinate and indeterminate. Determinate progress indicators indicate actual progress towards completion (e.g. progress bar), while indeterminate progress indicators only indicate the system is ‘busy’ (e.g. a spinner). Sherwin (2014) proposed (based on interaction thresholds proposed by Nielsen 1994) for ‘instantaneous’ actions (<1 second) one should not provide any visual feedback. When actions take longer than 1 second, but less than ten, feedback can be provided by an indeterminate progress indicator. When actions take longer than 10 seconds users should be provided with a determinate progress indication as users tend to quickly grow impatient at this duration. Other resources, however, suggest that a spinner should only be used for up to 5 seconds, as interactions with a longer duration break continuity (Shneiderman et al. 2016; Google Inc. 2016). The following progress indicators are common: