Websites suck. 

Plain and simple. Each and every website I look at is clunky and confusing, with the exception of Facebook, Twitter and Google. 

High claims from a reporter, is what you're thinking. You're thinking "who does she think she is? Does she know HTML? What does she know about design?" 

Before you ask these questions, consider this -- because I'm a journalist (writers are different, but that's a topic for a completely different sort of blog), my world of content production is closely intertwined with yours, that is, with the world of software development. I rely on applications and websites to produce content, find sources and - on my days off - find those perfect pair of pumps, on sale of course. 

I'm the ultimate end-user, I not only need to be able to navigate a Web page, I need to manipulate it each and every day. 

Prior to my job with SD Times, I worked with a small company you may have heard of -- AOL. I was one of the original Local Editors for the content giant, Patch.com. I worked with a CMS specially designed for reporters and Patch, AND still had problems. 

After working at SD Times for the past seven months, I realize it's not that software developers on these projects lack talent, it's that they lack communication with the end-users, and not just communication, but DIRECT communication and collaboration. 

Now you're thinking "she's totally lost her mind," but hear me out. 

Imagine a world where an end-user (in this case me, a reporter) could talk to the software developer (in this case SD Times' IT manager/computer guru) who worked on her website each and every day. That she could send him (or her) examples of what exactly she wanted to design; what exactly would work for the type of stories she wants to create? That, my friends, is development utopia. Or is it? 

Here at SD Times, I'm able to use my limited HTML knowledge (I'm excited when I can do a non-breaking space, so clearly it's not THAT advanced) and my knowledge of custom-designed CMS systems to describe exactly what I want down to the button, sticky box and widget. And my designer is able to create it based on my ability to communicate with him in a language he understands. 

I never realized how VITALLY important this sort of collaboration is and, until I did my Managing Requirements feature story (which you can see in the July issue of SD Times), I never realized how often this isn't done. 

What's my advice? TALK to your end-users. Talk on the phone, through email and wikis, online, via carrier pigeon -- you get the idea. And end-users - from reporters to accountants to HR professionals - talk to your development team. Stop saying "we want an application to do X." Figure out what you want (is it an application, a website, perhaps a Tumblr feed or plugin) and then figure out how to convey what you want to developers, in terms THEY can understand. 

This is a whole new world and while it may not be brave, it is most definitely powered by software, so it's up to all of us to make sure requirements are discussed in order to make sure they are delivered. 

Have thoughts on this? Share them with me in the comments section.