Application Concepting

Opening Thoughts on Opportunity Mapping

J_Burghardt — Tue, 15 Feb 2011 21:37:14 +0000

This post is part of blogging a new publication “Opportunity Mapping: A Working through Screens Sketchbook.”

Three opening thoughts that will kick off the sketchbook:

Research has become a new normal for designing powerful, engaging, and productive technologies. It’s generally accepted that researching users, systems, activities, behaviors, motivations, and attitudes can help technologists of all stripes build empathy for design problems. But how can teams better examine, distill, and communicate what they learn so that they generate more compelling design ideas — ideas that can make a real difference in peoples’ working lives?

“…solving a problem simply means representing it so as to make the solution transparent.”
Herbert Simon, The Sciences of the Artificial

“We are not starting from scratch here. Many affective representations of complex phenomena have been developed in recent times. Physicists have illustrated quarks. Biologists have mapped the genome. Doctors have found ways to represent immune systems in the body. Network designers have mapped communication flows in buildings. Managers have charted the locations of expertise in their organizations. Our world is filled with representations of invisible or complex phenomena… So the design challenge… [is] how to deploy new representations in such a way that they influence wider groups of people.”
Jon Thackara, In the Bubble

More to come on this topic, eventually to culminate in a new Application Concepting Series book.

@J_Burghardt

Characterizing Opportunity Maps

J_Burghardt — Wed, 05 Jan 2011 18:37:01 +0000

This post is part of blogging a new publication “Opportunity Mapping: A Working through Screens Sketchbook.”

Opportunity maps are a way to thoughtfully bridge UX data and conceptual design

Product teams may find it difficult to make the leap between researching knowledge work and designing concepts to improve it. In many cases, teams move into the spreadsheet mindset too soon, rationalizing and prioritizing individual ideas in disconnected lists.

Top 10 “Breakdowns” and “Painpoints” marked on process diagrams may provide a basis for many important innovations, but they can also leave a whole range of opportunities for improving knowledge work on the table. Where are the opportunities to make complex conclusions clear for users? Where are the delightful flows that surpass workers’ goals in unexpected ways?

Opportunity maps can represent both the “loud” and “quieter” insights from design research, providing a connective brief that communicates pointed and strategic questions for design ideation.

Opportunity maps focus a product team’s design efforts

It’s not easy to understand a complex job or established profession. When teams are scattered, they may reach for the comfort of visualizing detailed, literal design particulars before they finish considering big picture questions about their offering’s direction.

The poet E.E. Cummings said, “Always the beautiful answer who asks a more beautiful question.” A design brief of thoughtful questions, based in data, can propel a team forward by narrowing the problem space where they are looking for solutions.

The act of mapping opportunities can help teams to have more strategic conversations about how insights should be distilled and communicated, steering their competing visions in a more cohesive direction.

Opportunity maps can range from exploratory views to distilled stories

These visual tools can fall on a continuum ranging from raw and granular to synthesized and summarized.

On the early side of the continuum, opportunity maps can become a tool for collecting insights that a product team generates when looking at their data through different lenses.

In the middle of the continuum, where the team has worked to generate a range of insights, opportunity maps can showcase selected insights and begin synthesizing opportunities for design ideation.

On the summative end of the continuum, opportunity maps can present distilled, strategic directions for improving users’ experiences, communicating a legible vector for what a knowledge work offering could be.

Opportunity maps can be built from 100 “Working through Screens” ideas

Product teams often fall back on a limited set of contemporary patterns and “at hand” design ideas when identifying insights to propel their computing tools forward.

It’s easy to overlook existing information about the role that computing can play in knowledge work. To push a broader perspective, teams can hold useful concepts next to their research findings, trying them on like different hats, in order to identify new insights.

The 100 application envisioning ideas in “Working through Screens” can be used as lenses to identify potential design opportunities in user experience data. Product teams can use the 100 ideas as a flexible checklist of possible contributions to the knowledge work that they are targeting with their system.

Opportunity maps can fit into any system envisioning process

The toolbox for product teams designing workplace systems is already overflowing with exacting, often prescriptive, methods.

Step-by-step formulas do not guarantee success when creating a design brief, especially when the goal is to support complex, cognitive professions by advancing the design of a product or service.

