Tag: information_architecture

Defining and Applying a Language for Discovery

May 7th, 2014 — 1:10pm

Last year, I had the plea­sure of col­lab­o­rat­ing on a paper with Tony Russell-Rose and Stephann Makri that builds on and extends our work to under­stand and artic­u­late a frame­work for dis­cov­ery needs and activ­i­ties — what we refer to as the Lan­guage of Dis­cov­ery — show­ing exam­ples of con­crete appli­ca­tion and use.

It’s been a while in com­ing, but I’m happy to say the com­plete paper ‘Defin­ing and Apply­ing a Lan­guage for Dis­cov­ery’ — is avail­able now.

I’ve repro­duced the com­plete text of the paper below, and there’s also a pdf for download.



In order to design bet­ter search expe­ri­ences, we need to under­stand the com­plex­i­ties of human information-seeking behav­iour. In this paper, we pro­pose a model of infor­ma­tion behav­iour based on the needs of users across a range of search and dis­cov­ery sce­nar­ios. The model con­sists of a set of modes that users employ to sat­isfy their infor­ma­tion goals.

We dis­cuss how these modes relate to exist­ing mod­els of human infor­ma­tion seek­ing behav­iour, and iden­tify areas where they dif­fer. We then exam­ine how they can be applied in the design of inter­ac­tive sys­tems, and present exam­ples where indi­vid­ual modes have been imple­mented in inter­est­ing or novel ways. Finally, we con­sider the ways in which modes com­bine to form dis­tinct chains or pat­terns of behav­iour, and explore the use of such pat­terns both as an ana­lyt­i­cal tool for under­stand­ing infor­ma­tion behav­iour and as a gen­er­a­tive tool for design­ing search and dis­cov­ery experiences.

1 Introduction

Clas­sic IR (infor­ma­tion retrieval) is pred­i­cated on the notion of users search­ing for infor­ma­tion in order to sat­isfy a par­tic­u­lar ‘infor­ma­tion need’. How­ever, much of what we rec­og­nize as search behav­iour is often not infor­ma­tional per se. For exam­ple, Broder [2] has shown that the need under­ly­ing a given web search could in fact be nav­i­ga­tional (e.g. to find a par­tic­u­lar site) or trans­ac­tional (e.g. through online shop­ping, social media, etc.). Sim­i­larly, Rose & Levin­son [12] have iden­ti­fied the con­sump­tion of online resources as a fur­ther com­mon cat­e­gory of search behaviour.

In this paper, we exam­ine the behav­iour of indi­vid­u­als across a range of search sce­nar­ios. These are based on an analy­sis of user needs derived from a series of cus­tomer engage­ments involv­ing the devel­op­ment of cus­tomised search applications.

The model con­sists of a set of ‘search modes’ that users employ to sat­isfy their infor­ma­tion search and dis­cov­ery goals. It extends the IR con­cept of information-seeking to embrace a broader notion of discovery-oriented prob­lem solv­ing, address­ing a wider range of infor­ma­tion inter­ac­tion and infor­ma­tion use behav­iours. The over­all struc­ture reflects Marchionini’s frame­work [8], con­sist­ing of three ‘lookup’ modes (locate, ver­ifymon­i­tor), three ‘learn’ modes (com­pare, com­pre­hendeval­u­ate) and three ‘inves­ti­gate’ modes (explore, ana­lyze, syn­the­size).

The paper is struc­tured as fol­lows. In Sec­tion 2 we dis­cuss the modes in detail and their rela­tion­ship to exist­ing mod­els of infor­ma­tion seek­ing behav­iour. Sec­tion 3 describes the data acqui­si­tion and the analy­sis process by which the modes were derived. In Sec­tion 4 we inves­ti­gate the degree to which the model scales to accom­mo­date diverse search con­texts (e.g. from consumer-oriented web­sites to enter­prise appli­ca­tions) and dis­cuss some of the ways in which user needs vary by domain. In addi­tion, we explore the ways in which modes com­bine to form dis­tinct chains or pat­terns, and reflect on the value this offers as a frame­work for express­ing com­plex pat­terns of infor­ma­tion seek­ing behaviour.

In Sec­tion 5 we exam­ine the prac­ti­cal impli­ca­tions of the model, dis­cussing how it can be applied in the design of inter­ac­tive appli­ca­tions, at both the level of indi­vid­ual modes and as com­pos­ite struc­tures. Finally, in Sec­tion 6 we reflect on the gen­eral util­ity of such mod­els and frame­works, and explore briefly the qual­i­ties that might facil­i­tate their increased adop­tion by the wider user expe­ri­ence design community.

2 Models of Information Seeking

The frame­work pro­posed in this study is influ­enced by a num­ber of pre­vi­ous mod­els. For exam­ple, Bates [1] iden­ti­fies a set of 29 search ‘tac­tics’ which she organ­ised into four broad cat­e­gories, includ­ing mon­i­tor­ing (“to keep a search on track”). Like­wise, O’Day & Jef­fries [11] exam­ined the use of infor­ma­tion search results by clients of pro­fes­sional infor­ma­tion inter­me­di­aries and iden­ti­fied three cat­e­gories of behav­iour, includ­ing mon­i­tor­ing a known topic or set of vari­ables over time and explor­ing a topic in an undi­rected fash­ion. They also observed that a given search sce­nario would often evolve into a series of inter­con­nected searches, delim­ited by trig­gers and stop con­di­tions that sig­nalled tran­si­tions between modes within an over­all scenario.

Cool & Belkin [3] pro­posed a clas­si­fi­ca­tion of inter­ac­tion with infor­ma­tion which included eval­u­ate and com­pre­hend. They also pro­posed cre­ate and mod­ify, which together reflect aspects of our syn­the­size mode.

Ellis and his col­leagues [4, 5, 6] devel­oped a model con­sist­ing of a num­ber of broad infor­ma­tion seek­ing behav­iours, includ­ing mon­i­tor­ing and ver­i­fy­ing(“check­ing the infor­ma­tion and sources found for accu­racy and errors”). In addi­tion, his brows­ing mode (“semi-directed search­ing in an area of poten­tial inter­est”) aligns with our def­i­n­i­tion of explore. He also noted that it is pos­si­ble to dis­play more than one behav­iour at any given time. In revis­it­ing Ellis’s find­ings among social sci­en­tists, Meho and Tibbo [10] iden­ti­fied analysing (although they did not elab­o­rate on it in detail). More recently, Makri et al [8] pro­posed search­ing(“for­mu­lat­ing a query in order to locate infor­ma­tion”), which reflects to our own def­i­n­i­tion of locate.

In addi­tion to the research-oriented mod­els out­lined above, we should also con­sider practitioner-oriented frame­works. Spencer [14] sug­gests four modes of infor­ma­tion seek­ing, includ­ing known-item (a sub­set of our locate mode) andexploratory (which mir­rors our def­i­n­i­tion of explore). Laman­tia [7] also iden­ti­fies four modes, includ­ing mon­i­tor­ing.

In this paper, we use the char­ac­ter­is­tics of the mod­els above as a lens to inter­pret the behav­iours expressed in a new source of empir­i­cal data. We also exam­ine the com­bi­na­to­r­ial nature of the modes, extend­ing Ellis’s [5] con­cept of mode co-occurrence to iden­tify and define com­mon pat­terns and sequences of infor­ma­tion seek­ing behaviour.

3 Studying Search Behaviour

3.1 Data Acquisition

The pri­mary source of data in this study is a set of 381 infor­ma­tion needs cap­tured dur­ing client engage­ments involv­ing the devel­op­ment of a num­ber of cus­tom search appli­ca­tions. These infor­ma­tion needs take the form of ‘micro-scenarios’, i.e. a brief nar­ra­tive that illus­trates the end user’s goal and the pri­mary task or action they take to achieve it, for example:

  • Find best offers before the oth­ers do so I can have a high margin.
  • Get help and guid­ance on how to sell my car safely so that I can achieve a good price.
  • Under­stand what is sell­ing by area/region so I can source the cor­rect stock.
  • Under­stand a portfolio’s expo­sures to assess invest­ment mix
  • Under­stand the per­for­mance of a part in the field so that I can deter­mine if I should replace it

The sce­nar­ios were col­lected as part of a series of require­ments work­shops involv­ing stake­hold­ers and customer-facing staff from var­i­ous client organ­i­sa­tions. A pro­por­tion of these engage­ments focused on consumer-oriented site search appli­ca­tions (result­ing in 277 sce­nar­ios) and the remain­der on enter­prise search appli­ca­tions (104 scenarios).

The sce­nar­ios were gen­er­ated by par­tic­i­pants in break­out ses­sions and sub­se­quently mod­er­ated by the work­shop facil­i­ta­tor in a group ses­sion to max­imise con­sis­tency and min­imise redun­dancy or ambi­gu­ity. They were also pri­ori­tised by the group to iden­tify those that rep­re­sented the high­est value both to the end user and to the client organisation.

This data pos­sesses a num­ber of unique prop­er­ties. In pre­vi­ous stud­ies of infor­ma­tion seek­ing behav­iour (e.g. [5], [10]), the pri­mary source of data has tra­di­tion­ally been inter­view tran­scripts that pro­vide an indi­rect, ver­bal account of end user infor­ma­tion behav­iours.  By con­trast, the cur­rent data source rep­re­sents a self-reported account of infor­ma­tion needs, gen­er­ated directly by end users (although a pro­por­tion were cap­tured via proxy, e.g. through cus­tomer fac­ing staff speak­ing on behalf of the end users). This change of per­spec­tive means that instead of using infor­ma­tion behav­iours to infer infor­ma­tion needs and design insights, we can adopt the con­verse approach and use the stated needs to infer infor­ma­tion behav­iours and the inter­ac­tions required to sup­port them.

More­over, the scope and focus of these sce­nar­ios rep­re­sents a fur­ther point of dif­fer­en­ti­a­tion. In pre­vi­ous stud­ies, (e.g. [8]), mea­sures have been taken to address the lim­i­ta­tions of using inter­view data by com­bin­ing it with direct obser­va­tion of infor­ma­tion seek­ing behav­iour in nat­u­ral­is­tic set­tings. How­ever, the behav­iours that this approach reveals are still bounded by the func­tion­al­ity cur­rently offered by exist­ing sys­tems and work­ing prac­tices, and as such do not reflect the full range of aspi­ra­tional or unmet user needs encom­passed by the data in this study.

Finally, the data is unique in that is con­sti­tutes a gen­uine practitioner-oriented deliv­er­able, gen­er­ated expressly for the pur­pose of design­ing and deliv­er­ing com­mer­cial search appli­ca­tions. As such, it reflects a degree of real­ism and authen­tic­ity that inter­view data or other research-based inter­ven­tions might strug­gle to replicate.

3.2 Data Analysis

