Application Envisioning idea
B3.

Some knowledge work applications contain interaction
objects that are extensions of, rather than replacements for, offline artifacts. In these cases, product teams can envision interactions that tightly couple onscreen and off screen equivalents in order to promote a more efficient, direct,
and unified experience.

Examples from three knowledge work domains:
(Illustrated above) A scientist places a test tube containing a clinical sample into a rack next her computer workstation. Her lab’s information management application reads a signal emitted from a small tag on the test tube, then displays stored information about the tube’s contents on her screen.
An architect scans a cardboard model of a building form into her building modeling application. She gives the computing file the same name as the one she has written in black marker on the cardboard version.
A financial trader scans a barcode on a paper trade cancellation form that was faxed to him. His trading application pulls up the associated trade and prompts him to initiate the cancellation process.
The adoption of computing into knowledge work practices typically does not mean that workers will suddenly switch to only manipulating symbols on screens. In many types of knowledge work, tangible, real world objects can remain an important part of individual or collaborative behaviors (A).
The coupling of offline objects to their digital equivalent, or other associated content within a computing tool (G6), can be considered a special type of coordination between representations of workplace information (F1). The experience of carefully designed, tightly coupled coordinations can extend both into and out of a computer’s display. Physical objects can become interactive entry points into an application’s content. From the other side of the relationship, onscreen interactions can map back toward physical objects, potentially creating new forms of pervasive awareness and telepresence.
Product teams can envision compelling, goal oriented experiences of connective threads between the screen and material objects. At a minimum, common identifying information (B2) between tangible artifacts and their application equivalents can act as a coordinating link (G5). Some knowledge work domains present opportunities for teams to envision more extensive coordination of the physical and the intangible, based on, for example, well characterized transition points in work sequences (D5, G1, J3).
When product teams do not actively consider where bridges between physical and digital objects could be compelling, feasible, and valuable in their application concepts, opportunities to provide a powerful sense of direct action and engagement can be lost (K13). Workers may experience online and offline instances of an object as disjointed and separate, which can make such applications more effortful to use when compared with potential scenarios of interactive connection (D2, D3, K2, K6).
See also: B, E, F1, F9, G, H4, I5, J2, J5, J7, L3, M1

Application Envisioning questions:
What interaction objects in your team’s application concepts could benefit from a preserved connection to related off screen artifacts? What functionality concepts might your team envision to allow targeted knowledge workers to usefully recognize and meaningfully act through these connections?
More specific questions for product teams to consider:
What real world objects in the work practices that your team is striving to mediate are not likely not be replaced by an onscreen equivalent?
What scenarios could potentially lead to new physical objects being created based on the contents of your product?
What types of targeted organizations might be more likely to “hold onto” the physical incarnations of their otherwise onscreen work? Why?
What targeted tasks or larger activities might benefit from the tandem use of both physical and digital instantiations of an artifact?
What coordinations between interaction objects and their off screen equivalents, such as matching identification information, could provide clarifying utility and reduce workers’ efforts?
What larger technology and market trends could influence your team’s ideas about intentionally coupling physical and digital objects? What might be feasible if the value proposition was compelling enough?
What valued characteristics of real world objects could be difficult to include in corresponding onscreen objects, and vice versa?
How might these deficiencies drive workers to turn to the “other” version of an object? How could these transitions be crystallized into goal directed interaction pathways within your application concepts?
What novel interaction methods might your team envision to tightly couple certain real world objects with associated content in your computing tool? How could these methods directly bridge well characterized seams in specific work practices?
Do you have enough information to usefully answer these and other envisioning questions? What additional research, problem space models, and design concepting could valuably inform your team’s application envisioning efforts?
< PREVIOUS PAGE | NEXT PAGE >

Back to top | View Table of Contents
|