The visual language on the following pages is intended to broadly inspire, not inscribe a concrete approach. Opportunity maps could be created before, during, or even after conceptual design – whenever a range of opportunities need to be better understood and communicated beyond a small group of researchers and designers.

More to come on this topic, eventually to culminate in a new Application Concepting Series book.

Any and all comments appreciated, or tweet @J_Burghardt.

Why Opportunity Mapping?

J_Burghardt — Wed, 05 Jan 2011 01:07:31 +0000

This post is part of blogging a new publication “Opportunity Mapping: A Working through Screens Sketchbook.”

Teams designing tools for the knowledge workplace commonly research how users work

Today, most product teams creating tools for knowledge work understand that they can benefit from connecting with the workers that they are striving to design for.

Researching user needs has become a conventional part of the application design process, providing inspiration that can fuel innovative systems.

While breakthroughs may come from purely technological developments, insights into user needs and behavior can uncover opportunities to advance workplace systems in powerful, engaging, and productive ways.

The communication of design research outputs has room for improvement

The wall of post it notes has become a typical symbol of design research and sense making, showing how a product team’s design brief can inductively emerge from a collection of disordered ideas.

It turns out that the core team that makes sense of this data does most of the learning. Communicating deep insights beyond the ordered wall of paper particles can be difficult. Many important ideas remain in a small group of people, essentially shelved or forgotten.

Researchers and designers could benefit from exploring new ways of communicating their early, formative learnings, with the goal of making more lasting and traceable impacts in their organizations.

There are ongoing opportunities for transformative design in knowledge work applications

The problem of communicating a range of insights from the field is often a major obstacle for organizations that design tools for the knowledge workplace. The connective tissue between a product team’s learnings and resulting design outcomes can be tenuous.

Knowledge workers’ practices can be difficult for product teams to understand. Outsiders can find it difficult to meaningfully critique the systems supporting specialized jobs until they have built real empathy for the work.

For a knowledge worker, thoughtful function can be truly beautiful. However, teams envisioning workplace interactions often overlook or under-communicate key opportunities to make a transformative impact with design.

Designing the design problem can lead to new visual languages

How could new forms of visual communication help product teams to understand and evolve workplace systems, highlighting where to invest effort in order maximize value and meet user goals?

How could thoughtful information design allow teams to move past post-it note particles of information to more systemic frameworks for design ideation, pushing the boundaries of what’s considered core for workplace user experiences?

How might these frameworks become distilled throughout the design research process so that they communicate a strategic point of view, accelerating innovation for knowledge work?

More to come on this topic, eventually to culminate in a new Application Concepting Series book.

Any and all comments appreciated, or tweet @J_Burghardt.

Looking back at 2010 studio updates feed

J_Burghardt — Thu, 16 Dec 2010 20:02:26 +0000

Over a year ago, Flashbulb Interaction began posting daily studio updates using twitter.

So with all of the feeds that focus on designing compelling technology, why one more stream of thoughts and resources?

The designer Bruce Mau has said “The word ‘studio’ is derives from ‘study’. Our object is not to know the answers before we do the work. It’s to know them after we do it.”

Looking back across the @FlashbulbUX feed, it’s been a great way to formalize ongoing learning, continue to evolve a point of view, and pull together disparate ideas that may be useful for anyone who defines or designs workplace tools. It’s also been an excellent way to start conversations with colleagues and clients about emerging trends.

It’s interesting to scan some of the most popular tweets from the last year, tracing the interests of people who have “paid attention” to Flashbulb Interaction’s updates:

Overstated but relevant – If biz tech doesn’t catch up with UX we’re used to at home, workers may ditch corp network http://bit.ly/aYbT6u
Concern that current usability research methods are inadequate for evaluating complex, domain-specific tools http://bit.ly/9Jr6h5
A POV on app requirements “the collection of constraints that must be honored, or thoughtfully traversed” http://bit.ly/98IeIM
An emerging area of knowledge work – synthesizing and making sense of a there’s “data for that” world http://bit.ly/aQZVOg
To be successful, outputs of knowledge work must evoke knowledge in a recipient http://bit.ly/cZBzDm
Building Info Modeling “lets you discover ways of construction and sequencing and optimizing shapes for cost” http://bit.ly/aQZVOg
Case Management is the coordination of multiple tasks, planned or unplanned towards a concrete goal http://bit.ly/9aFSTc
Another POV on what UX strategy work can include http://bit.ly/a7Gx6X @inspireUX — Also thinking about opportunities http://bit.ly/aLnRde
One individual’s graph of own knowledge work, by outputs – reminiscent of Licklider’s formative introspection http://bit.ly/9GG8rg
Concept video on emergency response w/ apps for large displays. Familiar futurism + work rationalization http://bit.ly/baukj5