These sce­nar­ios were man­u­ally ana­lyzed to iden­tify themes or modes that appeared con­sis­tently through­out the set, using a num­ber of iter­a­tions of a ‘propose-classify-refine’ cycle based on that of Rose & Levin­son [14]. Inevitably, this process was some­what sub­jec­tive, echo­ing the obser­va­tions made by Bates [1] in her work on search tactics:

While our goal over the long term may be a par­si­mo­nious few, highly effec­tive tac­tics, our goal in the short term should be to uncover as many as we can, as being of poten­tial assis­tance. Then we can test the tac­tics and select the good ones. If we go for clo­sure too soon, i.e., seek that par­si­mo­nious few pre­ma­turely, then we may miss some valu­able tac­tics.”

In this respect, the process was par­tially deduc­tive, in apply­ing the insights from exist­ing mod­els to clas­sify the data in a top-down man­ner. But it was also par­tially induc­tive, apply­ing a bottom-up, grounded analy­sis to iden­tify new types of behav­iour not present in the orig­i­nal mod­els or to sug­gest revised def­i­n­i­tions of exist­ing behaviours.

A num­ber of the sce­nar­ios focused on needs that did not involve any explicit infor­ma­tion seek­ing or use behav­iour, e.g. “Achieve a good price for my cur­rent car”. These were excluded from the analy­sis. A fur­ther num­ber were incom­plete or ambigu­ous, or were essen­tially fea­ture requests (e.g. “Have flex­i­ble nav­i­ga­tion within the page”), and were also excluded.

The process resulted in the iden­ti­fi­ca­tion of nine pri­mary search modes, which are defined below along with an exam­ple sce­nario (from the domain of consumer-oriented search):

1. LocateTo find a spe­cific (pos­si­bly known) item, e.g. “Find my read­ing list items quickly”. This mode encap­su­lates the stereo­typ­i­cal ‘find­abil­ity’ task that is so com­monly asso­ci­ated with site search. It is con­sis­tent with (but a super­set of) Spencer’s [14] known item search mode. This was the most fre­quent mode in the site search sce­nar­ios (120 instances, which con­trasts with just 2 for enter­prise search).

2. Ver­ifyTo con­firm that an item meets some spe­cific, objec­tive cri­te­rion, e.g. “See the cor­rect price for sin­gles and deals”. Often found in com­bi­na­tion with locat­ing, this mode is con­cerned with val­i­dat­ing the accu­racy of some data item, com­pa­ra­ble to that pro­posed by Ellis et al.  [5] (39 site search instances, 4 for enter­prise search).

3. Mon­i­torMain­tain aware­ness of the sta­tus of an item for pur­poses of man­age­ment or con­trol, e.g. “Alert me to new resources in my area”. This activ­ity focuses on the state of asyn­chro­nous respon­sive­ness and is con­sis­tent with that of Bates [1], O’Day and Jef­fries [11], Ellis [4], and Laman­tia [7] (13 site search instances, 17 for enter­prise search).

4. Com­pareTo iden­tify sim­i­lar­i­ties & dif­fer­ences within a set of items, e.g. “Com­pare cars that are my pos­si­ble can­di­dates in detail”. This mode has not fea­tured promi­nently in most of the pre­vi­ous mod­els (with the pos­si­ble excep­tion of Marchionini’s), but accounted for a sig­nif­i­cant pro­por­tion of enter­prise search behav­iour [13]. Although a com­mon fea­ture on many ecom­merce sites, it occurred rel­a­tively infre­quently in the site search data (2 site search instances, 16 for enter­prise search).

5. Com­pre­hendTo gen­er­ate inde­pen­dent insight by inter­pret­ing pat­terns within a data set, e.g. “Under­stand what my com­peti­tors are sell­ing”. This activ­ity focuses on the cre­ation of knowl­edge or under­stand­ing and is con­sis­tent with that of Cool & Belkin [3] and Mar­chion­ini [9] (50 site search instances, 12 for enter­prise search).

6. Eval­u­ateTo use judge­ment to deter­mine the value of an item with respect to a spe­cific goal, e.g. “I want to know whether my agency is deliv­er­ing best value”. This mode is sim­i­lar in spirit to ver­ify, in that it is con­cerned with val­i­da­tion of the data. How­ever, while ver­ify focuses on sim­ple, objec­tive fact check­ing, our con­cep­tion of eval­u­ate involves more sub­jec­tive, knowledge-based judge­ment, sim­i­lar to that pro­posed by Cool & Belkin [3] (61 site search instances, 78 for enter­prise search).

7. ExploreTo inves­ti­gate an item or data set for the pur­pose of knowl­edge dis­cov­ery, e.g. “Find use­ful stuff on my sub­ject topic”. In some ways the bound­aries of this mode are less pre­scribed than the oth­ers, but what the instances share is the char­ac­ter­is­tic of open ended, oppor­tunis­tic search and brows­ing in the spirit of O’Day and Jef­fries [11] explor­ing a topic in an undi­rected fash­ion and Spencer’s [14] exploratory (110 site search instances, 16 for enter­prise search).

8. Ana­lyzeTo exam­ine an item or data set to iden­tify pat­terns & rela­tion­ships,e.g. Ana­lyze the mar­ket so I know where my strengths and weak­nesses are”. This mode fea­tures less promi­nently in pre­vi­ous mod­els, appear­ing as a sub-component of the pro­cess­ing stage in Meho & Tibbo’s [10] model, and over­lap­ping some­what with Cool & Belkin’s [3] orga­nize. This def­i­n­i­tion is also con­sis­tent with that of Makri et al. [8], who iden­ti­fied analysing as an impor­tant aspect of lawyers’ inter­ac­tive infor­ma­tion behav­iour and defined it as “exam­in­ing in detail the ele­ments or struc­ture of the con­tent found dur­ing information-seeking.” (p. 630). This was the most com­mon ele­ment of the enter­prise search sce­nar­ios (58 site search instances, 84 for enter­prise search).

9. Syn­the­sizeTo cre­ate a novel or com­pos­ite arte­fact from diverse inputs, e.g. “I need to cre­ate a read­ing list on celebrity spon­sor­ship”. This mode also appears as a sub-component of the pro­cess­ing stage in Meho & Tibbo’s [10] model, and involves ele­ments of Cool & Belkin’s [3] cre­ate and use. Of all the modes, this one is the most com­monly asso­ci­ated with infor­ma­tion use in its broad­est sense (as opposed to infor­ma­tion seek­ing). It was rel­a­tively rare within site search (5 site search instances, 15 for enter­prise search).

Although the modes were gen­er­ated from an inde­pen­dent data source and analy­sis process, we have ret­ro­spec­tively explored the degree to which they align with exist­ing frame­works, e.g. Marchionini’s [8]. In this con­text, locate, ver­ify, andmon­i­tor could be described as lower-level ‘lookup’ modes, com­pare, com­pre­hend, and eval­u­ate as ‘learn’ modes and explore, ana­lyze, and syn­the­size as higher-level ‘inves­ti­gate’ modes.

4 Mode Sequences and Patterns

The modes defined above pro­vide an insight into the needs of users of site search and enter­prise search appli­ca­tions and a frame­work for under­stand­ing human infor­ma­tion seek­ing behav­iour. But their real value lies not so much in their occur­rence as indi­vid­ual instances but in the pat­terns of co-occurrence they reveal. In most sce­nar­ios, modes com­bine to form dis­tinct chains and pat­terns, echo­ing the tran­si­tions observed by O’Day and Jef­fries [11] and the com­bi­na­to­r­ial behav­iour alluded to by Ellis [5], who sug­gested that infor­ma­tion behav­iours can often be nested or dis­played in parallel.

Typ­i­cally these pat­terns con­sist of chains of length two or three, often with one par­tic­u­lar mode play­ing a dom­i­nant role. Site search, for exam­ple, was char­ac­ter­ized by the fol­low­ing patterns:

  1. Insight-driven search: (Explore-Analyze– Com­pre­hend): This pat­terns rep­re­sents an exploratory search for insight or knowl­edge to resolve an explicit infor­ma­tion need,  e.g. “Assess the proper mar­ket value for my car
  2. Oppor­tunis­tic search: (Explore-Locate-Evaluate): In con­trast to the explicit focus of Insight-driven search, this sequence rep­re­sents a less directed explo­ration in the prospect of serendip­i­tous dis­cov­ery e.g. “Find use­ful stuff on my sub­ject topic
  3. Qual­i­fied search (Locate-Verify) This pat­tern rep­re­sents a vari­ant of the stereo­typ­i­cal find­abil­ity task in which some ele­ment of imme­di­ate ver­i­fi­ca­tion is required, e.g. “Find trucks that I am eli­gi­ble to drive

By con­trast, enter­prise search was char­ac­ter­ized by a larger num­ber of more diverse sequences, such as:

  1. Com­par­a­tive search: (Analyze-Compare– Eval­u­ate) e.g. “Replace a prob­lem­atic part with an equiv­a­lent or bet­ter part with­out com­pro­mis­ing qual­ity and cost
  2. Exploratory search: (Explore-Analyze-Evaluate) e.g. “Iden­tify oppor­tu­ni­ties to opti­mize use of tool­ing capac­ity for my commodity/parts
  3. Strate­gic Insight (Analyze-Comprehend-Evaluate) e.g. “Under­stand a lead’s under­ly­ing posi­tions so that I can assess the qual­ity of the invest­ment oppor­tu­nity
  4. Strate­gic Over­sight (Monitor-Analyze-Evaluate) e.g. “Mon­i­tor & assess com­mod­ity sta­tus against strategy/plan/target
  5. Comparison-driven Syn­the­sis (Analyze-Compare-Synthesize) e.g. “Ana­lyze and under­stand consumer-customer-market trends to inform brand strat­egy & com­mu­ni­ca­tions plan

A fur­ther insight into these pat­terns can be obtained by pre­sent­ing them in dia­gram­matic form. Fig­ure 1 illus­trates sequences 1–3 above plus other com­monly found site search pat­terns as a net­work (with sequence num­bers shown on the arrows). It shows how cer­tain modes tend to func­tion as “ter­mi­nal” nodes, i.e. entry points or exit points for a given sce­nario. For exam­ple, Explore typ­i­cally func­tions as an open­ing, while Com­pre­hend and Eval­u­ate func­tion in clos­ing a sce­nario. Ana­lyze typ­i­cally appears as a bridge between an open­ing and clos­ing mode. The shad­ing indi­cates the mode ‘level’ alluded to ear­lier: light tones indi­cate ‘lookup’ modes, mid tones are the ‘learn’ modes, and dark tones are the ‘inves­ti­gate’ modes.

Fig. 1. Mode network for site searchFig. 1. Mode net­work for site search 

Fig­ure 2 illus­trates sequences 4–8 above plus other com­monly found pat­terns in the enter­prise search data.

Fig. 2. Mode network for enterprise searchFig. 2. Mode net­work for enter­prise search 

