Idea Category
G.

Valued computing tools can support knowledge workers’ primary goals with truly compelling arcs of interaction.
The design of these central interactions can make or brake users’ perceptions of an onscreen product.
During application envisioning, product teams can simultaneously consider potential design strategies at both the macro, framework level, and at the lower level of important individual scenarios.
By taking time to explore divergent directions for a product’s central experiences, teams can discover important new design factors while at the same time addressing some more common needs in the design of onscreen pathways.

When using a new computing tool, people do not typically weigh all of its available options equally. Instead, they may heavily weigh their user experiences within a small subset of supported work practices, giving those areas a disproportionate emphasis in their larger judgements of a tool’s overall value. With this effect in mind, product teams’ larger ideas about design strategy and scoping often need to be thought through at the level of these crucial interactions before their application concepts can truly be considered viable.
A challenge for teams envisioning specific interactions is to not take sketching certain details so far as to limit the breadth of their explorations. Conversations about specific functionality concepts can easily return to the relatively uncritical straight to the details progression, limiting meaningful concepting around the different “shapes” that key experiences might take. During application envisioning, sketching relatively granular interactions can mean working through design possibilities with only as much detail
as is necessary to establish their key attributes and assess their viability.
As product teams move from high level models of work mediation down to sketching ideas for central interactions, they may identify some characteristic factors that often apply to computing tools for knowledge work. These common challenges and opportunities can be present whether an envisioned product is in a mature, understood genre or represents a novel, disruptive technology.
This category contains 7 of the 100 application envisioning ideas in this book:
G1. Narrative experiences
G2. Levels of selection and action scope
G3. Error prevention and handling in individual interactions
G4. Workspace awareness embedded in interactions
G5. Impromptu tangents and juxtapositions
G6. Contextual push of related information
G7. Transitioning work from private to public view
Product teams can use these ideas to explore concepts for effectively translating big picture ideas about work mediation into more concrete user experience scenarios. Some extra ideation around important functionality concepts can help teams drive high level considerations down to crucial interactions, without getting lost in every definition, design, and implementation detail. This additional concepting can also provide definers and designers with more opportunities to discover and model factors that could be pivotal across many of their products’ interactive threads.
The central notion of this category is most closely related to the “Exploring work mediation and determining scope” (A), “Defining interaction objects” (B), “Establishing an application framework” (C), and “Considering workers’ attentions” (D) categories.
< PREVIOUS PAGE | NEXT PAGE >

Back to top | View Table of Contents
|