insight

Real-Time Search: The New Reality

by Justin Clemens January 26, 2010

You may have noticed something new the last time you googled. Perhaps you were looking for a review of this weekend’s blockbuster, the score of yesterday’s playoff game or  when that new restaurant down the street starts serving dinner, and there it was … a real-time search result.

In case you still don’t know what I’m talking about, here’s a screen shot:


Whether it’s breaking news, an eyewitness tweet, a new blog post or a fresh status update, real-time search is every search engine’s hope to make all of their results both relevant and instant. Partnering with the big names in social media -- Twitter, Facebook, MySpace, et al — Google, Bing and the rest of the search giants hope to bring an always-changing, always-popular, always-relevant aspect to their results pages. But what does that mean if you want your company or brand to be included in the results?

Social networks are more important than ever.
If you’re not currently on social networks, you’re missing one of the best ways to have conversations with your customers. On top of that, now you’re also missing opportunities to connect with potential customers who look for you on popular search engines. The social networks presented in real-time search results have been given greater importance and staying power, and this should be reflected in your marketing plan.

SEO everywhere. People/companies who use social networking outlets should now become more concerned about their word choice. Having the right phrase in your last tweet or Facebook status could launch you directly onto the first page of Google. Not to mention, having posts about topics that aren’t directly related to your field will now help you reach an entirely new audience.

Stay relevant. Keeping current and relevant with your messages and messaging will be crucial. According to Google Fellow Amit Singhal, the characteristics that Google looks for in relevant real-time searches are author quality, probability of relevance and query hotness. Providing frequent, quality posts to all of your social networking outlets allows you to hit all three of these points.

Real-time search is just getting its sea legs, and users are just starting to understand what it is and how to use it. But if you position your company correctly and learn to use real-time search in your favor, you could be on the ground floor of the next boom in search.

A Designer's Perspective on Collaboration

by Phil Coffman January 22, 2010

Last week, Developer Josh Kemmerling wrote about his perspective on collaborating with designers. As Josh mentioned, he and I recently collaborated on the AMD Collateral Generator project and integrated a solution he proposed early into the project. Hearing each other's expertise at the conceptual phase of the project no doubt contributed to a stronger product for the client. I'm thankful that Josh felt the freedom to speak up and offer his point of view on the project.

It's a shame that in our industry designers and developers are timid to freely express ideas to each other's camps. I believe this timidity results from the overall flow of a project, which generally begins with a discovery phase, then proceeds to brainstorming, then to creative, development, testing and finally deployment. Because the creative portion occurs before the development stage, developers sometimes are not as involved in the project until comps are completed and ready for production. This usually means that the project (up until that point) has been seen by account service, creatives and possibly one developer who may have been involved at the discovery phase of the project, which hardly ever delves into the nuts and bolts of execution methods.



What I believe should occur, whether dictated by a company’s processes or not, is full-on, two-way communication between the creative(s) and developer(s) assigned to that project during the brainstorming and creative phases. While I believe strongly that a creative needs to have a firm understanding of web technologies, they must be willing to hear the expertise of their development team and facilitate in creating an environment of freely expressing ideas. 



Developers and creatives must continue to hone their skill-sets and work on building trust in each other's expertise. Beyond this, I believe it's the responsibility of both parties to have their finger on the pulse of the latest web technologies and trends. This means there might be times when a creative will have learned of a new technology, process or technique that the developer hasn't learned yet — and the creative should feel free to pass on that knowledge. In such a situation, it's imperative for the developer to be open to hearing this from a creative and not feel like the designer is stepping onto their own turf (and vice versa). 



Communication is vital and one of the most important ingredients to the success of any project, especially between a developer and a designer. A free exchange of ideas must take place at the onset of a project. We can't afford to work in silos. Our clients are counting on the best we can produce and that comes from collaboration and freedom of expression.

A Developer's Perspective on Collaboration

by Josh Kemmerling January 15, 2010

Everyone knows that developers aren’t as creative as designers. Not even close. Which is why developers find it hard to work with designers … we’re afraid of having our ideas shot down. Instead of volunteering our ideas, we wait until the designer asks for a suggestion. (Actually, from what I‘ve learned, designers like to have our input. Who knew?) How do we break this cycle of fear? How do we get to a point where we can give designers suggestions that we feel are useful? If designers don’t know what developers are capable of, many potential features could be left out of a project.

The hard part about giving designers suggestions or ideas is trying to give a technical suggestion without making it a design suggestion. This can be hard to do because we don’t always know what the designer is looking for. As developers, we should strive to make suggestions that enhance the way a site functions, without directly impacting the site’s aesthetics.