The pat­terns described above allow us to reflect on some of the dif­fer­ences between the needs of site search users and those of enter­prise search. Site search, for exam­ple, is char­ac­ter­ized by an empha­sis on sim­pler “lookup” behav­iours such as Locate and Ver­ify (120 and 39 instances respec­tively); modes which were rel­a­tively rare in enter­prise search (2 and 4 instances respec­tively). By con­trast, enter­prise search is char­ac­ter­ized by higher-level “learn” and “inves­ti­gate” behav­iours such as Ana­lyze and Eval­u­ate (84 and 78 instances respec­tively, com­pared to 58 and 61 for site search). Inter­est­ingly, in nei­ther case was the stereo­type of ‘search equals find­abil­ity’ borne out: even in site search (whereLocate was the most com­mon mode), known-item search was account­able for no more than a quar­ter of all instances.

But per­haps the biggest dif­fer­ence is in the com­po­si­tion of the chains: enter­prise search is char­ac­terised by a wide vari­ety of het­ero­ge­neous chains, while site searched focuses on a small num­ber of com­mon tri­grams and bigrams. More­over, the enter­prise search chains often dis­played a frac­tal nature, in which cer­tain chains were embed­ded within or trig­gered by oth­ers, to cre­ate larger, more com­plex sequences of behaviour.

5 Design Implications

Although the model offers a use­ful frame­work for under­stand­ing human infor­ma­tion seek­ing behav­iour, its real value lies in its use as a prac­ti­cal design resource. As such, it can pro­vide guid­ance on issues such as:

  • the fea­tures and func­tion­al­ity that should be avail­able at spe­cific points within a system;
  • the inter­ac­tion design of indi­vid­ual func­tions or components;
  • the design cues used to guide users toward spe­cific areas of task interface.

More­over, the model also has sig­nif­i­cant impli­ca­tions for the broader aspects of user expe­ri­ence design, such as the align­ment between the over­all struc­ture or con­cept model of a sys­tem and its users’ men­tal mod­els, and the task work­flows for var­i­ous users and con­texts. This broader per­spec­tive addresses archi­tec­tural ques­tions such as the nature of the work­spaces required by a given appli­ca­tion, or the paths that users will take when nav­i­gat­ing within a system’s struc­ture.  In this way, the modes also act as a gen­er­a­tive tool for larger, com­pos­ite design issues and structures.

5.1 Indi­vid­ual modes

On their own, each of the modes describes a type of behav­iour that may need to be sup­ported by a given infor­ma­tion system’s design. For exam­ple, an online retail site should sup­port locat­ing and com­par­ing spe­cific prod­ucts, and ide­ally alsocom­pre­hend­ing dif­fer­ences and eval­u­at­ing trade­offs between them. Like­wise, an enter­prise appli­ca­tion for elec­tronic com­po­nent selec­tion should sup­port mon­i­tor­ingand ver­i­fy­ing the suit­abil­ity of par­tic­u­lar parts, and ide­ally also ana­lyz­ing andcom­pre­hend­ing any rel­e­vant pat­terns and trends in their life­cy­cle. By under­stand­ing the antic­i­pated search modes for a given sys­tem, we can opti­mize the design to sup­port spe­cific user behav­iours. In the fol­low­ing sec­tion we con­sider indi­vid­ual instances of search modes and explore some of their design implications.


This mode encap­su­lates the stereo­typ­i­cal ‘find­abil­ity’ task that is so com­monly asso­ci­ated with site search. But sup­port for this mode can go far beyond sim­ple key­word entry. For exam­ple, by allow­ing the user to choose from a list of can­di­dates, auto-complete trans­forms the query for­mu­la­tion prob­lem from one of recall into one of recog­ni­tion (Fig­ure 3).

Figure 1: Auto-complete supports LocatingFig. 3. Auto-complete sup­ports locating 

Like­wise, Amazon’s par­tial match strat­egy deals with poten­tially failed queries by iden­ti­fy­ing the key­word per­mu­ta­tions that are likely to pro­duce use­ful results. More­over, by ren­der­ing the non-matching key­words in strikethrough text, it facil­i­tates a more informed approach to query refor­mu­la­tion (Fig­ure 4).

Figure 2: Partial matches support LocatingFig 4: Par­tial matches sup­port Locating 


In this mode, the user is inspect­ing a par­tic­u­lar item and wish­ing to con­firm that it meets some spe­cific cri­te­rion.  Google’s image results page pro­vides a good exam­ple of this (see Fig­ure 5).

Figure 3: Search result previews support verificationFig 5: Search result pre­views sup­port verification 

On mouseover, the image is zoomed in to show a mag­ni­fied ver­sion along with key meta­data, such as file­name, image size, cap­tion, and source. This allows the user to ver­ify the suit­abil­ity of a spe­cific result in the con­text of its alter­na­tives. Like­wise, there may be cases where the user needs to ver­ify a par­tic­u­lar query rather than a par­tic­u­lar result. In pro­vid­ing real-time feed­back after every key press, Google Instant sup­ports ver­i­fi­ca­tion by pre­view­ing the results that will be returned for a given query (Fig­ure 6). If the results seem unex­pected, the user can check the query for errors or try alter­na­tive spellings or key­word combinations.

Figure 4: Instant results supports verification of queriesFig 6: Instant results sup­ports ver­i­fi­ca­tion of queries 


The Com­pare mode is fun­da­men­tal to online retail, where users need to iden­tify the best option from the choices avail­able. A com­mon tech­nique is to pro­vide a cus­tom view in which details of each item are shown in sep­a­rate columns, enabling rapid com­par­i­son of prod­uct attrib­utes. Best Buy, for exam­ple, sup­ports com­par­i­son by organ­is­ing the attrib­utes into log­i­cal groups and auto­mat­i­cally high­light­ing the dif­fer­ences (Fig­ure 7).

Figure 5: Separate views support product comparisonFig 7: Sep­a­rate views sup­port prod­uct comparison 

But com­par­i­son is not restricted to qual­i­ta­tive attrib­utes. In finan­cial ser­vices, for exam­ple, it is vital to com­pare stock per­for­mance and other finan­cial instru­ments with indus­try bench­marks. Google Finance sup­ports the com­par­i­son of secu­ri­ties through a com­mon chart­ing com­po­nent (Fig­ure 8).

Figure 6: Common charts allow comparison of quantitative dataFig 8: Com­mon charts allow com­par­i­son of quan­ti­ta­tive data 


A key prin­ci­ple in explor­ing is dif­fer­en­ti­at­ing between where you are going andwhere you have already been. In fact, this dis­tinc­tion is so impor­tant that it has been woven into the fab­ric of the web itself; with unex­plored hyper­links ren­dered in blue by default, and vis­ited hyper­links shown in magenta. Ama­zon takes this prin­ci­ple a step fur­ther, through com­po­nents such as a  ‘Recent Searches’ panel show­ing the pre­vi­ous queries issued in the cur­rent ses­sion, and a ‘Recent His­tory’ panel show­ing the items recently viewed (Fig­ure 9).

Figure 7: Recent history supports explorationFig 9: Recent his­tory sup­ports exploration 

Another sim­ple tech­nique for encour­ag­ing explo­ration is through the use of “see also” pan­els. Online retail­ers com­monly use these to pro­mote related prod­ucts such as acces­sories and other items to com­ple­ment an intended pur­chase. An exam­ple of this can be seen at Food Net­work, in which fea­tured videos and prod­ucts are shown along­side the pri­mary search results (Fig­ure 10).

Figure 8: ‘See Also’ panels support explorationFig 10: ‘See Also’ pan­els sup­port exploration 

A fur­ther tech­nique for sup­port­ing explo­ration is through the use of auto-suggest. While auto-complete helps users get an idea out of their heads and into the search box, auto-suggest throws new ideas into the mix. In this respect, it helps users explore by for­mu­lat­ing more use­ful queries than they might oth­er­wise have thought of on their own. Home Depot, for exam­ple, pro­vides a par­tic­u­larly exten­sive auto-suggest func­tion con­sist­ing of prod­uct cat­e­gories, buy­ing guides, project guides and more, encour­ag­ing the dis­cov­ery of new prod­uct ideas and con­tent (Fig­ure 11).

Figure 9: Auto-suggest supports exploratory search Fig 11: Auto-suggest sup­ports exploratory search 


In modes such as explor­ing, the user’s pri­mary con­cern is in under­stand­ing theover­all infor­ma­tion space and iden­ti­fy­ing areas to ana­lyze in fur­ther detail. Analy­sis, in this sense, goes hand in hand with explor­ing, as together they present com­ple­men­tary modes that allow search to progress beyond the tra­di­tional con­fines of infor­ma­tion retrieval or ‘findability’.

A sim­ple exam­ple of this could be found at Google patents (Fig­ure 12). The alter­nate views (Cover View and List View) allow the user to switch between rapid explo­ration (scan­ning titles, brows­ing thumb­nails, look­ing for infor­ma­tion scent) and a more detailed analy­sis of each record and its metadata.

Figure 10: Alternate views support mode switching between exploration and analysisFig 12: Alter­nate views sup­port mode switch­ing between explo­ration and analysis 

In the above exam­ple the analy­sis focuses on qual­i­ta­tive infor­ma­tion derived from pre­dom­i­nantly tex­tual sources. Other appli­ca­tions focus on quan­ti­ta­tive data in the form of aggre­gate pat­terns across col­lec­tions of records. News­Sift, for exam­ple, pro­vided a set of data visu­al­iza­tions which allowed the user to ana­lyze results for a given news topic at the aggre­gate level, gain­ing an insight that could not be obtained from exam­in­ing indi­vid­ual records alone (Fig­ure 13).

Figure 11: Visualizations support analysis of quantitative informationFig 13: Visu­al­iza­tions sup­port analy­sis of quan­ti­ta­tive information 

5.2 Com­pos­ite patterns

The exam­ples above rep­re­sent instances of indi­vid­ual modes, show­ing var­i­ous ways they can be sup­ported by one or more aspects of a system’s design. How­ever, a key fea­ture of the model is its empha­sis on the com­bi­na­to­r­ial nature of modes and the pat­terns of co-occurrence this reveals [12]. In this respect, its true value is in help­ing design­ers to address more holis­tic, larger scale con­cerns such as the appro­pri­ate struc­ture, con­cept model, and orga­niz­ing prin­ci­ples of a sys­tem, as well as the func­tional and infor­ma­tional con­tent of its major com­po­nents and con­nec­tions between them.

Design at this level relies on trans­lat­ing com­pos­ite modes and chains that rep­re­sent sense-making activ­i­ties – often artic­u­lated as user jour­neys through a task and infor­ma­tion space – into inter­ac­tion com­po­nents that rep­re­sent mean­ing­ful com­bi­na­tions of infor­ma­tion and dis­cov­ery capa­bil­i­ties [13].  These com­po­nents serve as ‘build­ing blocks’ that design­ers can assem­ble into larger com­pos­ite struc­tures to cre­ate a user expe­ri­ence that sup­ports the antic­i­pated user jour­neys and aligns with their users’ men­tal mod­els [14].

