Application Envisioning idea
A2.

Social interactions in knowledge work activities often involve multiple categories of organizational roles and outside stakeholders. The cultural characteristics of knowledge workers’ social worlds can pose key challenges and opportunities for product teams as they attempt to outline
appropriate and compelling design strategies.

Examples from three knowledge work domains:
(Illustrated above) An architect typically works with other architects on her team, project managers and partners within her studio, a variety of specialized external consultants, and her clients. As a broad generalist, she has different goals, expectations, and methods of working with each of these groups, and she wants to use computing tools that will not get in the way of these differing approaches.
A financial trader typically works with other traders, back office support, several levels of management, and many business contacts outside his firm. The technologies and processes that his company has built up over time express underlying, top down — yet shared — norms and values about how these different groups should formally interact.
A scientist typically works with other researchers in her clinical lab, the lab’s technicians, representatives from regulatory bodies, a number of vendors, principle investigators at other labs, and members of the scientific community at large. As the head of her lab, she wants to have some measure of control over all of its key internal and public interactions.
Knowledge work is often performed within complex social spheres that contain a range of overlapping cultural expectations (A1). As part of everyday work practice, successful individuals can become skilled at acting within, and making use of, certain interpersonal relationships.
Product teams can model these relationships in search of valuable insights that could be meaningfully reflected in their divergent application concepts. Conventional professional practices, along with understood workflow and power structures within organizations, may dictate how different actors work together to accomplish certain outcomes (A4, C6). Additionally, local ways of working may arise organically from a shared grounding of implicit norms and customs, which can be reflected in divisions of labor (A7, A8) and resulting artifacts (B).
When product teams do not actively consider how the specifics of workers’ social worlds might impact their emerging ideas about work mediation and application scope, opportunities to clearly situate a product in the context of these interpersonal networks can be lost. Applications that do not allow expected social interactions or reflect expected power relationships (A2, C5, B7) can be more difficult for workers to learn (D2, K2, K6) and may not be seen as useful or attractive options (D3, K3). These products may also not adequately support important cooperative or collaborative work practices (C7, G4) such as handoffs (G7, J3) and other forms of communication (J).
See also: A, B8, C8, M

Application Envisioning questions:
How could your team’s insights into the connectivities and
qualities of targeted knowledge workers’ relationships shape your application concepts? How might your computing tool usefully and meaningfully reflect these social realities?
More specific questions for product teams to consider:
How are workforces divided up in the organizations that your team might be targeting with your interactive application?
What roles do different groups of knowledge workers play in the context of
different activities?
How do these groups of workers overlap and interrelate? How could your team characterize their goals and attributes based on observed relations in real world settings?
Which social network ties and interpersonal interactions are the most important
for successful work practice?
Which ties do targeted workers enjoy and value?
Which interactions are problematic? Could these breakdowns represent opportunities for your product?
What directions are these interpersonal connections trending in? What changes
in organizational relationships have occurred in the recent past?
What overriding management attitudes about workers’ interrelations could influence the success of your computing tool?
How might different models and understandings of these social factors allow your team to envision application concepts that could improve valued interpersonal interactions for all involved?
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
|