|
|
2. Across Sites
The next barrier is the inability to connect to and share information across multiple sites. Working across sites is analogous to working across groups, teams, or departments. It’s the cross-functional/cross-team dependencies and cooperation that tie directly to the productivity equation. The closer the tool or the system reflects the way we naturally work, the better.
When you are in SharePoint, you are in a team site. You have access to and can and see and work with only the information that is within that site. Imagine that you are working on multiple projects. You want to use a site as a department dashboard to show a single calendar of items from event lists in two different project sites. This is not possible, you need to use a different set of tools to begin to overcome this instead of using the same display configured in the same way.
CorasWorks easily cuts across the site barrier allowing you to See, Contribute, and Act on information as if it were in the local site that the user is in at the time. This capability is critical to bring structure to your workspaces and to do things such as to create an integrated, dynamic Intranet. Further, this capability dramatically reduces navigation which is the #1 reason for user dissatisfaction.
Here are two examples of crossing the site barrier. The first deals with seeing information. The second addresses the ability to act on information from multiple sites in one step.
Project Milestones for a Project Management Dashboard
The scenario is a Customer Project Management solution in Breeze. The organization has multiple projects. Each is its own workspace. They have created a dashboard to be able to see and act on information. They want a display of the key project milestones by their status from the various project workspaces. This is shown below. Note that you can use a scoped search to narrow down the milestones.
Click here to see this Milestone Status display in the Customer Project Management solution.
Marking Tasks Complete
Sounds like a simple task. However, imagine a person that is working on 7 projects and has 15 tasks for the week. They complete them. Normally, they would have to go to each project site, go to the task specific task list, and then, open a single task, change the status to completed, change the % to 100%, and then send an individual email to the task manager. They then have to repeat this for the other 15 tasks in the 6 other project sites.
With CorasWorks this entire process can happen in one step. Shown below is a list of the tasks from the project sites in a single display. Here they are choosing a CorasWorks action called Mark Completed. It is configured to change the two fields of information and then send off an email.
Click here to see this process in the Customer Project Management solution of Breeze.
|
|