Idea Category
K.

Valued computing tools can be designed to make “getting up to speed” as painless as possible.
Designing for such easy integration requires a clear understanding of the gaps that people will need to bridge in order to make use of
a tool.
During application envisioning, product teams can map and explore how targeted knowledge workers and their organizations might integrate new onscreen offerings into their working cultures and technological systems.
By taking time to explore potential product adoption experiences — in an expansive sense — teams can identify opportunities to set the stage for direct, trusted, extensive, and meaningful use.

Although technologies can deterministically drive some changes once they are made part of working cultures, only individuals and organizations can truly determine
whether computing tools will be successfully adopted into their own environments. Technologies do not create major cultural changes on their own, and brand messaging, or other background context, can only provide a frame for users’ embedded, concrete, and personal experiences with a new product. That being said, the particular design characteristics of an application can play a major role in whether and how integration into practice occurs.
Rather than waiting for their technologies to be finished before thinking through
potential adoption hurdles, product teams can consider adoption scenarios as part of generating their essential design strategy, envisioning services and functionality concepts to ease important learning and systemic challenges. Teams can envision these offerings and approaches as much broader responses than conventional, somewhat
dissociated “user assistance,” anticipating common needs and connecting with
knowledge workers in meaningful and lasting ways.
This category contains 13 of the 100 application envisioning ideas in this book:
K1. Application localization
K2. Introductory user experience
K3. Recognizable applicability to targeted work
K4. Verification of operation
K5. Understanding and reframing alternate interpretations
K6. Design for frequency of access and skill acquisition
K7. Clear and comprehensive instructional assistance
K8. Seamless inter-application interactivity
K9. Directed application interoperation
K10. Openness to application integration and extension
K11. End user programming
K12. Trusted and credible processes and content
K13. Reliable and direct activity infrastructure
Product teams can use these ideas to explore specific means of supporting individual users, and larger customer organizations, as they transition from current practices to practices mediated by their new or updated computing tools. Early ideation and
concepting focused on that support, rather than post hoc efforts during the final
stages of a product’s development, can help teams more fully integrate supportive
options into their products’ available user experiences.
The central notion of this category is most closely related to the “Exploring work
mediation and determining scope” (A), “Considering workers’ attentions” (D), and “Planning connection with use” (M) categories.
< PREVIOUS PAGE | NEXT PAGE >

Back to top | View Table of Contents
|