The pop­u­lar micro-blogging ser­vice twitter.com pro­vides a num­ber of exam­ples of the cor­re­spon­dence between com­pos­ite modes and inter­ac­tion com­po­nents assem­bled at var­i­ous lev­els to pro­vide a coher­ent user expe­ri­ence architecture.

Header Bar

The header bar at the top of most pages of twitter.com com­bines sev­eral infor­ma­tional and func­tional ele­ments together in a sin­gle com­po­nent that sup­ports a num­ber of modes and mode chains (Fig­ure 14). It includes four dynamic sta­tus indi­ca­tors that address key aspects of twitter’s con­cept model and the users’ men­tal models:

  • the pres­ence of new tweets by peo­ple the user follows
  • inter­ac­tions with other twit­ter users such as fol­low­ing them or men­tion­ing them in a tweet
  • activ­ity related to the user’s pro­file, such as their lat­est tweets and shared media
  • peo­ple, top­ics, or items of inter­est sug­gested by the sys­tems rec­om­mender functions

These sta­tus indi­ca­tor icons update auto­mat­i­cally and pro­vide links to spe­cific pages in the twitter.com appli­ca­tion archi­tec­ture that pro­vide fur­ther detail on each area of focus. The header bar thus enables Mon­i­tor­ing of a user’s activ­ity within the full scope of the twitter.com net­work; i.e. its con­tent, mem­bers, their activ­i­ties, etc.  The header bar also enables Mon­i­tor­ing activ­ity within almost all the work­spaces that users encounter in the course of their pri­mary jour­neys throughtwitter.com.

Fig. 14. twitter.com Header BarFig. 14. twitter.com Header Bar 

The Strate­gic Over­sight chain (Mon­i­tor – Ana­lyze – Eval­u­ate) is a fun­da­men­tal sequence for twit­ter users, repeated fre­quently with dif­fer­ent aspects of the user’s pro­file. The header bar sup­ports the first step of this chain, in which users Mon­i­tor the net­work for con­tent and activ­ity of inter­est to them, and then tran­si­tion to Analy­sis and Eval­u­a­tion of that activ­ity by nav­i­gat­ing to des­ti­na­tion pages for fur­ther detail.

The header bar also includes a search box fea­tur­ing auto-complete and auto-suggest func­tion­al­ity, which pro­vides sup­port for the Qual­i­fied Search mode chain (Locate – Ver­ify). The search box also enables users to ini­ti­ate many other mode chains by sup­port­ing the Explore mode. These include Exploratory Search (Explore – Ana­lyze – Eval­u­ate), Insight-driven Search (Explore – Ana­lyze – Com­pre­hend), and Opportunity-driven Search (Explore – Locate – Eval­u­ate). All these mode chains over­lap by shar­ing a com­mon start­ing point. This is one of the most read­ily rec­og­niz­able kinds of com­po­si­tion, and often cor­re­sponds to a sin­gle instance of a par­tic­u­lar inter­ac­tion component.

The header bar includes sup­port for post­ing or Syn­the­siz­ing new tweets, reflect­ing the fact that the cre­ation of new con­tent is prob­a­bly the sec­ond most impor­tant indi­vid­ual mode (after Mon­i­tor­ing). A menu of links to admin­is­tra­tive pages and func­tions for man­ag­ing one’s twit­ter account com­pletes the con­tent of the header bar.

Indi­vid­ual Tweets

The indi­vid­ual tweets and activ­ity updates that make up the stream at the heart of the pri­mary work­space are the most impor­tant inter­ac­tion com­po­nents of the twit­ter expe­ri­ence, and their design shows a direct cor­re­spon­dence to many com­pos­ite modes and chains (Fig­ure 15). Indi­vid­ual items pro­vide the con­tent of a tweet along with the author’s pub­lic name, their twit­ter user­name, pro­file image, and the time elapsed since the tweet’s cre­ation. Together, these details allow users to Com­pare and Com­pre­hend the con­tent and sig­nif­i­cance of tweets in their own stream.  As users read more tweets and begin to rec­og­nize authors and top­ics, they can Com­pare, Ana­lyze, and Eval­u­ate them.  The indi­ca­tors of ori­gin and activ­ity allow users to Com­pare and Com­pre­hend the top­ics and inter­ests of other twit­ter users.

Fig. 15. Individual TweetFig. 15. Indi­vid­ual Tweet 

Options to invoke a num­ber of func­tions that cor­re­spond to other dis­cov­ery modes are embed­ded within the indi­vid­ual items in the stream. For exam­ple, if an update was retweeted, it is marked as such with the orig­i­nal author indi­cated and their pro­file page linked. It also shows the num­ber of times the tweet has been retweeted and favor­ited, with links that open modal pre­views of the list of users who did so. This sup­ports Mon­i­tor­ing, Explo­ration and Com­pre­hen­sion of the sig­nif­i­cance and atten­tion an indi­vid­ual tweet has received, while the links sup­port Loca­tion, Ver­i­fi­ca­tion and Mon­i­tor­ing of the other users who retweeted or favor­ited it.

Pub­lic pro­file names and user­names are linked to pages which sum­ma­rize the activ­i­ties and rela­tion­ships of the author of a tweet, enabling users to Locate and Ver­ify authors, then tran­si­tion to Mon­i­tor­ing, Explor­ing and Com­pre­hend­ing their activ­i­ties, inter­ests, and how they are con­nected to the rest of the twit­ter network.

Hash­tags are pre­sented with dis­tinct visual treat­ment.  When users click on one, it ini­ti­ates a search using the hash­tag, allow­ing users to Locate, Explore, Com­pre­hend, and Ana­lyze the topic referred to, any con­ver­sa­tions in which the tag is men­tioned, and the users who employ the tag.

Fig. 16. Expanded TweetFig. 16. Expanded Tweet 

Longer tweets are trun­cated, offer­ing an ‘Expand’ link which opens a panel dis­play­ing the num­ber of retweets and favourites and the images of the users who did so, along with the date and time of author­ing and a link to a ‘details’ page for a per­ma­nent URL that other users and exter­nal ser­vices can ref­er­ence (Fig­ure 16). This sort of trun­ca­tion enables users to more eas­ily Explore the full set of tweets in a stream and Locate indi­vid­ual items of inter­est. Con­versely, the ‘Expand’ panel allows the user to more eas­ily Explore and Com­pre­hend indi­vid­ual items.

Tweets that con­tain links to other tweets offer a ‘View tweet’ link, which opens a panel dis­play­ing the full con­tents of the orig­i­nal tweet, the date and time of post­ing, the num­ber of retweets and favorites and a pre­view list of the users who did so.  The ‘View tweet’ link thus sup­ports the Locate, Explore, and Com­pre­hend modes for indi­vid­ual updates.

Tweets that con­tain links to dig­i­tal assets such as pho­tos, videos, songs, pre­sen­ta­tions, and doc­u­ments, offer users the abil­ity to pre­view these assets directly within an expanded dis­play panel, pro­vid­ing sup­port for the Locate, Explore, and Com­pre­hend modes. These pre­views link to the source of the assets, enabling users to Locate them.  Users can also ‘flag’ media for review by twit­ter (e.g. due to vio­la­tion of poli­cies about sen­si­tive or ille­gal imagery) – which is a very spe­cific form of Evaluation.

Fig. 17. Tweet Displaying a PhotoFig. 17. Tweet Dis­play­ing a Photo 

Tweets that con­tain links to items such as arti­cles pub­lished by news­pa­pers, mag­a­zines, and jour­nals, or rec­og­nized des­ti­na­tions such as Foursquare and Google + pages, offer a ‘Sum­mary’ link (Fig­ure 17). This link opens a panel that presents the first para­graph of the arti­cle or des­ti­na­tion URL, an image from the orig­i­nal pub­lisher, and a list of users who have retweeted or favor­ited it, thus sup­port­ing Loca­tion, Explo­ration and Ver­i­fi­ca­tion of the linked item.

A text input field seeded with the author’s user­name allows users to reply to spe­cific tweets directly from an indi­vid­ual update. Users can also ‘retweet’ items directly from the list. Both func­tions are forms of Syn­the­sis, and encour­age users to cre­ate fur­ther con­tent and rela­tion­ships within the network.

Users can mark tweets as ‘favorites’ to indi­cate the impor­tance or value of these tweets to oth­ers; a clear exam­ple of the Eval­u­a­tion mode. Favorites also allow users to build a col­lec­tion of tweets curated for retrieval and inter­pre­ta­tion, enabling the Locate, Com­pare, Com­pre­hend, and Ana­lyze modes for tweets as indi­vid­ual items or as groups.

A ‘More’ link opens a menu offer­ing ‘Email Tweet’ and ‘Embed Tweet’ options, allow­ing users to ini­ti­ate tasks that take tweets out­side the twit­ter envi­ron­ment.  These two func­tions sup­port infor­ma­tion usage modes, rather than search anddis­cov­ery modes, so their dis­tinct treat­ment – invoked via a dif­fer­ent inter­ac­tion than the other func­tions – is con­sis­tent with the great empha­sis the twit­ter expe­ri­ence places on dis­cov­ery and sense mak­ing activities.

If the tweet is part of a con­ver­sa­tion, a ‘View this con­ver­sa­tion’ link allows read­ers to open a panel that presents related tweets and user activ­ity as a sin­gle thread, accom­pa­nied by a reply field.  This pro­vides sup­port for the Locate, Explore, Com­pre­hend, Ana­lyze, Eval­u­ate and Syn­the­size modes (Fig­ure 18).

Fig. 18. Tweet Showing a Conversation Fig. 18. Tweet Show­ing a Conversation 

The infor­ma­tional and func­tional con­tent pre­sented by indi­vid­ual items in their var­i­ous forms enables a num­ber of mode chains. These include Strate­gic Over­sight, in which users main­tain aware­ness of con­ver­sa­tions, top­ics, other users, and activ­i­ties; Strate­gic Insight, wherein users focus on and derive insight into con­ver­sa­tions, top­ics, and other users; and Com­par­a­tive Syn­the­sis, in which users real­ize new insights and cre­ate new con­tent through direct engage­ment with con­ver­sa­tions, top­ics, and other users.

In a man­ner sim­i­lar to the search box, this inter­ac­tion com­po­nent serves as an ini­ti­a­tion point for a num­ber of mode chains, includ­ing Exploratory Search, Insight-driven Search, and Opportunity-driven Search. Indi­vid­ual tweets thus com­bine sup­port for many impor­tant modes and mode chains into a sin­gle inter­ac­tion com­po­nent.  As a con­se­quence, they need to be rel­a­tively rich and ‘dense’, com­pact­ing much func­tion­al­ity into a sin­gle inter­ac­tion com­po­nent, but this reflects their cru­cial role in the user jour­neys that char­ac­ter­ize the twit­ter experience.

Pri­mary Work­spaces and Pages