In 2011, look for more 140 character, “bite size” updates about the studio’s projects, including some broad-stroke learnings from our client work.

Also, watch for ten different trend names attached to many FlashbulbUX tweets (instead of the “Resource” identifier). Updates on these trends will also be a fixture on this blog:

Display Expansion
Interaction Options
Personal Assemblies
Connective Hubs
Collaborative Everyday
Unobtrusive Guidance
Informated Choices
Cacooned Concentration
Delightful Narratives
Data Deepend

Each of these macro trends for the emerging workplace may grow sub-trends over time…

@J_Burghardt

Inspiring documentary on the practice of data visualization

J_Burghardt — Sun, 03 Oct 2010 16:21:27 +0000

Goeff McGhee, currently at Stanford University, has posted “Journalism in the Age of Data,” a documentary on information visualization in the news. It’s a must watch — both informative and inspiring — for anyone looking to apply more visualization techniques.

The researchers and practitioners selectively showcased in this film self-consciously understand that they are at the forefront of a new frontier of knowledge work. In the new “there’s data for that” world, new specialties in analytics are emerging all the time, along with a stream of new applications and design approaches.

As mentioned in a previous post, I’m doing some studio research on how diverse user experience opportunities can be mapped for product team decision making and alignment. From that vantage point, two underlying information design tensions in the film ring true:

1. First glance appeal versus in-depth engagement

How do we create representations that draw the viewer in but then reward their attention with discernable, meaningful content?

2. Open exploration and discovery versus more fixed narrative storytelling

What models can we use to communicate central messages while at the same time allow the viewer to dig in for themselves?

This parallels a common problem in UX research: Not everyone in a product team has time to deeply engage with data to fully understand the context of research findings, but active navigation of structured outputs can help team members build valuable empathy and new perspectives.

Another point that struck me while watching this film was how detached the appearance of many visualizations are from their subjects. I think the design problem of how to inject more context into abstracted data displays is genuinely interesting. For example, without reading the title or the key of a typical information visualization, one wouldn’t necessarily know whether one was looking at a representation of obesity rates or new auto sales. I’m not advocating chart junk, just wondering about more refined approaches for triggering a viewer’s understandings – beyond the current minimalist, excessively data-rich fashions.

Many, but not all of the examples in the documentary have the heavy quantitative emphasis that is propelling the visualization field forward. However, I’m also curious about how the craft of information visualization can apply to mixed qualitative / quantitative data sets. A bit of the “everything can become numbers” mindset, but also more humanized somehow, without excessive distraction from primary content.

Flashbulb Interaction is increasingly basing design decisions on clients’ large stores of un-mined data about user behavior and subjective satisfaction. Although I quickly browsed some of the tools mentioned in this film (e.g. Swivel, Many Eyes), I am definitely going to give them more of a test drive in the near future.

What stands out to you about this documentary? What impact do you think the work of these pioneers will have on future threads of knowledge work?

@J_Burghardt

Broader lessons from health care app failures

J_Burghardt — Sun, 03 Oct 2010 16:21:00 +0000

Stumbled upon a lengthy discussion in the LinkedIn group “Healthcare Information and Management Systems Society” that had a number of interesting themes for anyone creating workplace applications.

The opening question was very broad, asking for input on why some implementations of Electronic Medical Records (EMR) are failing to meet expectations. The resulting conversation (over 700 comments) brought up a range of thoughtful points on the root causes of these failures, and I have summarized some of them here in no particular order:

• Lack of vision about system benefits at the leadership level.

• Reactive culture focused on fixing problems, rather than active knowledge work improvement.

• Current IT staff may not be qualified for such a large shift in IT responsibility.

• Emphasis on rapid deployment without sufficient long term evolution and follow through.

• Cultural clash between outside technologists and the knowledge workforce they are “serving.”

