Inaugural online book | Application Concepting Series No. 1



100 Ideas for Envisioning Powerful, Engaging, and Productive User Experiences in Knowledge Work

Download E-Book or Order Softcover Book



In addition to this website, Working through Screens
is available in several other formats:

    - Softcover print on demand books (NEW)

    - Free letter size .pdf (NEW)

    - Free large format .pdf

    - Free "Idea Cards" .pdf


View all Working through Screens Formats

Email List

Join our email list to receive updates about our publications:


Contact Our Consulting Studio

Contact Flashbulb Interaction to find out how we can help your team to better conceptualize and deliver your next application design.

E: info@FlashbulbInteraction.com
P: 206.280.3135

View Jacob Burghardt's profile on LinkedIn

Latest Studio Updates

From our FlashbulbUX Twitter feed:
  •  
Follow Flashbulb Interaction Studio Updates on Twitter



Feedback on Working through Screens?

Email us your thoughts or Twitter @FlashbulbUX

Application Envisioning idea
C8.
Defaults, Customization, and Automated Tailoring



Knowledge workers may want to make persistent changes to default settings in order to tailor how they interact with a computing tool. Product teams can endeavor to create useful defaults; provide clear, consistent, and direct means of changing them; and consider scenarios for useful automation around some setting changes.






Examples from three knowledge work domains:
(Illustrated above) A scientist modifies a certain parameter to influence how her analysis application will automatically compute a derived clinical variable. After double checking the effects of this parameter change within her most commonly used visualizations and procedures, she sets the modified value as the default setting for all new studies.

An architect finds that the input settings of a drawing tool in her building modeling application are making some parts of her work unnecessarily painstaking. She navigates to a single screen that contains all of her application preference settings and decreases the particular tool’s sensitivity to input.

A financial trader updates important automation defaults in his trading application that dictate how the computing tool will adaptively fill in proposed information under different circumstances.
In specialized products for knowledge work, a single parameter can make or break the effectiveness of an entire system. Product teams can envision default settings for their interactive applications that are optimized to cover the most common scenarios of use (A4) or the broadest variety of work practice (A6, A7, A8).

When default settings have the potential to shape workers’ interactions or outcomes in ways that are not in alignment with their goals, applications can provide customization functionality that allows for local modification of key parameters (C5, F8). Product teams can envision these customizations at the level of individual workers, larger groups, or entire organizations (B10).

In carefully selected cases, workers may appreciate suggested or automated tailoring of settings (E3) based on their logged behaviors within an application. To avoid confusion, definers and designers can envision ways to clearly communicate these adaptive changes (B6, F11, H4) as well as provide methods to easily reinstate earlier values (E6).

When product teams do not sufficiently consider the potential role of defaults, customization, and automated tailoring, resulting computing tools may not be suitably configured or configurable for the particulars of knowledge work. Opportunities for close alignment with work practices can be lost, and individuals may struggle through their adoption experiences (K), potentially creating and enacting excessively effortful work arounds (D2, D3).

Conversely, extensive changes to defaults may reduce representational common ground between workers (F1, J2) that is often needed for effective communication (J) and collaboration (B7, C7, G4).

See also: A, C, F, I, K11, M4




Application Envisioning questions:

How might your team clarify and reduce the effort needed to understand and set important parameters in your application concepts? How could the interplay of appropriate default values, manual customization, and automated tailoring enhance your product’s effectiveness across a breadth of targeted contexts?

More specific questions for product teams to consider:
Which variabilities in the operations, tasks, or larger activities that your team is striving to mediate might lead to a genuine need for customization options?

Which default settings in your team’s application concepts will individuals and organizations expect to have some control over? Why?

Which settings stand out as pivotal in your team’s sketched ideas for work mediation? Which will probably not capture workers’ interests and may only be accessed rarely, if at all?

What larger design and technology trends could influence your ideas about defaults and local tailoring of settings within your computing tool?

Which defaults in your application concepts could be optimized by covering the most common scenarios of use in targeted organizations?

Which defaults might be better optimized by considering the broadest variety of work practice?

Which parameters might be impossible for your team to set defaults for without local input from individual workers or their organizations?

Where could automated tailoring of settings be appropriate, useful, and clearly executed? Might it be more appropriate for such automations to suggest changes that workers could then select as customizations?

How might the scope of a single setting change apply to individual workers, larger groups, or entire organizations?

How could a central area for settings changes within your application’s framework enhance the clarity of related tasks?

How might new or unexpected changes to defaults be flagged and meaningfully communicated?

What negative impacts could changes to defaults have on cooperative and collaborative work? How might these impacts be mitigated?

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

All original contents of Working through Screens online book are subject to
the creative commons license (Attribution-NonCommercial- ShareAlike http://creativecommons.org/licenses/by-nc-sa/3.0/) unless otherwise noted.
Please attribute the work to “Jacob Burghardt / FLASHBULB INTERACTION Consultancy.”