Posts of the Original variety

Newer
Older

Noun-based Data vs. Intention-based Data

This comes from an internal Google memo, from Jonathan Rosenberg, SVP of Product Management, that was later released publicly.  Its tone is thoroughly optimistic but more importantly it lays out some of Google’s theses on the future of the web.   Particularly interesting is the piece on content creation, which stresses the importance of experts to craft our data, a very under-represented view point in new product development.

Systems that facilitate high-quality content creation and editing are crucial for the Internet’s continued growth, because without them we will all sink in a cesspool of drivel. We need to make it easier for the experts, journalists, and editors that we actually trust to publish their work under an authorship model that is authenticated and extensible, and then to monetize in a meaningful way.

He also communicates a bias for making all information available, dismissing the common model that charges for access to interesting data.

All of our products should reflect our bias toward giving our customers, users, and partners as much data as possible – and letting them do with it what they wish.

This makes sense if you’re Google, where the scale of information only compounds value to your core search product. I still think the ‘old’ model of packaging and selling access to such data has some legs left, especially if you’re a small  company focused on extracting intention-based data from a valuable niche.

You can segment the data into two types: noun-based data and intention-based data.  Noun-based data is mostly descriptive of the world around us – specs of a phone, who our friends on facebook are, etc.  This data, without a question, should be made freely available for all to use.  On the other side is intention-based data.  If you run a poll that asks a user to rank which aspects of a phone are most important to guiding their purchasing decision, you’re taping into intention-based data, the same type of data that google makes all of their money off of.

Intention-based data is a bit harder to set free, partly for reasons of privacy, but also because it’s intrinsically valuable.  You need to work hard to create value around noun-based data, that’s why it makes sense to set it free.  The richness of functionality that the Twitter and Facebook API’s created could not be possible if either company hoarded their data.  Intention-based data is different, it has implicit information leverage.  As soon as you set it free, you remove the leverage that creates the value to begin with.  You want to be the conduit of this data.

Feb 20 2009

Designing from the Outside In (kind of)

Over on the Adaptive Path blog, Brandon Schauer shows off a couple of nice diagrams, illustrating how new products typically get approached, how they they’re perceived, and how they should be approached.

How not to do it

How not to do it.

What the user sees

What the user sees.

Yep, that looks about right

That looks about right.

I’m a little bit divorced from the original context of the diagrams (“how businesses approach delivering value to their customers”?), but I was only thinking about something like this yesterday. What comes first, the interface or the data model?  There is no question, that the diagram of user’s perception of a product is spot-on, they could care less how and what you’re storing on the back-end.  However, with a complex-enough problem, it’s hard to make informed inroads without exploring the interface and data asynchronously.  

The user research and design process will always have the first stroke, but to understand the data and solve problems around the data is to acquire domain-specific knowledge of the problem space.  For instance: to meaningfully organize a product spec page for a laptop, you need to understand the data that surrounds a laptop.  And if you’re not using a more realized data model, you’re effectively using “lorem ipsum” and a lot can be said about the deficiencies of that strategy.

Feb 19 2009

Blowing Out the Dust: Recent Work Edition

It’s very appropriate that the last proper post on this blog was titled “Designing for Permanence” — a post espousing an approach to web design in which one aims to create an enduring artifact — and so this blog endured: static, fixed and not updated for a couple of months. That’s not exactly the type of permanence I was shooting for.

In an effort to jump-start a couple of topics and provide context for future posts, I thought I’d share some recent work highlights.

Glassbooth

Glassbooth HomeHome page.
The actual questionsQuestions based on issues you chose.
Glassbooth issue-by-issue breakdownThese aren’t my actual results.

This was probably the biggest personal project I worked on in a while. It started as a thought exercise by a couple of buddies of mine on the current state of representative democracy and ended in an interactive tool backed by some of the best data on the current presidential candidates. It’s now a fully-certified 501(c)(3) non-profit. What’s great about a project like this is the autonomy afforded in making design decisions. In this case, I got the opportunity to design everything you see except for the icons and logo.