• Technology vendors’ lack of understanding about users’ work practices.
See also WTS A1. Influential physical and cultural environments.

• Difficulty integrating diverse systems with conflicting technical standards.
See also WTS K10. Openness to application integration and extension.

• Existing workflow issues can be compounded by adoption of new systems.

• Mistakenly pushing open and emergent work into standardized workflows.
See also WTS A6. Open and emergent work scenarios and C6. Standardized application workflows.

• Skilled professionals need to understand the payoff before investing effort into changing their practices.
See also WTS K3. Recognizable applicability to targeted work.

• Diverse roles within organizations require application views designed to support their goals.
See also WTS C5. Permissions and views tailored to workers’ identities.

• Customization and flexibility are difficult given the range of professional practices.
See also WTS A3. Work practices appropriate for computer mediation and C8. Defaults, customization, and automated tailoring.

• Lack of trusted sources and technology leadership to drive motivated use.
See also WTS K12. Trusted and credible processes and content.

• Excessive data entry slowing common, day-to-day work.
See also WTS D2. Expected effort.

Deployments of EMRs, and the adoption of tech in the healthcare industry generally, provide great models for understanding how to augment cooperative work in layered cultures of established work practice. And it seems that a flock of designers have tuned in: the broader thread on healthcare design is inspiring, though the emphasis often seems to fall more on patients rather than caregivers.

The leading points in the list above can be humbling for designers, emphasizing that the primary factors for success or failure in workplace applications are often in the hands of project and organizational leadership.

I’m reminded of a quote from years ago by David Childs, a SOM architect working at Ground Zero: Something along the lines of “It takes a client to make a building.” I think of it often, and read it two ways: both as a statement of crass commercialism in the face of more civic-minded design intent, and as a basic truth of design services.

I love so-called “paper architecture” and open design exploration, but I’m also driven to promote real improvements in user experiences for people practicing their chosen vocations.

In a hand-waving sense, there are always plenty of abstract arguments about the benefits of computing tools in organizations. Shared industry beliefs, fashionable truisms, and rehearsed marketing pitches. Designers generate conceptual projects that show compelling advancements in user experience. In a conference room, futuristic applications can seem like near term inevitabilities.

But to successfully implement a system like an EMR — a messy, long term bet, involving systemic interventions — requires highly motivated leaders who have bought into a big picture.

Effective designers in these situations are facilitators of pragmatic process, collaborators in service of a vision, willing to dive into the unexpected hurdles of real world adoption. Else, design’s contributions are simply more visionary images projected on the wall, mismatched to the reality of what a client will actually follow through on, to be filed away on some repository and forgotten.

Caregivers and patients deserve better.

Know any great resources on the success or failure of Electronic Medical Records? Have any of the bullet points above impacted your projects?

@J_Burghardt

Outlining “Opportunity Mapping: A Working through Screens Sketchbook”

J_Burghardt — Mon, 12 Apr 2010 03:24:40 +0000

Another bit of planning similar to the last post, laying the groundwork for what’s to come on this blog:

I have been thinking though a series of posts that will culminate in another book, “Opportunity Mapping: A Working through Screens Sketchbook.” As mentioned in an earlier post, this will be one of two “sketchbooks” that will show ways to bring “Working through Screens” 100 envisioning ideas to life.

The motivation for this new work is in the opening thoughts of “Working through Screens.”

“Product teams creating computing tools for specialized workers struggle to understand what is needed and to successfully satisfy a myriad of constraints.”
“Targeted improvements in the design of these tools can have large impacts on workers’ experiences. Visionary design can advance entire fields and industries.”
“Dive into the specific cognitive challenges of knowledge workers’ practices in order to uncover new sources of product meaning and value.”
“Keep asking questions until you uncover driving factors that resonate. Create visual models of them. Focus your team on these shared kernels of understanding and insight. Lay the groundwork for inspiration.”
“Set higher goals for users’ experiences.”

If valuable application design action starts with the recognition of an opportunity, then this thread of posts will focus on presenting some ideas of how product teams might develop shared understandings of where to focus their limited design attention.

How can teams move beyond top ten lists of “breakdowns” to improve workplace user experiences in transformative ways? What maps of design opportunities could push the boundaries of what might be considered core to application user experiences?

“Opportunity Mapping” will provide an organizing point of view and plenty of highly visual examples to answer these questions.

