setting goals for a company site
| Many web sites are developed within the context of a company with employees, projects, and products that have a history both with customers and with each other. Goal-setting is a challenge in this environment, because you're weighing what's best not only for the web site and the company, but also for the individuals involved in the project. It's a political process as much as a strategic one. For have no doubt: Web sites are political. The site acts as a company's public face, and everyone wants their work to appear prominently on it. But goal-setting can help. By encouraging co-workers to agree on objective goals rather than specific, subjective solutions (about where buttons should be placed or what the sections should be called) you help them see a common purpose and force them to ignore irrelevant conflicts. The goals you set collectively will help steer your site in the right direction. But the purpose behind goal-setting is not only to chart a clear course, but also to get others on board. This buy-in at the beginning of the process gives you the information you need to be successful. 7 steps to setting goals:
A good way to get started on goals is to touch base with each of the key stakeholders. Sit down with them one-on-one, and discuss what they (or their departments) need the site to deliver. It's best to focus this conversation on what the site should accomplish, rather than how it should look or what it should do.
The web site acts as a company's public face. Everyone wants their work to appear prominently on it. In these interviews, you're playing amateur psychologist, journalist, and diplomat. Your goal is not only to take in what stakeholders are saying, but to understand their motivations. Are they fearful for their jobs? Resentful over past wrongs? Competitive with another individual or department? Once you understand their real concerns, you can begin to address them. In addition to the stakeholders, it's important to talk to the CEO or someone of high status. Nearly every web developer has a horror story about a CEO who pulled the plug on a web site just before launch, because it didn't line up with corporate goals, or because he didn't like surprises. The best way to avoid this is to solicit executive opinions early on. After collecting all these opinions, the producer should write a consolidated list of goals that best represent the company's interests. These goals should be approved by the stakeholders at a meeting attended by all: This ensures that everyone important to the process gets on board behind the objectives and shares an understanding of success. It's important to emphasize that this meeting is the moment for discussion and dissent: Speak now, cranky ones, or forever hold your peace! After the development process begins in force, you can't modify the goals without jeopardizing the launch date. Persuasive powers failing you? Rethink your approach: how to get everyone on board, p. 341.
|
EAN: 2147483647
Pages: 195