Because the aim of the project was to create a non-biased source of information for the upcoming election, the challenge was to present it as such. I also wanted to avoid cliched motifs: using red white and blue or the american flag. Colors in general were problematic, as their interpretation is often personal and subjective. Choosing any distinct palette would be tantamount to choosing a side (especially green). Not to mention the information design and interaction problems that needed to be solved.

Searchblog

Searchblog redesignedThis one looks better in person.

Having had a surplus of ideas on blog design, I decided to use them to re-think Searchblog. It was not prompted and I essentially imposed the design on John. Thankfully, he was a good sport about it and after a fun reader census, it’s now live. Speaking of reader feedback on design, this served as a good opportunity to revisit Daniel Burka’s presentation on that very same topic.

Feed Wrangler

Feed Wrangler screenshotMain settings screen where you can create new feeds and manage existing ones

Feed Wrangler is a WordPress plugin that came out of my work at FM. Feeds are an extremely important part of any publishing venture. Whether it’s to facilitate a syndication partnership or plug in to some third-party service. The requirements, however, can be quite diverse and unpredictable. For example, the feed widgets generated by FeedBurner are problematic if your blog is available on the Amazon Kindle.

To address the problem, Movable Type has the custom-feed-generation thing covered pretty well. On the other hand, there is a fair amount of work required to do the same if you are a WordPress publisher — this plugin aims to solve that, by making custom feed creation a more manageable process.

May 27 2008

Whooosshh

TumbleweedFigure 1. Tumbleweed.
Apr 23 2008

Designing for Permanence

Design history wouldn’t be able to teach us much if it weren’t for the enduring artifacts that compose it. The ability of a cultural artifact to persist and inform our collective consciousness defines a desirable quality of design: permanence.

Tangible artifacts have always suffered from preciousness – a poster or a book may succumb to a fire, garbage bin, or some other determinant of entropy. There is a very finite amount of books that are older than 500 years old. And to this, we limit access to them while dedicated professionals turn their pages in temperature-controlled environments.

The information space is young and quickly evolving, often times making it easy to think of published content as disposable. Sites update by the minute and yesterday’s topics are consigned to the category of the past. While we might not think about a news topic days afterwards, we still might stumble upon it years after it was published by means of a search engine or some obscure link.

Similar to natural disasters, technology and business disasters make a “404 – Page Not Found” error a common occurrence. It is easy to dismiss those lost digital bits that compose our work as forever-gone when the switches get flipped to 0. We create, we publish and a couple of years down the line our creations are supplanted by a redesign or a new website altogether. In this context, it’s difficult to think of our work as having relevance beyond a few years and, consequently, makes it more difficult to approach it as such. But it does. It’s fascinating to think that Google, effectively, has a copy of the internet (remember those Google Cache links?), and it’s not the only one (see any other search engine with a significant index). The most impressive and altruistic of web archival efforts, a project like archive.org, makes the notion of online content permanence a very explicit reality.

Just as tangible artifacts, like books, are subject to entropy, so is digital information. And while it’s difficult to imagine what a document looks like 200 years down the line, I have some thoughts on how to achieve that and the implicit benefits those choices entail.

For some reason my vision of 200 years into the future involves a bespectacled, bearded man in a safari outfit, in the desert, dusting off pages of source code belonging to someone by the name of Ephram Zerb. Back in his laboratory, he pieces together the astonishingly semantic markup and uses a tool to translate it into a visual representation. Either way, the content and design is well-preserved and highly intelligible. In that same trip, a cryptic, corrupt binary is found – unbeknownst to the information archaeologist, it’s the work of the illustrious design firm, Pentagram, encoded in Flash 8 format – it goes in the junk pile.

