<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Application Concepting</title>
	<atom:link href="http://flashbulbinteraction.com/appconcepting/feed" rel="self" type="application/rss+xml" />
	<link>http://flashbulbinteraction.com/appconcepting</link>
	<description>Ideas for advancing user experiences in the evolving knowledge workplace.</description>
	<lastBuildDate>Fri, 11 Jun 2010 17:09:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Outlining “Opportunity Mapping: A Working through Screens Sketchbook”</title>
		<link>http://flashbulbinteraction.com/appconcepting/archives/190</link>
		<comments>http://flashbulbinteraction.com/appconcepting/archives/190#comments</comments>
		<pubDate>Mon, 12 Apr 2010 03:24:40 +0000</pubDate>
		<dc:creator>J_Burghardt</dc:creator>
				<category><![CDATA["Opportunity Mapping"]]></category>

		<guid isPermaLink="false">http://flashbulbinteraction.com/appconcepting/?p=190</guid>
		<description><![CDATA[



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 [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://flashbulbinteraction.com/appconcepting/wp-content/uploads/2010/04/MappingText.png"><img src="http://flashbulbinteraction.com/appconcepting/wp-content/uploads/2010/04/MappingText.png" alt="“Working through Screens” Ideas + Visual Sense Making = “Opportunity Mapping”" title="MappingText" width="690" height="191" class="aligncenter size-full wp-image-218" /></a></p>
<table width="580" border="0" cellpadding="0" width="100%">
<tr>
<td align="left" valign="top">
Another bit of planning similar to <a href="http://flashbulbinteraction.com/appconcepting/archives/150">the last post</a>, laying the groundwork for what’s <a href="http://flashbulbinteraction.com/appconcepting/archives/45">to come on this blog</a>:<br/><br/></p>
<p>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.</p>
<p>The motivation for this new work is in the opening thoughts of “Working through Screens.”<br />
<br/></p>
<ul>
<li>“Product teams creating computing tools for specialized workers struggle to understand what is needed and to successfully satisfy a myriad of constraints.”
</li>
<li>“Targeted improvements in the design of these tools can have large impacts on workers’ experiences. Visionary design can advance entire fields and industries.”
</li>
<li>“Dive into the specific cognitive challenges of knowledge workers’ practices in order to uncover new sources of product meaning and value.”
</li>
<li>“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.”</li>
<li>“Set higher goals for users’ experiences.”
</li>
</ul>
<p><br/></p>
<p>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.</p>
<p>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?</p>
<p>“Opportunity Mapping” will provide an organizing point of view and plenty of highly visual examples to answer these questions.</p>
<p>The plan is to create posts for each of these points, 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.</p>
<p><strong>Front Matter</strong><br/><br />
• Opening thoughts: Accelerating innovation for specialized work<br />
• Opening thoughts: More systemic frameworks for design ideation<br />
• Table of Contents (this post)<br />
• Preface</p>
<p><strong>Common Sense Making Challenges in Product Teams</strong><br/><br />
• Challenge &#8211; Laying a foundation of shared understanding about current user experiences<br />
• Challenge &#8211; Thinking through common opportunities to improve knowledge work<br />
• Challenge &#8211; Representing problems before jumping into design solutions<br />
• Challenge &#8211; Choosing where to focus design attention in complex systems</p>
<p><strong>Why Opportunity Mapping</strong><br/><br />
• Opportunity maps are a way to thoughtfully bridge UX data and conceptual design<br />
• Opportunity maps focus a product team’s design efforts<br />
• Opportunity maps do not cover the full range of an eventual solution<br />
• Opportunity maps can have four different levels of focus<br />
• Opportunity maps offer a general approach, not a concrete process<br />
• Opportunity maps can be built from 100 “Working through Screens” ideas</p>
<p><strong>1. Identification </strong><br/><br />
• Identification &#8211; Collaboratively identifying a broad range of potential design opportunities<br />
• Identification &#8211; Medical system example<br />
• Identification &#8211; Clinical research system example<br />
• Identification &#8211; Architectural system example<br />
• Identification &#8211; Financial trading system example</p>
<p><strong>2. Consolidation</strong><br/><br />
• Consolidation &#8211; Distilling identified opportunities into consolidated maps<br />
• Consolidation &#8211; Medical system example<br />
• Consolidation &#8211; Clinical research system example<br />
• Consolidation &#8211; Architectural system example<br />
• Consolidation &#8211; Financial trading system example</p>
<p><strong>3. Selection</strong><br/><br />
• Selection &#8211; Selecting targeted opportunities and mapping the meaning of those choices<br />
• Selection &#8211; Medical system example<br />
• Selection &#8211; Clinical research system example<br />
• Selection &#8211; Architectural system example<br />
• Selection &#8211; Financial trading system example</p>
<p><strong>4. Communication</strong><br/><br />
• Communication &#8211; Distilling selected opportunity focus and direction for product team audience<br />
• Communication &#8211; Medical system example<br />
• Communication &#8211; Clinical research system example<br />
• Communication &#8211; Architectural system example<br />
• Communication &#8211; Financial trading system example</p>
<p><strong>Closing Matter</strong><br/><br />
• Using opportunity maps throughout the product development lifecycle<br />
• Bibliography and further reading<br />
• About the author + Flashbulb Interaction, Inc.</p>
<p>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 <a href="http://twitter.com/J_Burghardt">@J_Burghardt</a> or send an email to <a href="mailto:jburghardt@FlashbulbInteraction.com">jburghardt@flashbulbinteraction.com</a><br/></p>
</td>
</tr>
</table>
]]></content:encoded>
			<wfw:commentRss>http://flashbulbinteraction.com/appconcepting/archives/190/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Outlining “Application Snapshots: A Working through Screens Sketchbook&#8221;</title>
		<link>http://flashbulbinteraction.com/appconcepting/archives/150</link>
		<comments>http://flashbulbinteraction.com/appconcepting/archives/150#comments</comments>
		<pubDate>Mon, 29 Mar 2010 00:16:51 +0000</pubDate>
		<dc:creator>J_Burghardt</dc:creator>
				<category><![CDATA["Application Snapshots"]]></category>

		<guid isPermaLink="false">http://flashbulbinteraction.com/appconcepting/?p=150</guid>
		<description><![CDATA[



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 [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://flashbulbinteraction.com/appconcepting/wp-content/uploads/2010/03/SnapshotsText.png"><img src="http://flashbulbinteraction.com/appconcepting/wp-content/uploads/2010/03/SnapshotsText.png" alt="" title="SnapshotsText" width="690" height="191" class="aligncenter size-full wp-image-189" /></a></p>
<table width="580" border="0" cellpadding="0" width="100%">
<tr>
<td align="left" valign="top">
<p>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 <a href="http://flashbulbinteraction.com/appconcepting/archives/45">earlier post</a>, this will be one of two “sketchbooks” that will show ways to bring <a href="http://www.flashbulbinteraction.com/WTS.html" target="_blank">“Working through Screens”</a> 100 envisioning ideas to life.<br/></p>
<p>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.<br/></p>
<p>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.</p>
<p>Snapshot 1<br />
H3. Automated historical records and versions<br />
E1. Offloading long term memory effort<br />
D1. Respected tempos of work<br />
K9. Directed application interoperation</p>
<p>Snapshot 2<br />
L2. Contemporary application aesthetics<br />
E2. Offloading short term memory effort<br />
D7. Eventual habit and automaticity<br />
K3. Recognizable applicability to targeted work</p>
<p>Snapshot 3<br />
J4. Authorship awareness, presence, and contact facilitation<br />
J1. Integral communication pathways<br />
I4. Uncertain or missing content<br />
D6. Alerting and reminding cues </p>
<p>Snapshot 4<br />
L3. Iconic design resemblances within applications<br />
B4. Object associations and user defined objects<br />
A6. Open and emergent work scenarios<br />
M1. Iterative conversations with knowledge workers</p>
<p>Snapshot 5<br />
I2. Comprehensive and relevant search<br />
G4. Workspace awareness embedded in interactions<br />
G2. Levels of selection and action scope<br />
D3. Current workload, priority of work, and opportunity costs</p>
<p>Snapshot 6<br />
M3. Application user communities<br />
I7. Archived information<br />
F8. Representational transformations<br />
B6. Flagged variability within or between objects</p>
<p>Snapshot 7<br />
H2. Extensive and reconstructive undo<br />
E3. Automation of low level operations<br />
E5. Visibility into automation<br />
D2. Expected effort</p>
<p>Snapshot 8<br />
K2. Introductory user experience<br />
I3. Powerful filtering and sorting<br />
H1. Active versioning<br />
C2. Application interaction model</p>
<p>Snapshot 9<br />
B5. Object states and activity flow visibility<br />
F4. Support for visualization at different levels<br />
I5. Integration of information sources<br />
A5. Interrelations of operation, task, and activity scenarios</p>
<p>Snapshot 10<br />
J6. Streamlined standard communications<br />
G3. Error prevention and handling in individual interactions<br />
F6. Instrumental results representations<br />
B10. Object templates</p>
<p>Snapshot 11<br />
J3. Explicit work handoffs<br />
E6. Internal locus of control<br />
E4. Automation of task or activity scenarios<br />
C6. Standardized application workflows</p>
<p>Snapshot 12<br />
K12. Trusted and credible processes and content<br />
F10. Symbolic visual languages<br />
F11. Representational codes and context<br />
A4. Standardization of work practice through mediation</p>
<p>Snapshot 13<br />
K8. Seamless inter-application interactivity<br />
K13. Reliable and direct activity infrastructure<br />
D5. Resuming work<br />
F9. Simultaneous or sequential use of representations</p>
<p>Snapshot 14<br />
K10. Openness to application integration and extension<br />
F7. Highly functional tables<br />
L1. High quality and appealing work products<br />
J7. Pervasive printing</p>
<p>Snapshot 15<br />
B9. Common management actions for objects<br />
K6. Design for frequency of access and skill acquisition<br />
C4. Pathways for task and activity based wayfinding<br />
A9. High value ratio for targeted work practices</p>
<p>Snapshot 16<br />
H4. Working annotations<br />
I6. Explicit messaging for information updates<br />
C3. Levels of interaction patterns<br />
B3. Coupling of application and real world objects</p>
<p>Snapshot 17<br />
K4. Verification of operation<br />
K5. Understanding and reframing alternate interpretations<br />
B8. Explicit mapping of objects to work mediation<br />
A3. Work practices appropriate for computer mediation</p>
<p>Snapshot 18<br />
K1. Application localization<br />
F2. Established genres of information representation<br />
B2. Flexible identification of object instances<br />
A8. Local practices and scenario variations</p>
<p>Snapshot 19<br />
F1. Coordinated representational elements<br />
C8. Defaults, customization, and automated tailoring<br />
L4. Appropriate use of imagery and direct branding<br />
D4. Minimizing distraction and fostering concentration</p>
<p>Snapshot 20<br />
K7. Clear and comprehensive instructional assistance<br />
C5. Permissions and views tailored to workers’ identities<br />
C1. Intentional and articulated conceptual models<br />
A2. Workers’ interrelations and relationships</p>
<p>Snapshot 21<br />
K11. End user programming<br />
G6. Contextual push of related information<br />
B1. Named objects and information structures<br />
M2. System champions</p>
<p>Snapshot 22<br />
M4. Unanticipated uses of technology<br />
G7. Transitioning work from private to public view<br />
F5. Comparative representations<br />
C9. Error prevention and handling conventions</p>
<p>Snapshot 23<br />
J2. Representational common ground<br />
C7. Structural support of workspace awareness<br />
B7. Object ownership and availability rules<br />
A7. Collaboration scenarios and variations</p>
<p>Snapshot 24<br />
L5. Iconoclastic product design<br />
G1. Narrative experiences<br />
F3. Novel information representations<br />
C10. Predictable application states</p>
<p>Snapshot 25<br />
J5. Public annotation<br />
I1. Flexible information organization<br />
G5. Impromptu tangents and juxtapositions<br />
A1. Influential physical and cultural environments</p>
<p>Sound interesting? Have some thoughts on how <a href="http://www.flashbulbinteraction.com/WTS.html" target="_blank">“Working through Screens”</a> ideas could be illustrated through example “snapshot” sketches? Your input would be greatly appreciated! Please comment on this post, tweet @<a href="http://twitter.com/J_Burghardt" target="_blank">J_Burghardt</a> or send an email to <a href="mailto:jburghardt@FlashbulbInteraction.com">jburghardt@flashbulbinteraction.com</a>
		</td>
</tr>
</table>
]]></content:encoded>
			<wfw:commentRss>http://flashbulbinteraction.com/appconcepting/archives/150/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Seeking input on your experiences using “Working through Screens”</title>
		<link>http://flashbulbinteraction.com/appconcepting/archives/106</link>
		<comments>http://flashbulbinteraction.com/appconcepting/archives/106#comments</comments>
		<pubDate>Wed, 27 Jan 2010 04:49:53 +0000</pubDate>
		<dc:creator>J_Burghardt</dc:creator>
				<category><![CDATA["Working through Screens"]]></category>

		<guid isPermaLink="false">http://flashbulbinteraction.com/appconcepting/?p=106</guid>
		<description><![CDATA[


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, [...]]]></description>
			<content:encoded><![CDATA[<table width="580" border="0" cellpadding="0" width="100%">
<tr>
<td align="left" valign="top">
As part of launching <a href="http://stores.lulu.com/flashbulbinteraction" target="new">print on demand versions</a> of our inaugural publication, I am gathering anecdotes about how readers have applied the “Working through Screens” ideas to their own projects.<br/><br/><br />
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 <a href="http://twitter.com/J_Burghardt" target="blank">@J_Burghardt</a> or send an email to <a href=mailto:info@flashbulbinteraction.com>info@flashbulbinteraction.com</a>).<br/><br/><br />
Your input will help Flashbulb Interaction improve future publications in our “Application Concepting Series.”  I look forward to hearing about your experiences!
		</td>
</tr>
</table>
]]></content:encoded>
			<wfw:commentRss>http://flashbulbinteraction.com/appconcepting/archives/106/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Announcing “Working through Screens” print on demand softcover books</title>
		<link>http://flashbulbinteraction.com/appconcepting/archives/61</link>
		<comments>http://flashbulbinteraction.com/appconcepting/archives/61#comments</comments>
		<pubDate>Wed, 27 Jan 2010 04:14:36 +0000</pubDate>
		<dc:creator>J_Burghardt</dc:creator>
				<category><![CDATA["Working through Screens"]]></category>
		<category><![CDATA[Studio Reports]]></category>

		<guid isPermaLink="false">http://flashbulbinteraction.com/appconcepting/?p=61</guid>
		<description><![CDATA[



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,&#8221; I have converted the book to create two 400 page, softcover, print on demand versions through Lulu.com:

Full color: $85.50 + S&#038;H
Black and white (with color cover): $15.50 + S&#038;H
ORDER [...]]]></description>
			<content:encoded><![CDATA[<p><object style="width:696px;height:451px" ><param name="movie" value="http://static.issuu.com/webembed/viewers/style1/v1/IssuuViewer.swf?mode=embed&amp;layout=http%3A%2F%2Fskin.issuu.com%2Fv%2Fcolor%2Flayout.xml&amp;backgroundColor=CCCCCC&amp;showFlipBtn=true&amp;documentId=100113193340-43783d691cb24fc5b1098417c9c9c71e&amp;docName=working_through_screens_color_letter&amp;username=FlashbulbInteraction&amp;loadingInfoText=Working%20through%20Screens%20(Color%20Letter%20Size)&amp;et=1263412435933&amp;er=7" /><param name="allowfullscreen" value="true"/><param name="menu" value="false"/><embed src="http://static.issuu.com/webembed/viewers/style1/v1/IssuuViewer.swf" type="application/x-shockwave-flash" allowfullscreen="true" menu="false" style="width:696px;height:451px" flashvars="mode=embed&amp;layout=http%3A%2F%2Fskin.issuu.com%2Fv%2Fcolor%2Flayout.xml&amp;backgroundColor=CCCCCC&amp;showFlipBtn=true&amp;documentId=100113193340-43783d691cb24fc5b1098417c9c9c71e&amp;docName=working_through_screens_color_letter&amp;username=FlashbulbInteraction&amp;loadingInfoText=Working%20through%20Screens%20(Color%20Letter%20Size)&amp;et=1263412435933&amp;er=7" /></object><br/></p>
<table width="580" border="0" cellpadding="0" width="100%">
<tr>
<td align="left" valign="top">
To celebrate the first anniversary of Flashbulb Interaction’s inaugural book, “<a href="http://www.flashbulbinteraction.com/WTS.html">Working through Screens: 100 Ideas for Envisioning Powerful, Engaging, and Productive User Experiences in Knowledge Work</a>,&#8221; I have converted the book to create two 400 page, softcover, print on demand versions through <a href="http://stores.lulu.com/flashbulbinteraction" target="new">Lulu.com</a>:<br/><br/></p>
<ul>
<li><strong>Full color</strong>: $85.50 + S&#038;H</li>
<li><strong>Black and white</strong> (with color cover): $15.50 + S&#038;H</a></strong></li>
<li><strong><a href="http://stores.lulu.com/flashbulbinteraction" target="new">ORDER SOFTCOVER BOOKS</a></strong></li>
<p><br/>
</ul>
<p>NOTE: Prices are Lulu.com minimum cost for printing (without any author markup). <br/><br />
The new, 8.5” X 11” format is also available for <a href="http://www.flashbulbinteraction.com/Color_Letter_Working_Through_Screens_Book.pdf" target="new">download as a .pdf</a><br/><br />
<a href="http://www.flashbulbinteraction.com/WTS.html"><strong>View a list of all “Working through Screens” formats</strong></a><br/><br/></p>
<p>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. <br/><br/></p>
<p>Here are a few reader comments that I am particularly thrilled with: <br/><br/></p>
<ul>
<li>“This is gorgeous and insightful.” Christina Wodtke</li>
<li>“Beautiful illustrations and useful patterns abound.” Jess McMullin</li>
<li>“An excellent, well-illustrated ebook on concept design for designers and product developers.” Michael Angeles</li>
<li>“An impressive collection of semi-abstracted design ideas and considerations for knowledge work&#8230;” Jonas Löwgren</li>
<li>“I can’t wait to delve deeper into this thoughtfully designed document.” Keith Tatum</li>
<li>&#8220;I think that people will find it a very useful guide and idea-generator.&#8221; Judy Ramey</li>
<p><br/>
</ul>
<p>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): <br/><br/></p>
<ul>
<li>90 Percent of Everything <a href="http://bit.ly/53ScnC" target="new">http://bit.ly/53ScnC</a></li>
<li>Architectr <a href="http://bit.ly/9bQrQe">http://bit.ly/9bQrQe</a></li>
<li>Asynchrony Community Blog <a href="http://bit.ly/coktAA">http://bit.ly/coktAA</a></li>
<li>Anvandbart <a href="http://bit.ly/525izb" target="new">http://bit.ly/525izb</a></li>
<li>Benry Blog <a href="http://bit.ly/73WwJq" target="new">http://bit.ly/73WwJq</a></li>
<li>BplusD <a href="http://bit.ly/6Tugtx" target="new">http://bit.ly/6Tugtx</a></li>
<li>Business Process Management (BPM) &#8211; Insights <a href="http://bit.ly/5p5yCz" target="new">http://bit.ly/5p5yCz</a></li>
<li>Carriezh.com.cn <a href="http://bit.ly/8Zw2Ha" target="new">http://bit.ly/8Zw2Ha</a></li>
<li>{ design@tive } information design <a href="http://bit.ly/4R8L3D" target="new">http://bit.ly/4R8L3D</a></li>
<li>DMI Blogs <a href="http://bit.ly/9wfEws">http://bit.ly/9wfEws</a></li>
<li>ElearningPost <a href="http://bit.ly/5rlOBJ" target="new">http://bit.ly/5rlOBJ</a></li>
<li>Emergent Chaos <a href="http://bit.ly/bYQkSG" target="new">http://bit.ly/bYQkSG</a></li>
<li>Make IT Right <a href="http://bit.ly/8f20yy" target="new">http://bit.ly/8f20yy</a></li>
<li>ModernAnalyst <a href="http://bit.ly/4n6jjR" target="new">http://bit.ly/4n6jjR</a></li>
<li>Fresh.Gui.Ru <a href="http://bit.ly/5poy7M" target="new">http://bit.ly/5poy7M</a></li>
<li>Glue <a href="http://bit.ly/5oepEu" target="new">http://bit.ly/5oepEu</a></li>
<li>Kicker Studio <a href="http://bit.ly/7g1BHi" target="new">http://bit.ly/7g1BHi</a></li>
<li>Ideonexus <a href="http://bit.ly/6KYMli" target="new">http://bit.ly/6KYMli</a></li>
<li>Idle Together <a href="http://bit.ly/5nnigh" target="new">http://bit.ly/5nnigh</a></li>
<li>IDM ´08 <a href="http://bit.ly/7wyymr" target="new">http://bit.ly/7wyymr</a></li>
<li>I heart wireframes <a href="http://bit.ly/cgwFQj" target="new">http://bit.ly/cgwFQj</a></li>
<li>Informal Learning Flow <a href="http://bit.ly/4BOfjG" target="new">http://bit.ly/4BOfjG</a></li>
<li>Information Aesthetics <a href="http://bit.ly/4sjzXZ" target="new">http://bit.ly/4sjzXZ</a></li>
<li>Information Design <a href="http://bit.ly/7llLhg" target="new">http://bit.ly/7llLhg</a></li>
<li>Just Another Blog <a href="http://bit.ly/7keDoL" target="new">http://bit.ly/7keDoL</a></li>
<li>Jonas Löwgren’s “Interaction Design Bookshelf” <a href="http://bit.ly/uPJuU" target="new">http://bit.ly/uPJuU</a></li>
<li>Jose Florido <a href="http://bit.ly/9gmSEl">http://bit.ly/9gmSEl</a></li>
<li>Konigi <a href="http://bit.ly/8JpgYy" target="new">http://bit.ly/8JpgYy</a></li>
<li>KnowledgeeratLarge <a href="http://bit.ly/8AiCpL" target="new">http://bit.ly/8AiCpL</a></li>
<li>LBI Collective <a href="http://bit.ly/5qH1vq" target="new">http://bit.ly/5qH1vq</a></li>
<li>Make IT Right <a href="http://bit.ly/8f20yy" target="new">http://bit.ly/8f20yy</a></li>
<li>Nick Finck <a href="http://bit.ly/5p2nfH" target="new">http://bit.ly/5p2nfH</a></li>
<li>Putting People First <a href="http://bit.ly/68Al24" target="new">http://bit.ly/68Al24</a></li>
<li>Process for Usability <a href="http://bit.ly/bQgKvz">http://bit.ly/bQgKvz</a></li>
<li>SOXIAM <a href="http://bit.ly/7FZUfk" target="new">http://bit.ly/7FZUfk</a></li>
<li>ShareUX <a href="http://bit.ly/bo28J9" target="new">http://bit.ly/bo28J9</a></li>
<li>Slingthought <a href="http://bit.ly/4I8zK7" target="new">http://bit.ly/4I8zK7</a></li>
<li>Steven D. Krause <a href="http://bit.ly/8II8hV" target="new">http://bit.ly/8II8hV</a></li>
<li>Tape Bomb <a href="http://bit.ly/74DzbA" target="new">http://bit.ly/74DzbA</a></li>
<li>Topophilia <a href="http://bit.ly/9DFtzs">http://bit.ly/9DFtzs</a></li>
<li>The Dahl Pod <a href="http://bit.ly/4rMgRw" target="new">http://bit.ly/4rMgRw</a></li>
<li>The Hot Strudel <a href="http://bit.ly/57whZ8" target="new">http://bit.ly/57whZ8</a></li>
<li>The Strake <a href="http://bit.ly/4YmECf" target="new">http://bit.ly/4YmECf</a></li>
<li>This is Lovely <a href="http://bit.ly/8qw36i" target="new">http://bit.ly/8qw36i</a></li>
<li>U &#038; I <a href="http://bit.ly/agO3TF" target="new">http://bit.ly/agO3TF</a></li>
<li>Uiiniu <a href="http://bit.ly/7cVvud" target="new">http://bit.ly/7cVvud</a></li>
<li>Urban Mainframe <a href="http://bit.ly/6dYlj1" target="new">http://bit.ly/6dYlj1</a></li>
<li>Usability Friction <a href="http://bit.ly/4S5M48" target="new">http://bit.ly/4S5M48</a></li>
<li>Usability in Context <a href="http://bit.ly/bQgKvz">http://bit.ly/bQgKvz</a></li>
<li>Usability Watch India <a href="http://bit.ly/8SBBn1" target="new">http://bit.ly/8SBBn1</a></li>
<li>User Centered <a href="http://bit.ly/8zHgav" target="new">http://bit.ly/8zHgav</a></li>
<li>User Experience Design <a href="http://bit.ly/8kUcAe" target="new">http://bit.ly/8kUcAe</a></li>
<li>User Interface Design <a href="http://bit.ly/8OeWjf" target="new">http://bit.ly/8OeWjf</a></li>
<li>Usernomics <a href="http://bit.ly/4Zg16z" target="new">http://bit.ly/4Zg16z</a></li>
<li>Valspire <a href="http://bit.ly/5VnmwZ" target="new">http://bit.ly/5VnmwZ</a></li>
<li>Work / Space <a href="http://bit.ly/4nhEhI" target="new">http://bit.ly/4nhEhI</a></li>
<li>Workspace <a href="http://bit.ly/7N9RGW" target="new">http://bit.ly/7N9RGW</a></li>
<li>Xblog <a href="http://bit.ly/6uYu9X" target="new">http://bit.ly/6uYu9X</a></li>
</ul>
<p><br/><br />
What do you think of the print on demand versions of “Working through Screens”? Please comment on this post, tweet <a href="http://twitter.com/J_Burghardt" target="new">@J_Burghardt</a>, or send email to <a href=mailto:info@flashbulbinteraction.com>info@flashbulbinteraction.com</a>.  I look forward to hearing your thoughts!
		</td>
</tr>
</table>
]]></content:encoded>
			<wfw:commentRss>http://flashbulbinteraction.com/appconcepting/archives/61/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Announcing Iterative Blogging of Two New “Application Concepting Series” Titles</title>
		<link>http://flashbulbinteraction.com/appconcepting/archives/45</link>
		<comments>http://flashbulbinteraction.com/appconcepting/archives/45#comments</comments>
		<pubDate>Fri, 08 Jan 2010 20:51:34 +0000</pubDate>
		<dc:creator>J_Burghardt</dc:creator>
				<category><![CDATA["Application Snapshots"]]></category>
		<category><![CDATA["Opportunity Mapping"]]></category>
		<category><![CDATA[Studio Reports]]></category>

		<guid isPermaLink="false">http://flashbulbinteraction.com/appconcepting/?p=45</guid>
		<description><![CDATA[


Q: What will you find on this blog in the near future?
A: Ideas for advancing user experience in the evolving knowledge workplace.
More specifically, I will be using this space to iteratively write the next two titles in Flashbulb Interaction’s &#8220;Application Concepting Series&#8221; of publications:

“Opportunity Mapping: A Working through Screens Sketchbook”
“Application Snapshots: A Working through Screens [...]]]></description>
			<content:encoded><![CDATA[<table width="580" border="0" cellpadding="0" width="100%">
<tr>
<td align="left" valign="top">
Q: What will you find on this blog in the near future?<br/></p>
<p>A: Ideas for advancing user experience in the evolving knowledge workplace.</p>
<p>More specifically, I will be using this space to iteratively write the next two titles in Flashbulb Interaction’s &#8220;Application Concepting Series&#8221; of publications:</p>
<ul>
<li>“Opportunity Mapping: A Working through Screens Sketchbook”</li>
<li>“Application Snapshots: A Working through Screens Sketchbook”</li>
</ul>
<p></br></p>
<p>By iteratively blogging draft content for these publications, I hope to gather feedback from readers like you.</p>
<p>As the titles suggest, each of these publications will be extensions of Flashbulb Interaction’s first book, “<a title="Working through Screens page" href="http://www.flashbulbinteraction.com/WTS.html" target="_blank">Working through Screens: 100 Ideas for Envisioning Powerful, Engaging, and Productive User Experiences in Knowledge Work</a>.”  These two new volumes will showcase a variety of ways that product teams might apply the 100 envisioning ideas to early, strategic phases of application definition and design.</p>
<p>Since &#8220;Working through Screens&#8221; was an intensive writing project, these next two volumes are going to focus more on visuals – on showing instead of telling. In keeping with the “sketchbook” idea, these projects will also be shorter and more open in format.  In general, both publications will be made up of a series of discrete “sketches,” with each idea presented in a two page “illustration and explanation” spread.  Since each spread of content will be self contained, my hope is that these new works will be especially well suited to being drafted as blog posts, right here at <a title="Application Concepting Blog" href="http://www.ApplicationConcepting.com">www.ApplicationConcepting.com</a>.</p>
<p>When this blog is eventually full of content, and the two “Working through Screens Sketchbooks” have come together from the sum of all the parts, the plan is to make each publication available as free .pdf files and as print on demand books.</p>
<p>Sound interesting?  Have ideas that you would like to share about compelling new ways to visualize user experience opportunities?  Or maybe you 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 @<a title="J Burghardt Twitter feed" href="http://twitter.com/J_Burghardt" target="_blank">J_Burghardt</a> or send an email to <a href="mailto:jburghardt@FlashbulbInteraction.com">jburghardt@flashbulbinteraction.com </a>
		</td>
</tr>
</table>
]]></content:encoded>
			<wfw:commentRss>http://flashbulbinteraction.com/appconcepting/archives/45/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Kicking Off “Application Concepting” Blog</title>
		<link>http://flashbulbinteraction.com/appconcepting/archives/38</link>
		<comments>http://flashbulbinteraction.com/appconcepting/archives/38#comments</comments>
		<pubDate>Fri, 08 Jan 2010 19:59:31 +0000</pubDate>
		<dc:creator>J_Burghardt</dc:creator>
				<category><![CDATA[Studio Reports]]></category>

		<guid isPermaLink="false">http://flashbulbinteraction.com/appconcepting/?p=38</guid>
		<description><![CDATA[


Flashbulb Interaction’s studio blog is now up and running!
Over time, you will find that this “Application Concepting” URL (www.ApplicationConcepting.com) will be geared toward “ideas for advancing user experience in the evolving knowledge workplace.” As an extension of our “Application Concepting Series” of book publications, this blog will strive to contribute to a larger discussion around [...]]]></description>
			<content:encoded><![CDATA[<table width="580" border="0" cellpadding="0" width="100%">
<tr>
<td align="left" valign="top">
Flashbulb Interaction’s studio blog is now up and running!<br/><br/></p>
<p>Over time, you will find that this “Application Concepting” URL (<a title="Application Concepting Blog" href="http://www.ApplicationConcepting.com">www.ApplicationConcepting.com</a>) will be geared toward “ideas for advancing user experience in the evolving knowledge workplace.” As an extension of our “Application Concepting Series” of book publications, this blog will strive to contribute to a larger discussion around how to drive vision in specialized application design.</p>
<p>If you define or design computing tools for some type of knowledge work activity or highly targeted profession, then this blog will provide you with a regular drumbeat of inspiration and ideas (<a title="Application Concepting Blog RSS Feed" href="http://flashbulbinteraction.com/appconcepting/feed" target="_blank">subscribe to blog RSS updates</a>). I look forward to hearing your comments!</p>
<p>Also, for quick updates from our consulting studio, including relevant links to online resources and general news about our work in progress, see our <a title="FlashbulbUX Twitter Feed" href="http://twitter.com/FlashbulbUX" target="_blank">FlashbulbUX Twitter </a>feed or subscribe to our <a title="FlashbulbUX Twitter RSS" href="http://twitter.com/statuses/user_timeline/20417275.rss" target="_blank">Twitter RSS updates</a>.</p>
<p>Jacob Burghardt<br />
President + Principal Consultant<br />
Flashbulb Interaction, Inc.<br />
E: <a href="mailto:jburghardt@FlashbulbInteraction.com">jburghardt@FlashbulbInteraction.com</a><br />
P: 206.280.3135
		</td>
</tr>
</table>
]]></content:encoded>
			<wfw:commentRss>http://flashbulbinteraction.com/appconcepting/archives/38/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
