Project Smart ~ Exploring trends and developments in project management today

Calendar icon
Adobe PDF icon

Considerations Before Soliciting Input for Your Content Management Project

~ By Angela Baca

Close up of a browser address bar

When you manage a new project to streamline an organisation's website or to develop a new website, you must gather input from many people inside the organisation.

In "Content Management Bible," Bob Boiko has authored a section on the requirements process. His process concerns finding out what site users expect from the site improvement or the new website you will develop.

First, think about your direction from the person who hired you to perform this project. Are you supposed to brainstorm and create an innovative new web product for the organisation based on your outsider's perspective? Is your assignment to get feedback from employees and let that input guide your project? Management direction determines the approach you take for collecting input from inside the organisation.

Boiko also suggests maintaining a list of contacts that will provide information about the organisation and its needs. He recommends talking personally with contacts and asking questions like: which questions should be covered, how much turnaround time is needed, and who should be contacted.

Boiko describes the spreadsheet as an easy way of tracking responses to questions about user requirements for the project, including who said what and which answers were not consistent among respondents.

Does this all sound very complicated? It can be. Although a spreadsheet is useful for organising information, you have to keep everything straight in your head. Here are questions to reflect upon before meeting with your contacts for the project:

  1. What is the objective of this project?
  2. How much leeway have I been given to speak with whoever I need to inside the organisation?
  3. What is my deadline?
  4. How much am I supposed to worry about resolving conflicting responses from organisational employees about the requirements for the project?
  5. How often am I supposed to report my progress to the appropriate manager inside the organisation?
  6. Which requirements questions do I think should be asked of respondents?

These questions force you to think critically about the organisation, your role in the project, how you are going to accomplish the project, and how to establish a timeline that meets your directive. If you can draw a flowchart that describes the process you will use to gather input, you will be able to use a strategy similar to Boiko's method for organising all the responses you get to your requirements questions.

The bottom line is that the more you can organise your own thinking, the more organised you will portray yourself to key players in this project. Strive to maintain a professional image and reassure stakeholders that you have this big project under control. Don't jump blindly into the project with out ample pre-planning.


Advertisement


Comments

Be the first to comment on this article.

Add a comment



(never displayed)



 
2000
What is the month after April?
Notify me of new comments via email.
Remember my form inputs on this computer.

Seven Key Principles of Project Management

Hand holding a key with success written on the fob

If you're looking for guidance to help you manage your project with added confidence, then this article will help you.

The 8-Step Guide to Creating a Quality Project Schedule

Businessman with a Gantt chart

This article looks at a simple, practical approach to creating project schedules. After reading this article, you will have a sound approach to creating schedules that you can use for future projects.

Belbin and Successful Project Teams

Business team brainstorming using coloured labels on an office table

Creating successful project teams is a daunting task for project leaders. A good method for matching people to roles is the Belbin Team Inventory Method (BTIM).

Learning from Project Failures

Success and failure directional signs

Some of the most important lessons we learn come from failures. Kenneth Darter explains a simple four step process to make sure the same failures aren't repeated.

PROJECT SMART is the project management resource that helps managers at all levels improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With weekly exclusive updates, we keep you in touch with the latest project management thinking.

WE ARE CONNECTED ~ Follow us on social media to get regular updates and opinion on what's happening in the world of project management.


Latest Comments

Ashwini Pendharkar commented on…
10 Golden Rules of Project Risk Management
- Tue 20 June 1:32pm

Tery commented on…
A Brief History of SMART Goals
- Mon 19 June 10:10pm

Tammy Marin commented on…
Better Coaching Using the GROW Model
- Thu 15 June 10:37pm

Latest tweets

General Project Management • Re: Web based open source calendar recommendaton required https://t.co/D20GkodlzD #projectsmart #pmot about 12 hours ago

General Project Management • What degree should I choose to further my career? https://t.co/qGfgK50xLI #projectsmart #pmot about 12 hours ago

General Project Management • Re: Manage Your Projects in Just 60 Minutes a Day https://t.co/Bwo6NtZF3z #projectsmart #pmot about 3 days ago