In the pre­vi­ous sec­tion we reviewed the cor­re­spon­dence between groups of modes and the inter­ac­tion com­po­nents of a user expe­ri­ence. In this sec­tion, we review the ways in which modes and chains impact the com­po­si­tion and pre­sen­ta­tion of the next level of UX struc­ture within the sys­tem: work spaces.

The pri­mary work­spaces of twitter.com all empha­size inter­ac­tion with a stream of indi­vid­ual updates, but the focus and con­tent vary depend­ing on the con­text. On the Home page, for exam­ple, the cen­tral stream con­sists of tweets from peo­ple the user fol­lows, while on the ‘Me’ page the stream con­sists of the tweets cre­ated by the user (Fig­ure 19). How­ever, the lay­out of these pages remains con­sis­tent: the work­space is dom­i­nated by a sin­gle cen­tral stream of indi­vid­ual updates. The pri­mary inter­ac­tion mode for this stream is Mon­i­tor­ing, evi­dent from the count of new items added to the net­work since the last page refresh.

Fig. 19. twitter.com Home WorkspaceFig. 19. twitter.com Home Workspace 

The place­ment of the header bar at the top of all of the pri­mary work­spaces is a design deci­sion that reflects the pri­macy of Mon­i­tor­ing as a mode of engage­ment with the twit­ter ser­vice; sup­port­ing its role as a per­sis­tent ‘back­ground’ mode of dis­cov­ery inde­pen­dent of the user’s cur­rent point in a task or jour­ney, and its role as a com­mon entry point to the other mode chains and user journeys.

The con­sis­tent place­ment of the ‘Com­pose new Tweet’ con­trol in upper right cor­ner of the work­space reflects known inter­ac­tion design prin­ci­ples (cor­ners are the sec­ond most eas­ily engaged areas of a screen, after the cen­tre) and the under­stand­ing that Syn­the­sis is the sec­ond most impor­tant sin­gle mode for the twit­ter service.

The con­tent of the indi­vid­ual updates attracts and retains users’ atten­tion very effec­tively: the major­ity of the actions a user may want to take in regard to a tweet (or any of the related con­structs in twitter’s con­cept model such as con­ver­sa­tions, hash tags, pro­files, linked media, etc.) are directly avail­able from the inter­ac­tion com­po­nent.  In some cases, these actions are pre­sented via modal or light­box pre­view, wherein the user’s focus is ‘forced’ onto a sin­gle ele­ment – thus main­tain­ing the pri­macy of the stream.  In oth­ers, links lead to des­ti­na­tion pages that switch the user’s focus to a dif­fer­ent sub­ject – another user’s pro­file, for exam­ple – but in most of these cases the struc­ture of the work­space remains con­sis­tent: a two col­umn body sur­mounted by the ubiq­ui­tous header bar. There is lit­tle need to look else­where in the work­space, unless the user needs to check the sta­tus of one of the broader aspects of their account, at which point the header bar pro­vides appro­pri­ate func­tion­al­ity as dis­cussed above.

The absence of a page footer – scrolling is ‘infi­nite’ on the pri­mary pages oftwitter.com – reflects the con­scious deci­sion to con­vey updates as an end­less, dynamic stream.  This encour­ages users to con­tinue scrolling, increas­ing Explo­ration activ­ity, and enhanc­ing users’ Com­pre­hen­sion of addi­tional updates – which ben­e­fits twitter’s busi­ness by increas­ing the atten­tion users direct toward the service.

Although the two-tier, stream-centred struc­ture of twitter’s pri­mary work­spaces remains con­sis­tent, there are vari­a­tions in the com­po­si­tion of the left col­umn (Fig­ure 20). On the Home page, for exam­ple, the left col­umn offers four sep­a­rate com­po­nents. The first is a sum­mary of the user’s pro­file, includ­ing a pro­file image, a link to their pro­file page, counts of their tweets, fol­low­ers, and the peo­ple they fol­low, and a ‘com­pose new tweet’ box.  This is another exam­ple of a com­po­nent sup­port­ing a com­pos­ite of modes.

Fig. 20. Twitter Home Page - Left ColumnFig. 20. Twit­ter Home Page – Left Column 

The core pur­pose is to enable users to Mon­i­tor the most impor­tant aspects of their own account via the counts.  The links pro­vide direct Locate func­tion­al­ity for fol­low­ers, tweets, and accounts the user fol­lows; and also serve as a point of depar­ture for the same mode chains that can be ini­ti­ated from the header bar.  The ‘com­pose new tweet’ func­tion encour­ages users to cre­ate updates, under­lin­ing the impor­tance of Syn­the­sis as the source of new con­tent within the twit­ter network.

User Expe­ri­ence Architecture

The twitter.com expe­ri­ence is intended to sup­port a set of user jour­neys con­sist­ing largely of search and dis­cov­ery tasks which cor­re­spond with spe­cific mon­i­tor­ing and search-related mode chains. Fur­ther, we can see that pat­terns of recur­rence, inter­sec­tion, over­lap, and sequenc­ing in the aggre­gate set of search and dis­cov­ery modes are sub­stan­tially reflected in twitter’s user expe­ri­ence architecture.

From a struc­tural design per­spec­tive, the core [16] of the twitter.com user expe­ri­ence archi­tec­ture is a set of four inter­ac­tion con­soles, each of which focuses on mon­i­tor­ing a dis­tinct stream of updates around the most impor­tant facets of thetwitter.com con­cept model: the con­tent and activ­i­ties of peo­ple in the user’s per­sonal net­work (Home); inter­ac­tions with other users (Inter­ac­tions); the user’s pro­file (@Me); and a digest of con­tent from all users in the twitter.com net­work (Dis­cover) (Fig­ure 21).

The core mon­i­tor­ing con­soles are sup­ported by screens that assist and encour­age users to expand their per­sonal net­works through loca­tion and explo­ration tools; these include ‘Find friends’, ‘Who to fol­low’ ‘Browse cat­e­gories’, and the search results page.

Fig. 21. Twitter.com Discover WorkspaceFig. 21. Twitter.com Dis­cover Workspace 

Spe­cific land­ing pages pro­vide mon­i­tor­ing and cura­tion tools for the dif­fer­ent types of rela­tion­ships users can estab­lish in the social graph: fol­low and un-follow, fol­low­ers and fol­low­ing, pub­lic and pri­vate accounts, list mem­ber­ships, etc.  A small set of screens pro­vides func­tion­al­ity for admin­is­ter­ing the user’s account, such as ‘Settings’.

Under­ly­ing this user expe­ri­ence archi­tec­ture is a con­cept model con­sist­ing pri­mar­ily of a small set of social objects – tweets, con­ver­sa­tions, pro­files, shared dig­i­tal assets, and lists thereof – linked together by search and dis­cov­ery verbs. A rel­a­tively sim­ple infor­ma­tion archi­tec­ture estab­lishes the set of cat­e­gories used to iden­tify these objects by topic, sim­i­lar­ity, and con­tent (Fig­ure 22).

In its holis­tic and gran­u­lar aspects, the twit­ter user expe­ri­ence archi­tec­ture aligns well with users’ men­tal mod­els for build­ing a pro­file and par­tic­i­pat­ing in an ongo­ing stream of con­ver­sa­tions. How­ever, what emerges quite quickly from analy­sis of the twit­ter con­cept model and user expe­ri­ence archi­tec­ture is the role of search and dis­cov­ery modes in both atomic and com­pos­ite forms at every level of twitter’s design. Rather than merely sub­sum­ing modes as part of some larger activ­ity, many of the most com­mon actions users can take with twitter’s core inter­ac­tion objects cor­re­spond directly to modes themselves.

Fig. 22. Twitter.com User Experience ArchitectureFig. 22. Twitter.com User Expe­ri­ence Architecture 

The indi­vid­ual tweet com­po­nent is a prime exam­ple: the sum­maries of author pro­files and their recent activ­ity are a com­pos­ite of the Locate, Explore and Com­pre­hend modes (Fig­ure 23). Evi­dently, the pre­sen­ta­tion, labelling, and inter­ac­tion design may reflect adap­ta­tions spe­cific to the lan­guage and men­tal model of the twit­ter envi­ron­ment, but the activ­i­ties are clearly rec­og­niz­able. The ‘Show con­ver­sa­tion’ func­tion dis­cussed above also reflects direct sup­port to Locate, Explore and Com­pre­hend a con­ver­sa­tion object as a sin­gle interaction.

Fig. 23. Twitter Profile SummaryFig. 23. Twit­ter Pro­file Summary 

Because the twitter.com expe­ri­ence is so strongly cen­tred on sense-making, search and dis­cov­ery modes often directly con­sti­tute the activ­ity paths con­nect­ing one object to another within the user expe­ri­ence archi­tec­ture.  In this sense, the modes and chains could be said to act as a ‘skele­ton’ for twitter.com, and are directly vis­i­ble to an unprece­dented degree in the inter­ac­tion design built on that skeleton.

6 Discussion

The model described in this paper encom­passes a range of infor­ma­tion seek­ing behav­iours, from ele­men­tary lookup tasks through to more com­plex problem-solving activ­i­ties. How­ever, the model could also be framed as part of a broader set of infor­ma­tion behav­iours, extend­ing from ‘acqui­si­tion’ ori­ented tasks at one end of the spec­trum to ‘usage’ ori­ented activ­i­ties at the other (Fig­ure 24). In this con­text, modes can span more than one phase. For exam­ple, Explore entails a degree ofinter­ac­tion cou­pled with the antic­i­pa­tion of fur­ther dis­cov­ery, i.e. acqui­si­tion.  Like­wise, Eval­u­ate implies a degree of inter­ac­tion in the pur­suit of some higher goal or pur­pose to which the out­put will be put, i.e. usage.

It would appear that with the pos­si­ble excep­tion of syn­the­size, there are no exclu­sively usage-oriented behav­iours in the model. This may sug­gest that the model is in some senses incom­plete, or may sim­ply reflect the con­text in which the data was acquired and the IR-centric processes by which it was analysed.

Reduc­ing the ‘scope’ of the model such that modes serve only as descrip­tors of dis­tilled sense-making activ­ity inde­pen­dent of con­text (such as the user’s over­all goal and the nature of the infor­ma­tion assets involved) may help clar­ify the rela­tion­ship between acqui­si­tion, inter­ac­tion and usage phases. In this per­spec­tive, there appears to be a form of ‘par­al­lelism’ in effect; with users simul­ta­ne­ously under­tak­ing activ­i­ties focused on an over­all goal, such as Eval­u­at­ing the qual­ity of a finan­cial instru­ment, while also per­form­ing activ­i­ties focused on nar­rower information-centred objec­tives such as Locat­ing and Ver­i­fy­ing the util­ity of the infor­ma­tion assets nec­es­sary for them to com­plete the Eval­u­a­tion.  These ‘par­al­lel’ sets of activ­i­ties – one focused on infor­ma­tion assets in ser­vice to a larger goal, and the other focused on the goal itself – can be use­fully described in terms of modes, and what is more impor­tant, seem inter­twined in the minds of users as they artic­u­late their dis­cov­ery needs.

