Cookies help us display personalized product recommendations and ensure you have great shopping experience.

By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    data analytics and truck accident claims
    How Data Analytics Reduces Truck Accidents and Speeds Up Claims
    7 Min Read
    predictive analytics for interior designers
    Interior Designers Boost Profits with Predictive Analytics
    8 Min Read
    image fx (67)
    Improving LinkedIn Ad Strategies with Data Analytics
    9 Min Read
    big data and remote work
    Data Helps Speech-Language Pathologists Deliver Better Results
    6 Min Read
    data driven insights
    How Data-Driven Insights Are Addressing Gaps in Patient Communication and Equity
    8 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: New Tools, Same Problems on IT Projects
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Uncategorized > New Tools, Same Problems on IT Projects
Uncategorized

New Tools, Same Problems on IT Projects

PhilSimon
PhilSimon
5 Min Read
SHARE

Collaborative tools such as Microsoft’s SharePoint hold enormous promise on all sorts of IT projects. “Wikis” and their ilk contain amazing features. Going back a few years to the pre-SharePoint era, I can remember using different intranet sites to do the following:

  • facilitate document sharing and updating
  • improve intra-team communication
  • rid the organization of its dependency on email

Collectively, these collaborative tools can improve project management. Through their successful and consistent usage, the organization can improve its chances of achieving its goal: a smoothly run project.

Sounds good in theory, right? Unfortunately, many times the promise of these tools is far greater than their actual benefits. (This is also true of Enterprise 2.0 in general.)

But why is this the case? I’d offer two simple and related reasons:

  • Collaborative tools are only as good as the people who use them
  • Old habits (read: email) die hard

Email may be the Internet’s first killer app, as project-related messages convey important information about tasks, dates, and news. From a collaborative standpoint, there are a few major problems with email:

  • Emails can easily make the …

Collaborative tools such as Microsoft’s SharePoint hold enormous promise on all sorts of IT projects. “Wikis” and their ilk contain amazing features. Going back a few years to the pre-SharePoint era, I can remember using different intranet sites to do the following:

  • facilitate document sharing and updating
  • improve intra-team communication
  • rid the organization of its dependency on email

Collectively, these collaborative tools can improve project management. Through their successful and consistent usage, the organization can improve its chances of achieving its goal: a smoothly run project.

Sounds good in theory, right? Unfortunately, many times the promise of these tools is far greater than their actual benefits. (This is also true of Enterprise 2.0 in general.)

But why is this the case? I’d offer two simple and related reasons:

  • Collaborative tools are only as good as the people who use them
  • Old habits (read: email) die hard

Email may be the Internet’s first killer app, as project-related messages convey important information about tasks, dates, and news. From a collaborative standpoint, there are a few major problems with email:

  • Emails can easily make the content on a wiki dated or even irrelevant
  • Emails tend to be much less easier to find and search than content posted on wikis
  • People constantly forget to copy others on email
  • Most emails are downloaded to individual PCs, making them suboptimal for future reference

To be certain, wikis will never obviate the need for emails. What’s more, not every piece of information on a project should be posted on a wiki.“Hey Vince, didn’t you think that Nikki sounded like an idiot during the meeting today?” However, emails should constantly reference collaborative sites to reinforce the notion that the wiki governs the project, not 100 disparate emails.

Solutions

Organizations should take the following steps to ensure the optimal use of collaborative tools:

Start at the top

The PM or project leader sets the tone for the entire group. It’s hard to expect individual end-users to move from emails to wikis when the PM doesn’t lead by example. This type of leadership also includes making gentle suggestions to those who rely on email or—perish the thought—don’t update their documents anywhere.

Hold team members accountable for updates on wikis

Individual end-users must use collaborative tools consistently throughout the project. This goes beyond updating their own availability or progress. If the organization uses SharePoint, for example, then it needs to be the epicenter of the project. Unless the material is confidential or politically sensitive, all project plans, test scripts, requirements, and training materials need to go on the wiki. Period.

Cross-reference wikis in emails

Today, many people now routinely read email via BlackBerrys, iPhones, and other mobile devices. This isn’t changing anytime soon. To that extent, expecting everyone to abandon email simply is folly. However, emails should contain URLs to the same content on wikis. Doing so will help minimize conflicting or missing information.

Share This Article
Facebook Pinterest LinkedIn
Share
ByPhilSimon
Phil Simon is a recognized technology authority. He is the award-winning author of eight management books, most recentlyAnalytics: The Agile Way. He <consults organizations on matters related to communications, strategy, data, and technology. His contributions have been featured on The Harvard Business Review, CNN, The New York Times, Fox News, and many other sites. In the fall of 2016, he joined the faculty at Arizona State University’s W. P. Carey School of Business.

Follow us on Facebook

Latest News

data analytics and truck accident claims
How Data Analytics Reduces Truck Accidents and Speeds Up Claims
Analytics Big Data Exclusive
predictive analytics for interior designers
Interior Designers Boost Profits with Predictive Analytics
Analytics Exclusive Predictive Analytics
big data and cybercrime
Stopping Lateral Movement in a Data-Heavy, Edge-First World
Big Data Exclusive
AI and data mining
What the Rise of AI Web Scrapers Means for Data Teams
Artificial Intelligence Big Data Exclusive

Stay Connected

1.2kFollowersLike
33.7kFollowersFollow
222FollowersPin

You Might also Like

Ranked Set Retrieval

6 Min Read

Building a SAS Stored Process Log

10 Min Read

Top Six Traits of a Data Champion

6 Min Read

7 Signs You’re Dealing with Complex Data

10 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

AI and chatbots
Chatbots and SEO: How Can Chatbots Improve Your SEO Ranking?
Artificial Intelligence Chatbots Exclusive
AI chatbots
AI Chatbots Can Help Retailers Convert Live Broadcast Viewers into Sales!
Chatbots

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-25 SmartData Collective. All Rights Reserved.
Go to mobile version
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?