connecting*the*dots

In my long-term quest to become more localized with my business ventures, I recently partnered up with John Ford at Aldenta to design a web strategy for one of his clients: Louis’ Healthy Breads.

Louis is a local entrepreneur who pours his heart and soul into his amazing line of health food products. Prior to our initial meeting, John mentioned that he was passionate about his product, and after meeting him, I have to say that he’s as authentic as they come.

Okay, a gear clicked.

After speaking with his daughter, Ann (his soon-to-be-hired editor and marketing person) and hearing about his son, Grant (the Chief Chef of the operation), my original plan began to grow some serious legs.

Yep, we’re going to create a Louis’ Healthy Breads blog.

Logistically speaking, Louis’ hip to email, but he’s not technically savvy and he’s always on the go — visiting stores across the east coast and beyond, trying to land retail deals for his product. The best thing about his day to day is that he’s constantly meeting interesting people who are always sharing personal stories, ranging from pure testimonials to insight into their health issues and fitness goals. Hey, he’s a salesman from the heart; a great candidate for simple posting, but not necessarily the archival aspects of tagging or the community aspects of linking out.

Louis is already doing the conversational work of a blog, but his “interface” doesn’t have built-in permalinks, comments and trackbacks (heh). Our job is to figure out the best way to corral his conversational personality and guide it into a realm with a searchable past and a participatory interface.

As a next step, I sat down with Ann last week to discuss a blogging strategy for the company. We both realized that Louis’ strong suit is writing, so we’re going to play to his strengths and limit his role as much as possible, keeping his publishing responsibilities focused by sending emails to Ann for editing and posting. We applied the same thinking to Grant, who will be able to provide a “behind the scenes” look into the baking process, leads on new ingredients, etc.

By heading down this road, Ann has implicitly agreed to become the blogger, editor, curator extraordinaire. Essentially, she’ll be editing posts from Louis and Grant, applying structured tags to the posts, linking out to related conversations across the blogosphere, participating in related conversations, managing comment threads and tracking related information in her RSS aggregator.

The idea that I’m trying to impart is that we don’t need to “segment” people into groups or “target” them like they’re deer in order to “push” product. We already know that the majority of people who are drawn to Louis’ Healthy Breads share certain interests, desires; call them attributes if you will. Health enthusiasts gravitate toward the product, yet their reasons for doing so could be as diverse as a fear of heart disease and diabetes to wanting nutritious fuel just prior to a marathon.

Ann is going to make it her personal mission to explore these existing communities, enter the fray of their current conversations and build relationship with actual people (not segments). Once she finds these resources, she’s going to start tracking them for interesting conversational nuggets to point to and contextualize from the LHB blog. Then, and only then, will she (and LHB) come off as credible participants in the communities they wish to serve.

Checkout the above workflow (228k | .pdf) that I put together to help get them off the ground. Can you think of anything that I might have overlooked?

Is that Jamo under there?

Media Matters for America
Do Washington Post editorial writers read their own newspaper?

Last week, The Washington Post editorial page put forth numerous falsehoods in defense of President Bush’s reported authorization of I. Lewis “Scooter” Libby’s disclosure of classified information. The funny thing is, the Post’s own reporters had already debunked many of these falsehoods, including in the very same edition of the paper in which the editorial appeared.

That’s right: the Post’s editorial included claims that are directly contradicted by previous Post reporting. The Washington Post editorial board is entitled to its own opinions –- but not its own facts.

Help us encourage The Washington Post editorial board to do a better job. Use the contact information below and politely urge it to do more comprehensive research on the issues it writes about.

Contact information

The Washington Post
1150 15th St. NW
Washington, DC 20071
202-334-6000 or 800-627-1150

Email Post Editorial Page Editor Fred Hiatt

Email Post Ombudsman Deborah Howell

Blogger gal vs. Newspaper guy!

Well, not quite, but it makes a great lede, eh?

Sue, Lex and I met over lunch yesterday to discuss potential strategies for evolving the News & Record’s citizen journalism efforts. And no, we didn’t have a stare off.

Man… Lex is in a tough position; he’s completely open to forward-thinking ideas (I mean, his title is Citizen Journalism Coordinator), but he also seems to be up against a bottom line business that’s very adverse to risk. Apparently, changing the approach to meeting a historically profitable bottom line is a tough sell, even within an industry that’s on shaky ground.