One of my motives for publishing this was to frame web design from a long-term perspective and to shed some unproductive discourse. Search engine optimization rhetoric is the source of that ‘unproductive discourse’, which I don’t think should inform the temperament of a web designer; rather, it should be understood as an inevitable feature of a work that tends to the craft of web design.

The only rule of search engine optimization

I started thinking about design permanence about the time I was trying to find an approach to search engine optimization. I was frustrated by the lack of a unified body of knowledge, the mounds of misinformation published on the web, and paid ‘professionals’ that dispensed tremendously poor advice like stuffing the title attribute with irrelevant keywords. This, by the way, is tantamount to a modern-day doctor recommending you have some soda-pop for your belly-ache.

I was tired of thinking about published content through the narrowing prism of optimization – prose became a collection of keywords while other elements, like an image’s alt attribute, were bent against their physical will. I came to realize that any worthwhile (read effective) advice was simply a reiteration of rules already defined by some standards body or perpetuated by a professional culture. I began to dismiss or re-interpret any advice where optimization was an end in itself, and reframing it from the perspective of permanence.

Interpolation on the features of permanence and how craft is a requisite component

From my non-academic perspective, permanence has two dimensions: physical longevity and cultural longevity. These concepts are closely related and often times go hand-in-hand.

Physical longevity deals with the lifespan of the work – from creation to dust – where technology plays a central role in the preservation. Looking at the process by which quality books and prints are fabricated, the type of ink (non-fading) and type of paper (acid-free) play to our desire to have something persist.

On the web, I believe a standards-aware practice best-approaches physical longevity. I like to think of the digital medium as being defined by a process of translation. Before a web page gets rendered in a browser, the browser must interpret the 0’s and 1’s that compose the images, consider the HTML markup that hugs the text, and than transform those elements by reading through the rules defined with CSS. To do any one of those tasks, there needs to be an agreed-upon key that makes the translation possible. Web standards are that key, and the transparency, ubiquity and historical legacy of those standards help perpetuate countless copies of that key in the form of browsers and other symbiotic technologies (parsers, crawlers, etc.). Compared to the alternative, there’s tremendous cultural collateral and implicit future-proofing when designing with web standards.

Cultural longevity is different, and is largely the heart of this argument. It deals with the artifacts found in textbooks and design annuals. They are works that the design community has found to be important and worthy of recognition. While the rationale can vary greatly, they are usually a product not only of great design, but almost always a result of immaculate craft. To design a beautiful alphabet is one piece of the puzzle, but to transfer that design into digital form, by means of software, with different weights, sizes and proper kerning requires craft.

Craft can be seen as a function of tradition, skill and practice – it’s the baked-in history and best practices of a profession that provides that professional sheen.

Stating the obvious

There’s a striking similarity between what’s considered search engine optimization and good web production (craft). And in just about every case, the best practice always predates and informs the ‘SEO technique’. When Tim Berners-Lee defined best practices for URLs in 1998, he notably approaches the problem with a longitudinal perspective:

It is the the duty of a Webmaster to allocate URIs which you will be able to stand by in 2 years, in 20 years, in 200 years. This needs thought, and organization, and commitment.

Going through his recommendations, you’ll notice that a lot of them mirror modern SEO suggestions.

Take another example: you do not add the alt attribute to an image to increase “keyword density”, you add it because the image might require context for those that cannot see it. Once again, a common recommendation is already described in a documented best-practice. This isn’t news.

My point is that a web designer shouldn’t be burdened by the muddy, low-level(-of-abstraction) recommendations of search engine optimization – a place where I’ve been myself. Instead, a broader, more abstract perspective that focuses on creating a permanent artifact will address the very same problems with much more elegance and clarity.

If you feel some parts of this aren’t clear enough, would like more elaboration or would like to add your own voice to the topic, feel free to partake in the editorial process by adding your comment.

Oct 20 2007

Posts of the Original variety

Newer
Older