The plan is to create posts for these categories, and then pull them together at some point into a single Application Concepting Series volume (print on demand or free .pdf). I’m sure that I will be editing this rough Table of Contents along the way, and I will also link out to completed posts as this project rolls along.

Opening Thoughts

Table of Contents (this post)

Preface

Why Opportunity Mapping?
• Teams designing tools for the knowledge workplace commonly research how users work
• The communication of design research outputs has room for improvement
• There are ongoing opportunities for transformative design in knowledge work applications
• Designing the design problem could lead to new visual languages

Characterizing Opportunity Maps
• Opportunity maps are a way to thoughtfully bridge UX data and conceptual design
• Opportunity maps focus a product team’s design efforts
• Opportunity maps can range from exploratory views to distilled stories
• Opportunity maps can be built from 100 “Working through Screens” ideas
• Opportunity maps can fit into any system envisioning process

Example Opportunity Maps
• Four Types of Knowledge Work in Example Maps
• Index of 20 posts to be added here as they are completed

References

Sound interesting? Have ideas that you would like to share about compelling new ways to visualize user experience opportunities? Your input would be greatly appreciated! Please comment on this post, tweet @J_Burghardt or send an email to jburghardt@flashbulbinteraction.com

Outlining “Application Snapshots: A Working through Screens Sketchbook”

J_Burghardt — Mon, 29 Mar 2010 00:16:51 +0000

I have been thinking through a series of posts that will culminate in another book, “Application Snapshots: A Working through Screens Sketchbook.” As mentioned in an earlier post, this will be one of two “sketchbooks” that will show ways to bring “Working through Screens” 100 envisioning ideas to life.

Readers have responded positively to the illustrations and new design patterns in Flashbulb Interaction’s creative commons work, so “Application Snapshots” will be a fairly free form sketchbook of design ideas. Mostly showing, rather than telling. None of these ideas will have been vetted through usability research or real world implementation – and that’s not the point. Instead, this project will be about sparking ideas in a technology space where many potential user experience innovations are left unexplored and design often evolves in slow iterations.

So here are 25 groupings with four “Working through Screens” ideas in each cluster. The plan is to create an “Application Snapshot” for each grouping, and then pull them together at some point into a single Application Concepting Series volume (print on demand or free .pdf). I’m sure that I will be editing this rough Table of Contents along the way, and I will also link out to completed posts as this project rolls along.

Snapshot 1
H3. Automated historical records and versions
E1. Offloading long term memory effort
D1. Respected tempos of work
K9. Directed application interoperation

Snapshot 2
L2. Contemporary application aesthetics
E2. Offloading short term memory effort
D7. Eventual habit and automaticity
K3. Recognizable applicability to targeted work

Snapshot 3
J4. Authorship awareness, presence, and contact facilitation
J1. Integral communication pathways
I4. Uncertain or missing content
D6. Alerting and reminding cues

Snapshot 4
L3. Iconic design resemblances within applications
B4. Object associations and user defined objects
A6. Open and emergent work scenarios
M1. Iterative conversations with knowledge workers

Snapshot 5
I2. Comprehensive and relevant search
G4. Workspace awareness embedded in interactions
G2. Levels of selection and action scope
D3. Current workload, priority of work, and opportunity costs

Snapshot 6
M3. Application user communities
I7. Archived information
F8. Representational transformations
B6. Flagged variability within or between objects

Snapshot 7
H2. Extensive and reconstructive undo
E3. Automation of low level operations
E5. Visibility into automation
D2. Expected effort

Snapshot 8
K2. Introductory user experience
I3. Powerful filtering and sorting
H1. Active versioning
C2. Application interaction model

Snapshot 9
B5. Object states and activity flow visibility
F4. Support for visualization at different levels
I5. Integration of information sources
A5. Interrelations of operation, task, and activity scenarios

Snapshot 10
J6. Streamlined standard communications
G3. Error prevention and handling in individual interactions
F6. Instrumental results representations
B10. Object templates

Snapshot 11
J3. Explicit work handoffs
E6. Internal locus of control
E4. Automation of task or activity scenarios
C6. Standardized application workflows

Snapshot 12
K12. Trusted and credible processes and content
F10. Symbolic visual languages
F11. Representational codes and context
A4. Standardization of work practice through mediation

