Articles pour le mot-clé ‘operation’


I’m a business-oriented guy. I see returns in dollars. When I get final feedback from a client about a web site project I want to hear “It’s working.”

In the development of a web site, participative democracy is not just something to consider – it’s a key factor for success. In my experience, more input is better and input can come from multiple sources. While marketing and technical staff provide valuable information, the gemstones are often uncovered after talking to non-marketing stakeholders.

There are no bad ideas

Ignoring ideas from different departments and expertise’s can be fatal to a site’s ultimate success.  All shareholders have frustrations, fears and ideas to offer.

As a proven methodology at w.illi.am, participatory democracy proves itself time and time again. We were recently consulting France Telecom on a web site revamp, and it was through a candid conversation with a call center employee that we learned the help desk used “scenarios” to reply to technical questions from clients.

Something we never considered in initial meetings, we integrated the scenarios in the technical support section of the web site. The bottom-line results were immediate, alleviating the load of help desk calls, and giving web-savvy clients the option to help themselves. Had we worked in a web strategy “bubble” we never would have put the scenarios online.

Why involve multiple stakeholders?

  • It allows the web site strategy team to collect a lot of data and opinions, gaining insight on the true workings of a company, and the industry. Just when you think you know exactly what is needed, new information adds depth to the shortcomings of a current site plan, helping everyone gain a deeper understanding of what the site can –and should– accomplish.
  • Giving everyone a voice means better buy-in on the final product. It allows people to voice their concerns and be part of the web revamp process, ensuring the site will be a company-wide communications channel and a tool for smoothing operational processes.

Three types of consultation:

Meetings

Meetings involving multiple stakeholders are a good starting point for a global idea of what is needed. Key people at an initial meeting would be:

  • Marketing staff
  • Product Managers
  • Someone from each division (verticals ie B2B, B2C, etc.)
  • HR people (if needed)
  • Customer care managers

Face-to-face

The next line of consultations should be face-to-face interviews with internal users and stakeholders. Sometimes, in a large meeting, people are afraid to say things or –conversely- are “louder” than others lobbying for their department. One-on-one face time helps put things in perspective and offers a safe way to express ideas.

Focus Groups

Focused meetings with the customer care center or with specific departments or verticals helps define the scope of what is needed, what directions the company is moving in, and where the web site needs to evolve.

Some people may think too many cooks spoil the broth – but we’ve learned otherwise. We’ve revamped web sites for AT&T, Astral, Cogeco, Cyberpresse, Workopolis, Duproprio.com and thousands of others. By digging deeper to find information about the company as a whole, we are able to propose web solutions that are in line with business objectives, users’ expectations and a company’s reality.

Participatory democracy is part of a proven methodology in our consultation process – and our clients are telling us our process gets results. They’re telling us “It’s working.”

  • Twitter
  • Facebook

Ask web developers what they hate most about web technologies, chances are they will say javascript, and for some parts, they are right to do so. But to understand why Javascript is so much hated we need to go back in time. In the early years of Netscape, in 1995.

In the nineties, Netscape was flourishing with between 50% and 80% of the browsers’ market and was in a intense combat with Internet Explorer. A guy at Netscape, named Brendan Eich, was given a difficult task of creating a language to make Netscape interacting more dynamically with websites. And of course they wanted this language the day before they asked it . In the time Brendan had, he did the most he could, and created a versatile language that even script kids could pick up, Javascript, he also created the DOM (Document Object Model) on top of Javascript. Now the difference between Javascript and the DOM is simple. Javascript is the basic language you use to make sentence. But the DOM is what is understanding this sentence and makes it interact with the document the way you asked it.

Microsoft was not going to let that happen

Microsoft was certainly not going to let Netscape have « Javascript » and not them, they decided to reverse engineer and implement it in Internet Explorer. Now problems began. They, very unfortunately, did not do a very good job at this implementation. Which means that for doing one simple operation on Netscape and Internet explorer, you had to code 2 implementation for both of them, because the DOM was not understanding the same sentence for both. In fact javascript, the programming language is mostly fine, the biggest problem is the DOM API, some words means nothing to IE and some other means nothing to Firefox. This is what drives web developers crazy. You have to write code specifically to some browsers because they do not follow standards, you have no choice, Internet Explorer represent 67% of your user base, you have to do an implementation for them.

javascript Javascript, the most misunderstood coding language

You need to understand that this happened in 1995. The web did not had the same needs than today. Now web applications are vastly more complex. Some people had to step up and create cross browser API’s to deal with the DOM, and they did. Which means now you write one line, and some API dispatch the good implementation to each browser. This has make the life of web developers much easier.

There is currently 3 major « all round » Javascript libraries, jQuery, Mootools and Prototype

At w.illi.am, we decided to use the jQuery framework, which is now endorsed by a lot of major players, like Microsoft. Not only this is the most use Javascript framework in the world, this is the one we found the most powerful. Writing Javascript with jQuery enabled us to create more powerful web site than ever before and this tool is one of many that make us confident that we are ready for the future of the web.

  • Twitter
  • Facebook