I recently collaborated with a designer on a microsite, where I recognized an opportunity to streamline the user experience. I wasn’t trying to change the user flow or the way the site looked, I was trying to make the user experience faster. While working with Springbox Art Director Phil Coffman on the AMD Collateral Generator project, I offered suggestions on different technologies that would streamline performance. My idea was to make the site AJAX-based. This would keep the whole page from constantly refreshing, making the user experience a little faster. Much faster, actually. Without taking a chance and sharing my idea, I doubt Phil would have known that we could successfully use that technology.

So, as developers, we have to make sure we don’t cross the line into a designer’s territory. We want to give technical suggestions that aren’t design suggestions but rather complement the overall experience.

This post is first in a two-part series. Look for the second stanza, the Designer's perspective, next week. 

Green-Collar Locavore Earmarks Funds for Staycation 2.0 (Or New Vocabulary from 2009)

by Christi Evans January 13, 2010

January seems like a fine month for some lexicography fun, with all the top-this-and-that-of-2009 lists sprouting out there. And yes there is such a thing as lexicography fun … if, say, you belong to the Word Nerd club at Springbox. (I don’t, but my friend does.)

Let’s start with some neologisms (new words) of 2009 from Merriam-Webster, where  I learned a delicious new word (locavore) and got a serious laugh (sock puppet). Really? Ah, as it turns out, “sock puppet” hadn’t previously failed to join the ranks of official words, it merely earned a secondary definition as a “deceptive online identity.” Not quite as charming as definition #1.  

So then I tried to figure out a few of the new definitions before I clicked on them. Here’s how it went.

Zip line: “Hey Milton why don’t you ‘zip line’ your TPS report down to auditing for me.” As in, get it there quick. Nope, it actually means zip line.

Memory foam: “Um, I had a late night Lumbergh … Forgot … TPS … report. [pointing at head] ‘Memory foam.’” As in, hangover brain. Nope, it actually means memory foam.

Okay, that was fun but fruitless. Moving on …

Merriam-Webster also has a Word of the Year 2009 list, which is based on searches and appears to be largely driven by politics, with the likes of such words as inaugurate, rogue and philanderer.

The Global Language Monitor has a few nifty lists: Top Words, Phrases and Names of 2009, with Twitter, King of Pop and Barack Obama as the chart toppers, respectively. Twitter was such the universal list-topping sweetheart of 2009, that its verb form “tweet” has landed on Lake Superior State University’s 35th annual List of Words Banished from the Queen's English (for misuse, overuse and general uselessness).

Yes, the year-end lists are infinite. But if you didn’t see the word, expression or definition that you hoped to see in one of these examples, submit it to Merriam-Webster’s open dictionary! Or for some real fun just browse the open dictionary.  While you’re at it, see if you can guess the definition of polates, aughties or sneeve.

This feels like an appropriate time to point out that neologism has two definitions.

1. a new word, usage, or expression

2. a meaningless word coined by a psychotic

It’s true.

Crowdsourcing Customer Support

by Colin Walsh January 7, 2010

These days there’s an app for absolutely everything (if you haven’t already heard). AT&T’s free Mark the Spot app for the iPhone brings the country’s app obsession to a new arena: Customer Support.

Customers use Mark the Spot to report dead zones and locations of poor audio quality to AT&T. So when you’re on your phone and the call drops (and you embarrassingly find yourself talking to, well, yourself), just pull up the app and report it.

The AT&T application is an interesting take on customer support crowdsourcing and proactive PR. For marketers, there are plenty of reasons to crowdsource for customer support information.

Show your attentiveness: You know the old saying that the customer is always right? It still holds up today. When you allow customers to participate, you affirm your commitment to them and strengthen your brand’s relationship with the public.  

Increase transparency: Audiences are all-too-familiar with the bravado and over-promises of companies’ marketing claims. And odds are they’ve spent several hours of their lives on hold with customer service. Apps such as Mark the Spot not only let users control the pace of the customer support experience — they show that while your company isn’t perfect, you’re doing your best to improve the customer experience.

Foster dialogue: Online, conversation is the name of the game. Applications can provide customers with new, easy-to-use forums to share their thoughts and opinions with companies. Candid customer feedback is an invaluable asset for companies as they evaluate their product lines and develop new offerings.

Slash costs:
An obvious one, but still important. Compared to the costs of staffing a call center, applications are a cost-effective way to gather and document customer feedback.

In a do-it-yourself era, customers are willing and able to help — especially when their efforts will result in improved products and services. Marketers should take note. 

 

The way we see it, people who share insight with each other innovate, grow and succeed together.

Subscribe

Log in

The opinions contained in these pages do not necessarily reflect those of Springbox or its parent company, DG FastChannel.