site structure one or many

12
Site Structure One or Many

Upload: steve-brewer

Post on 04-Jul-2015

167 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Site structure   one or many

Site StructureOne or Many

Page 2: Site structure   one or many

One-or-many

“Should we create a separate collaborative space for each project team, or have everyone collaborate in a single, shared space”?

I call this the “one-or-many” question. It comes up all the time.

There’s no right or wrong answer. Both approaches have pros and cons, but there are very clear criteria for when you should take which approach.

Page 3: Site structure   one or many

The case for many

Good reasons to have multiple workspaces (e.g., one for each project):

• There’s confidential material that’s not shareable within the organization

• Employees are intensely risk-averse and won’t participate honestly if their contributions are broadly accessible outside the immediate team

• People work in disparate areas, and will view updates from other areas as spam

Page 4: Site structure   one or many

The case for one or few

Good reasons to have one workspace:

• You want to support and encourage cross-silo collaboration and coordination

• You want colleagues to have greater visibility into what’s happening in other parts of the organization

• You have a small implementation and don’t want to dilute the network effects by splitting the cocktail party up into multiple private rooms

Page 5: Site structure   one or many

100 user tipping point

In general, I find that very small implementations (<100 participants) almost always benefit from working in one big workspace. The group is small, confidentiality is rarely an issue, and business processes are so fluid that everyone needs to be in everyone else’s business.

Once you get over 100 people, however, business processes and accountabilities become more formal, and you want to augment that one big workspace with smaller workspaces that are specific to teams, geographies, projects, etc.

Page 6: Site structure   one or many

One workspace – everyone sees everything

Finance• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

Marketing• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

Sales• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

Engineering• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

Support• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

Production• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

Quality• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

Inventory• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

Accounting• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

HR• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

Info Tech• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

Corporate• Projects• KPIs - metrics• Processes• News, Blogs• Knowledge base• Meeting notes

Page 7: Site structure   one or many

Few workspaces by business groups

FinancePages

MarketingPages

SalesPages

EngineeringPages

SupportPages

ProductionPages

QualityPages

InventoryPages

AccountingPages

HRPages

Info TechPages

CorporatePages

Product DevPages

Page 8: Site structure   one or many

Few workspaces by geography

FinancePages

MarketingPages

SalesPages

EngineeringPages

SupportPages

ProductionPages

QualityPages

InventoryPages

AccountingPages

HRPages

Info TechPages

CorporatePages

Product DevPages

FinancePages

MarketingPages

SalesPages

EngineeringPages

SupportPages

ProductionPages

QualityPages

InventoryPages

AccountingPages

HRPages

Info TechPages

CorporatePages

Product DevPages

FinancePages

MarketingPages

SalesPages

EngineeringPages

SupportPages

ProductionPages

QualityPages

InventoryPages

AccountingPages

HRPages

Info TechPages

CorporatePages

Product DevPages

Page 9: Site structure   one or many

Few workspaces by function across geography

FinancePages

MarketingPages

SalesPages

EngineeringPages

SupportPages

ProductionPages

QualityPages

InventoryPages

AccountingPages

HRPages

Info TechPages

CorporatePages

Product DevPages

FinancePages

AccountingPages

CorporatePages

FinancePages

AccountingPages

CorporatePages

MarketingPages

SalesPages

EngineeringPages

SupportPages

Product DevPages

MarketingPages

SalesPages

EngineeringPages

SupportPages

Product DevPages

HRPages

HRPages

Info TechPages

Info TechPages

ProductionPages

QualityPages

InventoryPages

ProductionPages

QualityPages

InventoryPages

Page 10: Site structure   one or many

Many workspaces by department

FinancePages

MarketingPages

SalesPages

EngineeringPages

SupportPages

ProductionPages

QualityPages

InventoryPages

AccountingPages

HRPages

Info TechPages

CorporatePages

Product DevPages

Page 11: Site structure   one or many

Workspaces by knowledge type

ProcessesCompany-wide

Customer InfoPages

KPIs - metricsFinancial

Product InfoEngineering

Market InfoCompetitionTrends

News/AnnouncementsPages

Raw Material InfoPages

FAQsWikipedia-intranet

AdministrativeHR, forms

Info TechPages

ProjectsProgram mgmt

People/staff InfoPages

Page 12: Site structure   one or many

Workspaces organically grown as needed

Team / Group 1Company-wide

Location 1Department 1, 2, 3, 4

Product 1Specs, documents

Market 1CompetitionTrends

Project 1Tasks, Milestones, Risks, Scope

All Staff AnnouncementsNews, AdminFAQs

Team / Group 1Company-wide

Team / Group 1Company-wide

Team / Group 1Company-wide

Market 1CompetitionTrends

Market 1CompetitionTrends

Location 1Department 1, 2, 3, 4

Location 1Department 1, 2, 3, 4

Product 1Specs, documents

Product 1Specs, documents

Project 1Tasks, Milestones, Risks, Scope

Project 1Tasks, Milestones, Risks, Scope

Project 1Tasks, Milestones, Risks, Scope