Fig. 24. From information acquisition to information useFig. 24. From infor­ma­tion acqui­si­tion to infor­ma­tion use 

A key fea­ture of the cur­rent model is its empha­sis on the com­bi­na­to­r­ial nature of search modes, and the value this offers as a frame­work for express­ing com­plex pat­terns of behav­iour. Evi­dently, such an approach is not unique: Makri (2008), for exam­ple, has also pre­vi­ously explored the con­cept of mode chains to describe infor­ma­tion seek­ing behav­iours observed in nat­u­ral­is­tic set­tings. How­ever, his approach was based on the analy­sis of com­plex tasks observed in real time, and as such was less effec­tive in reveal­ing con­sis­tent pat­terns of atomic behav­iour such as those found in the cur­rent study.

Con­versely, this virtue can also be a short­com­ing: the fact that sim­ple repeat­ing pat­terns can be extracted from the data may be as much an arte­fact of the medium as it is of the infor­ma­tion needs it con­tains. These sce­nar­ios were expressly designed to be a con­cise, self-contained deliv­er­able in their own right, and applied as a sim­ple but effec­tive tool in the plan­ning and pri­ori­ti­sa­tion of soft­ware devel­op­ment activ­i­ties. This places a limit on the length and sophis­ti­ca­tion of the infor­ma­tion needs they encap­su­late, and a nat­ural bound­ary on the scope and extent of the pat­terns they rep­re­sent. Their for­mat also allows a researcher to apply per­haps an unre­al­is­tic degree of top-down judge­ment and iter­a­tion in align­ing the rel­a­tive gran­u­lar­ity of the infor­ma­tion needs to exist­ing modes; a ben­e­fit that is less read­ily avail­able to those whose approach involves real-time, obser­va­tional data.

A fur­ther caveat is that in order to progress from under­stand­ing an infor­ma­tion need to iden­ti­fy­ing the infor­ma­tion behav­iours required to sat­isfy those needs, it is nec­es­sary to spec­u­late on the behav­iours that a user might per­form when under­tak­ing a task to sat­isfy the need. It may tran­spire that users actu­ally per­form dif­fer­ent behav­iours which achieve the same end, or per­form the expected behav­iour but through a com­bi­na­tion of other nested behav­iours, or may sim­ply sat­isfy the need in a way that had not been envis­aged at all.

Evi­dently, the process of infer­ring infor­ma­tion behav­iour from self-reported needs can never be wholly deter­min­is­tic, regard­less of the con­sis­tency mea­sures dis­cussed in Sec­tion 3.1. In this respect, fur­ther steps should be taken to oper­a­tional­ize the process and develop some inde­pen­dent mea­sure of sta­bil­ity or objec­tiv­ity in its usage, so that its value and insights can extend reli­ably to the wider research community.

The com­po­si­tional behav­iour of the modes sug­gests fur­ther open ques­tions and avenues for research. One of these is the nature of com­po­si­tion­al­ity itself: one the one hand it could be thought of as a pseudo-linguistic gram­mar, with bigrams and tri­grams of modes that com­bine in turn to form larger sequences, anal­o­gous to coher­ent “sen­tences”. In this con­text, the modes act as verbs, while the asso­ci­ated objects (users, infor­ma­tion assets, processes etc.) become the nouns. The occur­rence of dis­tinct ‘open­ing’ and ‘clos­ing’ modes in the sce­nar­ios would seem to fur­ther sup­port this view. How­ever, in some sce­nar­ios the tran­si­tions between the modes are far less appar­ent, and instead they could be seen as apply­ing in par­al­lel, like notes com­bin­ing in har­mony to form a musi­cal chord. In both cases, the degree and nature of any such com­po­si­tional rules needs fur­ther empir­i­cal inves­ti­ga­tion. This may reveal other depen­den­cies yet to be observed, such as the pos­si­bil­ity alluded to ear­lier of higher-level behav­iours requir­ing the com­ple­tion of cer­tain lower level modes before they them­selves can terminate.

The process of map­ping from modes to design inter­ven­tions also reveals fur­ther obser­va­tions on the util­ity of infor­ma­tion mod­els in gen­eral. Despite their evi­dent value as ana­lyt­i­cal frame­works and their pop­u­lar­ity among researchers (Bates’ Berryp­ick­ing model has been cited over 1,000 times, for exam­ple), few have gained sig­nif­i­cant trac­tion within the design com­mu­nity, and fewer still are adopted as part of the main­stream work­ing prac­tices of sys­tem design practitioners.

In part, this may be sim­ply a reflec­tion of imper­fect chan­nels of com­mu­ni­ca­tion between the research and design com­mu­ni­ties. How­ever, it may also reflect a grow­ing con­cep­tual gap between research insights on the one hand and cor­re­spond­ing design inter­ven­tions on the other. It is likely that the most valu­able the­o­ret­i­cal mod­els will need to strike a bal­ance between flex­i­bil­ity (the abil­ity to address a vari­ety of domains and prob­lems), gen­er­a­tive power (the abil­ity to express com­plex pat­terns of behav­iour) and an appro­pri­ate level of abstrac­tion (such that design insights are read­ily avail­able; or may be inferred with min­i­mal speculation).

7 Conclusions

In this paper, we have exam­ined the needs and behav­iours of indi­vid­u­als across a wide range of search and dis­cov­ery sce­nar­ios. We have pro­posed a model of infor­ma­tion seek­ing behav­iour which has at its core a set of modes that peo­ple reg­u­larly employ to sat­isfy their infor­ma­tion needs. In so doing, we explored a novel, goal-driven approach to elic­it­ing user needs, and iden­ti­fied some key dif­fer­ences in user behav­iour between site search and enter­prise search.

In addi­tion, we have demon­strated the value of the model as a frame­work for express­ing com­plex pat­terns of search behav­iour, extend­ing the IR con­cept of information-seeking to embrace a broader range of infor­ma­tion inter­ac­tion and use behav­iours. We pro­pose that our approach can be adopted by other researchers who want to adopt a ‘needs first’ per­spec­tive to under­stand­ing infor­ma­tion behaviour.