It’s amazing how palpable sand can become to the heads of industry during innovative times.

That’s not to say that the N&R hasn’t been progressive with their citizen journalism efforts to date — they have — but Lex knows that in just a few years the N&R (both print and online) will have to directly compete with new forms of dynamic, community-based, participatory, online news applications (e.g. Newsvine), which will be free of legacy organizational overhead and be able to react with agility.

And you can’t forget those pesky bloggers.

The N&R needs to step up their game.

So we chatted. And ate. And chatted some more. And by the time our conversation came to a close, we had a number of interesting ideas on the table:

• Personal Relationships - Lex is looking to develop relationships with members of the Greensboro community, offering them the opportunity to use N&R resources (legal, photography, journalist feedback, etc.) to craft substantive citizen journalism. To me, this approach perfectly fits the future of print newspapers, as time-based news is dead on paper. They’ll have to compete as daily magazines (more depth, less coverage).

• Real-time Blogging Input - I suggested promoting a tagging schema that matched the classification structure of both the paper and the site:

  For example, identify and promote a unique set of “greensboro[xxxx]” tags, for anyone to use on blog posts, flickr images, etc. when generating Greensboro specific news, events, opinions, etc.

  Internally, the N&R editorial staff would then set up RSS aggregators with subscriptions of each tag search result.

  The real-time input of potential stories and assets would increase exponentially, while the N&R would continue to have editorial control, as the aggregator would serve as the queue into the publishing process

• Representation Across The Community - Sue focused on the concept of encouraging participation along the lines of community diversity (her connections with Uplifter is right along the lines of my focus with The People, Yes!). We talked about ideas ranging from developing blogging 101 material to share with a non-computer literate demographic to grass roots representation within sub-communities (e.g. school board meetings) to encourage live-blogging with the unique tag identifiers

An interesting start, but there’s still one major component that we’re skirting: Revenue incentives.

Lex made it clear that creating a participatory revenue model doesn’t fall under his charge, but the N&R is open to ideas. My perspective is that without incentive, participation will be lighter, with less quality and dedication. Any revenue generated out of these relationships should be viewed as found money, so share and share alike:

• To tap into the wisdom of the blogosphere by republishing the original post or an edited version, a buisness needs to develop a revenue model that fairly represents such a relationship.
• To partner with individuals from the community to generate community-based journalism, a business needs to develop a revenue model to encourage such a partnership.

It comes down to this: Pony up or we, the citizens, will simply get together and form collaborative blogs, creating relevant identities, gain a better footprint in Google over a 3 month period of time and, eventually, sign up with BlogAds to support our own voice.

That’s not a threat. ;-) I’m looking forward to our next conversation, folks.

UPDATE: Six months after the fact, in the NORG session at ConvergeSouth, Ed Cone backs up my philosophy regarding partnering with local bloggers/writers in a revenue share program.

Building a successful UX team — the right mix of roles, responsibilities, method, etc. — isn’t an easy task. It really does depend on the DNA of the organization (size, politics, legacy issues, etc.) and the type of domain (application, information centric site, desktop software, etc.).

Here’s a visual outline that I tried to follow at Ameritrade — an extremely secure, authenticated trading platform, with unique opportunities for collaborative filtering, interface customization, sussinct client messaging and knowledge management (both on the unauthenticated and authenticated areas of the site).

If I had to do it all over again, here are the top three things I would’ve done differently:

Reduced the emphasis on methodology
Due to the placement of the team in the org, the legacy of design within the domain and the lack of designer input in modeling requirement documents, I pushed to implement a flexible, yet smart, IxD Goal-Directed methodology. I probably would’ve still sought to implement a similar methodology, but I wouldn’t have pushed so hard to get it.

Introduced blogging as a means for knowledge sharing
KM is such a terrible term. In essence, an outward facing blog with a solid search engine and a rich tag approach could’ve served as both a conversation point for speaking with clients and providing answers to non-client account related questions. Internally, we could’ve dropped our stiff, architected KM tool with central controls and replaced it with internal blogs for every employee.

Focused on research, behavior, information contextuality, design and presentation
Editorial is *such* a complience issue within the financial industry, collaboration with designers on interfaces was beyond difficult to manage. I probably would’ve traded that card for the client-side team, where the rubber of behavior and design explicitly hits the road of server-side code.

Live and learn ;-)