Snapshot 13
K8. Seamless inter-application interactivity
K13. Reliable and direct activity infrastructure
D5. Resuming work
F9. Simultaneous or sequential use of representations

Snapshot 14
K10. Openness to application integration and extension
F7. Highly functional tables
L1. High quality and appealing work products
J7. Pervasive printing

Snapshot 15
B9. Common management actions for objects
K6. Design for frequency of access and skill acquisition
C4. Pathways for task and activity based wayfinding
A9. High value ratio for targeted work practices

Snapshot 16
H4. Working annotations
I6. Explicit messaging for information updates
C3. Levels of interaction patterns
B3. Coupling of application and real world objects

Snapshot 17
K4. Verification of operation
K5. Understanding and reframing alternate interpretations
B8. Explicit mapping of objects to work mediation
A3. Work practices appropriate for computer mediation

Snapshot 18
K1. Application localization
F2. Established genres of information representation
B2. Flexible identification of object instances
A8. Local practices and scenario variations

Snapshot 19
F1. Coordinated representational elements
C8. Defaults, customization, and automated tailoring
L4. Appropriate use of imagery and direct branding
D4. Minimizing distraction and fostering concentration

Snapshot 20
K7. Clear and comprehensive instructional assistance
C5. Permissions and views tailored to workers’ identities
C1. Intentional and articulated conceptual models
A2. Workers’ interrelations and relationships

Snapshot 21
K11. End user programming
G6. Contextual push of related information
B1. Named objects and information structures
M2. System champions

Snapshot 22
M4. Unanticipated uses of technology
G7. Transitioning work from private to public view
F5. Comparative representations
C9. Error prevention and handling conventions

Snapshot 23
J2. Representational common ground
C7. Structural support of workspace awareness
B7. Object ownership and availability rules
A7. Collaboration scenarios and variations

Snapshot 24
L5. Iconoclastic product design
G1. Narrative experiences
F3. Novel information representations
C10. Predictable application states

Snapshot 25
J5. Public annotation
I1. Flexible information organization
G5. Impromptu tangents and juxtapositions
A1. Influential physical and cultural environments

Sound interesting? Have some thoughts on how “Working through Screens” ideas could be illustrated through example “snapshot” sketches? Your input would be greatly appreciated! Please comment on this post, tweet @J_Burghardt or send an email to jburghardt@flashbulbinteraction.com

Seeking input on your experiences using “Working through Screens”

J_Burghardt — Wed, 27 Jan 2010 04:49:53 +0000

As part of launching print on demand versions of our inaugural publication, I am gathering anecdotes about how readers have applied the “Working through Screens” ideas to their own projects.

Have you applied “Working through Screens” to your own application definition and design efforts? If you have a story to share, please comment on this post, providing as much detail as you are comfortable sharing about your project and how you put “Working through Screens” to use. (Alternately, tweet @J_Burghardt or send an email to info@flashbulbinteraction.com).

Your input will help Flashbulb Interaction improve future publications in our “Application Concepting Series.” I look forward to hearing about your experiences!

Announcing “Working through Screens” print on demand softcover books

J_Burghardt — Wed, 27 Jan 2010 04:14:36 +0000

To celebrate the first anniversary of Flashbulb Interaction’s inaugural book, “Working through Screens: 100 Ideas for Envisioning Powerful, Engaging, and Productive User Experiences in Knowledge Work,” I have converted the book to create two 400 page, softcover, print on demand versions through Lulu.com:

Full color: $85.50 + S&H
Black and white (with color cover): $15.50 + S&H
ORDER SOFTCOVER BOOKS

NOTE: Prices are Lulu.com minimum cost for printing (without any author markup).

The new, 8.5” X 11” format is also available for download as a .pdf

View a list of all “Working through Screens” formats

The reader response from the e-book versions in the first year has been extremely gratifying, and I would like to enthusiastically thank everyone who has taken the time to let me know their thoughts on this project.

Here are a few reader comments that I am particularly thrilled with:

“This is gorgeous and insightful.” Christina Wodtke
“Beautiful illustrations and useful patterns abound.” Jess McMullin
“An excellent, well-illustrated ebook on concept design for designers and product developers.” Michael Angeles
“An impressive collection of semi-abstracted design ideas and considerations for knowledge work…” Jonas Löwgren
“I can’t wait to delve deeper into this thoughtfully designed document.” Keith Tatum
“I think that people will find it a very useful guide and idea-generator.” Judy Ramey