By illus­trat­ing ways in which indi­vid­ual modes are sup­ported in exist­ing search appli­ca­tions, we have made a prac­ti­cal con­tri­bu­tion that helps bridge the gap between inves­ti­gat­ing search behav­iour and design­ing appli­ca­tions to sup­port such behav­iour. In par­tic­u­lar, we have demon­strated how modes can serve as an effec­tive design tool across var­ied lev­els of sys­tem design: con­cept model, UX archi­tec­ture, inter­ac­tion design, and visual design.


  1. Bates, Mar­cia J. 1979. Infor­ma­tion Search Tac­tics. Jour­nal of the Amer­i­can Soci­ety for Infor­ma­tion Sci­ence 30, 205–214.
  2. Cool, C. & Belkin, N. 2002. A clas­si­fi­ca­tion of inter­ac­tions with infor­ma­tion. In H. Bruce (Ed.), Emerg­ing Frame­works and Meth­ods: CoLIS4: pro­ceed­ings of the 4th Inter­na­tional Con­fer­ence on Con­cep­tions of Library and Infor­ma­tion Sci­ence, Seat­tle, WA, USA, July 21–25, 1–15.
  3. Ellis, D.  1989.  A Behav­ioural Approach to Infor­ma­tion Retrieval Sys­tem Design.  Jour­nal of Doc­u­men­ta­tion, 45(3), 171–212.
  4. Ellis, D., Cox, D. & Hall, K. 1993.  A Com­par­i­son of the Information-seeking Pat­terns of Researchers in the Phys­i­cal and Social Sci­ences.  Jour­nal of Doc­u­men­ta­tion 49(4), 356–369.
  5. Ellis, D. & Hau­gan, M. 1997.  Mod­el­ling the Information-seeking Pat­terns of Engi­neers and Research Sci­en­tists in an Indus­trial Envi­ron­ment.  Jour­nal of Doc­u­men­ta­tion 53(4), pp. 384–403.
  6. Hobbs, J. (2005) An intro­duc­tion to user jour­neys. Boxes & Arrows. [Avail­able: http://www.boxesandarrows.com/an-introduction-to-user-journeys/
  7. Kalbach, J. (2012). Design­ing Screens Using Cores and Paths. Boxes & Arrows. [Avail­able:http://www.boxesandarrows.com/designing-screens-using-cores-and-paths/
  8. Laman­tia, J. 2006. 10 Infor­ma­tion Retrieval PatternsJoeLamantia.com. [Avail­able:http://www.joelamantia.com/information-architecture/10-information-retrieval-patterns.
  9. Laman­tia, J. (2009). Cre­at­ing Suc­cess­ful Por­tals with a Design Frame­work. Inter­na­tional Jour­nal of Web Por­tals (IJWP), 1(4), 63–75. doi:10.4018/jwp.2009071305
  10. Makri, S., Bland­ford, A. & Cox, A.L. 2008.  Inves­ti­gat­ing the Information-Seeking Behav­iour of Aca­d­e­mic Lawyers:  From Ellis’s Model to Design. Infor­ma­tion Pro­cess­ing and Man­age­ment 44(2), 613–634.
  11. Mar­chion­ini, G. 2006. Exploratory search: from find­ing to under­stand­ing. Com­mu­ni­ca­tions of the ACM 49(4), 41–46.
  12. Meho, L. & Tibbo, H. 2003.  Mod­el­ing the Information-seeking Behav­ior of Social Sci­en­tists: Ellis’s Study Revis­ited.  Jour­nal of the Amer­i­can Soci­ety for Infor­ma­tion Sci­ence and Tech­nol­ogy 54(6), 570–587.
  13. O’Day, V. & Jef­fries, R. 1993. Ori­en­teer­ing in an Infor­ma­tion Land­scape: How Infor­ma­tion Seek­ers get from Here to There.INTERCHI 1993, 438–445.
  14. Rose, D. and Levin­son, D. 2004. Under­stand­ing user goals in web search, Pro­ceed­ings of the 13th inter­na­tional con­fer­ence on World Wide Web, New York, NYUSA
  15. Russell-Rose, T., Laman­tia, J. and Bur­rell, M. 2011. A Tax­on­omy of Enter­prise Search and Dis­cov­ery. Pro­ceed­ings of HCIR 2011,Cal­i­for­nia, USA.
  16. Russell-Rose, T. and Makri, S. (2012). A Model of Con­sumer Search Behav­ior. Pro­ceed­ings of Euro­HCIR 2012, Nijmegen, Nether­lands.
  17. Spencer, D. 2006. Four Modes of Seek­ing Infor­ma­tion and How to Design for Them. Boxes & Arrows. [Avail­able:www.boxesandarrows.com/view/four_modes_of_seeking_information_and_how_to_design_for_them


Comment » | Information Architecture, Language of Discovery, User Research

'Designing the Search Experience' Available on Amazon

January 19th, 2013 — 11:53am

Design­ing the Search Expe­ri­ence: The Infor­ma­tion Archi­tec­ture of Dis­cov­ery is offi­cially avail­able for pur­chase from Ama­zon — con­grat­u­la­tions to authors Tony Russell-Rose and Tyler Tate. As I men­tioned in July, I was invited to con­tribute a piece. You can read my con­tri­bu­tion in chap­ter four, “Modes of Search and Discovery”.

Now, go buy the book!

Comment » | Language of Discovery, User Experience (UX)

The Architecture of Discovery: Slides from Discover Conference 2011

April 16th, 2011 — 1:11pm

Endeca invites cus­tomers, part­ners and lead­ing mem­bers of the broader search and dis­cov­ery tech­nol­ogy and solu­tions com­mu­ni­ties to meet annu­ally, and show­case the most inter­est­ing and excit­ing work in the field of dis­cov­ery.  As lead for the UX team that designs Endeca’s dis­cov­ery prod­ucts, I shared some of our recent work on pat­terns in the struc­ture of dis­cov­ery appli­ca­tions, as well as best prac­tices in infor­ma­tion design and visu­al­iza­tion that we use to drive prod­uct def­i­n­i­tion and design for Endeca’s Lat­i­tude Dis­cov­ery Framework.

This mate­r­ial is use­ful for pro­gram and project man­agers and busi­ness ana­lysts defin­ing require­ments for dis­cov­ery solu­tions and appli­ca­tions, UX and sys­tem archi­tects craft­ing high-level struc­tures and address­ing long-term growth, inter­ac­tion design­ers and tech­ni­cal devel­op­ers defin­ing and build­ing infor­ma­tion work­spaces at a fine grain, and

There are three major sec­tions: the first presents some of our tools for iden­ti­fy­ing and under­stand­ing people’s needs and goals for dis­cov­ery in terms of activ­ity (the Lan­guage of Dis­cov­ery as we call it), the sec­ond brings together screen-level, appli­ca­tion level, and user sce­nario / use-case level pat­terns we’ve observed in the appli­ca­tions cre­ated to meet those needs, and the final sec­tion shares con­densed best prac­tices and fun­da­men­tal prin­ci­ples for infor­ma­tion design and visu­al­iza­tion based on aca­d­e­mic research dis­ci­plines such as cog­ni­tive sci­ence and infor­ma­tion retrieval.

It’s no coin­ci­dence that these sec­tions reflect the appli­ca­tion of the core UX dis­ci­plines of user research, infor­ma­tion archi­tec­ture, and inter­ac­tion design to the ques­tion of “who will need to encounter infor­ma­tion for some end, and in what kind of expe­ri­ence will they encounter it”.  This flow and order­ing is delib­er­ate; it demon­strates on two lev­els the results of our own efforts apply­ing the UX per­spec­tive to the ques­tions inher­ent in cre­at­ing dis­cov­ery tools, and shares some of the tools, insights, tem­plates, and resources we use to shape the plat­form used to cre­ate dis­cov­ery expe­ri­ences across diverse industries.

Ses­sion outline

  1. Under­stand­ing User Needs
  2. Design Pat­terns for Dis­cov­ery Applications
  3. Design Prin­ci­ples and Gudielines for Infor­ma­tion Inter­ac­tion and Visualization

Ses­sion description

How can you har­ness the power and flex­i­bil­ity of Lat­i­tude to cre­ate use­ful, usable, and com­pelling dis­cov­ery appli­ca­tions for enter­prise dis­cov­ery work­ers? This ses­sion goes beyond the tech­nol­ogy to explore how you can apply fun­da­men­tal prin­ci­ples of infor­ma­tion design and visu­al­iza­tion, ana­lyt­ics best prac­tices and user inter­face design pat­terns to com­pose effec­tive and com­pelling dis­cov­ery appli­ca­tions that opti­mize user dis­cov­ery, suc­cess, engage­ment, & adoption.”

The pat­terns are prod­uct spe­cific in that they show how to com­pose screens and appli­ca­tions using the pre­de­fined com­po­nents in the Dis­cov­ery Frame­work library.  How­ever, many of the product-specific com­po­nents are built to address com­mon or recur­ring needs for inter­ac­tion with infor­ma­tion via well-known mech­a­nisms such as search, fil­ter­ing, nav­i­ga­tion, visu­al­iza­tion, and pre­sen­ta­tion of data.  In other words, even if you’re not using the lit­eral Dis­cov­ery Frame­work com­po­nent library to com­pose your spe­cific infor­ma­tion analy­sis work­space, you’ll find these pat­terns rel­e­vant at work­space and appli­ca­tion lev­els of scale.

The deeper story of these pat­terns is in demon­strat­ing the evo­lu­tion of dis­cov­ery and analy­sis appli­ca­tions over time.  Typ­i­cally, dis­cov­ery appli­ca­tions begin by offer­ing users a general-purpose work­space that sat­is­fies a wide range of inter­ac­tion tasks in an approx­i­mate fash­ion.  Over time, via suc­ces­sive expan­sions in the the scope and vari­ety of data they present, and the dis­cov­ery and analy­sis capa­bil­i­ties they pro­vide, dis­cov­ery appli­ca­tions grow to include sev­eral dif­fer­ent types of work­spaces that indi­vid­u­ally address dis­tinct sets of needs for visu­al­iza­tion and sense mak­ing by using very dif­fer­ent com­bi­na­tions of com­po­nents.  As a com­pos­ite, these func­tional and infor­ma­tion­ally diverse work­spaces span the full range of inter­ac­tion needs for dif­fer­ing types of users.

I hope you find this toolkit and col­lec­tion of pat­terns and infor­ma­tion design prin­ci­ples use­ful.  What are some of the resources you’re using to take on these challenges?

User Expe­ri­ence Archi­tec­ture For Dis­cov­ery Appli­ca­tions from Joe Laman­tia

Comment » | Dashboards & Portals, Enterprise, Information Architecture, User Experience (UX)

Understanding Frameworks: Beyond Findability IA Summit Workshop Slides

April 8th, 2010 — 6:05am

I’m post­ing slides for my ‘Under­stand­ing Frame­works’ por­tion of the Beyond Find­abil­ity work­shop on strate­gic prac­tices just given at the 2010 IA Sum­mit.  This por­tion of the full-day pro­gram empha­sizes under­stand­ing and iden­ti­fy­ing the com­mon things that make up a design frame­work, con­cen­trat­ing on the sim­ple struc­ture that design­ers need to grasp in order to cre­ate their own effec­tive frame­works for solv­ing design chal­lenges. I hope you find it infor­ma­tive and useful!

Design frame­works offer sub­stan­tial ben­e­fits to all par­ties involved in cre­at­ing high qual­ity user expe­ri­ences for prod­ucts, ser­vices, dig­i­tal media, and the emerg­ing inter­ac­tion spaces of aug­mented real­ity, ubiq­ui­tous com­put­ing, and cross-media sto­ry­telling. Frame­works allow design­ers to bet­ter adapt to the rapid shifts in the dig­i­tal envi­ron­ment by lever­ag­ing increas­ing mod­u­lar­ity, gran­u­lar­ity, and struc­ture, and accom­mo­dat­ing the far-reaching changes inher­ent in the rise of co-creative dynam­ics. This pre­sen­ta­tion — part of a full-day work­shop deliv­ered at the 2009 & 2010 Infor­ma­tion Archi­tec­ture Sum­mits — iden­ti­fies the ele­ments com­mon to all design frame­works, and offers best prac­tices on effec­tively putting frame­works into imme­di­ate use.  Alto­gether, it is a short course in the cre­ation and use of cus­tomized design frame­works for address­ing the com­plex­ity of strate­gic expe­ri­ence design.

Comment » | Building Blocks, Information Architecture, User Experience (UX)

Design For Goals: JBoye09 Workshop Slides

November 25th, 2009 — 5:42am

I’ve posted the slides from my tuto­r­ial / work­shop Design For Goals at JBoye 09 on slideshare: they’re embed­ded below.

The struc­ture for this tuto­r­ial is part method review (on how to under­stand people’s goals in a struc­tured way), and part shar­ing of re-usable pat­terns found after research­ing goals.   Since the con­text of ori­gin for both the goals and pat­terns was com­plex inter­na­tional finance, some trans­la­tion of the raw mate­ri­als and exam­ples and the syn­the­sized pat­terns into a realm closer to home for ordi­nary peo­ple is likely in order.

As you’re going through the slides, I sug­gest using your own activ­i­ties that involve infor­ma­tion find­ing and mak­ing sub­stan­tial finan­cial deci­sions as a ref­er­ence.  Not all the exam­ples that I selected as the basis of exer­cises dur­ing the tuto­r­ial made across the cul­tural bar­rier between North Amer­ica and North­ern Europe: I was sur­prised at how many peo­ple (in a pro­fes­sional audi­ence) have never bought house or car…  Which proves yet again that this is one of the areas for user expe­ri­ence design to work on as a discipline.

And as we had a small, noisy, and rather warm room right after lunch, I should say big thanks to all the par­tic­i­pants and vol­un­teers — every­one — who made an effort to engage.

Even design edu­ca­tion is a work-in-progress, it seems.

2 comments » | Customer Experiences, User Experience (UX), User Research

Two New UX Books: Modular Web Design & Card Sorting

July 22nd, 2009 — 5:39am

So many good books come out every year — even in the design and tech­nol­ogy fields — that it’s hard to ‘make a selec­tion’ as they say in Europe. To help through the dif­fi­cult choices, let me sug­gest two new user expe­ri­ence books worth adding to your library.

modularwebdesignMod­u­lar Web Design: Cre­at­ing Reusable Com­po­nents for User Expe­ri­ence Design and Doc­u­men­ta­tion, by Nathan Cur­tis, of eight­shapes fame. Com­po­nents, frame­works, and mod­u­lar­ity are near and dear to my heart (when applied in the right times and places for design pur­poses), so I can say with con­fi­dence that Mod­u­lar Web Design is the best explo­ration of the what, how and why of mod­u­lar design cur­rently avail­able. It should change the way you think about archi­tect­ing expe­ri­ences of all kinds, and — if you’re on board already — help you put this approach into prac­tice with clear exam­ples, advice, and guidance.

cardsorting-mdCard Sort­ing: Design­ing Usable Cat­e­gories, from the good peo­ple at Rosen­feld Media. Card Sort­ing is a thor­ough treat­ment of one of the most flex­i­ble, afford­able, and light­weight meth­ods in the user expe­ri­ence toolkit. Use my tool, but for chap­ter and verse on card sort­ing, read Donna Spencer’s book.

Buy both, and enjoy!

Comment » | Information Architecture, User Experience (UX)

Designing Frameworks For Interaction and User Experience: IA Summit Workshop Presentation

April 5th, 2009 — 11:05am

I’ve posted my slides and mate­ri­als from the Beyond Find­abil­ity work­shop Andrew Hin­ton, Livia Labate, Matthew Milan and I put on at the IA Sum­mit in Mem­phis recently.

This set of mate­ri­als addresses some of the most impor­tant ques­tions for prac­ti­tion­ers con­sid­er­ing a framework-based approach to design: why frame­warks mat­ter for user expe­ri­ence and inter­ac­tion design, what frame­works are use­ful for, and how you can work with them effectively.

Why *do* frame­works mat­ter? As I’m argu­ing, look around and you’ll see pro­found shifts chang­ing the struc­tural makeup of the dig­i­tal envi­ron­ment, the con­texts and bound­aries of the expe­ri­ences, and the role of pro­fes­sional designers.

For design­ers, very com­pli­cated and inter­est­ing prob­lems are on the way: think of Mike Kuniavsky’s work defin­ing some of the fun­da­men­tal con­cepts behind the ‘smart things’ that will inhabit this new design envi­ron­ment, such as infor­ma­tion shad­ows and ser­vice avatars. It’s plain that this world will require new tools, and I believe frame­works are part of that toolkit. (See my col­umn Every­ware: Design for the Ubiq­ui­tous Expe­ri­ence for ongo­ing perspective.)

And check out the slides for the rest of the work­shop :)

Noth­ing bet­ter than blues, bar­be­cue, and Build­ing Blocks!

Comment » | Building Blocks, User Experience (UX)

Frameworks Are the Future (Slides From EuroIA 2008)

October 8th, 2008 — 6:28am

In case you couldn’t make it to Ams­ter­dam for EuroIA 2008, or if you were in town but pre­ferred to stay out­side in the warmth of a sunny Sep­tem­ber Sat­ur­day than ven­ture into the mar­velous Tsuchin­ski the­ater, I’ve posted the slides from my talk Frame­works are the Future of Design.

Comment » | Building Blocks, Information Architecture, User Experience (UX)

Ubiquity and Chrome: Modular Is the New Black

September 19th, 2008 — 10:23am

The recent launches of Ubiq­uity (Mozilla Labs) and Chrome (Google) show how sexy it is to be mod­u­lar on the web, from the user expe­ri­ence [Ubiq­uity], to basic appli­ca­tion archi­tec­ture of the browser [Chrome]. This shouldn’t be a sur­prise to any­one, but it’s not some­thing I hear much about in the user expe­ri­ence com­mu­nity. The frag­men­ta­tion of the web into a ver­i­ta­ble bliz­zard of ser­vices, feeds, wid­gets, and API’s that cre­ate tidal waves of portable and sharable socially rich objects makes think­ing about mod­u­lar­ity indis­pens­able. In all design con­texts.
It’s time the user expe­ri­ence com­mu­nity embraced this way of think­ing, not least because it has excel­lent pedi­gree. Fifty years ago, in his famous talk There’s Plenty of Room At the Bot­tom, physi­cist Richard Fey­man said, “What I want to talk about is the prob­lem of manip­u­lat­ing and con­trol­ling things on a small scale.” His point was sim­ple: think about *all* the lev­els of scale and struc­ture that are part of the world, from very small to very large. Feyn­man wasn’t talk­ing about design­ing ser­vices and expe­ri­ences for the web or the wider realm of inte­grated expe­ri­ences(nice to see the com­mu­nity pick­ing up my ter­mi­nol­ogy…), but his mes­sage still applies. Work­ing, think­ing and design­ing at [sm]all lev­els of scale means doing it mod­u­larly.
The micro­for­mats com­mu­nity has under­stood this mes­sage for a long time, and is very suc­cess­ful at cre­at­ing small, use­ful, mod­u­lar things.
So how are you think­ing mod­u­larly about user experience?

Comment » | Building Blocks, Information Architecture

Frameworks are the Future of IA: A Case Study and Example

August 20th, 2008 — 7:43am

Sep­tem­ber in Ams­ter­dam approaches: in addi­tion to the inevitable mix of clouds, rain, more rain, and tiny sliv­ers of sun­light, Sep­tem­ber means EuroIA 2008, where yours truly will speak about design frame­works.
In case you can’t make the con­fer­ence, here’s a text only sum­mary of my talk. Pic­tures will fol­low the pre­sen­ta­tion — promise!

It’s a DIY Future
The Web is shift­ing to a DIY [Do It Your­self] model of user expe­ri­ence cre­ation, one where peo­ple assem­ble indi­vid­ual com­bi­na­tions of con­tent gath­ered form else­where for expres­sive, func­tional, and (many) other pur­poses. The rapid growth of wid­gets, the resur­gence of enter­prise por­tals, the spread of iden­tity plat­forms from social net­work des­ti­na­tions to blog­ging ser­vices, and the rapid increase in the num­ber of pub­lic APIs syn­di­cat­ing func­tion­al­ity and data, are all exam­ples of the DIY shift.

Archi­tects of the Future
For design pro­fes­sion­als, the defin­ing char­ac­ter­is­tic of DIY future is co-creation: the par­tic­i­pa­tion of a broad spec­trum of peo­ple in cre­at­ing expe­ri­ences. In this new world, the role of design­ers is to define the tools co-creators use to assem­ble expe­ri­ences for them­selves and oth­ers. These tools will increas­ingly take the form of design frame­works that define the mod­u­lar com­po­nents of famil­iar struc­tures such as social net­works, func­tional appli­ca­tions, col­lab­o­ra­tion plat­forms, per­son­al­ized dash­boards, and man­age­ment con­soles.

Why Frame­works?
Frame­works are the future for three rea­sons. First, every­one can cre­ate sophis­ti­cated infor­ma­tion struc­tures now, and design­ers no longer serve as a gate­way. Sec­ond, the def­i­n­i­tion of frame­works allows design­ers to con­tinue to pro­vide valu­able ser­vices and exper­tise in a cost effec­tive man­ner: It’s some­thing design­ers can sell in a com­mod­i­fied dig­i­tal econ­omy. Third, design­ers have an good com­bi­na­tion of human insight and archi­tec­ture design skills; this hybrid way of think­ing can serve as a dif­fer­en­tia­tor and strength.

One exam­ple of the sort of design frame­work infor­ma­tion archi­tects will cre­ate more of in the DIY future is the Por­tal Build­ing Blocks sys­tem described herein. Prov­i­den­tially, this design frame­work addresses many of the prob­lems inher­ent in the cur­rent archi­tec­tural schema for DIY self-assembled expe­ri­ences.

His­tory Repeats Itself: The Prob­lem With Por­tals
The rise and fall of the Web 1.0 por­tal form offers a use­ful his­tor­i­cal les­son for cre­ators of the new gen­er­a­tion of design frame­works under­ly­ing DIY self-assembled expe­ri­ences.
Despite early promises of util­ity and con­ve­nience, por­tals built with flat portlets could only grow by expand­ing hor­i­zon­tally. The result­ing expe­ri­ence of low-density infor­ma­tion archi­tec­tures was sim­i­lar to that of nav­i­gat­ing post­war sub­ur­ban sprawl. Like the rapid decline of many once-prosperous sub­urbs, the incon­ve­nience of these sprawl­ing col­lec­tions of portlets quickly over­whelmed the value of the con­tent they aggre­gated.
The com­mon prob­lem that doomed many very dif­fer­ent por­tals to the same fate was the com­plete lack of any pro­vi­sion for struc­ture, inter­ac­tion, or con­nec­tion between the self-contained portlets of the stan­dard por­tal design frame­work.
Look­ing ahead, the co-created expe­ri­ences of the DIY future will repeat this cycle of unhealthy growth and sprawl — think of all those apps clog­ging your iPhone’s home screen right now — unless we cre­ate design frame­works that effec­tively pro­vide for struc­ture, con­nec­tion, and inter­ac­tion.

The Build­ing Blocks — An Exam­ple Design Frame­work
The build­ing block frame­work is meant to serve as a robust archi­tec­tural foun­da­tion for the many kinds of tools and func­tion­al­ity — par­tic­i­pa­tory, social, col­lab­o­ra­tive — that sup­port the vision of two-way flows within and across the bound­aries of infor­ma­tion struc­tures. This means:

  • Allow for rapid growth and struc­tural change
  • Estab­lish a com­mon lan­guage for all co-creation perspectives
  • Encour­age con­struc­tion of scal­able, reusable structures
  • Cre­ate high-quality user experiences
  • Enable shar­ing of assets across boundaries
  • Enhance social dynam­ics, such as 2-way con­ver­sa­tion flows

The Build­ing Blocks frame­work defines two types of infor­ma­tion archi­tec­ture com­po­nents in detail — build­ing blocks (or Con­tain­ers), and nav­i­ga­tion com­po­nents (or Con­nec­tors) — as well as the sup­port­ing rules and guide­lines that make it pos­si­ble to assem­ble com­plex user expe­ri­ence archi­tec­tures quickly and effec­tively.
The Con­tain­ers and Con­nec­tors specif­i­cally pro­vide for struc­ture, inter­ac­tion, and con­nec­tion at all lev­els of the infor­ma­tion envi­ron­ment; from the user expe­ri­ence — visual design, infor­ma­tion design, inter­ac­tion design, infor­ma­tion archi­tec­ture — to func­tion­al­ity, meta­data, busi­ness rules, sys­tem archi­tec­ture, admin­is­tra­tive processes, and strate­gic gov­er­nance.
Case Study: Evo­lu­tion of an Enter­prise Por­tal Suite
The Build­ing Blocks began life as an inter­nal tool for low­er­ing costs and speed­ing design dur­ing the course of sus­tained por­tal work done for a For­tune 100 client. Over a span of ~24 months, the Build­ing Blocks pro­vided an effec­tive frame­work for the design, expan­sion, and even­tual inte­gra­tion of nearly a dozen dis­tinct por­tals.
The design frame­work evolved in response to changes in the audi­ences, struc­tures, and con­tents of por­tals con­structed for users in dif­fer­ent coun­tries, dif­fer­ent oper­at­ing units, and sev­eral orga­ni­za­tional lev­els.
The por­tal suite went through sev­eral stages of evo­lu­tion and growth:

  • Exper­i­men­ta­tion
  • Rapid expan­sion
  • Con­sol­i­da­tion & integration
  • Sta­bil­ity and continuity

Lessons In Design­ing Frame­works
Suc­cess­ful co-created expe­ri­ences — Flickr (com­mer­cial) and Wikipedia (non-commercial) — com­bine delib­er­ate top-down archi­tec­ture and design with emer­gent or bottom-up con­tri­bu­tion and par­tic­i­pa­tion in a new kind of struc­ture Kevin Kelly calls the “hybrid”. Frame­works sup­port hybrids!
Hope to see many of you in Amsterdam!

Comment » | Building Blocks, Dashboards & Portals, Information Architecture

Back to top