I also want to thank everyone who tweeted, emailed about, and socially bookmarked “Working through Screens” – your sharing and responses have been truly inspiring. I would particularly like to thank all of the blogs and sites that posted about the free e-book (apologies if I have missed anyone):

90 Percent of Everything http://bit.ly/53ScnC
AHOi http://bit.ly/ggxtpD
All the good things http://bit.ly/feKg5Q
Architectr http://bit.ly/9bQrQe
Asynchrony Community Blog http://bit.ly/coktAA
Anvandbart http://bit.ly/525izb
Benry Blog http://bit.ly/73WwJq
BIM Buzz http://bit.ly/mrVIbL
BplusD http://bit.ly/6Tugtx
Business Process Management (BPM) – Insights http://bit.ly/5p5yCz
Carriezh.com.cn http://bit.ly/8Zw2Ha
Cloud Forest Design Resources Page http://bit.ly/hVwqBF
{ design@tive } information design http://bit.ly/4R8L3D
DMI Blogs http://bit.ly/9wfEws
ebookDB http://bit.ly/bAEdZe
ElearningPost http://bit.ly/5rlOBJ
Emergent Chaos http://bit.ly/bYQkSG
Free Computer Books http://bit.ly/bn76Av
Fresh.Gui.Ru http://bit.ly/5poy7M
Glue http://bit.ly/5oepEu
Kicker Studio http://bit.ly/7g1BHi
LorieLue http://bit.ly/hoFxZv
Ideonexus http://bit.ly/6KYMli
Idle Together http://bit.ly/5nnigh
IDM ´08 http://bit.ly/7wyymr
I heart wireframes http://bit.ly/cgwFQj
Informal Learning Flow http://bit.ly/4BOfjG
Information Aesthetics http://bit.ly/4sjzXZ
Information Design http://bit.ly/7llLhg
Integrating Your Enterprise http://bit.ly/cz9Myz
Just Another Blog http://bit.ly/7keDoL
Jonas Löwgren’s “Interaction Design Bookshelf” http://bit.ly/uPJuU
Jose Florido http://bit.ly/9gmSEl
Konigi http://bit.ly/8JpgYy
KnowledgeeratLarge http://bit.ly/8AiCpL
LBI Collective http://bit.ly/5qH1vq
Make IT Right http://bit.ly/8f20yy
ModernAnalyst http://bit.ly/4n6jjR
Murilo Lima http://bit.ly/iUZGzS
Nick Finck http://bit.ly/5p2nfH
Ph4re http://bit.ly/kj2nxS
Putting People First http://bit.ly/68Al24
Process for Usability http://bit.ly/bQgKvz
SOXIAM http://bit.ly/7FZUfk
ShareUX http://bit.ly/bo28J9
Slingthought http://bit.ly/4I8zK7
Steven D. Krause http://bit.ly/8II8hV
Tape Bomb http://bit.ly/74DzbA
Topophilia http://bit.ly/9DFtzs
The Dahl Pod http://bit.ly/4rMgRw
The Hot Strudel http://bit.ly/57whZ8
The Online Books Page http://bit.ly/dmsuMA
The Strake http://bit.ly/4YmECf
This is Lovely http://bit.ly/8qw36i
U & I http://bit.ly/agO3TF
Uiiniu http://bit.ly/7cVvud
Urban Mainframe http://bit.ly/6dYlj1
Usability Friction http://bit.ly/4S5M48
Usability in Context http://bit.ly/bQgKvz
Usability Watch India http://bit.ly/8SBBn1
User Centered http://bit.ly/8zHgav
User Experience Design http://bit.ly/8kUcAe
User Interface Design http://bit.ly/8OeWjf
Usernomics http://bit.ly/4Zg16z
Valspire http://bit.ly/5VnmwZ
Work / Space http://bit.ly/4nhEhI
Workspace http://bit.ly/7N9RGW
Xblog http://bit.ly/6uYu9X

What do you think of the print on demand versions of “Working through Screens”? Please comment on this post, tweet @J_Burghardt, or send email to info@flashbulbinteraction.com. I look forward to hearing your thoughts!